Yes, I modified the post
Just shared this discussion in public. Let’s try to scale our community!
1 Like
Ok, I’m waiting for OpenHub stats to come back to see if it can help to track NethServer contributors/developers. Should be a matter of hours now…
1 Like
Nice try but I can’t still see anything
The stats are available again, however they can’t be the only metric to decide who can join the dev team. Past contributions are important, but not a requirement.
What is important to be a dev team member IMO:
- goal (develop and maintain module, validate bugs, implement issues solution…)
- availability, willingness (occasional, periodic, continuous…)
I’d measure them both with code commits and activity on this community forum. I belive the #development category should become the place where development discussions and decisions occur.
I’m striving to put the decision process on this forum as much as possible, though I’ve been a bit busy on the upgrade tool development and extra-community activities in the last weeks.
During yesterday’s hangout I promised @mark_nl to be more responsive about development issues and I asked him to poke me as needed.
What do you think?
1 Like
Which are the guidelines to be accepted and stay into the group? Having at least a PR accepted?
- Beginner developed at least 1 PR accepted
- Mantainer developed at least 1 module
- Dev - how many commits?
- Core Dev
We can use badges 
I guess something like that, but past experience is not a strict requirement IMO. Personal goals and offered time are important too…
As said, I’d like to find a couple of team coordinators, like @dnutan and @mrmarkuz did with the support team. Then they’ll propose the criteria and come to a consensus here.
Coordinators are like mini-community-managers, and should help other developers to get in touch with each other to achieve their personal goals and the community goals.
For me the willingness is the most important, the need inside you to do something for others … or just to satisfy yourself 
I would love a co-optation like for the ambassador group…do not set a limit, just propose and vote for people.
Agree. For now you can be that mini-cmgr and find a helper along the way
Good idea. List some dev people and ask for more
- mini PR
- simple modules
- check and review code
Find some people and ask them specific things or list some tasks to do
1 Like
Would you like to be co-optated with me? 
Let’s get dev_team and start it again!
1 Like
Dev Team
Current Members
We can set up a new group called @dev_padawan
Dev_padawan
Potential members
@gecco
@mrmarkuz
@dnutan
@danb35
@mark_nl
Anyone else to coopt @davidep ? I can’t found all the PRs suggested
List of tasks to achieve
- Junior Jobs
https://github.com/orgs/NethServer/projects/1#column-1062039 - any PR to propose?
2 Likes
I don’t like the idea of another group. I think that anyone who’s maintaining a project or a package for NethServer, or would like to create something new can be a member of dev_team.
As there are dependencies between our code lines, we need a place where to meet together. We are the dev_team and the Development category is that place, IMO.
There we can discuss about the development process, how the things work, can be developed further and of course, learn something new.
1 Like
Yep I agree…you are IN because you deserve it…no other group please
You’re talking like a leader 
Good, those are the requirements.
Who’s just submitted a PR is able to join the @dev_team ?
Would you like to join the team?
1 Like
Vote yes for all, I Hope you will be agreed
1 Like
It is an honour for me to join the dev team so I’m in.
3 Likes
I don’t like to have too team, but I think that dev-team can be the divided in two team
1- the core_team to work on the firewall, the router, and services ( squid, filtering, ad, dns, dhcp), cli.
2-the software_team to work on project over the core, like mail, cloud, cms, etc, etc
Yes, of couse
4 Likes
Now there’s a proposal
Let’s continue the dev_team discussion there!
I hope this discussion will go on for other teams too!
1 Like