Staging Apache Rat 0.9
Unless anyone jumps in sometime soon with an issue with the latest[1] snapshot[2], following the guidelines[3] I hope to cut a 0.9 and upload it to the staging repository. Once this is done I'll ask the community to review the release and vote. Everyone is encouraged to vote. Before the uploaded artefact can be blessed as a official Apache Software Foundation (ASF) release, at least three binding +1 votes and more +1 votes than -1 votes are needed (see [4] and [5] for more information). Votes from PMCers are bind the ASF. (PMCers often add 'binding' to help tally the vote. Sometimes people add 'non-binding'. Both are optional :-) For more information on the way Apache project conduct themselves, browse [6] Robert [1] 0.9-20130323.083323 [2] https://repository.apache.org/content/repositories/snapshots/org/apache/rat/ [3] http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven [4] http://www.apache.org/foundation/glossary.html#MajorityApproval [5] www.apache.org/dev/release.html#distribute-raw-artifact [6] http://community.apache.org/committers/index.html
GSoc2013 Ideas
With a little bit of luck, I hope to have enough typing time (outside work) and stability this summer to think about mentoring GSoc. If I submit some project ideas later today then we may not be too late. Ideas: * Refactor Apache Rat Core [1] * License Lexicon [2] * More Tentacles [3] * Port Rat [4] Opinions? Objections? Improvements? If anyone else wants to dive in with new ideas, that would be very much appreciated - or just dive in and create them in JIRA. For more information see: http://www.google-melange.com/gsoc/homepage/google/gsoc2013 http://community.apache.org/guide-to-being-a-mentor.html http://s.apache.org/gsoc2013ideas http://community.apache.org/gsoc.html Apologies for picking this up so late :-/ Robert [1] Refactor Apache Rat Core The base code for Apache Rat has issues which lead to a high bar for contribution: * based on an experimental streaming architecture * hard to understand * poorly covered by edge-to-edge tests For a student interested in agile test-first approaches and object oriented design, driving a new core with a conventional OOP design would be an interesting introduction to open source and would reduce the barriers to contribution. [2] License Lexicon Both Rat and Whiskers lack a comprehensive library and consistent terminology for licenses. This project would both compile a set of meta-data, plus support libraries which could be reused both by these projects and more widely. Collate comprehensive license meta-data, beginning with all OSI approved open source licenses and working outwards to include other common binary only licenses including: * descriptions of common source boilerplates * generation and recognition templates * consistent language, both machine and human readable This is most suitable for students whose interests focus more in semantics than coding. For students interested in text parsing, this data could be used to create fast parsers. For students interested in technology law, the semantics could be extend to include relationships between licenses. For students more interested in informatics, there would be an opportunity to work on a comprehensive collection. For all students, an opportunity to showcase communication skills. [3] More Tentacles Many open source projects at Apache face the problem that one release contains many libraries. Reviewing all these libraries without automated assistance takes time and is error prone. Tentacles builds on Rat to provide this assistance. This project will be organised in an agile fashion around a number of short sprints with direction determined by users in the Apache Incubator and elsewhere. This is most suitable for a students who is interested in the wider process of developing software well fitting to the needs of users using an Agile process. Focus is essential for an open ended project like this, and adopting an Agile approach is well suited to ensuring success. [4] Port Rat Today, Apache Rat supports only Java. Ports to other other languages and build systems would help increase adoption beyond the Java community here at Apache. * New languages eg Python, Ruby, JavaScript, CoffeeScript * New build systems eg buildr For a student interested in using a variety of languages, perhaps one language or build system per week.
[jira] [Created] (RAT-130) GSOC Port Apache Rat to New Languages, Integrate With New Build Systems
Robert Burrell Donkin created RAT-130: - Summary: GSOC Port Apache Rat to New Languages, Integrate With New Build Systems Key: RAT-130 URL: https://issues.apache.org/jira/browse/RAT-130 Project: Apache Rat Issue Type: Wish Reporter: Robert Burrell Donkin Apache Rat helps projects audit and comprehend the licenses qualities of the software they ship. Today, Apache Rat is coded in Java and integrates with Apache Maven and Apache Ant (as well as the command line). Ports to other other languages and build systems would help increase adoption. This would be an ideal project for a student interested in using a variety of languages (for example Ruby, Python, JavaScript and CoffeeScript) perhaps porting to a new language or build system each week.The exact scope of schedule would be negotiable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (RAT-131) GSOC Refactor Apache Rat Core to a Classic Object Oriented Design
Robert Burrell Donkin created RAT-131: - Summary: GSOC Refactor Apache Rat Core to a Classic Object Oriented Design Key: RAT-131 URL: https://issues.apache.org/jira/browse/RAT-131 Project: Apache Rat Issue Type: Wish Reporter: Robert Burrell Donkin The core code for Apache Rat has difficulties which lead to a high bar for contributions: * based on an experimental streaming architecture * hard to understand * poorly covered by edge-to-edge tests Replace this by a conventional object-oriented design with clear model based on the domain. A good opportunity for a student interested in Agile, test-first approaches and domain-driven design with a good sense of object-oriented design to showcase their skills and learn about open source development. The emphasis would be on high quality, test-driven code driving a clear, well documented design, -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (RAT-132) GSOC License Lexicon
Robert Burrell Donkin created RAT-132: - Summary: GSOC License Lexicon Key: RAT-132 URL: https://issues.apache.org/jira/browse/RAT-132 Project: Apache Rat Issue Type: Wish Reporter: Robert Burrell Donkin Apache Rat and Apache Whiskers are tools which help people to audit and comprehend licenses within releases. Both Rat and Whiskers lack both a comprehensive library and consistent terminology for licenses: a license lexicon. Though this ticket is raised under Rat, a successful GSOC would hopefully lead to the development of an independent product. This GSOC project would both compile a set of meta-data, plus perhaps support libraries which could be reused both by these projects and more widely. Collate comprehensive license meta-data, beginning with all OSI approved open source licenses and working outwards to include other common binary only licenses. This meta-data might include: * descriptions of common source boilerplates * generation and recognition templates * consistent language, both machine and human readable This is most suitable for students whose interests focus more in semantics than coding. The scope and direction are negotiable. For students interested in text parsing, this meta-data could be used to create fast parsers. For students interested in technology law, the semantics could be extend to include relationships between licenses. For students more interested in informatics, there would be an opportunity to work on a comprehensive collection. For all students, this is an opportunity to showcase communication skills. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
