Transition to ASF

[codefromthecrypt]

This meta-issue will help organize folks as we transition into apache incubation. With shared understanding, we can work together to get tasks done and hack in the ASF as soon as possible. Feel free to add or revise tasks, and update this as we progress.

cc apache mentors: @brianm @tomwhite @hgschmie @ke4qqq @jbonofre @mnour @olamy @kami @smarru @carlossg

Tasks

• [x] Monday morning, April 29th, we can close the vote for jclouds to enter Apache Incubation
• [x] request jclouds podling creation
• [x] request ml jclouds-dev: for development discussions
• [x] request ml jclouds-user: for community discussions
• [x] request ml jclouds-private: for PPMC discussions
• [x] request ml jclouds-commits: for code changes
• [x] request git repo incubator-jclouds from jclouds/jclouds, following this example
• [x] send notication to jclouds and jclouds-dev google groups noting our new locations
• [x] ensure all initial committers have an ICLA on file with the ASF

[ke4qqq]

Davanum Srinivias, Bertrand Delecratz, Henry Saputra all are IPMC members and thus have binding votes. If you want to double check the list, you can use this page: http://people.apache.org/committer-index.html You are looking for the group incubator-pmc.

--David

[codefromthecrypt]

fixed. thx @ke4qqq

[codefromthecrypt]

created temporary repositories for labs aws, openstack, and google apis

[demobox]

This vote has PASSED with 15 binding +1s and 9 non-binding +1s.

@jclouds CONGRATULATIONS all!!

[demobox]

Is requesting an issue tracker project (in ASF JIRA?) part of the podling creation?

[mattstep]

@brianm @hgschmie I believe the recommendation from one of you was just 2 mls, is 4 ok?

[mnour]

Hi Matt

You need to have at least 3 mls:

1- Development 2- Commits 3- Private (Where discussions that should not be in public go)

You can make source code commits go to development mailing list, but I would not recommend that as this will clutter the development mailing list and make it hard to follow

As for the users mailing list, it depends from one project to the other, the more users traffic you have the better to have a separate mailing list for that traffic, so it is really up to the community to decide/choose

On Mon, Apr 29, 2013 at 3:55 PM, Matt Stephenson notifications@github.comwrote:

@brianm https://github.com/brianm @hgschmiehttps://github.com/hgschmieI believe the recommendation from one of you was just 2 mls, is 4 ok?

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17167898 .

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein

[codefromthecrypt]

FWIW, there's about a hundred more users on the existing jclouds google group than the jclouds-dev one, and the former tends to be more how-to than design and dev updates the latter.

Personally, I'd prefer to keep these separate since we are talking magnitude of hundreds. That said, I sometimes over-engineer things, and aware of that :) IOTW, I'm open to consolidating if there's a compelling reason to.

-A

On Mon, Apr 29, 2013 at 7:06 AM, Mohammad Nour notifications@github.comwrote:

Hi Matt

You need to have at least 3 mls:

1- Development 2- Commits 3- Private (Where discussions that should not be in public go)

You can make source code commits go to development mailing list, but I would not recommend that as this will clutter the development mailing list and make it hard to follow

As for the users mailing list, it depends from one project to the other, the more users traffic you have the better to have a separate mailing list for that traffic, so it is really up to the community to decide/choose

On Mon, Apr 29, 2013 at 3:55 PM, Matt Stephenson notifications@github.comwrote:

@brianm https://github.com/brianm @hgschmie< https://github.com/hgschmie>I believe the recommendation from one of you was just 2 mls, is 4 ok?

— Reply to this email directly or view it on GitHub< https://github.com/jclouds/jclouds/issues/1576#issuecomment-17167898> .

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17168473 .

[mnour]

Hi Adrian

On Mon, Apr 29, 2013 at 4:17 PM, Adrian Cole notifications@github.comwrote:

FWIW, there's about a hundred more users on the existing jclouds google group than the jclouds-dev one, and the former tends to be more how-to than design and dev updates the latter.

Personally, I'd prefer to keep these separate since we are talking magnitude of hundreds. That said, I sometimes over-engineer things, and aware of that :) IOTW, I'm open to consolidating if there's a compelling reason to.

With that numbers you are talking about I would definitely go with two different mailing lists for for dev and users. I totally agree with what you said

-A

On Mon, Apr 29, 2013 at 7:06 AM, Mohammad Nour notifications@github.comwrote:

Hi Matt

You need to have at least 3 mls:

1- Development 2- Commits 3- Private (Where discussions that should not be in public go)

You can make source code commits go to development mailing list, but I would not recommend that as this will clutter the development mailing list and make it hard to follow

As for the users mailing list, it depends from one project to the other, the more users traffic you have the better to have a separate mailing list for that traffic, so it is really up to the community to decide/choose

On Mon, Apr 29, 2013 at 3:55 PM, Matt Stephenson notifications@github.comwrote:

@brianm https://github.com/brianm @hgschmie< https://github.com/hgschmie>I believe the recommendation from one of you was just 2 mls, is 4 ok?

— Reply to this email directly or view it on GitHub< https://github.com/jclouds/jclouds/issues/1576#issuecomment-17167898> .

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein

— Reply to this email directly or view it on GitHub< https://github.com/jclouds/jclouds/issues/1576#issuecomment-17168473> .

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17169207 .

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein

[mattstep]

@mnour this is interesting, because we currently do not have a private list, what types of discussions should go there vs the dev list? we've been a pretty open community aside from the occasional private irc conversation

[jbonofre]

+1 with both of you guys.

