On Mon, 23 Jul 2018, Ralph Goers wrote:
Date: Mon, 23 Jul 2018 15:24:58 +0200
From: Ralph Goers <[email protected]>
To: [email protected]
Subject: Re: Clarifying the process for PMCs adopting codebases from the Attic
On Jul 23, 2018, at 1:47 AM, Bertrand Delacretaz <[email protected]> wrote:
As for having a Board decision when reviving a project, that probably
makes sense for symmetry with the Board resolution that moved the
project to the Attic. But I don't think the Board necessarily needs to
be involved in the discussions that lead to that resolution, I think
the Attic PMC can simply add a resolution to the Board agenda as
needed, and the Board just ratifies it.
There is no symmetry. The board terminated the PMC and gave its
assets to the attic to manage.
The board passed a resolution saying :
RESOLVED, that the Attic PMC be and hereby is tasked with
oversight over the software developed by the Apache XXXXX
Project; and
My question is : can Attic 'un-task' itself, or is a board
resolution required ?
If a resolution is required, board might as well (symmetry)
task the new PMC with "oversight over ...".
Since you (rightly, in my view) broaden "the software"
to "all assets", the resolution would effectively
move the PROJECT (== all assets) to another PMC.
The board is NOT reinstating a PMC or
creating a new one.
True.
Once the attic owns the assets it should be free to assign those
assets to any PMC willing to manage them.
Ralph
Thanks ; regards,
Henk Penning
------------------------------------------------------------ _
Henk P. Penning, ICT-beta R Uithof MG-403 _/ \_
Faculty of Science, Utrecht University T +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M [email protected] \_/
