[SeasonOfDocs] Bootstrapping TheGoodDocsProject Steering Committee

[Felicity Brand]

Okay, as a bit of an experiment, I put a rule on the Governance repo so
that it requires at least one review on a PR. I couldn't restrict that
further to block approving your own PR. I did a bit of digging around - if
anyone know how to do that, let me know.

cheers
Felicity

On Mon, Jul 15, 2019 at 11:59 PM Jennifer Rondeau <
jennifer.rondeau at gmail.com> wrote:

> I can confirm my availability, however rash such confirmation may
> eventually prove to be.
>
> You can write rules to block people from merging their own PRs. I'd have
> to look up how to do it, but I've worked on projects that implement such an
> approach. Not sure how complex, though
>
> On Mon, Jul 15, 2019 at 9:34 AM Jo Cook <jo.k.cook at gmail.com> wrote:
>
>> Hi All,
>>
>> I confirm my availability to be on the PSC too. How exciting!
>>
>> Felicity/Cameron, I've made a quick change to the governance document to
>> ensure I have write access and can merge pull requests. I can ask around
>> for how to get around the issue of needing write access but not wanting
>> people to approve their own PRs- no doubt someone has considered this
>> elsewhere!
>>
>> Jo
>>
>> On Mon, Jul 15, 2019 at 1:32 AM Felicity Brand <felicitybrand at gmail.com>
>> wrote:
>>
>>> Looks good Cameron.
>>>
>>> I can confirm my availability.
>>>
>>> Apologies you weren't able to commit. I didn't get any email
>>> notifications because I didn't realise my old work email was configured as
>>> my default in Github. Gah!
>>>
>>> I have now made all members of the Org "owners" so you should be able to
>>> approve your own PRs. I realise this probably isn't kosher for ensuring
>>> quality. The other thing I could do is create a "team". I am new to
>>> Organizations in Github so if anyone wants to guide me, please do so!
>>>
>>> Thanks
>>> Felicity
>>>
>>> On Sun, Jul 14, 2019 at 9:02 PM Cameron Shorter <
>>> cameron.shorter at gmail.com> wrote:
>>>
>>>> In order to get our decision making processes set up, I've written a
>>>> draft Project Steering Committee governance doc for TheGoodDocsProject.
>>>>
>>>> https://github.com/camerons/governance/blob/master/ProjectSteeringCommittee.rst
>>>>
>>>> The next step is to add the initial people to this committee. I suggest
>>>> these people should:
>>>> * Have been actively involved in TheGoodDocsProject conversation to
>>>> date.
>>>> * Have tech writing experience, integrity and insights to share.
>>>> * Be willing to contribute a few hours a fortnight for the next 6 to 12
>>>> months or more.
>>>> * Agree to abide by the PSC governance doc above.
>>>>
>>>> People I suspect might be ready to join our initial PSC:
>>>> Cameron Shorter
>>>> Felicity Brand
>>>> Jo Cook
>>>> Erin McLean
>>>> Becka Todd
>>>> Jennifer Rondeau
>>>> Stephanie Blotner
>>>> Eric Holscher
>>>> Jarad Morgan
>>>> Clarence Cromwell
>>>> Riona Macnamara (I'm hoping, but am aware of your other priorities)
>>>>
>>>> If this sounds like you then please reply to confirm your availability.
>>>>
>>>> (Felicity, I don't seem to have permissions accept my github pull
>>>> request for this doc)
>>>>
>>>>
>>>> --
>>>> Cameron Shorter
>>>> Technology Demystifier
>>>> Open Technologies and Geospatial Consultant
>>>>
>>>> M +61 (0) 419 142 254
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> SeasonOfDocs mailing list
>>>> SeasonOfDocs at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/seasonofdocs
>>>>
>>> _______________________________________________
>>> SeasonOfDocs mailing list
>>> SeasonOfDocs at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/seasonofdocs
>>>
>>
>>
>> --
>> ------------------------
>> http://about.me/jocook
>> _______________________________________________
>> SeasonOfDocs mailing list
>> SeasonOfDocs at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/seasonofdocs
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/seasonofdocs/attachments/20190716/98c8dec9/attachment-0001.html>