Quoting Michal Hrusecky
Michal Hrusecky - 14:24 12.12.13 wrote:
Robert Schweikert - 8:14 12.12.13 wrote:
...
The wiki is open, enables easy collaboration and has a history, thus it is still easy to see who made the changes. And the person that added the pink hats requirement can be asked why that would be a potentially good idea.
The point of OSEP is to document the agreement, not to collaborate on document easily. And be the source of trusted information. All changes should be discussed. Not that somebody switches blue hats for pink hats and after new ambassador creates tons of pink hats he will find out, that somebody just though that blue meant pink and pink was nicer formulation.
Think about it in terms like RFC, JEP, ISO, ... It's something you create, agree upon and then never ever modify once accepted, unless patch goes through the mailing list review process.
Over-complicating the process doesn't help in the end. A Wiki page can be locked (see the SDB: namespace for example. Only a handful of users can actually make changes visible). That sounds sufficient to 'ensure an agreed standard is not changed'. Until it is locked, it can't be considered 'agreed' or ready for approval, but in fact _open_ for collaboration. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org