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

Why do you not maintain these popular projects anymore? #72

Open
IonicaBizau opened this issue Oct 13, 2015 · 89 comments
Open

Why do you not maintain these popular projects anymore? #72

IonicaBizau opened this issue Oct 13, 2015 · 89 comments

Comments

@IonicaBizau
Copy link

IonicaBizau commented Oct 13, 2015

@harthur I was looking at your profile and saw this:

image

Why do you not maintain these projects anymore? If you don't have time to do that, why do you not search somebody to keep them alive?

@nickpoorman
Copy link
Contributor

nickpoorman commented Oct 13, 2015

@harthur - If you would like to move this repo into an organization, I would be happy to maintain it.

@IonicaBizau
Copy link
Author

IonicaBizau commented Oct 13, 2015

@nickpoorman I was going to suggest that. 😄 👍

@janwirth
Copy link

janwirth commented Oct 14, 2015

That would be great. I am using this software in a project thesis because it is just the simplest solution out here :)

@ilanbiala
Copy link

ilanbiala commented Oct 28, 2015

@harthur any response?

@IonicaBizau
Copy link
Author

IonicaBizau commented Oct 28, 2015

😞

image

@janwirth
Copy link

janwirth commented Oct 28, 2015

how about forking the repos and creating an organisation for maintenance during her absence?

@jobsamuel
Copy link

jobsamuel commented Nov 5, 2015

I like that idea @nickpoorman 👍

@IonicaBizau
Copy link
Author

IonicaBizau commented Nov 5, 2015

@FranzSkuffka I am not for forking and maintaining. It's much harder to maintain your own fork because most of the people will find this popular repository.

I also vote for moving these projects in an organization, like @nickpoorman suggested. 💫

@irony
Copy link

irony commented Nov 5, 2015

I also agree, it would be nice to get an response from @harthur

@irony
Copy link

irony commented Nov 5, 2015

She have switched jobs to something secret so maybe she isn't even allowed to reply here: https://harthur.wordpress.com

@IonicaBizau
Copy link
Author

IonicaBizau commented Nov 5, 2015

@irony Oh, interesting read! 📖

@DinerIsmail
Copy link

DinerIsmail commented Dec 28, 2015

Any update on this, guys? It would be awesome if this would be moved into an organization.

@IonicaBizau
Copy link
Author

IonicaBizau commented Dec 28, 2015

I just emailed @harthur! Hope she will reply me and save these nice goodies. 😁 🎁 🙏

@pablodenadai
Copy link

pablodenadai commented Jan 2, 2016

Thanks @IonicaBizau let us know how it goes.

@scrussell24
Copy link

scrussell24 commented Jan 5, 2016

I would also like this!

@michaelpittino
Copy link

michaelpittino commented Jan 12, 2016

Any update on this?

@IonicaBizau
Copy link
Author

IonicaBizau commented Jan 12, 2016

No response from the author yet... 😞

@pablodenadai
Copy link

pablodenadai commented Jan 12, 2016

There's an opportunity here for someone to take this over. Preferably someone who understands the codebase and is willing to move the project forward. That said, the project owner seems to have been the only major contributor in the past.

@michaelpittino
Copy link

michaelpittino commented Jan 12, 2016

Yes but as @IonicaBizau said that's not easy to fork and maintain because of popularity of THIS repository.

@pablodenadai
Copy link

pablodenadai commented Jan 12, 2016

Fair point - I agree that moving this project to an org would be the best solution - it's a shame the owner isn't responding the messages. 😞

@IonicaBizau
Copy link
Author

IonicaBizau commented Jan 12, 2016

@michaelpittino I contacted GitHub support–maybe they will be able to help us since @harthur had a talk at Passion Projects. Hopefully they will have a solution. 🙏

@IonicaBizau
Copy link
Author

IonicaBizau commented Jan 21, 2016

From GitHub support:

Unfortunately we don't have any contact details for Heather Arthur from her Passion Projects appearance. Hopefully she'll reply to your email if she's able to help.

