simon04 on master
Changed the display absolute to… Merge pull request #1253 from D… (compare)
simon04 on master
Fix how 'notable trait' section… Update Rust to 1.48.0 and impro… Merge pull request #1371 from M… (compare)
Hi all, yes, DevDocs is kind of dying at the moment... lots of issues, stale PRs, no commits since months.... I hope it can still be saved, because it's been my favorite docs browser for years and there's really no alternative to it.
@Thibaut , we understand that you don't have the time to maintain this project, but what is your vision for its future?
How would it be possible to onboard maintainers/contributors?
What I imagine as goals:
-> for all this, probably no extensive Ruby knowledge is needed. It would be enough to leave the project in a maintenance state.
As I see from the count of PRs, the community is here to help.
What would be the way to move forward?
@sbrl @baelter @gombosg if you're able to rally a small team behind maintaining DevDocs over the long haul, feel free to email me at firstname.lastname@example.org and I'll be happy to help set this up with Quincy + share context on an ongoing basis.
In the past whenever we've had a single active maintainer it has proven impossible to sustain over time and we end up burning that person out. I think for DevDocs to thrive we need a team, but to this day we haven't been able to find enough maintainers to form one.
Unlike most other open source projects, it's a big time commitment to maintain DevDocs and the work is quite repetitive. On the flip side, DevDocs is still very popular and helping out many thousands of developers. I'd love to see it thrive.
Adding all of them to DevDocs would make the search unusable
Hey DevDocs contributors,
I have some exciting news.
First of all, freeCodeCamp has reached a point where we are pretty sustainable. I am confident that our nonprofit will be able to sustain itself for the rest of the decade – and all this in spite of the global recession and its impact on charitable giving.
And freeCodeCamp's codebase and curriculum are in a good place as well. We recently shipped our Python certifications, and are close to localizing our curriculum into major world languages like Spanish, Arabic, and Chinese.
We are now at a point where we can focus more energy on DevDocs, and allocate some of our engineering team to help as well.
Oliver (@ojeytonwilliams) has been contributing to freeCodeCamp since 2018 – mostly to our core Node.js + React codebase – and recently joined our team full time. He has a Ph.D. in particle physics from University of Southampton, is based in Brussels, and enjoys playing games of strategy. He is new to DevDocs, but is steeping himself in the codebase.
I met with @simon04_gitlab a few hours ago, and discussed his perspective on DevDocs and his experience as a contributor over the past year. Oliver and I also spent some time reading through the commit history, outstanding issues, and the chat history here on Gitter.
I propose that everyone here who is interested in contributing – including past contributors and maintainers like @j-f1 and @jmerle and of course @thibaut – meet for a 1 hour Google Hangout call. The purpose of this call will be for us to share ideas, and for Oliver to learn as much as he can about everyone's priorities for DevDocs.
If you are interested in attending, could you add your availability to this When2Meet so we can find an optimal time? I hope to meet early next week – or even over the weekend if that works best: https://www.when2meet.com/?10203106-nTvMG
With your help, we can not just maintain DevDocs, but expand it. And we can continue to serve the global developer community with fast, accessible, and enjoyable documentation.