-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prospective return of former contributors #3480
Comments
Really? Now LMMS is in the business of fixing personal/employment/bandwidth problems? No. |
I don't see how this is a meta issue, it'd be more appropriate under |
Because he wants each fallen soldier to write a testimonial in a separate bug report that we can cross-link to fix the problem as a whole. I think I get the motive... if we can find things that are similar, we can correct the problem, but I don't know if going after past developers helps at all, it will only add unnecessary exposure to the developers. I'd much rather work with some new aspiring developers. I think that's more in the spirit of progression. I also wholeheartedly disagree with @jasp00 that recruitment and keeping developers are unrelated. The question was WHY WE LOSE THEM and a bit part of that is lack of core documentation and burn-out. So a solid recruitment strategy is part of the big picture of keeping developers. We need a place to send new developers and we need a way for them to know which tasks are good to start working on. I really think @jasp00 is missing the mark on this. Not every human resources issue can be fixed with a bulleted list. We need to shape a platform for developers, not debug one into existence with process. |
Reply to off-topic matters at #3447 (comment). Former contributors that want to come back to LMMS, but cannot for whatever reason, you may open a separate issue for your case. As long as I am available, you will get feedback from me. |
@jasp00 please add some information which properly categorizes this as a |
It has such information. What data do you request?
This is not a conversation thread.
I realized later, JavaScript did not show the profile. She is welcome anyway. |
No she's not, she's not a former contributor. Fixed.
We generally work from a true bulleted list of work in order to fly the This current -- #3480 -- bug report is more like an open-ended invite, and one that would really have to be spearheaded, since it's unlikely past developers are just going to find this bug and decide they want to chime in. We run the
This current -- #3480 -- bug report appears to be On the other hand, if it starts to become useful before then... great. 🕥 |
I meant JaneDoe is welcome as a new contributor. How about a I will add information to the wiki, not about specific contributors. |
This issue originates from #3447 (comment). This keeps track of former contributors that may return if we can solve their situation given enough technical and economic resources; if there is no way to solve the case, it does not belong here. Causes should be identified. Each case should be an issue; list open ones in this entry.
@JaneDoe
#NNNN: two jobs.The text was updated successfully, but these errors were encountered: