Request for comment (RFC)
A QGIS Request for comment (RFC) describes a major change in technology, major additions to functionality, or changes in the direction of the project. It is published on the RFC wiki page (http://wiki.qgis.org/qgiswiki/RequestForComment) and announced on the developer and user mailing lists.
QGIS community members have the possibility to comment and vote on an RFC. Community members give comments and votes directly on the wiki page. Votes may be -1 (refusal), 0 (indifference), +1(acceptance).
A RFC is necessary in the following cases:
- Change that breaks API compatibility
- Merge of a branch
- Change in development model
If it turns out that the technical solution described in an accepted RFC is not feasible and needs to be changed, the developer contacts the technical advisor of the QGIS project steering committee to decide if a new RFC is needed or not.
The following template RfcTemplate shows the basic structure of an RFC, but it can be modified depending on the subject
The procedure of an RFC is the following:
- Author makes an RFC page in the wiki and announces RFC comment period on the developer and user mailing lists
- Community members have five working days to give comments (directly on the wiki page)
- Author states, how he plans to consider or not consider the comments
- Author announces voting on RFC on developer and user mailing lists
- Community members have five working days to give their votes on the wiki page (using -1, 0, +1)
- RFC is accepted or refused
Existing RFCs
RasterRefactorRfc (Still in draft stage)
DragAndDrop (Draft)