Podling setup tasks...

[Chip Childers <ch...@apache.org>]

The mailing lists are (obviously) now working.

The git repo has been created: https://issues.apache.org/jira/browse/INFRA-7662

The jira project has been created:
https://issues.apache.org/jira/browse/INFRA-7663

If you can provide me with your jira account, I'll add folks to the project.

-chip

Re: Fwd: Podling setup tasks...

[Olivier Lamy <ol...@apache.org>]

See pr https://github.com/brooklyncentral/brooklyn/pull/1365

just run mvn apache-rat:check
and see target/rat.txt content


:-)


On 6 May 2014 04:59, Chip Childers <ch...@apache.org> wrote:
> On Mon, May 5, 2014 at 2:53 PM, Andrew Kennedy (Cloudsoft)
> <an...@cloudsoftcorp.com> wrote:
>> Chip Childers wrote:
>>>
>>> With the exception of any code that wasn't developed as part of this
>>> project (copied from another project), all of the files should have
>>> the standard ASF licensing header.
>>>
>>> I suggest that everyone read through the following links (any anything
>>> else on the a.o or i.a.o sites that you find potentially relevant):
>>>
>>> http://www.apache.org/legal/src-headers.html
>>> http://incubator.apache.org/guides/releasemanagement.html
>>> http://www.apache.org/dev/licensing-howto.html
>>> http://incubator.apache.org/incubation/Incubation_Policy.html
>>
>>
>> OK, the links above were very helpful.
>>
>> It looks like we need to update our source files to contain the ASF license
>> *only* and no copyright statements except in NOTICES. I'll run my script
>> again with the changed text...
>>
>
> Correct, the NOTICE file is where we do our copyright notice.
>
> INAL, but the idea is that individuals participating in our projects
> actually own the copyright to their submitted code, but the ASF
> maintains copyright over the entire "work".  Plus, that makes it easy
> to change a single file when the year rolls over!
>
> You may also find Apache Rat to be helpful...  especially for Java
> projects, it's the go-to tool for checking license header compliance.
>
> http://creadur.apache.org/rat/
>
> You can look at the following POM file for an example of how to configure RAT:
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=pom.xml;h=ecae71ac4ead62292b2116ed5c83100adec3a35f;hb=HEAD
>
> -chip
>
>>
>> Andrew.
>> --
>> -- andrew kennedy ? software engineer : https://github.com/grkvlt/ ;



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Fwd: Podling setup tasks...

[Chip Childers <ch...@apache.org>]

On Mon, May 5, 2014 at 2:53 PM, Andrew Kennedy (Cloudsoft)
<an...@cloudsoftcorp.com> wrote:
> Chip Childers wrote:
>>
>> With the exception of any code that wasn't developed as part of this
>> project (copied from another project), all of the files should have
>> the standard ASF licensing header.
>>
>> I suggest that everyone read through the following links (any anything
>> else on the a.o or i.a.o sites that you find potentially relevant):
>>
>> http://www.apache.org/legal/src-headers.html
>> http://incubator.apache.org/guides/releasemanagement.html
>> http://www.apache.org/dev/licensing-howto.html
>> http://incubator.apache.org/incubation/Incubation_Policy.html
>
>
> OK, the links above were very helpful.
>
> It looks like we need to update our source files to contain the ASF license
> *only* and no copyright statements except in NOTICES. I'll run my script
> again with the changed text...
>

Correct, the NOTICE file is where we do our copyright notice.

INAL, but the idea is that individuals participating in our projects
actually own the copyright to their submitted code, but the ASF
maintains copyright over the entire "work".  Plus, that makes it easy
to change a single file when the year rolls over!

You may also find Apache Rat to be helpful...  especially for Java
projects, it's the go-to tool for checking license header compliance.

http://creadur.apache.org/rat/

You can look at the following POM file for an example of how to configure RAT:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=pom.xml;h=ecae71ac4ead62292b2116ed5c83100adec3a35f;hb=HEAD

-chip

>
> Andrew.
> --
> -- andrew kennedy ? software engineer : https://github.com/grkvlt/ ;

Re: Fwd: Podling setup tasks...

["Andrew Kennedy (Cloudsoft)" <an...@cloudsoftcorp.com>]

Chip Childers wrote:
> With the exception of any code that wasn't developed as part of this
> project (copied from another project), all of the files should have
> the standard ASF licensing header.
>
> I suggest that everyone read through the following links (any anything
> else on the a.o or i.a.o sites that you find potentially relevant):
>
> http://www.apache.org/legal/src-headers.html
> http://incubator.apache.org/guides/releasemanagement.html
> http://www.apache.org/dev/licensing-howto.html
> http://incubator.apache.org/incubation/Incubation_Policy.html

OK, the links above were very helpful.

It looks like we need to update our source files to contain the ASF 
license *only* and no copyright statements except in NOTICES. I'll run 
my script again with the changed text...

Andrew.
-- 
-- andrew kennedy ? software engineer : https://github.com/grkvlt/ ;

Re: Podling setup tasks...

[David Nalley <da...@gnsa.us>]

