Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get listed on the gothinkster/realworld repo #170

Closed
tobiu opened this issue Dec 11, 2019 · 6 comments
Closed

Get listed on the gothinkster/realworld repo #170

tobiu opened this issue Dec 11, 2019 · 6 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@tobiu
Copy link
Collaborator

tobiu commented Dec 11, 2019

Already applied on the project page 12 days ago, zero feedback:
gothinkster/realworld#446

In case you would like to see the neo.mjs app there, please do add some weight to the linked ticket. After all, it is already feature complete for a while.

I did already ping Thinkster on their FB page, but it had no effect.

Screenshot 2019-12-09 at 22 33 51

Thanks a lot for your support on this one!

@tobiu tobiu added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Dec 11, 2019
@tobiu tobiu pinned this issue Dec 11, 2019
@mrsunshine
Copy link
Contributor

added a comment to push it

@tobiu
Copy link
Collaborator Author

tobiu commented Dec 20, 2019

@EricSimons still has not even looked at our feature complete implementation =/

@tobiu
Copy link
Collaborator Author

tobiu commented Apr 5, 2020

added a comment since we got a question there. this topic is really messing with my brain.


Hi @shabbirulhasan,

this topic here is messing with my emotions. The neo.mjs RealWorld App is feature complete for more than 4 months now and it never got reviewed. It did not even get listed on the repo page as in progress.

I have rarely encountered this unsupportive people than the Gothinkster guys here.
Especially @anishkny and @EricSimons. They simply don't care and would rather let a new promising framework die in the void of being unknown than doing their part.

Regarding your question: please use the issue tracker inside the neo repo you are using (there is more than 1 neo covid repo inside the https://github.com/neomjs/ namespace). In short: if you got a neo app running on localhost you are almost there. Just deploy it to your webserver (or into the cloud) and specify which files should get mapped to which urls inside your webserver settings.

@tobiu
Copy link
Collaborator Author

tobiu commented Apr 7, 2020

to keep this ticket in sync and you guys updated:

Eric Simoens wrote:

@tobiu FYI RealWorld is a sideproject we maintain. We have families to feed, mortgages to pay, etc and RealWorld doesn't pay those bills. RealWorld is an incredibly large OSS learning project, and as such, has a ton of issues/PRs that I honestly have no idea how @anishkny makes the time to even look at much less comment on or review.

If you want to make someone the "bad guy" here, have it be me, not Anish. The dude is a beast and has single handedly scaled this project into what it is today. Outside of founding the project, I literally do jack squat at this point for RealWorld, so if you want a punching bag I think I'm your guy.

I will not tolerate slander against any of the admins/maintainers. If you do this again, you will be banned.

Now lets talk about the fun things!

If I had to guess why this hasn't been merged in yet, I'd wager it's because the answers given weren't super straightforward. I took some time to review what you've made, and it LGTM, but the only thing I'd request is that the link at the top of your realworld app repo points at the actual running Conduit app itself instead of your bare GH pages URL.

Once you've got that taken care of I'll merge this PR. Thanks

My response:

Hi @EricSimons,

thank you for looking into this. I changed the link on top of the repo page to point to the dist/prod version directly (same for the "demo" link on the top part of the readme).

The reason for pointing to the main examples page was simply that there are 3 different versions of the neo RW app out there (dev mode, dist/dev, dist/prod). Added all 3 direct links to the very bottom of the readme now.

I also took the time to update the repo to the latest neo version, adjusted the build processes & the docs app (the repo was created before the unified npx build scripts were in place).

So, ready for a merge on my end!

Regarding your comment: Of course I do appreciate your work as well as @anishkny's with this Conduit repository. If I would not like it, I would not have invested around 1 month to create this RW app to share it with you.

I am also very well aware of the OSS limitations. I spent 1.5 years of my full and unpaid working time to get neo to a first public release & this was 4 months ago. Literally burned all all of my personal savings and this was only possible since I did work on some very high profile JS projects before. I felt that it was time to give back and share my knowledge with everyone who is interested in scaling UIs via multithreading. Now, without creating an awareness that this framework even exists all the effort would be pointless. This is why it feels important to me to get listed here.

Best regards,
Tobias

[Off topic] In case you got a couple of minutes of spare time I would love your input on the Covid19 in numbers neo app. It needed less code than the RW app to create it (pictures and links inside the main repo readme => https://github.com/neomjs/neo). Thx!

So, please try to not ping me on social media or slack about this one for a bit longer :)

@tobiu
Copy link
Collaborator Author

tobiu commented Apr 13, 2020

the PR did not get merged in for 6 days, sorry for the delay, not much i can do on my end.

https://github.com/gothinkster/realworld/pulls

@tobiu
Copy link
Collaborator Author

tobiu commented May 19, 2020

Screenshot 2020-05-20 at 01 06 25

might take a bit until the list gets updated (the last update was on may 2nd, monthly?), but neo should be inside the next iteration.

@tobiu tobiu closed this as completed May 19, 2020
@tobiu tobiu unpinned this issue May 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants