Re: [Qgis-user] Re: [Qgis-developer] Using Request for changes (RFC) in QGIS project
Howdy, I would like to take a slightly different view on this. Wikis, to me, are not discussion boards but a good mechanism to hammer out documentation. E-mail is much better for discussion, as it can be viewed more readily than a wiki that wants to be updated frequently to see if something's been added. I've gotten to this position based on hard experience with another project. I totally concur with keeping an RFC template on the wiki, and in updating said RFC with concise comments, evolving to a final document. I'd prefer to see RFC discussion on either both users and developers lists, or on a new list dedicated to RFC discussion that folks can subscribe to if they want. gerry Tim Sutton wrote: Hi It would be good to make an rfc template on the wiki and store all the rfcs on the wiki - then keep all the commentry on the wiki. IMHO email is not a good medium if you want to go back and look at the discussion surrounding an RFC. By all means of course we should advertise the rfcs on the mailing lists etc. Regards Tim 2007/6/5, Paolo Cavallini [EMAIL PROTECTED]: +1 pc Marco Hugentobler ha scritto: Dear QGIS community members, In the last PSC meeting we agreed that QGIS needs a more formalized development model. One idea was to use Requests for changes (RFC), similar to the what UMN mapserver does (http://mapserver.gis.umn.edu/development/rfc). If you are also in favour of RFCs, we need to agree on how the procedure should be for the QGIS project. To start the discussion, I wrote down some initial ideas (see below). Please comment them and bring your own ideas. After the discussion, I'm going to make a document that describes the RFC procedure for QGIS on the Wiki. -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 developer and user mailing lists and community members vote about it. -It is necessary in the following cases: Change that breaks API compatibility, merge of a branch, change in development model -Procedure: Author publishes RFC on qgis-developer and qgis-user lists Community votes in the next 5 working days with -1, 0, +1 Finished RFCs are stored and are available on the website, together with the voting result Regards, Marco -- Paolo Cavallini http://www.faunalia.it/pc ___ Qgis-user mailing list Qgis-user@lists.qgis.org http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-user -- Gerry Creager -- [EMAIL PROTECTED] Texas Mesonet -- AATLT, Texas AM University Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.862.3983 Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843 ___ Qgis-user mailing list Qgis-user@lists.qgis.org http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-user
Re: [Qgis-user] Re: [Qgis-developer] Using Request for changes (RFC) in QGIS project
I updated the RFC page on the wiki (http://wiki.qgis.org/qgiswiki/RequestForComment) with: FAQ section in the template (proposed by Martin) A section about changes to existing RFCs (based on the comments of Martin and Tim). cheers, Marco -- Dr. Marco Hugentobler Institute of Cartography ETH Zurich Technical Advisor QGIS Project Steering Committee [EMAIL PROTECTED] ___ Qgis-user mailing list Qgis-user@lists.qgis.org http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-user
Re: [Qgis-user] Re: [Qgis-developer] Using Request for changes (RFC) in QGIS project
Hi I like the template, five working days seem OK to me. Author of the RFC should also add a FAQ section and fill it with questions and answers based on the discussion on the mailing list. In case that RFC is changed based on the discussions, the voting should get another five days. I like it too! Also what about the cases when later the dev finds out that he needs to do things differently? Change the RFC and start voting again? Or create a new RFC ...? I think he should defer to our technical lead (Marco) to see if the adjustments merrit a new RFC. BTW. That new template on wiki looks cool :-) Glad you like it. Im also trying to get the front page a little more organised along the lines of the PSC roles. Tim Bye Martin ___ Qgis-user mailing list Qgis-user@lists.qgis.org http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-user -- -- Tim Sutton Visit http://qgis.org for a great Open Source GIS Home Page: http://linfiniti.com Skype: timlinux MSN: [EMAIL PROTECTED] Yahoo: [EMAIL PROTECTED] Jabber: timlinux Irc: timlinux on #qgis at freenode.net ___ Qgis-user mailing list Qgis-user@lists.qgis.org http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-user
Re: [Qgis-user] Re: [Qgis-developer] Using Request for changes (RFC) in QGIS project
On 6/8/07, Marco Hugentobler [EMAIL PROTECTED] wrote: You mean that people directly insert their votes into the wiki page? I made a RFC wiki page (http://wiki.qgis.org/qgiswiki/RequestForComment) and a template that can be copied. Individual votings would then be separated with === vote === at the bottom of the RFC. Links to the RFC instances would be inserted below 'Existing RFCs' on the RFC wiki page. @all can you agree with this? Please have a look at the wiki page and write your opinion. Are five working days enough as a voting period or should it be longer? I like the template, five working days seem OK to me. Author of the RFC should also add a FAQ section and fill it with questions and answers based on the discussion on the mailing list. In case that RFC is changed based on the discussions, the voting should get another five days. Also what about the cases when later the dev finds out that he needs to do things differently? Change the RFC and start voting again? Or create a new RFC ...? BTW. That new template on wiki looks cool :-) Bye Martin ___ Qgis-user mailing list Qgis-user@lists.qgis.org http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-user
[Qgis-user] Re: [Qgis-developer] Using Request for changes (RFC) in QGIS project
+1 pc Marco Hugentobler ha scritto: Dear QGIS community members, In the last PSC meeting we agreed that QGIS needs a more formalized development model. One idea was to use Requests for changes (RFC), similar to the what UMN mapserver does (http://mapserver.gis.umn.edu/development/rfc). If you are also in favour of RFCs, we need to agree on how the procedure should be for the QGIS project. To start the discussion, I wrote down some initial ideas (see below). Please comment them and bring your own ideas. After the discussion, I'm going to make a document that describes the RFC procedure for QGIS on the Wiki. -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 developer and user mailing lists and community members vote about it. -It is necessary in the following cases: Change that breaks API compatibility, merge of a branch, change in development model -Procedure: Author publishes RFC on qgis-developer and qgis-user lists Community votes in the next 5 working days with -1, 0, +1 Finished RFCs are stored and are available on the website, together with the voting result Regards, Marco -- Paolo Cavallini http://www.faunalia.it/pc signature.asc Description: OpenPGP digital signature ___ Qgis-user mailing list Qgis-user@lists.qgis.org http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-user
Re: [Qgis-user] Re: [Qgis-developer] Using Request for changes (RFC) in QGIS project
Hi It would be good to make an rfc template on the wiki and store all the rfcs on the wiki - then keep all the commentry on the wiki. IMHO email is not a good medium if you want to go back and look at the discussion surrounding an RFC. By all means of course we should advertise the rfcs on the mailing lists etc. Regards Tim 2007/6/5, Paolo Cavallini [EMAIL PROTECTED]: +1 pc Marco Hugentobler ha scritto: Dear QGIS community members, In the last PSC meeting we agreed that QGIS needs a more formalized development model. One idea was to use Requests for changes (RFC), similar to the what UMN mapserver does (http://mapserver.gis.umn.edu/development/rfc). If you are also in favour of RFCs, we need to agree on how the procedure should be for the QGIS project. To start the discussion, I wrote down some initial ideas (see below). Please comment them and bring your own ideas. After the discussion, I'm going to make a document that describes the RFC procedure for QGIS on the Wiki. -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 developer and user mailing lists and community members vote about it. -It is necessary in the following cases: Change that breaks API compatibility, merge of a branch, change in development model -Procedure: Author publishes RFC on qgis-developer and qgis-user lists Community votes in the next 5 working days with -1, 0, +1 Finished RFCs are stored and are available on the website, together with the voting result Regards, Marco -- Paolo Cavallini http://www.faunalia.it/pc ___ Qgis-user mailing list Qgis-user@lists.qgis.org http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-user -- -- Tim Sutton Visit http://qgis.org for a great Open Source GIS Home Page: http://linfiniti.com Skype: timlinux MSN: [EMAIL PROTECTED] Yahoo: [EMAIL PROTECTED] Jabber: timlinux Irc: timlinux on #qgis at freenode.net ___ Qgis-user mailing list Qgis-user@lists.qgis.org http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-user
