Re: [PROPOSAL] Apache RAT
On Oct 25, 2007, at 3:52 PM, Yoav Shapira wrote: Hi, On 10/25/07, Noel J. Bergman [EMAIL PROTECTED] wrote: Yoav Shapira wrote: Project name uniqueness should not be a criterion for Incubator acceptance. I would even go further and say clear copyright infringement is probably the only reason to ask for a name change. You mean trademark? :-) Yes. My mistake, sorry for the confusion, if any ;) Heh. Regardless, thanks a lot for the explanation... --kevan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
How about ErroRat, a play on Ararat? On 10/24/07, Hiram Chirino [EMAIL PROTECTED] wrote: I like plain rat, and since rat is common word I doubt we have to worry about trademark violations. I also don't confuse it with any other projects in the java space.. so I think it's ok. On 10/23/07, Robert Burrell Donkin [EMAIL PROTECTED] wrote: http://wiki.apache.org/incubator/RatProposal has been stable for a while now so i'd like to throw it open to final scrutiny before i call for a VOTE. (please don't vote yet ;-) the name RAT has been discussed previously - see http://mail-archives.apache.org/mod_mbox/incubator-general/200710.mbox/[EMAIL PROTECTED] RAT is a good name and popular but i'm still a little concerned that there are existing open source projects named RAT as well as commercial software containing RAT in their name. Apache aRAT has the advantage of being unused but the disadvantage of being a common name in some other languages. if anyone strongly disagrees with the consensus that RAT is ok and prefers aRAT please jump in now. - robert Rat Proposal == Abstract -- RAT is comprehension and auditing for distributions and source code. Proposal --- RAT will provide a focus for components, applications and integration tools for the comprehension and audit of distributions and source code. It will collect data and meta-data as required. It will create suitable schemas for this data and meta-data as required. Background -- RAT began as an attempt to automate the technical part of reviewing releases in the incubator. Following requests for access from release managers, RAT was developed as an open source project under the Apache License 2.0. Rationale --- Reviewing releases for compliance with Apache technical criteria and policies is time consuming. The Incubator requires that all releases are reviewed. Though small mistakes are common, this process typically adds only a little value. It is common for candidates to be presented with small but significant defects which then must be fixed and the candidate represented. Significant energy and good will is wasted by this process. This is unnecessary. Given effort, these technical criteria are capable of automation. Automated continuous checking of the source would allow the Incubator PMC to be alerted promptly to potential issues. Integration with build tools (such as Apache Ant and Apache Maven) would allow releases to be checked automatically and continuously. Initial Goals - * Read standard license meta-data for documents without license headers * Improved RAT reporting * RAT source reporting for major build tools * Continuous RAT * RAT analytics: using meta-data to verify rules o Apache third party documents policy analysis o license compatibility analysis * Discordia integration to allow distributed binaries to be recognised * RAT analytic integration for major build tools * Improved recursive RAT scripts for better analysis of release with many distributables Current Status Meritocracy -- I'm very happy to move from a solo development model towards a collective one as more active developers are recruited. Community - The RAT community needs to be developed. Having RAT here at Apache will hopefully encourage release managers to take a more active role in developing RAT. Core Developers It has been developed principally by myself but with significant contributions of small amounts of code from other Apache members and committers. Alignment RAT has found itself becoming a standard part of the Apache release infrastructure. The Incubator needs fully featured release tools. It makes sense to bring the project here. Known Risks == Orphaned Projects -- This is a project with a set of definite goals aimed at serving the wider Apache community. There may well come a time when the coding is actually finished. It has a small set of developers who all have many other calls on their time. The target user audience is relatively small. So, this risk is real. I think that it's clear that something similar to RAT is required. So, unless another better product is developed, time will be found to push RAT forward. Even if one day, RAT is orphaned then it will have done it's job. Inexperience With Open Source - The contributors are Apache members or experienced Apache committers. Reliance On Salaried Developers --- I know of no one who's paid to work on RAT. Relationships with Other Apache Products -- RAT contains an Ant reporting
Re: [PROPOSAL] Apache RAT
On Oct 23, 2007, at 3:59 PM, Robert Burrell Donkin wrote: http://wiki.apache.org/incubator/RatProposal has been stable for a while now so i'd like to throw it open to final scrutiny before i call for a VOTE. (please don't vote yet ;-) the name RAT has been discussed previously - see http://mail-archives.apache.org/mod_mbox/incubator-general/ 200710.mbox/% [EMAIL PROTECTED] RAT is a good name and popular but i'm still a little concerned that there are existing open source projects named RAT as well as commercial software containing RAT in their name. Apache aRAT has the advantage of being unused but the disadvantage of being a common name in some other languages. if anyone strongly disagrees with the consensus that RAT is ok and prefers aRAT please jump in now. Looks good to me. As a RAT user, I look forward to improved RAT capabilities. There's the other side of the coin which I think communities need help with -- and that's tools to help simplify the building of legally compliant distributions. There's been some work with the maven-remote- resources-plugin, but that's fodder for another conversation... I like the name RAT. Can anybody give me guidance on how unique names need to be? For instance there's currently a vote to accept 'Apache Composer'. A simple search on 'composer open source' turns up a number of open source projects with 'composer' in their name (Violet Composer, Mozilla Composer, Eclipse EPF Composer). Should I have been more diligent in reviewing the Composer proposal? By comparison, RAT looks more unique... --kevan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
Hey, On 10/25/07, Kevan Miller [EMAIL PROTECTED] wrote: Can anybody give me guidance on how unique names need to be? For My take on it (IANAL) is that uniqueness doesn't matter. In fact, that's why there's already N1 projects named Composer as you noted in your example. Project name uniqueness should not be a criterion for Incubator acceptance. I would even go further and say clear copyright infringement is probably the only reason to ask for a name change. Otherwise, let the project's PMC decide. Sometimes it's useful to let the PMC know there are other names, and they might consider uniqueness as a marketing tactic or a differentiator. But that's just advice, not a reason to vote -1. Anyhow, that's my personal take on it. I like to be permissive in these sort of artistic expression issues. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [PROPOSAL] Apache RAT
RAT is a good name and popular but i'm still a little concerned that there are existing open source projects named RAT as well as commercial software containing RAT in their name. aRATicate, known as RAT for short? ;-) --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
RATify? Or rat as in the verb - to rat on something ;-) On 25/10/2007, Noel J. Bergman [EMAIL PROTECTED] wrote: RAT is a good name and popular but i'm still a little concerned that there are existing open source projects named RAT as well as commercial software containing RAT in their name. aRATicate, known as RAT for short? ;-) --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
On 10/25/07, sebb [EMAIL PROTECTED] wrote: RATify? that sounds cool(er) ;) Or rat as in the verb - to rat on something ;-) On 25/10/2007, Noel J. Bergman [EMAIL PROTECTED] wrote: RAT is a good name and popular but i'm still a little concerned that there are existing open source projects named RAT as well as commercial software containing RAT in their name. aRATicate, known as RAT for short? ;-) --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [PROPOSAL] Apache RAT
Yoav Shapira wrote: Project name uniqueness should not be a criterion for Incubator acceptance. I would even go further and say clear copyright infringement is probably the only reason to ask for a name change. You mean trademark? :-) --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
RATify ratifies Artifacts? :) cool! -- dims On 10/25/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: On 10/25/07, sebb [EMAIL PROTECTED] wrote: RATify? that sounds cool(er) ;) Or rat as in the verb - to rat on something ;-) On 25/10/2007, Noel J. Bergman [EMAIL PROTECTED] wrote: RAT is a good name and popular but i'm still a little concerned that there are existing open source projects named RAT as well as commercial software containing RAT in their name. aRATicate, known as RAT for short? ;-) --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
Personally, I prefer RAT over RATify regardless of the capitalization. Let's leave something to the imagination... But in the end, I'll defer to the authors. Craig On Oct 25, 2007, at 9:39 AM, Davanum Srinivas wrote: RATify ratifies Artifacts? :) cool! -- dims On 10/25/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: On 10/25/07, sebb [EMAIL PROTECTED] wrote: RATify? that sounds cool(er) ;) Or rat as in the verb - to rat on something ;-) On 25/10/2007, Noel J. Bergman [EMAIL PROTECTED] wrote: RAT is a good name and popular but i'm still a little concerned that there are existing open source projects named RAT as well as commercial software containing RAT in their name. aRATicate, known as RAT for short? ;-) --- Noel --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Re: [PROPOSAL] Apache RAT
On 10/25/07, Craig L Russell [EMAIL PROTECTED] wrote: Personally, I prefer RAT over RATify regardless of the capitalization. Let's leave something to the imagination... Same here, Apache RAT sounds good to me. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
Noel J. Bergman wrote: Yoav Shapira wrote: Project name uniqueness should not be a criterion for Incubator acceptance. I would even go further and say clear copyright infringement is probably the only reason to ask for a name change. You mean trademark? :-) Noel , I cam imagine why did you ask this question :) -Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
Hi, On 10/25/07, Noel J. Bergman [EMAIL PROTECTED] wrote: Yoav Shapira wrote: Project name uniqueness should not be a criterion for Incubator acceptance. I would even go further and say clear copyright infringement is probably the only reason to ask for a name change. You mean trademark? :-) Yes. My mistake, sorry for the confusion, if any ;) Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
On Oct 23, 2007, at 4:52 PM, Robert Burrell Donkin wrote: On 10/23/07, Robert Burrell Donkin [EMAIL PROTECTED] wrote: Mentors -- * Yoav Shapira yoavs AT guess ;) * Ross Gardler rgardler AT apache.org I would prefer mentors who have not been involved with RAT. This will allow a more objective perspective. I doubt that supervision will be too great a burden. RAT would benefit from another mentor if there's anyone willing to volunteer I volunteer :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
I like plain rat, and since rat is common word I doubt we have to worry about trademark violations. I also don't confuse it with any other projects in the java space.. so I think it's ok. On 10/23/07, Robert Burrell Donkin [EMAIL PROTECTED] wrote: http://wiki.apache.org/incubator/RatProposal has been stable for a while now so i'd like to throw it open to final scrutiny before i call for a VOTE. (please don't vote yet ;-) the name RAT has been discussed previously - see http://mail-archives.apache.org/mod_mbox/incubator-general/200710.mbox/[EMAIL PROTECTED] RAT is a good name and popular but i'm still a little concerned that there are existing open source projects named RAT as well as commercial software containing RAT in their name. Apache aRAT has the advantage of being unused but the disadvantage of being a common name in some other languages. if anyone strongly disagrees with the consensus that RAT is ok and prefers aRAT please jump in now. - robert Rat Proposal == Abstract -- RAT is comprehension and auditing for distributions and source code. Proposal --- RAT will provide a focus for components, applications and integration tools for the comprehension and audit of distributions and source code. It will collect data and meta-data as required. It will create suitable schemas for this data and meta-data as required. Background -- RAT began as an attempt to automate the technical part of reviewing releases in the incubator. Following requests for access from release managers, RAT was developed as an open source project under the Apache License 2.0. Rationale --- Reviewing releases for compliance with Apache technical criteria and policies is time consuming. The Incubator requires that all releases are reviewed. Though small mistakes are common, this process typically adds only a little value. It is common for candidates to be presented with small but significant defects which then must be fixed and the candidate represented. Significant energy and good will is wasted by this process. This is unnecessary. Given effort, these technical criteria are capable of automation. Automated continuous checking of the source would allow the Incubator PMC to be alerted promptly to potential issues. Integration with build tools (such as Apache Ant and Apache Maven) would allow releases to be checked automatically and continuously. Initial Goals - * Read standard license meta-data for documents without license headers * Improved RAT reporting * RAT source reporting for major build tools * Continuous RAT * RAT analytics: using meta-data to verify rules o Apache third party documents policy analysis o license compatibility analysis * Discordia integration to allow distributed binaries to be recognised * RAT analytic integration for major build tools * Improved recursive RAT scripts for better analysis of release with many distributables Current Status Meritocracy -- I'm very happy to move from a solo development model towards a collective one as more active developers are recruited. Community - The RAT community needs to be developed. Having RAT here at Apache will hopefully encourage release managers to take a more active role in developing RAT. Core Developers It has been developed principally by myself but with significant contributions of small amounts of code from other Apache members and committers. Alignment RAT has found itself becoming a standard part of the Apache release infrastructure. The Incubator needs fully featured release tools. It makes sense to bring the project here. Known Risks == Orphaned Projects -- This is a project with a set of definite goals aimed at serving the wider Apache community. There may well come a time when the coding is actually finished. It has a small set of developers who all have many other calls on their time. The target user audience is relatively small. So, this risk is real. I think that it's clear that something similar to RAT is required. So, unless another better product is developed, time will be found to push RAT forward. Even if one day, RAT is orphaned then it will have done it's job. Inexperience With Open Source - The contributors are Apache members or experienced Apache committers. Reliance On Salaried Developers --- I know of no one who's paid to work on RAT. Relationships with Other Apache Products -- RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting plugin. Analytic plugins for Ant and Maven will be developed. There are overlaps with Tika and there has been some talk of collaboration. The discordia lab will likely be
Re: [PROPOSAL] Apache RAT
On Wednesday 24 October 2007 03:59, Robert Burrell Donkin wrote: before i call for a VOTE. I think you can go ahead with RAT. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PROPOSAL] Apache RAT
http://wiki.apache.org/incubator/RatProposal has been stable for a while now so i'd like to throw it open to final scrutiny before i call for a VOTE. (please don't vote yet ;-) the name RAT has been discussed previously - see http://mail-archives.apache.org/mod_mbox/incubator-general/200710.mbox/[EMAIL PROTECTED] RAT is a good name and popular but i'm still a little concerned that there are existing open source projects named RAT as well as commercial software containing RAT in their name. Apache aRAT has the advantage of being unused but the disadvantage of being a common name in some other languages. if anyone strongly disagrees with the consensus that RAT is ok and prefers aRAT please jump in now. - robert Rat Proposal == Abstract -- RAT is comprehension and auditing for distributions and source code. Proposal --- RAT will provide a focus for components, applications and integration tools for the comprehension and audit of distributions and source code. It will collect data and meta-data as required. It will create suitable schemas for this data and meta-data as required. Background -- RAT began as an attempt to automate the technical part of reviewing releases in the incubator. Following requests for access from release managers, RAT was developed as an open source project under the Apache License 2.0. Rationale --- Reviewing releases for compliance with Apache technical criteria and policies is time consuming. The Incubator requires that all releases are reviewed. Though small mistakes are common, this process typically adds only a little value. It is common for candidates to be presented with small but significant defects which then must be fixed and the candidate represented. Significant energy and good will is wasted by this process. This is unnecessary. Given effort, these technical criteria are capable of automation. Automated continuous checking of the source would allow the Incubator PMC to be alerted promptly to potential issues. Integration with build tools (such as Apache Ant and Apache Maven) would allow releases to be checked automatically and continuously. Initial Goals - * Read standard license meta-data for documents without license headers * Improved RAT reporting * RAT source reporting for major build tools * Continuous RAT * RAT analytics: using meta-data to verify rules o Apache third party documents policy analysis o license compatibility analysis * Discordia integration to allow distributed binaries to be recognised * RAT analytic integration for major build tools * Improved recursive RAT scripts for better analysis of release with many distributables Current Status Meritocracy -- I'm very happy to move from a solo development model towards a collective one as more active developers are recruited. Community - The RAT community needs to be developed. Having RAT here at Apache will hopefully encourage release managers to take a more active role in developing RAT. Core Developers It has been developed principally by myself but with significant contributions of small amounts of code from other Apache members and committers. Alignment RAT has found itself becoming a standard part of the Apache release infrastructure. The Incubator needs fully featured release tools. It makes sense to bring the project here. Known Risks == Orphaned Projects -- This is a project with a set of definite goals aimed at serving the wider Apache community. There may well come a time when the coding is actually finished. It has a small set of developers who all have many other calls on their time. The target user audience is relatively small. So, this risk is real. I think that it's clear that something similar to RAT is required. So, unless another better product is developed, time will be found to push RAT forward. Even if one day, RAT is orphaned then it will have done it's job. Inexperience With Open Source - The contributors are Apache members or experienced Apache committers. Reliance On Salaried Developers --- I know of no one who's paid to work on RAT. Relationships with Other Apache Products -- RAT contains an Ant reporting plugin. Codehaus hosts a Maven reporting plugin. Analytic plugins for Ant and Maven will be developed. There are overlaps with Tika and there has been some talk of collaboration. The discordia lab will likely be used for license and artifact meta-data. RAT may integrate with Gump for continuous code scanning. Initial Source --- * [WWW] http://code.google.com/p/arat/source * [WWW] http://mojo.codehaus.org/rat-maven-plugin External Dependencies Compliant with current Apache policy. Cryptography
Re: [PROPOSAL] Apache RAT
On 10/23/07, Robert Burrell Donkin [EMAIL PROTECTED] wrote: http://wiki.apache.org/incubator/RatProposal has been stable for a while now so i'd like to throw it open to final scrutiny before i call for a VOTE. (please don't vote yet ;-) Looks like a solid proposal to me! As far as the name is concerned, I still like RAT the most. You could opt for 'ratifier'. A google search didn't come up with commercial products or open source projects. Martijn -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
On 10/23/07, Robert Burrell Donkin [EMAIL PROTECTED] wrote: Mentors -- * Yoav Shapira yoavs AT guess ;) * Ross Gardler rgardler AT apache.org I would prefer mentors who have not been involved with RAT. This will allow a more objective perspective. I doubt that supervision will be too great a burden. RAT would benefit from another mentor if there's anyone willing to volunteer - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Apache RAT
I'll volunteer...having done lot's of releases for Geronimo I have an affinity for the little beast. On Oct 23, 2007, at 4:52 PM, Robert Burrell Donkin wrote: On 10/23/07, Robert Burrell Donkin [EMAIL PROTECTED] wrote: Mentors -- * Yoav Shapira yoavs AT guess ;) * Ross Gardler rgardler AT apache.org I would prefer mentors who have not been involved with RAT. This will allow a more objective perspective. I doubt that supervision will be too great a burden. RAT would benefit from another mentor if there's anyone willing to volunteer - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
