|eclipse test & performance tools platform project
Contributing to the Project
This project proposal is in the Proposal Phase and is posted here to solicit additional project participation and ways the project can be leveraged from the Eclipse membership-at-large. You are invited to comment on and/or join the project. Please send all feedback to the eclipse.test-and-performance newsgroup or the test-and-performance-proposal mailing list.
This document was inspired by the Contributing to the CDT document.
People often ask, "What does it take to get involved with the development of the Test & Performance Project?" There are many ways to get involved. On the lightweight end of scale, there is involvement by using the Hyades Platform and providing feedback and sharing your experiences on the Eclipse and Test & Performance Project newsgroups. Beyond that, you can report problems that you discover, so that they may be addressed in future releases. A deeper level of involvement would be to actually solve some of the problems that you or others have uncovered by modifying/writing the necessary code and creating patches that can applied by the project committers. The final, and most beneficial way to get involved, is to take responsibility for a significant piece of development work, whether it's enhancing a particular area of the tool or creating new functionality.
The purpose of this document is to help people and organizations understand what it means to "commit" to the Test & Performance Project development at this highest level. Basically, it involves a commitment to describe, develop, test and document your contributions.
|Commitment to Development|
Communicating Your Desires/Intentions
Bugzilla is the open source change management system used by Eclipse projects. To set these Bugzilla entries apart from other problem reports, the word "plan" should be used in the keywords field, and the severity of the entry should be set to "enhancement". Following these guidelines will ensure that all of these proposals get picked up by the appropriate query and recorded in the plan for the upcoming release.
Feature specifications (what your code will do) and design specifications (how it will do it) are an important aspect of the development effort. These specifications will allow the Test & Performance Project community and the rest of the development team to understand what you are doing and to provide feedback. The format of these documents is not important, the content is.
Becoming a Committer
Delivering the Code
Commitment To Testing
So, committing to contribute significant code to the Test & Performance Project also means committing to participate in the test-fix cycles by executing your test plans against the release candidates build leading up to the final release build.
Commitment to Documentation
Until a Documentation Style Guide is available for the Test & Performance Project, you may refer to the CDT Documentation Style Guide to help maintain a constant look and feel for documentation originating from different contributors. There also a couple of links that take you to additional information on how to contribute help content for Eclipse projects.
So, finally, committing to contribute code to the Test & Performance Project also means committing to contributing the associated on-line documentation content for the part of the tool that is being enhanced or created.