On Mon, May 5, 2014 at 2:33 PM, Chip Childers <ch...@apache.org> wrote:
> On Mon, May 5, 2014 at 2:07 PM, Andrew Kennedy (Cloudsoft)
> <an...@cloudsoftcorp.com> wrote:
>> Chip Childers wrote:
>>>
>>> The mailing lists are (obviously) now working.
>>
>>
>> Brilliant, thanks for all your work so far, Chip. Much appreciated.
>>
>
> No problem.
>
>>
>>> The git repo has been created
>>
>>
>> So, what is the procedure for migration? We are still raising and merging
>> pull requests against GitHub. What are the actual repositories we should now
>> be using? Is this perhaps a good time to just freeze, make a 0.7.0 release,
>> and then all 0.8.0 development will *definitely* be happening on the ASF
>> repositories.
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-brooklyn.git
>
> The initial committers all need to have filed their ICLA's to get
> apache.org accounts, which have write access to your repo.
>
> I absolutely suggest that you start the process of moving entirely
> over to the ASF now.  The first release of Brooklyn as a podling is
> going to take some time to get right as a new ASF incubating project.
>
> The workflow that jclouds uses (which I'm not all that familiar with)
> IIRC uses pull requests against the ASF read-only repo.  That repo is
> here: https://github.com/apache/incubator-brooklyn
>
> There may be things that need to be configured on the ASF side to send
> PR notices to this list.
>
> Ping to David Nalley...  can you help point the Brooklyn folks to the
> right documentation for what to do here?
>

Details here:
https://blogs.apache.org/infra/entry/improved_integration_between_apache_and

>>
>> I also have some questions about code ownership. I've make a PR to add a
>> Cloudsoft copyright to the Java and groovy code files extant in our repo,
>> but this could be modified to any other appropriate ASF approved statement.
>> As I understand it, the contributors retain copyright, but it is licensed to
>> the ASF?
>
> I've been working offline with Alex H and Duncan to have CloudSoft
> sign the required software grant agreement. This is the agreement that
> formally donates the Brooklyn code to the ASF.
>
> With the exception of any code that wasn't developed as part of this
> project (copied from another project), all of the files should have
> the standard ASF licensing header.
>
> I suggest that everyone read through the following links (any anything
> else on the a.o or i.a.o sites that you find potentially relevant):
>
> http://www.apache.org/legal/src-headers.html
> http://incubator.apache.org/guides/releasemanagement.html
> http://www.apache.org/dev/licensing-howto.html
> http://incubator.apache.org/incubation/Incubation_Policy.html
>
>>
>> I also found some LGPL files, not sure what needs to be done there, if
>> anything?
>
> It will need to be removed.  We (ASF) do not ship code that is
> incompatible with our licensing philosophies.  Dependencies will also
> have to go through a rigorous vetting process, to be sure that any
> incompatible licensing issues are either (1) removed or (2) expected
> to be installed on the target system as a "system dependency" (i.e.:
> not pulled down by default). See the following link for more
> information:
>
> http://www.apache.org/legal/resolved.html
>
>>
>>> The jira project has been created
>>>
>>> If you can provide me with your jira account, I'll add folks to the
>>> project.
>>
>>
>> I'm 'andrew.kennedy' on JIRA, so add that account to the BROOKLYN project,
>> please.
>
> Done
>
> -chip

Fwd: Podling setup tasks...

[Chip Childers <ch...@apache.org>]

On Mon, May 5, 2014 at 2:07 PM, Andrew Kennedy (Cloudsoft)
<an...@cloudsoftcorp.com> wrote:
> Chip Childers wrote:
>>
>> The mailing lists are (obviously) now working.
>
>
> Brilliant, thanks for all your work so far, Chip. Much appreciated.
>

No problem.

>
>> The git repo has been created
>
>
> So, what is the procedure for migration? We are still raising and merging
> pull requests against GitHub. What are the actual repositories we should now
> be using? Is this perhaps a good time to just freeze, make a 0.7.0 release,
> and then all 0.8.0 development will *definitely* be happening on the ASF
> repositories.

https://git-wip-us.apache.org/repos/asf?p=incubator-brooklyn.git

The initial committers all need to have filed their ICLA's to get
apache.org accounts, which have write access to your repo.

I absolutely suggest that you start the process of moving entirely
over to the ASF now.  The first release of Brooklyn as a podling is
going to take some time to get right as a new ASF incubating project.

The workflow that jclouds uses (which I'm not all that familiar with)
IIRC uses pull requests against the ASF read-only repo.  That repo is
here: https://github.com/apache/incubator-brooklyn

There may be things that need to be configured on the ASF side to send
PR notices to this list.

Ping to David Nalley...  can you help point the Brooklyn folks to the
right documentation for what to do here?

>
> I also have some questions about code ownership. I've make a PR to add a
> Cloudsoft copyright to the Java and groovy code files extant in our repo,
> but this could be modified to any other appropriate ASF approved statement.
> As I understand it, the contributors retain copyright, but it is licensed to
> the ASF?

I've been working offline with Alex H and Duncan to have CloudSoft
sign the required software grant agreement. This is the agreement that
formally donates the Brooklyn code to the ASF.

With the exception of any code that wasn't developed as part of this
project (copied from another project), all of the files should have
the standard ASF licensing header.

I suggest that everyone read through the following links (any anything
else on the a.o or i.a.o sites that you find potentially relevant):

http://www.apache.org/legal/src-headers.html
http://incubator.apache.org/guides/releasemanagement.html
http://www.apache.org/dev/licensing-howto.html
http://incubator.apache.org/incubation/Incubation_Policy.html

>
> I also found some LGPL files, not sure what needs to be done there, if
> anything?

It will need to be removed.  We (ASF) do not ship code that is
incompatible with our licensing philosophies.  Dependencies will also
have to go through a rigorous vetting process, to be sure that any
incompatible licensing issues are either (1) removed or (2) expected
to be installed on the target system as a "system dependency" (i.e.:
not pulled down by default). See the following link for more
information:

http://www.apache.org/legal/resolved.html

>
>> The jira project has been created
>>
>> If you can provide me with your jira account, I'll add folks to the
>> project.
>
>
> I'm 'andrew.kennedy' on JIRA, so add that account to the BROOKLYN project,
> please.

Done

-chip