Apache OpenOffice operates in CTR mode regarding all changes, commits to svn repositories.
Changes to source, those files integral to the product, in reality, are almost never made, save for compiler deprecation or option changes, without either referencing an issue, or, in the case of larger significant changes, a discussion on dev@openoffice.apache.org. The absence of an issue or a discussion for a code change can lead to unnecessary vetoes, a situation no one wants. Now, in addition to product source files contained in /trunk, and various branches, we have logo source files in a web area which are also product artifacts: http://www.openoffice.org/marketing/art/galleries/logos/aoo-working/ Better placement for these source files is under discussion. See current mail thread: http://markmail.org/message/6aoohsq4jbx5z7us Last week, two of the original svg files -- files prefixed with: Apache_OpenOffice_Logo_ChrisR_selected_2013-06 were changed. These changes were not discussed in advance, nor an issue submitted for them. Given the events of the day, it was the PMC's decision to not veto these changes, but to copy these changed originals to new files and restore the originals. As with any changes, we welcome any discussion concerning these changes. So, back the original topic. Given recent events, do we want to have a changed policy to require issue submission and/or list discussion before new commits? -- ------------------------------------------------------------------------------------------------- MzK Success is falling nine times and getting up ten." -- Jon Bon Jovi
