Wiki/Feats

Minor rewrite to improve the flow by minimizing repetitive wording.
This commit is contained in:
Bracconiere 2015-04-18 07:21:16 +03:00
parent 6c3ca2c347
commit cfb6d9eeea

View File

@ -6,19 +6,17 @@ order: 11
parent: wiki
---
### Before requesting
### Background
ACE2, AGM and CSE had a lot of features implemented or planned. All of them are or have been evaluated for inclusion in ACE3 itself, and we'd like to port the majority of them eventually. However, due to time constraints, we have managed to finish only a fraction of the job so far.
ACE 2, AGM and CSE had a lot of features implemented or planned. All of them are or have been evaluated for inclusion in ACE3 itself, and we'd like to port the majority of them eventually. However, due to time constraints, we have only managed to do a fraction of the job so far.
There's really no point on making feature requests for anything included or planned for inclusion in ACE2, AGM or CSE. The majority of those things are been considered for porting or rewritting already.
Please refrain from making requests for any planned or existing features from either ACE2, AGM or CSE. Most of them are already being or have been considered for porting or a rewrite.
<div class="panel callout">
<h5>Please note:</h5>
<p>Due to the pace at which development is taking place, we are establishing a feature request embargo during the first week weeks prior and posterior to the first release. Feel free to add feature requests as described below, but don't expect them to be evaluated or discussed yet. Any dev activity on the feature request thread is highly unlikely during that period.</p>
<h5>Note:</h5>
<p>Due to our current work load, in the period of weeks prior and posterior to the first release, new feature requests are under embargo. Feel free to submit yours now, but don't expect them to be considered just yet. Any treatment or attention by developers towards the feature request thread is highly unlikely during this time.</p>
</div>
### Requesting a feature
In order to avoid duplicates and keep the issue tracker organized, we have created a common <a href="{{ site.githubUrl }}/issues/414/" target="_blank">Issue for feature request</a>. Any and all relevant requests should be submitted there, where they will also get discussed and evaluated. Before adding a new one, make sure to check the previous entries from the thread and do a quick search for similar suggestions; please don't reiterate requests for features that had already been accepted for inclusion, or those which were disregarded earlier.
In order not to spam the issue tracker with duplicated requests, we have have created a single <a href="{{ site.githubUrl }}/issues/414/" target="_blank">Issue for feature request</a>. Any and all requests should be done there, where they will get discussed and evaluated. Before posting a new one, please make sure to check the previous entries on the thread and make a quick search; please don't reiterate requests that had already been either accepted for inclusion or disregarded.
Accepted feature requests may be moved to a separate issue by moderators for further discussion.
Following their approval, feature requests may be moved by moderators to a separate issue for further discussion.