Hi Martin,
I am not on the PMC but would like to voice an opinion
anyway: I think that being on the PMC confers authority and implies good
judgement, but it clearly does not imply domain knowledge about every
subproject. And I think that to the extent possible, we should restrict
commit access to those people who do have domain knowledge.
For instance, the only situation I can imagine where a
PMC member (who was not a JDT committer already) would need to commit to the JDT
APT project is if I (the lead) and all other committers to the project are
unreachable and some change needs to be reverted. That seems sufficiently
unlikely that it can be handled if or when it comes up.
Is there a situation I'm not aware of? I don't have a
specific concern about giving access, I'm just trying to keep master keys from
floating around unnecessarily.
Thanks,
-walter
Hi all,
one thing we didn't discuss in the PMC meeting today
is:
Do we agree that PMC Members should have CVS write
access to the entire repository?
I'll need to know that such that I can make the
bugzilla request with the webmasters accordingly.
Personally, I'm already Platform Core and e4
committer and I'm fine with just adding Website (org.eclipse/www/eclipse)
access.
What do you think?
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management
Project Lead, DSDP PMC Member
