[Qgis-psc] Improving the functioning of PSC

[Marco Bernasocchi]

Thanks a lot Paolo for the updated version, looks interesting

looking forward to discuss it shortly in the PSC meeting as, as this 
thread proves, following decision making by email is terrible in my opinion.

Cheers

Marco

On 02.12.19 18:16, Paolo Cavallini wrote:
> Hi all,
> a third revision of the proposal based on previous replies.
> I call for a vote on this.
>
> Decision making
> =================
> * one PSC member raise on the PSC mailing list a topic to be decided
> * if the proponent believes the discussion in ML is sufficient, he calls
> for a vote
> * if not, he adds the point to the next PSC voice meeting, where it will
> be discussed and voted
> * once voted, he passes the decision to the Secretary, who adds the
> resolution to the list of resolutions (see below)
>
> Meetings
> =========
> * regular meeting once a month, at a fixed date
> * ad hoc short meetings are encouraged, and can be called anytime, to
> discuss single issues and to have faster decisions and avoid too long
> regular meetings; only a subset of the PSC members can be present at the
> ad hoc meetings, if they are not interested in that specific topic;
> their vote will be counted as +0. A PSC member can block an ad hoc
> meeting if he feels strongly about participating but has not a time slot
> available. In this case it will be postponed to the monthly standard meeting
> * every meeting will appoint a Chair, normally the PSC Chair, and a
> Secretary (not necessarily always the same person), who will have the
> responsibility for completing the minutes; cooperative editing should be
> allowed
>
> List of resolutions
> ====================
> * each decision will be listed according to a simple template:
> Date of voting
> Proponent
> Rationale
> Votes
> Decision
> Notes
> * all decisions will be added to a single location#
>
> Reporting
> ==========
> * for each expenditure, before payment, a report must be completed by
> the proponent, according to a simple template:
> Date of resolution
> Date of delivery
> Proponent
> Description of results
> Eventual links to full description, commit etc.
> Evaluation (success, partial success, failure)
> * reports can be very short in case they are simple tasks, but we aim at
> completeness
> * for recurring costs, only the initial report should be done
> * all reports will be added to a single location#
>
> To Do list
> ===========
> * managed through a trouble ticketing system (GitHub or similar) that
> will automatically record Proponent and Date of proposal
> * for each item it will be listed a Deadline and a Responsible
>
>
> # I propose to add all documents to
> https://github.com/qgis/QGIS-Website/tree/master/source/site/getinvolved/governance
> and compiled into the main website, as this is simple and easy to
> search, also in the long term.
> Minutes IMHO can stay in a dynamic infrastructure, like GDocs, where the
> advantages of communal editing are evident.

-- 
Marco Bernasocchi

QGIS.org Co-chair
http://berna.io