user and dev mailing list make sense (it's what all Apache projects use).

Regards JB

On 04/29/2013 04:27 PM, Mohammad Nour wrote:

Hi Adrian

On Mon, Apr 29, 2013 at 4:17 PM, Adrian Cole notifications@github.comwrote:

FWIW, there's about a hundred more users on the existing jclouds google group than the jclouds-dev one, and the former tends to be more how-to than design and dev updates the latter.

Personally, I'd prefer to keep these separate since we are talking magnitude of hundreds. That said, I sometimes over-engineer things, and aware of that :) IOTW, I'm open to consolidating if there's a compelling reason to.

With that numbers you are talking about I would definitely go with two different mailing lists for for dev and users. I totally agree with what you said

-A

On Mon, Apr 29, 2013 at 7:06 AM, Mohammad Nour notifications@github.comwrote:

Hi Matt

You need to have at least 3 mls:

1- Development 2- Commits 3- Private (Where discussions that should not be in public go)

You can make source code commits go to development mailing list, but I would not recommend that as this will clutter the development mailing list and make it hard to follow

As for the users mailing list, it depends from one project to the other, the more users traffic you have the better to have a separate mailing list for that traffic, so it is really up to the community to decide/choose

On Mon, Apr 29, 2013 at 3:55 PM, Matt Stephenson notifications@github.comwrote:

@brianm https://github.com/brianm @hgschmie< https://github.com/hgschmie>I believe the recommendation from one of you was just 2 mls, is 4 ok?

— Reply to this email directly or view it on GitHub< https://github.com/jclouds/jclouds/issues/1576#issuecomment-17167898> .

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein

— Reply to this email directly or view it on GitHub< https://github.com/jclouds/jclouds/issues/1576#issuecomment-17168473> .

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17169207

.

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein

— Reply to this email directly or view it on GitHub https://github.com/jclouds/jclouds/issues/1576#issuecomment-17169788.

Jean-Baptiste Onofré jbonofre@apache.org http://blog.nanthrax.net Talend - http://www.talend.com

[mattstep]

I understand the user/dev and thought that was a good thing to keep, what's private for?

[smarru]

On Apr 29, 2013, at 10:32 AM, Matt Stephenson notifications@github.com wrote:

@mnour this is interesting, because we currently do not have a private list, what types of discussions should go there vs the dev list? we've been a pretty open community aside from the occasional private irc conversation

Hi Matt,

The only recommended emails to private are security related issues which you do not to be discussing in public (until a resolution is made) and adding new committers/pmc members. The goal of having the personal additions in private is to ensure free opinions.

Suresh

— Reply to this email directly or view it on GitHub.

[jbonofre]

Private is used for project PMC members (at Apache).

It's where we vote the new committers, new PMC, propose private section for the Apache board (if some concerns have to be raised).

Regards JB

On 04/29/2013 04:37 PM, Matt Stephenson wrote:

I understand the user/dev and thought that was a good thing to keep, what's private for?

— Reply to this email directly or view it on GitHub https://github.com/jclouds/jclouds/issues/1576#issuecomment-17170281.

Jean-Baptiste Onofré jbonofre@apache.org http://blog.nanthrax.net Talend - http://www.talend.com

[smarru]

Hi All,

Unless I missed any email, I did not see an email on ASF General mailing list regarding vote closure and vote result.

Can one of you post the vote summary on the list with adding [RESULT] in front of the current VOTE thread? Once the result is called for, we can proceed with the podling creating jira with all the mailing lists, jira, and accounts (ICLA's and so forth).

Thanks, Suresh

On Apr 29, 2013, at 9:36 AM, Andrew Phillips notifications@github.com wrote:

This vote has PASSED with 15 binding +1s and 9 non-binding +1s.

@jclouds CONGRATULATIONS all!!

— Reply to this email directly or view it on GitHub.

[mnour]

Hi Matt

In general what is private and what is not is actually more of a sense than a well defined rules, but formally speaking for example discussions that are more related to the PPMC (Podling Project Manager Committee) [1] goes on private list, discussions related to recommending a new committer also goes on the private list. You can also use a rule of thumb, that is if you are not really sure it will not harm to start by sending the e-mail to private and if agreed to make the subject public then goes on either development or users lists

For general rules have a look at [2] & [3]

[1] http://incubator.apache.org/guides/ppmc.html [2] http://www.apache.org/foundation/how-it-works.html#confidential [3] http://www.apache.org/dev/contrib-email-tips.html

On Mon, Apr 29, 2013 at 4:32 PM, Matt Stephenson notifications@github.comwrote:

@mnour https://github.com/mnour this is interesting, because we currently do not have a private list, what types of discussions should go there vs the dev list? we've been a pretty open community aside from the occasional private irc conversation

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17170048 .

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein

[mattstep]

That makes a bit more sense, private is new to us, and commits is a bit archaic (doesn't make sense in a distributed version control world) and sounds like a duplicate of what we'll get from github.

[mnour]

Hi Suresh

On Mon, Apr 29, 2013 at 4:40 PM, Suresh Marru notifications@github.comwrote:

Hi All,

Unless I missed any email, I did not see an email on ASF General mailing list regarding vote closure and vote result.

Can one of you post the vote summary on the list with adding [RESULT] in front of the current VOTE thread? Once the result is called for, we can proceed with the podling creating jira with all the mailing lists, jira, and accounts (ICLA's and so forth).

Good catch, it would be better if the one who started the [VTE] to send also the [RESULT] one. Take a look at [1] for an example

[1] http://markmail.org/message/ikkuvs2c6b4x72oz

Thanks, Suresh

On Apr 29, 2013, at 9:36 AM, Andrew Phillips notifications@github.com wrote:

This vote has PASSED with 15 binding +1s and 9 non-binding +1s.

@jclouds CONGRATULATIONS all!!

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17170514 .

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein

[mnour]

Hi Matt

On Mon, Apr 29, 2013 at 4:46 PM, Matt Stephenson notifications@github.comwrote:

That makes a bit more sense, private is new to us, and commits is a bit archaic (doesn't make sense in a distributed version control world) and sounds like a duplicate of what we'll get from github.

Pardon me I didn't understand your comment about the commits mailing list part

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17170889 .

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein

[mattstep]

@mnour sorry, I just haven't seen it used since I worked at amazon, didn't mean to offend anyone. If we're using github, we should see when a pull request is merged in.

[mnour]

Hi Matt

On Mon, Apr 29, 2013 at 4:56 PM, Matt Stephenson notifications@github.comwrote:

@mnour https://github.com/mnour sorry, I just haven't seen it used since I worked at amazon, didn't mean to offend anyone. If we're using github, we should see when a pull request is merged in.

1st of all, there is no offend at all :D, besides I am not an easy person to offend ;),. I just really didn't get what you mean with the comment you sent :)

Actually now I understand your point of view, but in ASF we have a rule that "If didn't happen on a mailing list then it didn't happen" which is a general rule that applies in mailing lists in general, but also it is either for people to follow the commits and search among those sent e-mails as well

I agree with you the working on Github is different than in ASF, but the difference in not about being positive or negative. ASF way of doing things is more oriented towards building and maintaining a community around the project as wise it will die out, and communication among people of this community is important and e-mail is one major channel of this communication for the different activities of that community whether code/development related or not

But as you and the others are going to be part of the ASF community you have all the right to suggest enhancements and be totally open about your opinions about how we can make ASF better :)

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17171518 .

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein

[silkysun]

Hello all,

I have emailed the vote result to the ASF General mailing list. Apologies for the delay in posting here. I am just catching up with reading through emails this morning.

Thanks!

Becca

On Apr 29, 2013, at 8:28 AM, Mohammad Nour wrote:

Hi Matt

On Mon, Apr 29, 2013 at 4:56 PM, Matt Stephenson notifications@github.comwrote:

@mnour https://github.com/mnour sorry, I just haven't seen it used since I worked at amazon, didn't mean to offend anyone. If we're using github, we should see when a pull request is merged in.

1st of all, there is no offend at all :D, besides I am not an easy person to offend ;),. I just really didn't get what you mean with the comment you sent :)

Actually now I understand your point of view, but in ASF we have a rule that "If didn't happen on a mailing list then it didn't happen" which is a general rule that applies in mailing lists in general, but also it is either for people to follow the commits and search among those sent e-mails as well

I agree with you the working on Github is different than in ASF, but the difference in not about being positive or negative. ASF way of doing things is more oriented towards building and maintaining a community around the project as wise it will die out, and communication among people of this community is important and e-mail is one major channel of this communication for the different activities of that community whether code/development related or not

But as you and the others are going to be part of the ASF community you have all the right to suggest enhancements and be totally open about your opinions about how we can make ASF better :)

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17171518 .

Thanks

- Mohammad Nour

"Life is like riding a bicycle. To keep your balance you must keep moving"

• Albert Einstein — Reply to this email directly or view it on GitHub.

[silkysun]

So it seems that we need a mentor to setup the jclouds podling. Any volunteers?

[smarru]

JClouds is mentor rich, you will have the benefit of it now:)

