On quinta-feira, 30 de janeiro de 2014 18:12:22, Patrick Ohly wrote:
> I think it is time to establish a procedure for identifying such absent
> developers. Thiago, you helped define the Tizen Governance and how
> contributors can obtain some of the roles [2]. Can you also do the next
> step and define how inactive developers can be identified and what
> should be done in such cases?
> 
> It might be as simple as pinging people at certain intervals to see
> whether and how they respond; some might have simply forgotten that
> certain roles are still assigned to them. More drastic measures might be
> needed when developers are not doing their job, but refuse to step down
> or no replacement can be found.
> 
> [1] https://lists.tizen.org/pipermail/dev/2013-December/001164.html
> [2]
> http://events.linuxfoundation.org/sites/events/files/slides/Tizen%20Develop
> ment%20and%20Governance%20Model%20TDS%2020131111.pdf

Ensuring that everything got reviewed is the responsibility of the maintainer. 
But it's the *interest* of the contributor, so the contributor should pay 
attention to the state of the contribution.

If a contribution goes unreviewed after a while, ping the reviewers. If it 
still doesn't get reviewed, ping the maintainer (write "maintainer ping", for 
example). Sometimes the maintainer will not notice that it's the same 
contribution that no one else reviewed.

It's also the maintainer's responsibility to submit reviewed contributions 
into the Tizen repositories. If a contribution is reviewed but unstaged, again 
ping the maintainer. In this case, the maintainer may give a reason for 
delaying, like "trying to get Milestone Bar's high-priority changes in".

If pinging doesn't result in action, raise it to the mailing list and Cc me in 
particular. Community Management is here to help keep track of these things 
and I try to read every email to tizen-dev but I can definitely not follow 
every Gerrit submission.

MIA maintainers will be contacted to see what's going on. Hopefully, the 
interruption is temporary and can be resolved soon. But permanent MIA 
maintainers will be removed and the position declared vacant.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to