Re: transfer proj to existing PMC
On Mon, Oct 08, 2018 at 10:56:47AM +0200, Henk P. Penning wrote: > [1] the point is not valid > [2] the point is valid but don't raise it now > [3] raise the point ; just ask for advice > I vote for [3] with the clear understanding that we don't want the formal responsibility for a project that some other PMC has taken over. vh Mads Toftum -- http://flickr.com/photos/q42/
transfer proj to existing PMC
Hi, I've fixed the Attic index page re: "Process of leaving the Attic again", adding "Transfering to an existing PMC". The additional details are not exhaustive but the main points are clear, I think. I think this addition addresess the remarks in "Board feedback on 2018-07-18 Attic report" : https://lists.apache.org/thread.html/51b845f7b54d25f60a858eb39fff1dbfd1be9f05344556f6eafd83d0@%3Cprivate.attic.apache.org%3E Agree ? About the next report : -- activity : lucy was retired Board of Directors Meeting Minutes July 17, 2013, section 7.E says : https://www.apache.org/foundation/records/minutes/2013/board_minutes_2013_07_17.txt RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the software developed by the Apache XMLBeans Project; and be it further ... I think that Attic is formally still tasked with this oversight, where in practice isn't ; only a board resolution can fix that. I don't want to re-open the can of worms again, but I'm tempted to suggest to the board that, in future cases like Poi/Xmlbeans, board officially -- un-tasks Attic and, in the same resolution, -- tasks the receiving PMC [ack'ing that the transfer is ok] What do you think ? [1] the point is not valid [2] the point is valid but don't raise it now [3] raise the point ; just ask for advice Thanks ; regards, Henk Penning _ Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ -- Forwarded message -- Date: Mon, 8 Oct 2018 09:44:09 +0200 From: build...@apache.org To: general@attic.apache.org Subject: svn commit: r1843115 - /attic/site/docs/index.html Author: buildbot Date: Mon Oct 8 07:44:09 2018 New Revision: 1843115 URL: http://svn.apache.org/viewvc?rev=1843115=rev Log: Automatic Site Publish by Buildbot Modified: attic/site/docs/index.html Modified: attic/site/docs/index.html URL: http://svn.apache.org/viewvc/attic/site/docs/index.html?rev=1843115=1843114=1843115=diff == --- attic/site/docs/index.html (original) +++ attic/site/docs/index.html Mon Oct 8 07:44:09 2018 @@ -106,10 +106,23 @@ Options are: -Forking the project - we'll link to any forks which have been created so please let us know +Forking the project - we'll link to any forks which have been + created so please let us know Restarting the community in the Apache Incubator Recreating a PMC for the project +Transfering to an existing PMC + +A receiving PMC must be willing to assume all responsibilities that come +with running a project : maintain code, answer questions, fix bugs, +publish releases etc. + +If the Board does not object, PMC Attic will transfer the project's +assets (code-base, TLP website, maven group-id etc) to the receiving PMC. + +After the transfer the receiving PMC will report to the Board about the +project's activities, and publish project releases in the PMC's dist area. +
svn commit: r1843115 - /attic/site/docs/index.html
Author: buildbot Date: Mon Oct 8 07:44:09 2018 New Revision: 1843115 URL: http://svn.apache.org/viewvc?rev=1843115=rev Log: Automatic Site Publish by Buildbot Modified: attic/site/docs/index.html Modified: attic/site/docs/index.html URL: http://svn.apache.org/viewvc/attic/site/docs/index.html?rev=1843115=1843114=1843115=diff == --- attic/site/docs/index.html (original) +++ attic/site/docs/index.html Mon Oct 8 07:44:09 2018 @@ -106,10 +106,23 @@ Options are: -Forking the project - we'll link to any forks which have been created so please let us know +Forking the project - we'll link to any forks which have been + created so please let us know Restarting the community in the Apache Incubator Recreating a PMC for the project +Transfering to an existing PMC + +A receiving PMC must be willing to assume all responsibilities that come +with running a project : maintain code, answer questions, fix bugs, +publish releases etc. + +If the Board does not object, PMC Attic will transfer the project's +assets (code-base, TLP website, maven group-id etc) to the receiving PMC. + +After the transfer the receiving PMC will report to the Board about the +project's activities, and publish project releases in the PMC's dist area. +
svn commit: r1843114 - /attic/site/xdocs/index.xml
Author: henkp Date: Mon Oct 8 07:44:01 2018 New Revision: 1843114 URL: http://svn.apache.org/viewvc?rev=1843114=rev Log: += un-retire to existing PMC [2] Modified: attic/site/xdocs/index.xml Modified: attic/site/xdocs/index.xml URL: http://svn.apache.org/viewvc/attic/site/xdocs/index.xml?rev=1843114=1843113=1843114=diff == --- attic/site/xdocs/index.xml (original) +++ attic/site/xdocs/index.xml Mon Oct 8 07:44:01 2018 @@ -83,10 +83,24 @@ Options are: -Forking the project - we'll link to any forks which have been created so please let us know +Forking the project - we'll link to any forks which have been + created so please let us know Restarting the community in the Apache Incubator Recreating a PMC for the project +Transfering to an existing PMC + +A receiving PMC must be willing to assume all responsibilities that come +with running a project : maintain code, answer questions, fix bugs, +publish releases etc. + +If the Board does not object, PMC Attic will transfer the project's +assets (code-base, TLP website, maven group-id etc) to the receiving PMC. + +After the transfer the receiving PMC will report to the Board about the +project's activities, and publish project releases in the PMC's dist area. + +
svn commit: r1843113 - /attic/site/docs/index.html
Author: buildbot Date: Mon Oct 8 07:27:40 2018 New Revision: 1843113 URL: http://svn.apache.org/viewvc?rev=1843113=rev Log: Automatic Site Publish by Buildbot Modified: attic/site/docs/index.html Modified: attic/site/docs/index.html URL: http://svn.apache.org/viewvc/attic/site/docs/index.html?rev=1843113=1843112=1843113=diff == --- attic/site/docs/index.html (original) +++ attic/site/docs/index.html Mon Oct 8 07:27:40 2018 @@ -106,24 +106,10 @@ Options are: - Forking the project - we'll link to any forks which have been created - so please let us know - - Restarting the community in the Apache Incubator - Recreating a PMC for the project - Transfering to an existing PMC - - -A receiving PMC must be willing to assume all responsibilities that come -with running a project : maintain code, answer questions, fix bugs, -publish releases etc. - -If the Board does not object, PMC Attic will transfer the project's -assets (code-base, TLP website, maven group-id etc) to the receiving PMC. - -After the transfer the receiving PMC will report to the Board about the -project's activities, and publish project releases in the PMC's dist area. - +Forking the project - we'll link to any forks which have been created so please let us know +Restarting the community in the Apache Incubator +Recreating a PMC for the project +
svn commit: r1843112 - /attic/site/docs/index.html
Author: henkp Date: Mon Oct 8 07:27:31 2018 New Revision: 1843112 URL: http://svn.apache.org/viewvc?rev=1843112=rev Log: += un-retire to existing PMC Modified: attic/site/docs/index.html Modified: attic/site/docs/index.html URL: http://svn.apache.org/viewvc/attic/site/docs/index.html?rev=1843112=1843111=1843112=diff == --- attic/site/docs/index.html (original) +++ attic/site/docs/index.html Mon Oct 8 07:27:31 2018 @@ -106,10 +106,24 @@ Options are: -Forking the project - we'll link to any forks which have been created so please let us know -Restarting the community in the Apache Incubator -Recreating a PMC for the project - + Forking the project - we'll link to any forks which have been created + so please let us know + + Restarting the community in the Apache Incubator + Recreating a PMC for the project + Transfering to an existing PMC + + +A receiving PMC must be willing to assume all responsibilities that come +with running a project : maintain code, answer questions, fix bugs, +publish releases etc. + +If the Board does not object, PMC Attic will transfer the project's +assets (code-base, TLP website, maven group-id etc) to the receiving PMC. + +After the transfer the receiving PMC will report to the Board about the +project's activities, and publish project releases in the PMC's dist area. +
