Guidelines for feature requests and proposals
We would like to encourage you to follow the procedure below for contributing to SED-ML development.
Feature requests are “wishes for support” by (potential) SED-ML users. They are submitted and tracked using the SourceForge feature request tracker. The editors will revise these wishes at their regular meetings and start discussion on them on sed-ml-discuss if necessary. Solutions to feature requests can be provided (independently of a feature request) by starting a new proposal item on SF.
Proposals are welcome at all times via the sourceforge proposals tracker. Proposals could be derived from a sed-ml-discuss discussion field (for example, in response to a feature request), or created de novo.
- Together with your proposal you must provide a sufficiently detailed description of your desired feature, including XML examples, i.e. SED-ML files, containing the proposed new elements in Annotation elements. Final element and attribute names may be decided on later (maybe even hierarchy).
- The editors then collect vote on whether the
outlined proposal goes in to the right direction and
should become part of SED-ML.
- The proposal will be voted on by sedml-discuss members,
- requiring a majority in favour to be accepted. The vote includes yes-no-revise options.
- There will be no minimum requirement for the the number of votes needed.
- The voting process will take place over a 3 week period.
- Proposals that are rejected will not be rejected for all time, but would need to address the reasons for their rejection before resubmission. Resubmission therefore requires revision of the proposal.
- Accepted proposals will be integrated with the
specification document by the SED-ML editors with the next release.
- at least two implementations in applications ( to demonstrate interoperability)
- updated examples
- a written description of the proposal
- an XML schema for the proposed extension
- UML diagrams illustrating any new class