Making the podling RTC will help protect the podling and ASF, but I think we should also try to guide the community to better understand and work the Apache way.
One way or another, I'd suggest couple of other items to the Blue Sky community : - Community members should be more responsive - Community members should act quickly when there are license related concerns - Mentors should help community members to get more familiar with working the apache way, a good start could be [1], and then a little about Apache License [2][3] If the community needs basic "how to work with open source", some materials also available in [4] [1] http://www.apache.org/dev/contributors.html [2] http://www.apache.org/licenses/ [3] http://www.apache.org/legal/src-headers.html [4] http://tuscany.apache.org/working-in-open-source.html On Fri, Sep 5, 2008 at 11:45 PM, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > On Fri, Sep 5, 2008 at 8:32 PM, Bernd Fondermann > <[EMAIL PROTECTED]> wrote: >> ...I'd like to propose that bluesky changes to Review-Then-Commit, >> instead of Commit-Then-Review because of apparent lack of >> eyeballs/mentor oversight.... > > Given the recent events, I support this request. > > What do the Bluesky mentors think? > > -Bertrand > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