If no one gets to it before 7pm eastern time today, I will get it going then.

Suresh

On Apr 29, 2013, at 1:39 PM, Becca Wood notifications@github.com wrote:

So it seems that we need a mentor to setup the jclouds podling. Any volunteers?

— Reply to this email directly or view it on GitHub.

[silkysun]

Cool. Thanks, Suresh!

I also need an ASF member to help setup the jclouds mailing lists. Any takers for this task?

[olamy]

I'm asking the mailing list creation. I need 2 more volunteers for moderation.

[olamy]

I wonder about an other mailing issues for jira issues notifications ?

[codefromthecrypt]

I'll volunteer as a moderator. I currently moderate the old lists. Anybody want to join me?

On Mon, Apr 29, 2013 at 4:15 PM, Olivier Lamy notifications@github.comwrote:

I'm asking the mailing list. I need 2 more volunteers for moderation.

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17200626 .

[olamy]

@adriancole email you want to use for moderation ? send it to me to olamy at apache dot org. We can start with two and add other later.

[olamy]

@adriancole your asf one ?

[codefromthecrypt]

either way is fine. I should be checking my asf one anyway!

On Mon, Apr 29, 2013 at 4:31 PM, Olivier Lamy notifications@github.comwrote:

@adriancole https://github.com/adriancole your asf one ?

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17201187 .

[olamy]

mailing lists request done. NOTE: I have added issues ml too .

