Hello, > From: Marcus [mailto:[email protected]]
> he needs to be a committer. > > So, you can work together: He is suggesting the text changes (or > deliveres actually patches) and you can commit them to the CMS. Yes, I am (principally) aware of this possibility. --------------------- Only I probably needed some help in organizing the practical work, BECAUSE: I don't know how to keep non-committed changes in the CMS for a longer period of time, because all pending changes to the OO website will always be transferred with a commit. Example: if I change the web page "a. html" at 20:00 and save it as a stating build (and not commited) and another one at 21:00 changes the web page "b. html" and commits immediately, then both changes will be published. --------------------- > Here is a short list how to become a committer [1]. These are general > ASF process steps, so it doesn't apply directly to > OpenOffice. But the > priciple is the same: Yes, I know this procedure. If I read that Dave offers to discuss the committer-status in the PMC, can I assume that Apache will grant the committer rights relatively soon? Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
