Thanks Colm Cloned and built without any errors :)
On Wed, Apr 15, 2015 at 1:59 PM, Colm O hEigeartaigh <[email protected]> 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 <[email protected]> > 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 < >> [email protected]> 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: [email protected] >> > > > > -- > 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: [email protected]