@pablodenadai
Copy link

pablodenadai commented Jan 21, 2016

Let's start a petition at change.org. :-)

@voxpelli
Copy link

voxpelli commented Jan 22, 2016

Why not just create a fork, move development there, keep an eye on this repo and point people to the fork whenever they open issues or PR:s here and then if/when the owner of this repo gets back to you then this repo can be updated to point to that repo.

@janwirth
Copy link

janwirth commented Jan 22, 2016

+1, basically what I suggested already.

@DinerIsmail
Copy link

DinerIsmail commented Jan 22, 2016

I also agree with @voxpelli

@robertleeplummerjr
Copy link

robertleeplummerjr commented Jan 23, 2016

I did contact @harthur about being a maintainer, no reply. I did read her website, and why she ended up doing so, and totally respect it. I would really like to continue in her absence, hoping the best for her. There is a risk that she doesn't like any of the changes we do, but there is also the chance we may end up improving these fantastic libraries. That being said, there are enough of us and these libraries are useful enough I went ahead and created: https://github.com/harthur-org and forked all libraries. If you'd like access, open a pull request.

@IonicaBizau
Copy link
Author

IonicaBizau commented Jan 24, 2016

@robertleeplummerjr That's cool! 👍

I would still recommend having real source repositories, not forks (that means: delete forks, create repos, git push --all from local clones of @harthur's repos). I do not like forks because they have limitations like:

  • they are not searchable
  • commits in forks are not counted in the contributions calendar (big thing, right? 😂)

Instead we can explicitly state it's the repos are a continuation of the original projects.

@janwirth
Copy link

janwirth commented Jan 24, 2016

I agree with @IonicaBizau, that makes perfect sense.

@robertleeplummerjr
Copy link

robertleeplummerjr commented Feb 13, 2016

@ilanbiala, What if @harthur decides to re-maintain? We open a single pull request, and merge, and then the org can go away.

@pablodenadai
Copy link

pablodenadai commented Apr 8, 2016

Results as of Apr 8, 2016, 10:43 AM GMT+1

  1. brain.js 10 votes (45%)
  2. js-brain 4 votes (18%)
  3. brain-plus 2 votes (9%)
  4. brain2 2 votes (9%)
  5. contrib-brain 1 vote (5%)
  6. community-brain 1 vote (5%)
  7. org-brain 1 vote (5%)
  8. brain-ng 1 vote (5%)
  9. com-brain 0 votes (0%)

@mickdekkers
Copy link

mickdekkers commented Apr 8, 2016

Here's two more ideas:
brain-next
brain++ (as in c++; brain incremented by one)

@IonicaBizau
Copy link
Author

IonicaBizau commented Apr 8, 2016

@SoullessWaffle I don't think + can be used in the package names.

@janwirth
Copy link

janwirth commented Apr 8, 2016

harthur-brain could be a good choice SEO-wise

@mickdekkers
Copy link

mickdekkers commented Apr 8, 2016

@IonicaBizau you're right, perhaps we could use brainpp

@hadesara
Copy link

hadesara commented Apr 13, 2016

Can we decide on the date by which everyone should vote.

@pablodenadai
Copy link

pablodenadai commented Apr 15, 2016

The poll has been open for just over a week now.

Updated results:

  1. brain.js 13 votes (46%)
  2. js-brain 4 votes (14%)
  3. brain2 4 votes (14%)
  4. community-brain 2 votes (7%)
  5. brain-plus 2 votes (7%)
  6. contrib-brain 1 vote (4%)
  7. org-brain 1 vote (4%)
  8. brain-ng 1 vote (4%)
  9. com-brain 0 votes (0%)

28 total votes

@IonicaBizau I guess you could call brain.js the winner?

@IonicaBizau
Copy link
Author

IonicaBizau commented Apr 15, 2016

I npm published it under the brain.js name on npm. 🚀

If any of you wants to have superpowers on npm, feel free to 🔔 me and I will npm owner add you. 😁 Also, if you want to contribute to the project we can add you as member in the @harthur-org organization.

/cc BrainJS/brain.js#4

@janwirth
Copy link

janwirth commented Apr 16, 2016

Thank you @IonicaBizau

@robertleeplummerjr
Copy link

robertleeplummerjr commented Apr 16, 2016

Devs, I believe a "huzza" is in order.

@robertleeplummerjr
Copy link

robertleeplummerjr commented Apr 16, 2016

Huzza!!!!

@roccomuso
Copy link

roccomuso commented Apr 27, 2016

Great job guys. ;)

