(This is a discussion I started on Slack but I think this is a better place) Hi! First of all, the Julia community is awesome! Amazing! People are very receptive and really help when the users need. However, I have a small critic (a constructive one, I hope) about the development of Julia itself. …

[image] jonathanBieler: I went through the first 15 pages of PRs and about 10% of them don’t have any reply. A few are simple doc or convenience changes (e.g. this one from a year ago). On later pages you can find some stuff that are outdated and could be closed (e.g. this bug has been fixed …

Yes, GitHub has a moderator role. It would be good to be quite liberal with giving that out.

[image] Ronis_BR: The problem is that a new developer might not understand that and just think, “they don’t want me here”. Since this is unwarranted, it may just be a problem that better communication can resolve.

JupyterHub has automated welcome messages, I got one recently: https://github.com/jupyterhub/the-littlest-jupyterhub/pull/636 Would something like that help to make new contributiors feel more welcome? Of course, it needs to be followed up eventually. Maybe the welcome-message could state someth…

Yes! This is a very interesting approach. In fact, I think @logankilpatrick was testing something in those lines.

Hi @johnmyleswhite , Thanks for the article! Rust is definitely an example of a successful community. I know that implementing a bot to handle those things should not be trivial, but I would like to make a proposal. Maybe in the future, we can have this implemented: A bot, like Homu will handle th…

[image] Ronis_BR: When a PR is made, the bot ping the core developers / maintainers. I think that most core devs are already “watching” the repo on Github, so they get notified about new PRs. [image] Ronis_BR: After 3 acceptances, the bot merge the PR only if all the test passes. I th…

[image] Tamas_Papp: Designing a computer language requires a small number of core architects with a mostly consistent vision about how it should evolve — this is not something that you can simply leave to CI . This is the real bottleneck, and it is difficult to work around since it is a resource…

[image] thofma: This was not the suggestions. No one suggested to make API changes merge by popular vote and passing CI. It was explicitely stated that it is about minor things: Exactly! [image] thofma: Not true, even if repeated hundreds of times. Something in Base is known to not brea…

Suggestion to slightly improve Julia development

Community

johnmyleswhite November 30, 2020, 12:13pm 53

I’d recommend looking into how Rust does a lot of this stuff as they have some useful tools they’ve used for years: Rust infrastructure can be your infrastructure | Huon on the internet

Topic		Replies	Views
Making the review process more pleasant for new contributors General Usage github , contributing	59	4232	July 18, 2024
Identifying barriers to new contributions to Julia and its ecosystem Community github , contributing	14	1096	January 5, 2025
Package growth tips and tricks: Creating an organization, triage, better management Community question	8	2403	July 27, 2021
Improving the Julia issue tracker Meta Discussion github	14	1927	July 1, 2022
Why open-source timelines/roadmaps don't work Internals & Design	40	4984	June 26, 2023

Suggestion to slightly improve Julia development

Related topics