First thing to do is get all the project developers to sign up to the bluesky developers mailing list. The mailing list will be the development team's meeting place, where all bluesky project discussions are conducted. When everyone is subscribed to the mailing list, I'll send instructions to the mailing list about what comes next.

To subscribe to the bluesky developers mailing list, send an email to
[EMAIL PROTECTED]

What do you think of the following idea? When a member of the bluesky team subscribes to the mailing list, their very first email to the list should be an introduction, to let the community know who they are. We don't normally do that with other projects, but there will be a lot of bluesky people I and the other mentors have never met (in person or online). It might be fun :-). What do you think? If you think it is not such a great idea, just speak up and say so. That is how we do things in the the Apache Software Foundation.

Best Regards,
Bill

Ting Peng wrote:
Hi, bill
I am very glad to hear this wonderful news.  Thank you very much.

By the way, what should we do in the next step? If anything I can do, please let me know.

On Jan 13, 2008 8:51 AM, Bill Stoddard < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    I am pleased to announce that project Bluesky has been accepted
    into the
    Apache Incubator with 24 votes in favor and no dissenting votes!
    Congratulations Bluesky team, this was an exceptionally high voter
    turnout for an incubator proposal!

    Thanks to everyone who contributed to the proposal, this promises
    to be
    a very interesting project. Link to the proposal is here:
    http://wiki.apache.org/incubator/BlueSky

    Next Steps:
    - Open an INFRA Jira to request mailing lists to be setup (Bill S)
    - Arrange to collect CLAs and user id preference from each project
    member (Bill)
    - Work on the CCLA (Bill)

    Bill Stoddard




--

      Best regards!

Ting Peng ([EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>)
XJTU-IBM Open Tech. R&D Center

Reply via email to