BTW, are there any points or guidelines on ranking projects? Is there anything I should consider improving?
I asked for comments for my proposal, sometime back and I saw Marnie commenting good on the proposal in google web app. Thanks, SD On Fri, Apr 11, 2008 at 11:14 AM, Sachith Dhanushka < [EMAIL PROTECTED]> wrote: > Oops sorry. Here is the project proposal. > > I am not sure how to get a link to this from google web app. > > Project > ======= > Qpid Java broker configuration > Motivation > ========== > I like to work with Java and XML technologies for sometime now I am having > fun with it. Even though I do not have any previous experience with open > source development, I like to contribute to open source and to the > communities around them. I hope my experience with the related technologies > together with myenthusiasm will produce something good for the open source > community. > Project Proposal > ================ > Apache Qpid is a multiple language implementation of Advanced Message > Queueing Protocol (AMQP). Qpid project has multiple configurations in > different files. This project is to refactor the existing Qpid Java Broker > configuration into a more elegant xml schema, with xsd, covering all > existing configuration options and allowing for extension. Additionally I > will also implement a module to validate broker configuration files, which > could be run standalone i.e. before starting a broker, to check that they're > well formed and validate against the xsd.* > Project Timeline > ================ > [April, 14: accepted students known] > Familiarize and getting myself into Qpid > - learning on AMQP > - using Qpid and understanding its functionality by running examples > - looking at the existing functionality with respect to my project > - working with the qpid community to better understand the > requirements > [May, 26 coding starts] > - start the refactoring process > - propose a schema and other related configurations to be implemented > - implement the proposal with testing code > [July, 7-14 mid term evaluation] > - include specific mentor feedback in to the implementation > - improve the existing code with more tests > - implement the validation module and more tests for that > - start working on documentation > - integration with the main project > [August, 11 suggested pencil 'down' date] > - final changes to implementation and documentation > - fixing integration issues, if any > [August, 18 final evaluations] > >
