bradymiller wrote on Thursday, November 11, 2010:
hey,
Also, to avoid confusion; I yanked the Near-privileged role:
http://openmedsoftware.org/wiki/Repository_work_flow_structure
-brady
bradymiller wrote on Thursday, November 11, 2010:
hey,
Also, to avoid confusion; I yanked the Near-privileged role:
http://openmedsoftware.org/wiki/Repository_work_flow_structure
-brady
sunsetsystems wrote on Thursday, November 11, 2010:
Brady, yes that’s how I understood your proposal. Just wanted the option to ask questions if my name will be on a commit. This in no way implies that the Integrator is expected to review it.
bradymiller wrote on Thursday, November 11, 2010:
Rod,
Of course we can stop it or raise questions if needed. But I’d rather document that this does not happen; thus the onus of the commit is placed on the independent “Privileged Developer” whom wishes to commit their code. If they expect a “proof” of their code via this mechanism, then it negates the process and the "Integration Developer’ role will become too involved.
Cleaned up the procedures and developer list a bit:
http://openmedsoftware.org/wiki/Repository_work_flow_structure
-brady
sunsetsystems wrote on Thursday, November 11, 2010:
Brady I understand the goal and reasoning, but the thing is if someone asks me to commit something and I happen to think there’s a serious problem with it then I’m not doing it. How about removing “no questions asked” and instead saying “do not request commits of code that might need further review”.
bradymiller wrote on Thursday, November 11, 2010:
Rod,
Changed the wording:
http://openmedsoftware.org/wiki/Repository_work_flow_structure
Let me know if ok.
The page also now shows developers (and company associations) along with their public repos, which should be useful.
-brady