/
ms-rfc-23.txt
237 lines (188 loc) · 9.5 KB
/
ms-rfc-23.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
.. _rfc23:
====================================================================
MS RFC 23: Technical Steering Committee Guidelines
====================================================================
:Author: Frank Warmerdam, Steve Lime
:Contact: warmerdam at pobox.com, sdlime at dnr.state.mn.us
:Status: Adopted
:Last Updated: 2016-08-23
Summary
-----------
This document describes how the MapServer Project Steering Committee (PSC)
determines membership, and makes decisions on all aspects of the
MapServer project - both technical and non-technical.
Examples of PSC management responsibilities:
* setting the overall development road map
* developing technical standards and policies (e.g. coding standards,
file naming conventions, etc...)
* ensuring regular releases (major and maintenance) of MapServer software
* reviewing RFC for technical enhancements to the software
* project infrastructure (e.g. GitHub, CVS/SVN, Trac/Bugzilla, hosting options, etc...)
* formalization of affiliation with external entities such as OSGeo
* setting project priorities, especially with respect to project sponsorship
* creation and oversight of specialized sub-committees (e.g. project
infrastructure, training)
In brief the project team votes on proposals on the `mapserver-dev <https://lists.osgeo.org/listinfo/mapserver-dev>`_
mailing list. Proposals are available for review for at least two days, and a single
veto is sufficient delay progress though ultimately a majority of members can
pass a proposal.
List of PSC Members
-------------------
(up-to-date as of 2016-08)
* Steve Lime `@sdlime <https://github.com/sdlime>`_ (USA) **Chair**
* Thomas Bonfort `@tbonfort <https://github.com/tbonfort>`_ (FR)
* Howard Butler `@hobu <https://github.com/hobu>`_ (USA)
* Olivier Courtin `@ocourtin <https://github.com/ocourtin>`_ (FR)
* Jukka Rahkonen `@jratike80 <https://github.com/jratike80>`_ (FI)
* Tom Kralidis `@tomkralidis <https://github.com/tomkralidis>`_ (CA)
* Jeff McKenna `@jmckenna <https://github.com/jmckenna>`_ (CA)
* Stephan Meissl `@Schpidi <https://github.com/Schpidi>`_ (AT)
* Daniel Morissette `@dmorissette <https://github.com/dmorissette>`_ (CA)
* Perry Nacionales (USA)
* Mike Smith `@msmitherdc <https://github.com/msmitherdc>`_ (USA)
* Tamas Szekeres `@szekerest <https://github.com/szekerest>`_ (HU)
* Steve Woodbridge `@woodbri <https://github.com/woodbri>`_ (USA)
* Assefa Yewondwossen `@assefay <https://github.com/assefay>`_ (CA)
Detailed Process
-----------------------
* Proposals are written up and submitted on the mapserver-dev mailing list
for discussion and voting, by any interested party, not just
committee members.
* Proposals need to be available for review for at least two business
days before a final decision can be made.
* Respondents may vote "+1" to indicate support for the proposal and a
willingness to support implementation.
* Respondents may vote "-1" to veto a proposal, but must provide clear
reasoning and alternate approaches to resolving the problem within
the two days.
* A vote of -0 indicates mild disagreement, but has no effect. A 0
indicates no opinion. A +0 indicate mild support, but has no
effect.
* Anyone may comment on proposals on the list, but only members of the
Project Steering Committee's votes will be counted.
* A proposal will be accepted if it receives +2 (including the
author) and no vetoes (-1).
* If a proposal is vetoed, and it cannot be revised to satisfy all
parties, then it can be resubmitted for an override vote in which a
majority of all eligible voters indicating +1 is sufficient to pass it.
Note that this is a majority of all committee members, not just those who
actively vote.
* Upon completion of discussion and voting the author should announce
whether they are proceeding (proposal accepted) or are withdrawing
their proposal (vetoed).
* The Chair gets a vote.
* The Chair is responsible for keeping track of who is a member of the
Project Steering Committee (perhaps as part of a PSC file in CVS).
* Addition and removal of members from the committee, as well as selection
of a Chair should be handled as a proposal to the committee.
* The Chair adjudicates in cases of disputes about voting.
When is Vote Required?
-----------------------
* Any change to committee membership (new members, removing inactive members)
* Changes to project infrastructure (e.g. tool, location or substantive
configuration)
* Anything that could cause backward compatibility issues.
* Adding substantial amounts of new code.
* Changing inter-subsystem APIs, or objects.
* Issues of procedure.
* When releases should take place.
* Anything dealing with relationships with external entities such as OSGeo
* Anything that might be controversial.</li>
Observations
----------------
* The Chair is the ultimate adjudicator if things break down.
* The absolute majority rule can be used to override an obstructionist
veto, but it is intended that in normal circumstances vetoers need to be
convinced to withdraw their veto. We are trying to reach consensus.
* It is anticipated that separate "committees" will exist to manage
conferences, documentation and web sites. That said, it is expected
that the PSC will be the entity largely responsible for creating any
such committees.
Committee Membership
---------------------
The PSC is made up of individuals consisting of technical contributors
(e.g. developers) and prominent members of the MapServer user community.
There is no set number of members for the PSC although the initial desire
is to set the membership at 9.
Adding Members
..............
Any member of the mapserver-dev mailing list may nominate someone for
committee membership at any time. Only existing PSC committee members may
vote on new members. Nominees must receive a majority vote from existing
members to be added to the PSC.
Stepping Down
.............
If for any reason a PSC member is not able to fully participate then they
certainly are free to step down. If a member is not active (e.g. no
voting, no IRC or email participation) for a period of two months then
the committee reserves the right to seek nominations to fill that position.
Should that person become active again (hey, it happens) then they would
certainly be welcome, but would require a nomination.
Membership Responsibilities
-----------------------------
Guiding Development
...............................
Members should take an active role guiding the development of new features
they feel passionate about. Once a change request has been accepted
and given a green light to proceed does not mean the members are free of
their obligation. PSC members voting "+1" for a change request are
expected to stay engaged and ensure the change is implemented and
documented in a way that is most beneficial to users. Note that this
applies not only to change requests that affect code, but also those
that affect the web site, technical infrastructure, policies and standards.
IRC Meeting Attendance
...............................
PSC members are expected to participate in pre-scheduled IRC development
meetings. If known in advance that a member cannot attend a meeting,
the member should let the meeting organizer know via e-mail.
Mailing List Participation
...............................
PSC members are expected to be active on both the
`mapserver-users <https://lists.osgeo.org/listinfo/mapserver-users>`_
and `mapserver-dev <https://lists.osgeo.org/listinfo/mapserver-dev>`_
mailing lists, subject to Open Source mailing list
etiquette. Non-developer members of the PSC are not expected to respond
to coding level questions on the developer mailing list, however they
are expected to provide their thoughts and opinions on user level
requirements and compatibility issues when RFC discussions take place.
Bootstrapping
-----------------
Prior to the TSC anointing itself the PSC this RFC must be distributed before
the MapServer community via MapServer-Users for comment. Any and all
substantive comments must be discussed (and hopefully, but not necessarily,
addressed via MapServer-Dev.
All members of the existing Technical Steering Committee will form the initial
Project Steering Committee. Steve Lime is declared initial Chair of
the Project Steering Committee.
Initial members are:
* Steve Lime
* Daniel Morissette
* Frank Warmerdam
* Assefa Yewondwossen
* Howard Butler
* Steve Woodbridge
* Perry Nacionales
There are two open committee positions at the initial formation of the PSC.
Updates
---------
**29 May 2007**
The following members were were added to the PSC after discussion and consensus:
* Tom Kralidis
* Jeff McKenna
* Umberto Nicoletti
* Tamas Szekeres
**30 March 2009**
Thomas Bonfort was added to the PSC after discussion and consensus.
**19 August 2011**
Olivier Courtin was added to the PSC after RFC 70 was passed.
**21 September 2011**
Mike Smith was added to the PSC after a PSC vote.
**17 May 2013**
Stephan Meissl was added to the PSC after a PSC vote.
Frank Warmerdam retired from the PSC; members of the steering committee are grateful for
all of his contributions to help grow MapServer through the years.
**11 February 2015**
Umberto Nicoletti retired from the PSC. The members of the PSC thank him for all
his work over the past years.
**20 february 2015**
Jukka Rahkonen was added to the PSC after a PSC vote.