Emmanuel has already updated the source code with Apache license headers. The poms remain to be updated (plus possibly resources - I didn't check).
Colm. On Tue, Apr 14, 2015 at 5:07 PM, <[email protected]> wrote: > I think adding licenses could be automated. > will give it a try and let you know > > Sent from my Xiaomi > On Hal Lockhart <[email protected]>, Apr 14, 2015 8:57 PM wrote: > > 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 > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
