Date: prev next · Thread: first prev next last

Hi Gianluca,

On 16/05/2011 10:32, Gianluca Turconi wrote:
Sophie Gautier wrote:
So that could be a task for somebody who has recurrent time slots
available to [partly] manage the tasks planning. If the tool really
provide efficiency in time management, we should be able to avoid
harassing volunteers already overwhelmed.

Are we talking about "coordinators", aren't we?


If so, that may work as long as the "lower levels", this is to say who
really wants the help for a project, sends his/her requests for help to
the coordinators. This is an (little) overload too. However, I think
it's bearable.

Or the "lower levels" could add the request to the wiki, but the coordinator check that's it's well filled, there is enough information on the duration, etc, somewhat the same way a moderator on a forum organize and tag or remove the posts.

So, the work flow should be:

a) Maintainers/current contributors sends their requests for help to -->
coordinators who add those requests to the "employment system" so that
--> wannabe contributors can choose the task to which they want to

yes or see above,

b) after wannabe contributors have chosen the preferred task, they
contact --> the coordinators who will communicate to --> the
maintainers/current contributors that somebody else has completed or
wants to collaborate to a task.

It may work, if everybody do everything in the right way. :)

:) yes, but I think it's good also to have this person the coordinator who has an overall vision of the system and the workflow, more than only people who have a fragmented view, because resources can be moved from one task to another sometime, or tasks can overlap.

We should discuss about how huge and difficult could be such
coordination work. What skills are needed for such role? Knowledge of
the TDF/LibO project as a whole? Technical skills? Others?

Knowledge of the project and a good understanding of what are the different tasks or development areas on the product, not necessarily technical skills, understanding is enough. Coordination could be a greedy task, imho, so also there should be a good communication between the different coordinators, may be irc channel/meetings. I should have a look at Mediawiki and there organization, may be we could pick ideas.

Once determined how many "coordinators" are needed for the start-up of
the project, we may discuss about the technical feasibility (wiki or
bugzilla?) and the recruiting campaign for those coordinators.

Yes. I'm more for a wiki than a bugzilla, unless you know one that has a very nice interface and is not frightening for non technical contributors.

Kind regards
Founding member of The Document Foundation

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.