@antoniodeluca
Copy link

antoniodeluca commented Jul 30, 2016

In the past I have used Brain.js and some other JavaScript based machine learning libraries but unfortunately I have found them not matching my needs. That's why, working on my personal projects, I have developed the idea of creating a different approach by myself. So, sorry to be here to talk about another project but I would really like to receive some opinions and suggestions from experienced people that, being into this specific field, could help me to set useful and shared expectations. By the way, thanks for the great support given to Brain.js so far. The library is called DN2A and is on https://github.com/dn2a/dn2a-javascript

@robertleeplummerjr
Copy link

robertleeplummerjr commented Jul 31, 2016

Can you please open a new issue, that way this issue stays focused?

@shimondoodkin
Copy link

shimondoodkin commented Dec 27, 2017

https://medium.com/@heatherarthur/what-happens-when-you-retire-from-github-979fb6b143b3

Basically, he writes: This is hard work for him, A one with limited resources to maintain his repositories for others. He is overwhelmed by a large number of people contacting him. He has no resources for this. He dislikes this. So he quit GitHub. he "declared bankruptcy" on time devoted to Github, and He regrets sharing his repositories because it took so much time from his life. He expected people would fork and the code would be maintained by users themselves. but many good wishing people fall into his open door smashing him because they are just too much for him. So he asked to not contact him anymore regarding Github. even if you find him or his name.

@robertleeplummerjr
Copy link

robertleeplummerjr commented Dec 27, 2017

expected people would fork and the code would be maintained by users themselves

And that is exactly what happened.

@kjprice
Copy link

kjprice commented Jan 5, 2018

This is one of the most fascinating issues I have ever scrolled through. I love coders and the code community. Way to go for pulling together, people!

@k1r0s
Copy link

k1r0s commented Mar 17, 2018

what happened to @harthur ? lol

@janwirth
Copy link

janwirth commented Mar 17, 2018

She's alive and well - machine-learning-engineering. I think there was more than one issue motivating her to abandon github. But I don't want to seed any rumors here. You better google any information up yourself. She has a medium account.

@vickylance
Copy link

vickylance commented Mar 22, 2018

@FranzSkuffka But her profile says deceased https://github.com/harthur what happened to her. It saddens me to see a github profile like that.

@janwirth
Copy link

janwirth commented Mar 23, 2018

Wow - that must be very recent. The last post on medium was Feb 24.

edit: She's alive. Or Twitter has an API for ghosts.
https://twitter.com/harthvader

@youngkaneda
Copy link

youngkaneda commented Mar 26, 2018

I'm not still understand why she left the Github, someone can explain?

@AlibekJ
Copy link

AlibekJ commented Mar 26, 2018

@youngkaneda
Copy link

youngkaneda commented Mar 26, 2018

@AlibekJ my English is not so good, but here we go, I care because she's contributed a lot with the community and she just disappeared, why? Some problem with her career, or personal? Is it something we can help with? Is just empathy with the next!

@leeoniya
Copy link

leeoniya commented Apr 2, 2018

@Berkmann18
Copy link

Berkmann18 commented Apr 29, 2019

This is one of the most fascinating issues I have ever scrolled through. I love coders and the code community. Way to go for pulling together, people!

Exactly my thought.
I'm surprised in why she didn't set maintainer permissions for those who contacted about that but at least BrainJS is a community thing.

@dialex
Copy link

dialex commented Jul 19, 2019

Consider this: https://github.com/rejuvenate/rejuvenate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests