You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Peter Kovacs <pe...@apache.org> on 2022/08/29 18:50:50 UTC

How to scale the Project

Hi all,


I had on the weekend a philosophical talk with a friend of mine. One 
Claim ha did in this discussion has been that (for whatever Reasons) not 
a lot of people have the trait of initiative. Having initiative is a 
special trait.

Since we suffer from the Issue that there are people who would like to 
help, but not show any signs of Intiative, I thought we should maybe 
discuss how we could empower programmers to work on Issues.

My friend suggested in the discussion that maybe it could work out that 
volunteers with initiative write what is to do in a specific case.

And then we look for someone to do the task. This might be inefficient 
at first. But maybe we can get people to volunteer by this method.


What do you think?  Does anyone have experience from other Projects?

And how much needxs to be layed out in order other volunteers look into it?


Any thoughts?

All the best

Peter


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Re: How to scale the Project

Posted by Carl Marcum <cm...@apache.org>.
Hi Peter,

I have often thought about starting some TODO type lists on the planning 
wiki but haven't had time yet.
We may already have one somewhere.

Besides the obvious 4.2 blockers, there are probably a number of things 
we could come up with divided by areas like main office development, QA, 
docs, infrastructure, etc.
Like in QA there are a number of new tests that need done and a large 
project could be to update the framework JUnit from 4 to 5 for example.

Maybe for areas or tasks we could and volunteers for mentors and tasks.

Then we would have concrete things to point volunteers to by interest 
instead of letting them try to find things to work on on their own.
When there is a volunteer maybe they feel a need to complete the task.

After all that maybe a new call for volunteers?

Just a thought.

Best regards,
Carl

On 8/29/22 2:50 PM, Peter Kovacs wrote:
> Hi all,
>
>
> I had on the weekend a philosophical talk with a friend of mine. One 
> Claim ha did in this discussion has been that (for whatever Reasons) 
> not a lot of people have the trait of initiative. Having initiative is 
> a special trait.
>
> Since we suffer from the Issue that there are people who would like to 
> help, but not show any signs of Intiative, I thought we should maybe 
> discuss how we could empower programmers to work on Issues.
>
> My friend suggested in the discussion that maybe it could work out 
> that volunteers with initiative write what is to do in a specific case.
>
> And then we look for someone to do the task. This might be inefficient 
> at first. But maybe we can get people to volunteer by this method.
>
>
> What do you think?  Does anyone have experience from other Projects?
>
> And how much needxs to be layed out in order other volunteers look 
> into it?
>
>
> Any thoughts?
>
> All the best
>
> Peter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org