[olamy]

I can try working on podlings.xml file later today (7pm Australian time) except if someone beat me.

[demobox]

Anybody want to join me?

@adriancole +1

[smarru]

Hi Olivier,

I am creating JIRA's for all tasks and then add sub tasks - https://issues.apache.org/jira/browse/INFRA-6209

I realize you already created mailing lists and added a comment. I think it will be good to create all the task and mark them resolved as they are being worked on.

I am requesting a JIRA as mentioned in the proposal - "jclouds currently uses GitHub for issue tracking. The intent is to request an allocation for Jira upon acceptance into the Incubator. Proposed project name: jclouds"

Suresh

On Apr 29, 2013, at 7:35 PM, Olivier Lamy notifications@github.com wrote:

I can try working on podlings.xml file later today (7pm Australian time) except if someone beat me.

— Reply to this email directly or view it on GitHub.

[silkysun]

I am also happy to volunteer time for moderation, but I do not currently have an apache email address. Is it possible for me to claim silkysun@apache?

[olamy]

sure. You will have that with your account creation. But at least we will be able to start with ml for various discussions.

[mattstep]

Should the creation of accounts for people who don't have them yet be an item on this list? Sounds like it.

Matt

On Mon, Apr 29, 2013 at 6:01 PM, Olivier Lamy notifications@github.comwrote:

sure. You will have that with your account creation. But at least we will be able to start with ml for various discussions.

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17204208 .

[smarru]

@Olivier: Created the podlings.xml entry and the status page. Reflected in clutch now - http://incubator.apache.org/clutch

@Matt: Yes, before we request account creation, we need all new committers file ICLA's. I will check on committer status and send pointers and instructions shortly, meanwhile you can see other podling tasks here - http://incubator.apache.org/projects/jclouds.html

Suresh

On Apr 29, 2013, at 9:25 PM, Matt Stephenson notifications@github.com wrote:

Should the creation of accounts for people who don't have them yet be an item on this list? Sounds like it.

Matt

On Mon, Apr 29, 2013 at 6:01 PM, Olivier Lamy notifications@github.comwrote:

sure. You will have that with your account creation. But at least we will be able to start with ml for various discussions.

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17204208 .

— Reply to this email directly or view it on GitHub.

[smarru]

Hello Ignasi, Andrew (Gaul), Andrew (Phillips), Matt, Everett, Becca,

From the initial committers, I see all of you do not have ASF accounts. Please read the new committer guide - http://www.apache.org/dev/new-committers-guide.html#guide-for-new-committers.

The key thing is to have your ICLA on file with Apache, please follow instructions on the form - http://www.apache.org/licenses/icla.txt (http://www.apache.org/licenses/icla.pdf) and email a signed & scanned copy to secretary at apache dot org. Once you have the accounts approved, we can then proceed to adding you to jclouds committers.

--Suresh

On Apr 28, 2013, at 9:32 PM, Adrian Cole notifications@github.com wrote:

This meta-issue will help organize folks as we transition into apache incubation. The main point of this issue is to help those who can help understand and move tasks so that we can hack in the ASF as soon as possible. Feel free to add or revise tasks, and update this as we progress.

cc apache mentors: @brianm @tomwhite @hgschmie @ke4qqq @jbonofre @mnour @olamy @kami @smarru @carlossg

Tasks

Monday morning, April 29th, we can close the vote for jclouds to enter Apache Incubation request jclouds podling creation request ml jclouds-dev: for development discussions request ml jclouds-user: for community discussions request ml jclouds-private: for PPMC discussions request ml jclouds-commits: for code changes request git repo incubator-jclouds from jclouds/jclouds, following this example request git repo incubator-jclouds-labs-google request git repo incubator-jclouds-labs-aws send notication to jclouds and jclouds-dev google groups noting our new locations Content

Close of Vote

make sure you add RESULT to the subject, ex. [RESULT] [VOTE] Accept jclouds into the Apache Incubator

This vote has PASSED with 12 binding +1s and 12 non-binding +1s.

Binding +1 VOTES:

