this post was submitted on 10 Jun 2023
57 points (100.0% liked)
Asklemmy
1457 readers
57 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you want to start contributing to a complex open source project, there are different approaches depending on how well prepared the project is for new contributors.
Some projects label some issues as "good first issue." If you find those, go ahead and comment into the issue that you are interested in resolving it. It helps to discuss first what you want to change, and especially ask if the issue is still relevant and the text in the issue still up to date. You may then even get some help and some pointers what to watch out for when implementing, which help you understand the code better.
If there are no such issues but you have some ideas anyways, you could create an issue and discuss the idea.
If you don't have any own ideas, you can make an issue asking what issues are good for first timers.
But in the end, always communicate, and sometimes also don't fear to create a prototype if the community around a project does not seem to know well what they want for certain issues.
hmmm all good thoughts. I would like to see about trying to do some stuff locally without discussion to see if it is viable for me at my level of skill and time availability. If I can get a dev environment running and figure out the basic tasks involved then I would probably start discussions about what I might do.
There doesn't seem to be much prior issues, especially kbin, on this topic, unless it is in a separate repo that I am not seeing.
I am guessing that neither project anticipated it was about to get slammed and may not be ready to deal with that on the server admin side and also be managing bug requests and onboarding new devs with all kinds of ideas.
That is a great approach! I think if you manage to set it up yourself, the project may benefit from a pull request with a dev setup guide ๐
Even in the best case scenario I probably don't have the breadth to write something PR-ready but an issue with notes would probably be doable. (Unless the existing docs are already docs are already perfect, which they could be.)