-
Notifications
You must be signed in to change notification settings - Fork 1
RFF1 — Introduction to Requests For Features
Request For Feature: 1
This is an introductive issue defining the basic goal of the present file and some useful guidelines.
This document is a chronologicaly ordered list of features ideas. It could have been named "TODO list", but giving the same name to every file is too boring so we chose another name. We believe this is a good name, but if you don't like it, it is up to you to append a new Request For Feature (a.k.a. RFF) about it to that file.
You SHOULD try and use about the same typological style for each issue. E.g. start with an explicit title, then note your RFF id (please have it increase by step of exactly 1…). Write down a little abstract of your feature content and its type in a section named "Status of this issue". Developp, conclude and finally sign and date your request.
For each undefined situation, you MUST refere to your common sense.
Note that RFFs can be modified, although it MUST be done though the common git workflow so that a trace of each modification is kept. Actually they MUST be modified if the implementation definitely diverges from it.
Élie Michel, 07.19.2014