David Nally Suresh Marru Nandana Mihindukulasooriya Tomaz Muraus
Olivier Lamy Mark Struberg Mohammad Nour El-Din
Roman Shaposhnik Brian McCallister Jean-Baptiste Onofré Tom White Alan Cabrera

Non-binding +1 VOTES:

Edward J. Yoon Henry Saputra Chip Childers John D. Ament Kevin Kludge Ashish Paliwala Andrea Turli Andrei Savu Bertrand Delacretaz Jordan Zimmerman Carlos Sanchez Davanum Srinivas

Thanks to all who voted and participated in the discussions. — Reply to this email directly or view it on GitHub.

[mattstep]

You can also GPG sign it! Which is awesome, and done, and makes me want to hug an ASF member.

[etoews]

Things are in motion at Rackspace for the ICLAs and CCLA. I'll update when I have more info.

[gaul]

Wheels turning at Maginatics for the ICLA.

[nacx]

Same here at Abiquo

[codefromthecrypt]

hi, mentors.

jclouds, Inc. has distribution rights for all contributed code in the various repos. Code has been submitted over the years under almost identical copies of the ASF contributor agreements. http://www.jclouds.org/documentation/devguides/contributing-to-jclouds

Most of these agreements are stored in echosign, though some emailed scanned copies of hand-signed forms. There are over a hundred agreements, but they are fairly well organized.

jclouds, Inc also has trademark documentation for "jclouds" and can assign it to apache. Same goes for dns names, etc.

Since I have access to all relevant artifacts, and am the sole authority over jclouds, Inc., I volunteer to get whatever's needed for http://incubator.apache.org/ip-clearance/index.html

Can I have a couple volunteer mentors to help me with the process? I can give whoever access to anything we need to get this done.

[ke4qqq]

On Tue, Apr 30, 2013 at 11:47 AM, Adrian Cole notifications@github.comwrote:

hi, mentors.

jclouds, Inc. has distribution rights for all contributed code in the various repos. Code has been submitted over the years under almost identical copies of the ASF contributor agreements. http://www.jclouds.org/documentation/devguides/contributing-to-jclouds

Most of these agreements are stored in echosign, though some emailed scanned copies of hand-signed forms. There are over a hundred agreements, but they are fairly well organized.

jclouds, Inc also has trademark documentation for "jclouds" and can assign it to apache. Same goes for dns names, etc.

Since I have access to all relevant artifacts, and am the sole authority over jclouds, Inc., I volunteer to get whatever's needed for http://incubator.apache.org/ip-clearance/index.html

Can I have a couple volunteer mentors to help me with the process? I can give whoever access to anything we need to get this done.

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds/issues/1576#issuecomment-17235450 .

So assuming you have the authority to (and I am guessing from your copious documentation referenced that you do), what is really needed is for the SGA to get signed on behalf of jclouds Inc. and submitted to secretary@ I don't think secretary will require your complete documentation of provenance, but I won't pretend to speak for him. I'd wait for private@jclouds.i.a.o to be established, and then start the conversation with secretary@.

That said - the jclouds proposal vote in the incubator obviates the need for a vote on code import

That said SGA is just the first step in getting something that's ready to ship, we'll still need to go through and do a number of additional things like change source license headers, LICENSE and NOTICE files, etc.

--David

[codefromthecrypt]

thanks for the clarification, david. So, I'll work on the background on the SGA, and in the mean time, folks can I suppose start importing repos, changing headers, packages, etc.

[mattstep]

ICLA has been received, so whoever is setting up accounts, I'm cleared by secretary@

[ke4qqq]

On Tue, Apr 30, 2013 at 1:22 PM, Matt Stephenson notifications@github.comwrote:

ICLA has been received, so whoever is setting up accounts, I'm cleared by secretary@

Generally Craig will automagically create the account when he processes the ICLA.

--David

[abayer]

re: git repos - from what I read, it looks like an IPMC member has to submit the request. So, IPMC members, help? =) We want to start with just one for jclouds proper, but will eventually want multiple labs/examples/chef/karaf/cli ones.