Replies: 1 comment
-
Hey @Dynnammo, thanks for taking the time to write this up. I think you've summed things up very well. The good thing is, there is already a discord which I've had help setting up from other members of the community. However, it's not very active and I haven't done much to change that. It would be great to get help with making that community more active. I do have plans to write a contributing guide and to start creating issues that would be easy for new comers to pick up. On that note, I just spent some time labelling some of the issues and will try to create some more approachable ones for people to pick up. A contributing guide will follow. Thanks again for opening this topic. I really appreciate the effort. |
Beta Was this translation helpful? Give feedback.
-
Context
Rallly is quite a big project. It has (when I write these lines):
The problem
I'm really concerned about the fact that @lukevella seems to handle 99% of the Rallly project (as a matter of fact, if I run a
git shortlog -s -n
I obtain these results :TL;DR : the creator and maintainer of the project is responsible of 92% of the commits of Rallly.
If I compare to similar OSS projects that have similar numbers, having such indicators while being alone is not a good thing.
As such stage, handling :
requires much time, and it's the role of a community to help.
The AGPLv3 under which is licensed Rallly has the following motto : "Free as in freedom, not as in free beer", meaning users have the right to take advantage of the project, while having the responsability of taking care of it.
Solutions
As a member of multiple OSS communities, I think there's some actions that can be done in order to make Rallly a project that thrives with a community.
Beta Was this translation helpful? Give feedback.
All reactions