Have you ever thought about assigning "15 minute jobs"?
I've seen it in KDE. Simple jobs are posted publicly to pave the way for those who are interested but don't yet know exactly how they can make a meaningful contribution. For example, a single bid might look like this:
Java I2P postinstall.sh: Posix-compliant rewrite of the script. Basic knowledge of shell scripting and the use of analysis tools such as shellcheck should be available.
You must also clearly describe where the finished work is to be delivered. In this simple way, you get a win-win situation – and in the worst case, everything stays as it is.
Suggestion for posting simple tasks.
Suggestion for posting simple tasks.
Luther H. Gillis · Private Investigator · Discreet & Confidential
Re: Suggestion for posting simple tasks.
from experience, that works best when we know the skills and interests of the assignee.
otherwise, and normally the case, it's much better if an idea or proposal comes in from the person doing the work.
anybody looking for assignments, come join the discussions in IRC so we can get to know you
otherwise, and normally the case, it's much better if an idea or proposal comes in from the person doing the work.
anybody looking for assignments, come join the discussions in IRC so we can get to know you
Re: Suggestion for posting simple tasks.
The point of such a call is that those who have the "skills and interests" feel addressed. Of course, this does not exempt the leaders from the acceptance test. Nor was that the intention.
When applicants have to present themselves to the IRC and are accepted, it is no longer a public tender. They are then employees. In this case, you can also assign the work to your employees. But you refused to do this in the past. I see that you have now changed your mind.
If you are going to ask people to visit the IRC, it would be appropriate to tell them what you mean. We have at least two IRCs with different channel lists. The one where zzz and other (java i2p) developers are is ipd-dev. When I wanted to discuss this in advance the other day, I couldn't because as a stranger in i2p-dev I have no right to speak.
In addition and in conclusion, I would like to refer to the KDE project and its exemplary management. These include the This Week in Plasma report and the aforementioned 15-Minute Bug Initiative. No matter how you end up implementing it, if you don't show people what's happening, they'll think the project is already dying.
When applicants have to present themselves to the IRC and are accepted, it is no longer a public tender. They are then employees. In this case, you can also assign the work to your employees. But you refused to do this in the past. I see that you have now changed your mind.
If you are going to ask people to visit the IRC, it would be appropriate to tell them what you mean. We have at least two IRCs with different channel lists. The one where zzz and other (java i2p) developers are is ipd-dev. When I wanted to discuss this in advance the other day, I couldn't because as a stranger in i2p-dev I have no right to speak.
In addition and in conclusion, I would like to refer to the KDE project and its exemplary management. These include the This Week in Plasma report and the aforementioned 15-Minute Bug Initiative. No matter how you end up implementing it, if you don't show people what's happening, they'll think the project is already dying.
Luther H. Gillis · Private Investigator · Discreet & Confidential
Re: Suggestion for posting simple tasks.
irc2p #i2p-dev, PM me for voice
Don't recall any past refusals, and asking people to join a chat does not make them employees, I'm really not sure what you're getting at. #i2p-dev is +m due to spammers, it's unfortunate but unavoidable, it's not any indication of our attitude towards new people and volunteers.
We are a loosely organized group, there's not a lot of "management", exemplary or otherwise. "assignments" is not usually how we've done things, but maybe it could work if we know who wants assignments and of what type and skill level.
Don't recall any past refusals, and asking people to join a chat does not make them employees, I'm really not sure what you're getting at. #i2p-dev is +m due to spammers, it's unfortunate but unavoidable, it's not any indication of our attitude towards new people and volunteers.
We are a loosely organized group, there's not a lot of "management", exemplary or otherwise. "assignments" is not usually how we've done things, but maybe it could work if we know who wants assignments and of what type and skill level.
Re: Suggestion for posting simple tasks.
I don't want to believe at first, that the people addressed are unwilling to understand. This reveals another problem. My translations into English are miserable. Although I invest a lot of time in each translation. So people like me can't even take part in the kind of conversations that are common on IRC. Another fact that should not be underestimated is the different time zones. When one is active, the other is at rest and vice versa.
Luther H. Gillis · Private Investigator · Discreet & Confidential
Re: Suggestion for posting simple tasks.
I like the idea of having a well-organized list of quick tasks, and "15-minute contribution initiative" sounds like good branding. I'm pretty sure that at the high-level, zzz also agrees with that. The idea is good and not a problem. The problem is the administrative effort to implement it. Somebody's got to put in the work to sort and file these 15-minute tasks. The task of sorting and filing the tasks is a days-to-weeks task.
Right now there's only a handful people working on the code, and we're focused on the tasks we need to complete at the other end of the scale, the days-to-weeks tasks. We're not giving eachother assignments, we are identifying the tasks we think are most interesting or most critical and attempting to complete them.
What it sounds like, to me, is that you see this days-to-weeks task of sorting and filing the beginner contributions as a task that should be high priority. I see the point of that. You also identified one specific task you want to see completed already(POSIX rewrite of launcher shell script). Are you offering to make the list of quick tasks?
Right now there's only a handful people working on the code, and we're focused on the tasks we need to complete at the other end of the scale, the days-to-weeks tasks. We're not giving eachother assignments, we are identifying the tasks we think are most interesting or most critical and attempting to complete them.
What it sounds like, to me, is that you see this days-to-weeks task of sorting and filing the beginner contributions as a task that should be high priority. I see the point of that. You also identified one specific task you want to see completed already(POSIX rewrite of launcher shell script). Are you offering to make the list of quick tasks?