Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 08:53
    ojeytonwilliams commented #1317
  • 03:09
    MasterEnoc commented #1372
  • Nov 23 17:33
    MasterEnoc commented #1372
  • Nov 23 17:24
    MasterEnoc synchronize #1372
  • Nov 22 21:47
    simon04 commented #1372
  • Nov 22 20:56
    Thibaut commented #1317
  • Nov 22 19:11
    MasterEnoc opened #1372
  • Nov 22 19:11
    MasterEnoc review_requested #1372
  • Nov 22 18:49

    simon04 on master

    Changed the display absolute to… Merge pull request #1253 from D… (compare)

  • Nov 22 18:49
    simon04 closed #1253
  • Nov 22 18:49
    simon04 labeled #1253
  • Nov 22 18:49
    simon04 assigned #1253
  • Nov 22 18:47

    simon04 on master

    Fix how 'notable trait' section… Update Rust to 1.48.0 and impro… Merge pull request #1371 from M… (compare)

  • Nov 22 18:47
    simon04 closed #1371
  • Nov 22 18:47
    simon04 closed #1360
  • Nov 22 18:44
    simon04 assigned #1371
  • Nov 22 18:44
    simon04 labeled #1371
  • Nov 22 18:44
    simon04 labeled #1371
  • Nov 22 18:44
    simon04 edited #1371
  • Nov 22 04:29
    MasterEnoc commented #1371
Starbeamrainbowlabs
@sbrl
Just a user here, but that would be awesome! I've been noticing that they've been getting out of date @baelter
Gergely Gombos
@gombosg

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:

  • keep the builds running!
  • merging doc update PRs, reviewing, keeping code quality up
  • triaging issues
  • if possible, fixing some critical bugs

-> 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?

Senya
@cmrd-senya
Hello! I've opened this little PR with a change for the Gemfile today: freeCodeCamp/devdocs#1271
Its main purpose to fix the issue that is blocking devdocs to be run as a systemd service.
Would be great if someone could take a look
Starbeamrainbowlabs
@sbrl
Might be worth sending an email, @gombosg. Maybe use the git commit history and cc in a bunch of recent contributors?
If that doesn't work, I'm afraid it might be time for a fork.
I don't know Ruby at all, but I'd be happy to help out with reviewing, triaging issues etc
Thibaut Courouble
@Thibaut

@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 thibaut@me.com 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.

