Talking about some roles in the NethServer community

[alefattorini (Alessio Fattorini)]

I think that we should move on two parallel tracks:

• list all jobs, tagged by area and execution time ( not only list “jobs” but also responsibilities of something here )
• collect everyone’s availability: interests, time, skills.

For example:

Jobs

• write a guide on “HowTo block Facebook with NethServer Content Filter” (medium, at least 1 hour)
• Write an (extensive) howto on creating a NethServer module. Installing an application isn’t that hard, but modeling it into a NethServer webgui supported module is another thing. In order to get NethForge filled with high quality modules, we need to know the basics of creating a module.

Responsibilities

• Welcoming Commitee
• welcome new members replying to @alefattorini’s post. Frequency every week.

People

@mabeleira: translate docs from English to Spanish
@jgjimenezs: in charge of translations from English to Spanish. Daily.
@WillZen: write an HowTo.
@chuckk: testing
@jeffbales: writer and testing

@WillZen

To come to a roadmap we need first a meeting with the volunteers who wants to help. At the meeting we can discus how to go on, who will do which task and when will it be finish.

Agree, we have to schedule it. In the meantime, we need a list of all jobs and responsibilities, so people can pick up from it.