Hi, On Fri, Jun 6, 2008 at 9:34 AM, Jukka Zitting <[EMAIL PROTECTED]> wrote: > ...Since we're using sling-commits for commit notifications and SLING > Jira for tracking progress, could we also grant Janandith limited > commit access to sling svn?...
That would be nice, do you think Apache infrastructure currently allows that? We did that in Cocoon in the first GSoC year, but IIRC infra wasn't too enthusiastic about it. We could create a whiteboard/gsoc folder and give Janandith write access to that, if that's possible. > ...a) The google code commit notifications seem to use a bounce detection > mechanism that prevents the sender address to be permanently allowed > to bypass moderation, causing all commit messages to be individually > moderated.... Ok, that's not usable then - I have suppressed the notifications for now. > ...b) If and when the code becomes a part of Sling proper, it would be > nice if we could keep the full svn history. The easiest way to do that > is to have the code in sling svn right from the beginning.... Sure - my idea was to use the google code project as a scratchpad, and commit via jira patches at regular intervals. But of course, if the code lives in our svn right away that'd be better. -Bertrand
