[committee] [wheel] Wheel generational issues

[James Cox]

Whether we implement “up or out” or any other major policy changes or not,
I think the “commit log” idea is a good one.
I think it probably makes more sense as a master log rather than per-person
pages that can’t be coalesced.

[RME]~Coxy

On Fri, 15 Mar 2019 at 05:47, Lyndon White <oxinabox at ucc.asn.au> wrote:

> Seems reasonable.
> At least as a starting point
>
> As to technical implementation.
>
> How about a contributions journal.
> Where one just notes down a thing g done.
> E.g.
> ```
>  - 20140424: helped [BOB] setup CUPS server on new VM midshipman
> ```
>
> This would make it easy to look back at a year and see what was done.
>
> And the effort of recording it in a very terse form is low vs the doing of
> anything worth recording.
>
> It would also serve as a useful historical record.  If say each person
> kept it on a public page on the wiki with their username/TLA. We could e.g.
> search that to findout who knows how to setup CUPS,or who set it up on
> midshipman.
>
> It would also set a standard and sprocket members or general members could
> (by choice) keep one similarly, which would've useful when they apply for
> wheel.
>
> [*OX]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ucc.gu.uwa.edu.au/pipermail/committee/attachments/20190315/bbdefcee/attachment.htm>