Feature Request writing Guidelines

Principles

• One feature request per ticket
• Write short and precise requirements such as "deegree shall support the brand new spec YX".
• Provide as much information as possible as every detail is essential to a good feature request.
• Earn Votes and Support by involving the community and invite everybody to discuss your feature and to vote for it (votes are +1 , 0 or -1) by sending a message to the deegree-users mailing list. Read the DeegreeVotingProcess.

Requesting a new feature

Enter an issue and fill the following fields:

• Title: Enter a clear and meaningful titel for your feature request
• Description: Please give at least some information about:
• Need
• Briefly explain, use 2-3 sentences, why the new feature is important or necessary.
• Value
• Explain what will be the value of this feature for other deegree users.
• Funding
• Tell the community if you have money to fund this feature request or not. If you plan to implement the feature yourself this is a kind of funding as well.
• Milestone: leave this field empty. The milestone will be set by the TMC members.

Process and lifecycle of an issue

• After submitting your feature request the ticket will have state NEW. In this state the TMC will read the request and decide if this fits into deegree webservices or not.
• As soon as the TMC has accepted this feature it will change to state ACCEPTED.
• After the funding is clarified and a developer is available the TMC will assign the ticket to someone. The state will change to ASSIGNED.
• The assigned developer reviews the issue and sets a fix version. When the work is finished and the pull request is accepted by the TMC the developer will resolves it with the appropriate resolution and set the state to CLOSED.