Feature Requests

Process

• The feature proposal process flow is described at release process description
• We have a special 14-days rule which is good to be familiar with
• You do not have to have a committed developer to get a proposal discussed but it cannot be accepted and obviously not implemented either unless a developer steps in and commits to implement the proposal.

Submit new feature request

Please start a new topic for each feature request.

• Consider filing a Support question unless you are very sure that you cannot do what you want with the current feature set or with one of the many Plugins.
• Please scan over the existing feature requests to see if it has been requested already.
• NOTE: you might want to make yourself familiar with our Acceptance/Rejection Process of new features.
• If you are including code to implement features, thanks for contributing to TWiki's development! Please see the PatchGuidelines to make your patch easier to apply.

Currently open feature requests

The topic TWikiFeatureProposals gives a good overview over all feature requests raised since release 4.1 and is also used for release 5.0 and forward.

The topic OldWorkflowNote gives an overview of very old feature proposals. However if you want to revive one of the old ones you should refresh the form of the topic to get it re-entered in the new feature request flow.

Related topics:

• FeatureRequestTopicTemplate : Template topic for new feature requests
  • NOTE: Please don't edit this page unless you are a TWiki.org administrator!
  • To submit new feature request, use above form.

Related topics:

Process from TWiki 4.1 and forward

• NewFeatureProposals
• ProposalsReadyForReleaseMeeting
• AcceptedFeatureProposals
• CompletedFeatureProposals
• RejectedFeatureProposals
• ParkedFeatureProposals

Topics from old process

• FeatureEnhancementRequests
• FeatureToDo
• FeatureUnderConstruction
• FeatureDone
• FeatureNotSuitable