Jasper van Merle
@jmerle
I can confirm the time commitment and the repetitiveness of the work (I guess I was that single active maintainer once) and can definitely recommend getting at least 2 people together so you can divide the workload a bit (and to have someone to review your own PR's)
Starbeamrainbowlabs
@sbrl
Perhaps an advertisement for more maintainers in the README would help here, with a direction to this Gitter?
I'd perhaps say a team of 3-5 at least would be ideal
I don't have the xp with Ruby to assist with the code, which is my main concern
Thibaut Courouble
@Thibaut
I can merge PRs to the README if you or some else wants to organize the search for maintainers (just @mention me on the PR)
Jed Fox
@j-f1
I think the reason I burned out was a combination of not enough free time left after schoolwork and the backlog of PRs and updates that resulted in. I’d be happy to collaborate with other folks — maybe we could each pick a subset of the docs to maintain?
Jed Fox
@j-f1
It would also be great to figure out a way to automatically update the docs — @jmerle’s bot is a great start but it would be great if it could act on the updates and only open an issue if it detects a problem with the update. I could also add a link to report issues with the docs to each page so the burden of checking for errors resulting from changes in the sites we scrape rests a little more on the users (who know the docs they’re reading pretty well).
Senya
@cmrd-senya
IMO it really helps when you work as a team rather than maintaining a project alone. This way you can motivate each other and also you don't feel pressured because you know that someone else can help whenever you need a break. I think it can really help to avoid burn out if there are 3-4 people who share the maintenance work.
Michael Skorokhodov
@Samsuper_gitlab
Hello! When will the information about C ++ be updated? I mean C++ 20. Or should I start adding information myself?
Starbeamrainbowlabs
@sbrl
@Samsuper_gitlab Devdocs scrapes from websites. It's probable that the scraper hasn't been run in a while. See the conversation above for that.
Pavel
@yekm
docs from man pages section 2?
Starbeamrainbowlabs
@sbrl
@yekm As far as I know DevDocs doesn't scrape man pages. I don't know of another project that does that, but it must exist.
Pavel
@yekm
cant find it
Adding all of them to DevDocs would make the search unusable
it will be slow or it is just a matter of too many seemingly useless results in the seach results
?
Starbeamrainbowlabs
@sbrl
I'm not sure. I'd assume they mean that the search would be too slow
Jasper van Merle
@jmerle
I know that there is a man docset for Dash (and therefore for Zeal and Velocity as well) at https://github.com/Yanpas/mandocset
Pavel
@yekm
thats just html generation. it is easy. i saw 13 steps in adding-docs.md and i am starting to doubt the whole idea of adding man pages to devdocs, especially if perfomance imact will be noticeable.
HARI VARDANACHARI KORRAPATI
@chari1239
Hi all
I'm setting up the devdocs locally for the first time
Downloading docs via "bundle exec thor docs:download --default" fails for all 6. For example, "(1/6) DOM Events FAILED (Errno::ENOENT: No such file or directory - gunzip)
Can anyone help me on this to resolve?
Sam
@samfundev
@chari1239 I wasn't able to figure out what was wrong but maybe this would be a good starting point: April 27, 2020 8:36 PM
HARI VARDANACHARI KORRAPATI
@chari1239
Hi @samfundev , I was able to resolve. With my analysis, this error mostly happens in windows machine.
  1. gunzip is not available, have to install it.(make sure gunzip cmd works rather gzip)
  2. by default tar cmd will use git's tar path which will give error : "C: cannot find path error", add System32/tar.exe path to your ENV PATH variable
that link will help
HARI VARDANACHARI KORRAPATI
@chari1239
Hi @all , I want to work on the following issue
add the new version of pandas, I'm trying to understand the code. If anyone has any idea, who can walk me through what needs to be done, that will be helpful
Kenneth-Fries
@Kenneth-Fries
Any prospects for adding LISP? Devdocs has become my favorite goto for documentation, and now that I have to learn LISP, I see there is a dearth of information on the internet. It all seems disorganized and not laid out well. Wish I knew it well enough to contribute.
Starbeamrainbowlabs
@sbrl
@Kenneth-Fries you probably want this trello board for that : https://trello.com/b/6BmTulfx/devdocs-documentation
Kenneth-Fries
@Kenneth-Fries
Thanks @sbrl ! I'm learning my way.
Jörg Thalheim
@Mic92
So let's say I want to build a scraper for Nix language manual, what would be the process? Should I first suggest it on the mentioned trello board or should I open a work-in-progress PR?
Anders Bälter
@baelter
I only check in here occasionally, but still interested in keeping this alive. I know ruby and would like to contribute, but only have time and interest to keep the docs I use up to date. Created that PR you asked for @Thibaut freeCodeCamp/devdocs#1285
Starbeamrainbowlabs
@sbrl
At this point @Mic92, I'd open a WIP PR
Jiawen Geng
@gengjiawen
I don't ruby, but I can build the doc and like to keep Node.js doc up to date.
Anders Bälter
@baelter
So atm we have, @gengjiawen, @j-f1, @sbrl, @gombosg and me who are willing to pitch in? Sound like a team to me :)
Starbeamrainbowlabs
@sbrl
I'm in (but don't know Ruby, so can't help there)
Bryan Hernández
@MasterEnoc
Hi everyone, I made a PR of the elisp documentation freeCodeCamp/devdocs#1270 . Im willing to help maintaning devdocs, if you need one maintainer more count with me
Jiawen Geng
@gengjiawen
Quincy Larson
@QuincyLarson

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.

For example:

  • Could we localize DevDocs into other world languages? (I've read the past GitHub issues related to this, but I think it's worth discussing again.)
  • Could we design a way that library maintainers could submit their documentation as a supplement to our scrapers?
  • Could we figure out the highest-priority APIs that need to be updated so we can triage our contribution efforts?

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.

Jed Fox
@j-f1
Awesome! Will be great to see this get off the ground again.
Starbeamrainbowlabs
@sbrl
:tada: