Hi,

There are also other projects in the Jupyter ecosystem that you might
be interested in contributing to, including:

  - https://github.com/nteract   -- a local desktop way to use Jupyter
  - https://github.com/sagemathinc/cocalc -- multiuser realtime
collaboration  (my project)
  - https://github.com/jupyter/nbgrader -- using Jupyter for homework
assignments
  - and dozens of others.

It's a thriving ecosystem.

 -- William

On Thu, Feb 20, 2020 at 6:46 PM Nicholas Bollweg <[email protected]> wrote:
>
> Hooray!
>
>> Is there any document for start point?
>
>
> This is probably the best starting point:
>
> https://jupyter.readthedocs.io/en/latest/contributor/content-contributor.html
>
>>
>> For me interesting contribution on architecture/code-base/documentation
>
>
> That pretty much sounds like... everything! Like most things in open source, 
> new code/docs/service get to users of Jupyter when:
>
> - someone has an itch to scratch (might be a person, company, or bot)
> - someone can do the work to scratch it (maybe the first someone, maybe 
> someone else)
> - someone reviews the work (usually, initially by a bot, but then a person)
> - someone merges the work (maybe the reviewer, maybe someone else)
> - someone cuts a release containing the new work (sometimes a person, 
> sometimes a bot)
>
> Concretely, as most development on Jupyter happens on GitHub, you can take 
> your pick of "good first issue" issues on the respective repositories. Here's 
> a random smattering of repos:
>
> - 
> https://github.com/jupyter/notebook/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
> - 
> https://github.com/jupyter/nbconvert/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
> - 
> https://github.com/jupyterhub/jupyterhub/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
> - 
> https://github.com/jupyterlab/jupyterlab/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
>
> If none of those sound interesting, you may wish to watch/star some repos and 
> and start watching the issues that crop up, and see if something takes your 
> fancy. Ocotobox.io is very handy for this, as you can search across many 
> repos.
>
> Once you find a thing you want to work on, It's "good form" to announce that 
> you intend to work on an issue, but few projects will turn down good code on 
> a drive-by PR if is:
>
> - fixing a known issue
> - small
> - well-written
> - tested
> - documented
>
> in roughly that order of importance.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Project Jupyter" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jupyter/5a9f2831-99d5-47c0-8580-9cbe04c7e80d%40googlegroups.com.



-- 
William (http://wstein.org)

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CACLE5GA3T8GtTTw-BvMsN8nOTwgRMbZDdCd971f6-uO%2BHUET6w%40mail.gmail.com.

Reply via email to