You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openaz.apache.org by Colm O hEigeartaigh <co...@apache.org> on 2015/04/14 11:31:06 UTC
Project source
Hi all,
Great that we now have the initial project source code at Apache. Let's
discuss some next steps:
a) Website: Currently there is nothing at
http://openaz.incubator.apache.org/. Is someone willing to start adding
some content here? Some initial description of the project + a link to the
incubator proposal should suffice for now. Do we have any architecture
documents or the like that could be put online as well? Are there existing
websites to migrate over?
b) Source code formatting: The source uses tabs + contains some control m
characters (root pom). The norm at Apache is to use "spaces" indentation
instead of tabs in my experience, and normally 4 spaces at that. What do
you all think about changing this?
c) The code that has been merged is the AT&T + JP. Morgan code. What
remains to be merged?
d) All of the source/test code + poms etc. require the Apache header
license. Copyright notices should be moved to a NOTICE file in the root
directory. Use of @author annotations are also generally frowned upon at
Apache.
If we can get some agreement on initial steps then we can start creating
JIRAs. Are there existing JIRA/bugzilla tasks to migrate to Apache?
Colm.
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Project source
Posted by Emmanuel Lecharny <el...@apache.org>.
Four Java source :
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*
*/
For XML files :
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
For property files :
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership. The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
On Tue, Apr 14, 2015 at 12:00 PM, Farazath Ahamed <me...@gmail.com>
wrote:
> Whats the license header we are supposed to use?
>
> On Tue, Apr 14, 2015, 3:01 PM Colm O hEigeartaigh <co...@apache.org>
> wrote:
>
> > Hi all,
> >
> > Great that we now have the initial project source code at Apache. Let's
> > discuss some next steps:
> >
> > a) Website: Currently there is nothing at
> > http://openaz.incubator.apache.org/. Is someone willing to start adding
> > some content here? Some initial description of the project + a link to
> the
> > incubator proposal should suffice for now. Do we have any architecture
> > documents or the like that could be put online as well? Are there
> existing
> > websites to migrate over?
> >
> > b) Source code formatting: The source uses tabs + contains some control m
> > characters (root pom). The norm at Apache is to use "spaces" indentation
> > instead of tabs in my experience, and normally 4 spaces at that. What do
> > you all think about changing this?
> >
> > c) The code that has been merged is the AT&T + JP. Morgan code. What
> > remains to be merged?
> >
> > d) All of the source/test code + poms etc. require the Apache header
> > license. Copyright notices should be moved to a NOTICE file in the root
> > directory. Use of @author annotations are also generally frowned upon at
> > Apache.
> >
> > If we can get some agreement on initial steps then we can start creating
> > JIRAs. Are there existing JIRA/bugzilla tasks to migrate to Apache?
> >
> > Colm.
> >
> >
> > --
> > Colm O hEigeartaigh
> >
> > Talend Community Coder
> > http://coders.talend.com
> >
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: Project source
Posted by Farazath Ahamed <me...@gmail.com>.
Whats the license header we are supposed to use?
On Tue, Apr 14, 2015, 3:01 PM Colm O hEigeartaigh <co...@apache.org>
wrote:
> Hi all,
>
> Great that we now have the initial project source code at Apache. Let's
> discuss some next steps:
>
> a) Website: Currently there is nothing at
> http://openaz.incubator.apache.org/. Is someone willing to start adding
> some content here? Some initial description of the project + a link to the
> incubator proposal should suffice for now. Do we have any architecture
> documents or the like that could be put online as well? Are there existing
> websites to migrate over?
>
> b) Source code formatting: The source uses tabs + contains some control m
> characters (root pom). The norm at Apache is to use "spaces" indentation
> instead of tabs in my experience, and normally 4 spaces at that. What do
> you all think about changing this?
>
> c) The code that has been merged is the AT&T + JP. Morgan code. What
> remains to be merged?
>
> d) All of the source/test code + poms etc. require the Apache header
> license. Copyright notices should be moved to a NOTICE file in the root
> directory. Use of @author annotations are also generally frowned upon at
> Apache.
>
> If we can get some agreement on initial steps then we can start creating
> JIRAs. Are there existing JIRA/bugzilla tasks to migrate to Apache?
>
> Colm.
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
Re: Project source
Posted by Farazath Ahamed <me...@gmail.com>.
Thanks Colm
Cloned and built without any errors :)
On Wed, Apr 15, 2015 at 1:59 PM, Colm O hEigeartaigh <co...@apache.org>
wrote:
>
> git clone https://git-wip-us.apache.org/repos/asf/incubator-openaz.git
>
> Colm.
>
> On Wed, Apr 15, 2015 at 8:43 AM, Farazath Ahamed <me...@gmail.com>
> wrote:
>
>> Tried cloning the repo at apache incubator[1]. It seem to return an empty
>> repository. What's the correct link of the read only git repo?
>>
>>
>>
>> [1] git://git.apache.org/incubator-openaz.git
>>
>> On Tue, Apr 14, 2015 at 10:03 PM, Colm O hEigeartaigh <
>> coheigea@apache.org> wrote:
>>
>>> Thanks for your response Hal. Comments inline as well:
>>>
>>>
>>> > We will probably move most of it over. However, I assume the same
>>> > licensing considerations apply here as for the code, so I have not
>>> done any
>>> > work on it yet. I have an action to investigate whether we can retain
>>> the
>>> > current email archive at Liberty or whether we will have to move it to
>>> some
>>> > other location.
>>> >
>>> >
>>> Ok cool. I was just about to encourage you to log JIRAs to track these
>>> when
>>> it appears that JIRA has not yet been set up. I will investigate this.
>>>
>>>
>>> > > b) Source code formatting: The source uses tabs + contains some
>>> control
>>> > > m characters (root pom). The norm at Apache is to use "spaces"
>>> > > indentation instead of tabs in my experience, and normally 4 spaces
>>> at
>>> > > that. What do you all think about changing this?
>>> >
>>> > In general we want to conform to Apache standard/best practices. This
>>> > sounds tricky to automate. Are there tools?
>>> >
>>>
>>> It's pretty simple to automate this using standard unix tooling. I will
>>> take care of this. I will also add support for checkstyle, so that the
>>> maven build process will fail if tabs have been added to the code.
>>>
>>>
>>> >
>>> > That is it. The "JP" code is actually all the code contributed to the
>>> > project by various parties all of whom executed an Apache 2.0 license
>>> > agreement, other than the work done at AT&T.
>>> >
>>>
>>> Ok thanks for the clarification.
>>>
>>>
>>> >
>>> > General comment: I have probably spent more time than anyone else in
>>> > OpenAz browsing the Apache and in particular the Incubator pages.
>>> > Unfortunately, I have found the documentation to be hard to find,
>>> > incomplete and in some cases self-contradictory. I have found documents
>>> > which appear to describe current standard practice, but are labeled
>>> > preliminary or draft. In other cases I located a useful document, but
>>> the
>>> > page structure was so unintuitive (to me) that it took considerable
>>> effort
>>> > to find it again a few days later. I also have had trouble in some
>>> cases
>>> > determining what applies to Apache overall and what only to the
>>> Incubator.
>>> >
>>> > Now I have worked for the last 15 years in standards organizations (on
>>> > behalf of my employers) so I am well aware that Apache is a volunteer
>>> > organization and I understand the limitations this presents. I freely
>>> admit
>>> > that I don't have the time (or knowledge) to fix many of these
>>> problems or
>>> > even to systematically identify them.
>>> >
>>> > So what I am requesting is not a comprehensive solution. However,
>>> > especially for the benefit of other members of the project who are even
>>> > less familiar than me with Apache practices and procedures, it would be
>>> > very helpful if one of the mentors (or any knowledgeable person on this
>>> > list) could post a list of the most useful links or for common
>>> procedures
>>> > that come up frequently. I am never in favor of make work, so it this
>>> > information already exists, just point me to it.
>>> >
>>>
>>> These links may or may not be helpful:
>>>
>>> http://community.apache.org/
>>> http://www.apache.org/foundation/how-it-works.html
>>>
>>> Feel free to ask anything more specific. Developing at Apache is actually
>>> pretty simple IMO :-) The main goal we have here is to start building a
>>> community around OpenAZ so that we can exit from the incubator to become
>>> an
>>> Apache top level project some time in the future. So once we get the
>>> issue
>>> tracking system up and running, I encourage all of you to start creating
>>> JIRAs describing the stuff you are working on, or want to work on in the
>>> future.
>>>
>>> Remember that to exit the incubator you will have to add new committers
>>> to
>>> the project, so the more open we are, and the more we make it easier to
>>> get
>>> people involved the better.
>>>
>>> You should feel free to commit any such work (reference the JIRA number
>>> in
>>> the commit message so we can link the commit in the JIRA itself). If
>>> there
>>> are any objections to the commit, then one of the developers will
>>> normally
>>> reply to the commit message and we can hash it out via mailing list. Very
>>> important to note that all decisions relating to the project MUST take
>>> place / be recorded via public mailing list, and not offline.
>>>
>>> Colm.
>>>
>>>
>>>
>>> > Hal
>>> >
>>> >
>>> > >
>>> > > --
>>> > > Colm O hEigeartaigh
>>> > >
>>> > > Talend Community Coder
>>> > > http://coders.talend.com
>>> >
>>>
>>>
>>>
>>> --
>>> Colm O hEigeartaigh
>>>
>>> Talend Community Coder
>>> http://coders.talend.com
>>>
>>
>>
>>
>> --
>> *A.Farasath Ahamed*
>> Undergraduate | Department of Computer Science and
>> Engineering,University of Moratuwa
>> Article Writer | MoraSpirit
>> Mobile: +94 777 603 866
>> E-Mail: mefarazath@gmail.com
>>
>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
--
*A.Farasath Ahamed*
Undergraduate | Department of Computer Science and Engineering,University
of Moratuwa
Article Writer | MoraSpirit
Mobile: +94 777 603 866
E-Mail: mefarazath@gmail.com
Re: Project source
Posted by Colm O hEigeartaigh <co...@apache.org>.
git clone https://git-wip-us.apache.org/repos/asf/incubator-openaz.git
Colm.
On Wed, Apr 15, 2015 at 8:43 AM, Farazath Ahamed <me...@gmail.com>
wrote:
> Tried cloning the repo at apache incubator[1]. It seem to return an empty
> repository. What's the correct link of the read only git repo?
>
>
>
> [1] git://git.apache.org/incubator-openaz.git
>
> On Tue, Apr 14, 2015 at 10:03 PM, Colm O hEigeartaigh <coheigea@apache.org
> > wrote:
>
>> Thanks for your response Hal. Comments inline as well:
>>
>>
>> > We will probably move most of it over. However, I assume the same
>> > licensing considerations apply here as for the code, so I have not done
>> any
>> > work on it yet. I have an action to investigate whether we can retain
>> the
>> > current email archive at Liberty or whether we will have to move it to
>> some
>> > other location.
>> >
>> >
>> Ok cool. I was just about to encourage you to log JIRAs to track these
>> when
>> it appears that JIRA has not yet been set up. I will investigate this.
>>
>>
>> > > b) Source code formatting: The source uses tabs + contains some
>> control
>> > > m characters (root pom). The norm at Apache is to use "spaces"
>> > > indentation instead of tabs in my experience, and normally 4 spaces at
>> > > that. What do you all think about changing this?
>> >
>> > In general we want to conform to Apache standard/best practices. This
>> > sounds tricky to automate. Are there tools?
>> >
>>
>> It's pretty simple to automate this using standard unix tooling. I will
>> take care of this. I will also add support for checkstyle, so that the
>> maven build process will fail if tabs have been added to the code.
>>
>>
>> >
>> > That is it. The "JP" code is actually all the code contributed to the
>> > project by various parties all of whom executed an Apache 2.0 license
>> > agreement, other than the work done at AT&T.
>> >
>>
>> Ok thanks for the clarification.
>>
>>
>> >
>> > General comment: I have probably spent more time than anyone else in
>> > OpenAz browsing the Apache and in particular the Incubator pages.
>> > Unfortunately, I have found the documentation to be hard to find,
>> > incomplete and in some cases self-contradictory. I have found documents
>> > which appear to describe current standard practice, but are labeled
>> > preliminary or draft. In other cases I located a useful document, but
>> the
>> > page structure was so unintuitive (to me) that it took considerable
>> effort
>> > to find it again a few days later. I also have had trouble in some cases
>> > determining what applies to Apache overall and what only to the
>> Incubator.
>> >
>> > Now I have worked for the last 15 years in standards organizations (on
>> > behalf of my employers) so I am well aware that Apache is a volunteer
>> > organization and I understand the limitations this presents. I freely
>> admit
>> > that I don't have the time (or knowledge) to fix many of these problems
>> or
>> > even to systematically identify them.
>> >
>> > So what I am requesting is not a comprehensive solution. However,
>> > especially for the benefit of other members of the project who are even
>> > less familiar than me with Apache practices and procedures, it would be
>> > very helpful if one of the mentors (or any knowledgeable person on this
>> > list) could post a list of the most useful links or for common
>> procedures
>> > that come up frequently. I am never in favor of make work, so it this
>> > information already exists, just point me to it.
>> >
>>
>> These links may or may not be helpful:
>>
>> http://community.apache.org/
>> http://www.apache.org/foundation/how-it-works.html
>>
>> Feel free to ask anything more specific. Developing at Apache is actually
>> pretty simple IMO :-) The main goal we have here is to start building a
>> community around OpenAZ so that we can exit from the incubator to become
>> an
>> Apache top level project some time in the future. So once we get the issue
>> tracking system up and running, I encourage all of you to start creating
>> JIRAs describing the stuff you are working on, or want to work on in the
>> future.
>>
>> Remember that to exit the incubator you will have to add new committers to
>> the project, so the more open we are, and the more we make it easier to
>> get
>> people involved the better.
>>
>> You should feel free to commit any such work (reference the JIRA number in
>> the commit message so we can link the commit in the JIRA itself). If there
>> are any objections to the commit, then one of the developers will normally
>> reply to the commit message and we can hash it out via mailing list. Very
>> important to note that all decisions relating to the project MUST take
>> place / be recorded via public mailing list, and not offline.
>>
>> Colm.
>>
>>
>>
>> > Hal
>> >
>> >
>> > >
>> > > --
>> > > Colm O hEigeartaigh
>> > >
>> > > Talend Community Coder
>> > > http://coders.talend.com
>> >
>>
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>
>
> --
> *A.Farasath Ahamed*
> Undergraduate | Department of Computer Science and Engineering,University
> of Moratuwa
> Article Writer | MoraSpirit
> Mobile: +94 777 603 866
> E-Mail: mefarazath@gmail.com
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Project source
Posted by Farazath Ahamed <me...@gmail.com>.
Tried cloning the repo at apache incubator[1]. It seem to return an empty
repository. What's the correct link of the read only git repo?
[1] git://git.apache.org/incubator-openaz.git
On Tue, Apr 14, 2015 at 10:03 PM, Colm O hEigeartaigh <co...@apache.org>
wrote:
> Thanks for your response Hal. Comments inline as well:
>
>
> > We will probably move most of it over. However, I assume the same
> > licensing considerations apply here as for the code, so I have not done
> any
> > work on it yet. I have an action to investigate whether we can retain the
> > current email archive at Liberty or whether we will have to move it to
> some
> > other location.
> >
> >
> Ok cool. I was just about to encourage you to log JIRAs to track these when
> it appears that JIRA has not yet been set up. I will investigate this.
>
>
> > > b) Source code formatting: The source uses tabs + contains some control
> > > m characters (root pom). The norm at Apache is to use "spaces"
> > > indentation instead of tabs in my experience, and normally 4 spaces at
> > > that. What do you all think about changing this?
> >
> > In general we want to conform to Apache standard/best practices. This
> > sounds tricky to automate. Are there tools?
> >
>
> It's pretty simple to automate this using standard unix tooling. I will
> take care of this. I will also add support for checkstyle, so that the
> maven build process will fail if tabs have been added to the code.
>
>
> >
> > That is it. The "JP" code is actually all the code contributed to the
> > project by various parties all of whom executed an Apache 2.0 license
> > agreement, other than the work done at AT&T.
> >
>
> Ok thanks for the clarification.
>
>
> >
> > General comment: I have probably spent more time than anyone else in
> > OpenAz browsing the Apache and in particular the Incubator pages.
> > Unfortunately, I have found the documentation to be hard to find,
> > incomplete and in some cases self-contradictory. I have found documents
> > which appear to describe current standard practice, but are labeled
> > preliminary or draft. In other cases I located a useful document, but the
> > page structure was so unintuitive (to me) that it took considerable
> effort
> > to find it again a few days later. I also have had trouble in some cases
> > determining what applies to Apache overall and what only to the
> Incubator.
> >
> > Now I have worked for the last 15 years in standards organizations (on
> > behalf of my employers) so I am well aware that Apache is a volunteer
> > organization and I understand the limitations this presents. I freely
> admit
> > that I don't have the time (or knowledge) to fix many of these problems
> or
> > even to systematically identify them.
> >
> > So what I am requesting is not a comprehensive solution. However,
> > especially for the benefit of other members of the project who are even
> > less familiar than me with Apache practices and procedures, it would be
> > very helpful if one of the mentors (or any knowledgeable person on this
> > list) could post a list of the most useful links or for common procedures
> > that come up frequently. I am never in favor of make work, so it this
> > information already exists, just point me to it.
> >
>
> These links may or may not be helpful:
>
> http://community.apache.org/
> http://www.apache.org/foundation/how-it-works.html
>
> Feel free to ask anything more specific. Developing at Apache is actually
> pretty simple IMO :-) The main goal we have here is to start building a
> community around OpenAZ so that we can exit from the incubator to become an
> Apache top level project some time in the future. So once we get the issue
> tracking system up and running, I encourage all of you to start creating
> JIRAs describing the stuff you are working on, or want to work on in the
> future.
>
> Remember that to exit the incubator you will have to add new committers to
> the project, so the more open we are, and the more we make it easier to get
> people involved the better.
>
> You should feel free to commit any such work (reference the JIRA number in
> the commit message so we can link the commit in the JIRA itself). If there
> are any objections to the commit, then one of the developers will normally
> reply to the commit message and we can hash it out via mailing list. Very
> important to note that all decisions relating to the project MUST take
> place / be recorded via public mailing list, and not offline.
>
> Colm.
>
>
>
> > Hal
> >
> >
> > >
> > > --
> > > Colm O hEigeartaigh
> > >
> > > Talend Community Coder
> > > http://coders.talend.com
> >
>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
--
*A.Farasath Ahamed*
Undergraduate | Department of Computer Science and Engineering,University
of Moratuwa
Article Writer | MoraSpirit
Mobile: +94 777 603 866
E-Mail: mefarazath@gmail.com
Re: Project source
Posted by Colm O hEigeartaigh <co...@apache.org>.
Thanks for your response Hal. Comments inline as well:
> We will probably move most of it over. However, I assume the same
> licensing considerations apply here as for the code, so I have not done any
> work on it yet. I have an action to investigate whether we can retain the
> current email archive at Liberty or whether we will have to move it to some
> other location.
>
>
Ok cool. I was just about to encourage you to log JIRAs to track these when
it appears that JIRA has not yet been set up. I will investigate this.
> > b) Source code formatting: The source uses tabs + contains some control
> > m characters (root pom). The norm at Apache is to use "spaces"
> > indentation instead of tabs in my experience, and normally 4 spaces at
> > that. What do you all think about changing this?
>
> In general we want to conform to Apache standard/best practices. This
> sounds tricky to automate. Are there tools?
>
It's pretty simple to automate this using standard unix tooling. I will
take care of this. I will also add support for checkstyle, so that the
maven build process will fail if tabs have been added to the code.
>
> That is it. The "JP" code is actually all the code contributed to the
> project by various parties all of whom executed an Apache 2.0 license
> agreement, other than the work done at AT&T.
>
Ok thanks for the clarification.
>
> General comment: I have probably spent more time than anyone else in
> OpenAz browsing the Apache and in particular the Incubator pages.
> Unfortunately, I have found the documentation to be hard to find,
> incomplete and in some cases self-contradictory. I have found documents
> which appear to describe current standard practice, but are labeled
> preliminary or draft. In other cases I located a useful document, but the
> page structure was so unintuitive (to me) that it took considerable effort
> to find it again a few days later. I also have had trouble in some cases
> determining what applies to Apache overall and what only to the Incubator.
>
> Now I have worked for the last 15 years in standards organizations (on
> behalf of my employers) so I am well aware that Apache is a volunteer
> organization and I understand the limitations this presents. I freely admit
> that I don't have the time (or knowledge) to fix many of these problems or
> even to systematically identify them.
>
> So what I am requesting is not a comprehensive solution. However,
> especially for the benefit of other members of the project who are even
> less familiar than me with Apache practices and procedures, it would be
> very helpful if one of the mentors (or any knowledgeable person on this
> list) could post a list of the most useful links or for common procedures
> that come up frequently. I am never in favor of make work, so it this
> information already exists, just point me to it.
>
These links may or may not be helpful:
http://community.apache.org/
http://www.apache.org/foundation/how-it-works.html
Feel free to ask anything more specific. Developing at Apache is actually
pretty simple IMO :-) The main goal we have here is to start building a
community around OpenAZ so that we can exit from the incubator to become an
Apache top level project some time in the future. So once we get the issue
tracking system up and running, I encourage all of you to start creating
JIRAs describing the stuff you are working on, or want to work on in the
future.
Remember that to exit the incubator you will have to add new committers to
the project, so the more open we are, and the more we make it easier to get
people involved the better.
You should feel free to commit any such work (reference the JIRA number in
the commit message so we can link the commit in the JIRA itself). If there
are any objections to the commit, then one of the developers will normally
reply to the commit message and we can hash it out via mailing list. Very
important to note that all decisions relating to the project MUST take
place / be recorded via public mailing list, and not offline.
Colm.
> Hal
>
>
> >
> > --
> > Colm O hEigeartaigh
> >
> > Talend Community Coder
> > http://coders.talend.com
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Project source
Posted by Emmanuel Lecharny <el...@apache.org>.
On Tue, Apr 14, 2015 at 5:27 PM, Hal Lockhart <ha...@oracle.com>
wrote:
>
>
>
> >
> > b) Source code formatting: The source uses tabs + contains some control
> > m characters (root pom). The norm at Apache is to use "spaces"
> > indentation instead of tabs in my experience, and normally 4 spaces at
> > that. What do you all think about changing this?
>
> In general we want to conform to Apache standard/best practices. This
> sounds tricky to automate. Are there tools?
>
Depends on the IDE you are using. Most of them have a formatter. I do have
some configuration file for Eclipse, if needed.
RE: Project source
Posted by Hal Lockhart <ha...@oracle.com>.
Comments inline:
> a) Website: Currently there is nothing at
> http://openaz.incubator.apache.org/. Is someone willing to start adding
> some content here? Some initial description of the project + a link to
> the incubator proposal should suffice for now. Do we have any
> architecture documents or the like that could be put online as well?
> Are there existing websites to migrate over?
The existing project web page is here:
http://www.openliberty.org/wiki/index.php/OpenAz_Main_Page
We will probably move most of it over. However, I assume the same licensing considerations apply here as for the code, so I have not done any work on it yet. I have an action to investigate whether we can retain the current email archive at Liberty or whether we will have to move it to some other location.
>
> b) Source code formatting: The source uses tabs + contains some control
> m characters (root pom). The norm at Apache is to use "spaces"
> indentation instead of tabs in my experience, and normally 4 spaces at
> that. What do you all think about changing this?
In general we want to conform to Apache standard/best practices. This sounds tricky to automate. Are there tools?
>
> c) The code that has been merged is the AT&T + JP. Morgan code. What
> remains to be merged?
That is it. The "JP" code is actually all the code contributed to the project by various parties all of whom executed an Apache 2.0 license agreement, other than the work done at AT&T.
>
> d) All of the source/test code + poms etc. require the Apache header
> license. Copyright notices should be moved to a NOTICE file in the root
> directory. Use of @author annotations are also generally frowned upon
> at Apache.
This seems clearly to be a manual process.
>
> If we can get some agreement on initial steps then we can start
> creating JIRAs. Are there existing JIRA/bugzilla tasks to migrate to
> Apache?
General comment: I have probably spent more time than anyone else in OpenAz browsing the Apache and in particular the Incubator pages. Unfortunately, I have found the documentation to be hard to find, incomplete and in some cases self-contradictory. I have found documents which appear to describe current standard practice, but are labeled preliminary or draft. In other cases I located a useful document, but the page structure was so unintuitive (to me) that it took considerable effort to find it again a few days later. I also have had trouble in some cases determining what applies to Apache overall and what only to the Incubator.
Now I have worked for the last 15 years in standards organizations (on behalf of my employers) so I am well aware that Apache is a volunteer organization and I understand the limitations this presents. I freely admit that I don't have the time (or knowledge) to fix many of these problems or even to systematically identify them.
So what I am requesting is not a comprehensive solution. However, especially for the benefit of other members of the project who are even less familiar than me with Apache practices and procedures, it would be very helpful if one of the mentors (or any knowledgeable person on this list) could post a list of the most useful links or for common procedures that come up frequently. I am never in favor of make work, so it this information already exists, just point me to it.
Hal
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com