Re: Moving projects to the Attic
On Thu, 16 Jan 2014, sebb wrote:
Date: Thu, 16 Jan 2014 00:39:23 +0100
From: sebb seb...@gmail.com
To: Henk P. Penning penn...@uu.nl
Cc: general@attic.apache.org,
Apache Infrastructure infrastruct...@apache.org
Subject: Re: Moving projects to the Attic
On 15 January 2014 09:01, Henk P. Penning penn...@uu.nl wrote:
On Wed, 15 Jan 2014, Henri Yandell wrote:
Date: Wed, 15 Jan 2014 04:30:02 +0100
From: Henri Yandell he...@yandell.org
To: general@attic.apache.org
Cc: Apache Infrastructure infrastruct...@apache.org
Subject: Re: Moving projects to the Attic
Sender: hyand...@gmail.com
So updating with Sebb's response:
Hi,
Can be done by Attic:
- Create page on Attic site
- Inform users
- Delete from committee-info.txt (members)
- Remove from www.apache.org navigation
- Announce on announce at apache.org
Needs permissions from Infra for Attic:
Shouldn't the (svn) permissions for 'site' and 'dist' be
transfered from project committers to attic committers ?
to freeze the web-site and dist-area, and let 'attic' do
its thing?
If Infra are happy with the idea, then updating the authn files can be
done by the following groups:
[/infrastructure/trunk/subversion/authorization]
@member = rw
@pmc-chairs = rw
@svnadmins = rw
@board = rw
@exec-officers = rw
Which should be enough for Attic to assign themselves the necessary
karma for the site, as has already been done here:
[/websites/production/esme]
@attic-pmc = rw
@esme = rw
Not sure where the dist/release permissions are defined, so I don't
know if this can be done by Attic personnel
That file is generated by 'infra' with :
https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/generate-dist-authorization
As you can see, at the moment, 'esme' is a special case :
@attic-pmc = rw is added to [/dev/esme], [/release/esme].
Also, for the record, infra wants to remove the dist/dev/esme
and dist/release/esme areas (six months after 'attic' day).
IHMO, it would be a lot simpler if 'project' esme could simply
move from (defunct) pmc-esme to pmc-attic ; A PMC can run more
than one project.
Regards,
HPP
for dist : [eg esme] https://dist.apache.org/repos/dist/release/esme
eg : svn ls -v https://dist.apache.org/repos/dist/release/esme
[ there may also be a https://dist.apache.org/repos/dist/dev/esme ]
for site : don't know how this would work for a CMS site.
- Update website with Attic notice
- Update HEADER.html in downloads
- Update the project DOAP file
- 6 months+: strip dist/project and add a .htaccess redirect
Needs to be done by Infra:
- Point SVN mails to general at attic
- Make SVN + JIRA/Bugzilla read-only
- Turn off automated builds
- Close down infrastructure resources
- 6 months+: Consider deleting the user list
With sites on the CMS, updating the website with an Attic notice is likely
to be a challenge. Typically I did a search and replace on every .html
page
and inserted a div at the top of the page. Any thoughts from anyone
CMS-knowledgable about whether it's best to try and do that in the CMS
somehow, or perhaps to have a more programmatic notion that marks a site
as
retired and inserts a header?
... or add to the site's style-sheet
body:before
{ content:This project retired ...;
background-color:yellow;
float : top ;
color:red;
font-weight:bold;
}
Hen
_
Henk P. Penning, ICT-beta R Uithof BBL-761 _/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Princetonplein 5, 3584CC Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
_
Henk P. Penning, ICT-beta R Uithof BBL-761 _/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Princetonplein 5, 3584CC Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Moving projects to the Attic
On 16 January 2014 14:56, Henk P. Penning penn...@uu.nl wrote:
On Thu, 16 Jan 2014, sebb wrote:
Date: Thu, 16 Jan 2014 12:51:57 +0100
From: sebb seb...@gmail.com
To: Henk P. Penning penn...@uu.nl
Cc: general@attic.apache.org,
Apache Infrastructure infrastruct...@apache.org
Subject: Re: Moving projects to the Attic
On 16 January 2014 10:45, Henk P. Penning penn...@uu.nl wrote:
On Thu, 16 Jan 2014, sebb wrote:
https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/generate-dist-authorization
Also, for the record, infra wants to remove the dist/dev/esme
and dist/release/esme areas (six months after 'attic' day).
The dev/esme tree could be deleted immediately.
I assume svnpubsub will have to be switched off for the release tree
first.
And that can only happen after the .htaccess redirects have been set up.
Once release/esme is deleted, the esme/.htaccess file will no longer
be anywhere in current SVN - the only copy will in backups.
Ah yes ; I forgot that after six months the dist/TLP/ should be
stripped down to a .htaccess (not removed, as I said).
Perhaps the .htaccess redirects should be added to the parent (dist)
directory, in which case the esme directory could be removed entirely
from dist?
It seems a bit unnecessary for all attic projects to have directories
which only contain .htaccess files, but perhaps there is a reason why
this is better than updating the parent .htaccess file.
I dont' think putting the redirects in dist/.htaccess can be made
to work properly. In the 'Redirect' the first argument must be an
absolute path, and that won't work on the mirrors ;
.htaccess doesn't take Directory directives ;
hence the 'RedirectMatch' in (fi) dist/beehive/.htaccess.
OK, that's a pity.
I /would/ like to remove (in /dist/) anything pointing to an attic'ed
TLP after some time ; say 2 years.
-- Would anybody veto that :-?
So for example beehive and harmony and jakarta would now be candidates
for deletion?
I assume the original websites would remain.
If the redirects were removed, the mirror download pages would break completely.
At present they redirect to the Attic holding page; I think they would
404 instead.
It would be a lot of effort to update all the site download pages to
document or fix this, and deleting the pages would lose useful
information.
Keeping the redirects would avoid this.
My vote would be -1 (but is not binding).
I note that the parent directory (dist) does not seem to be in SVN.
Maybe it should be, in which case attic dirs could be moved to that
for ongoing maintenance.
... dist/.htaccess doesn't get synced from mino to the rsync servers ...
... I think the attic'ed TLP's shouldn't be moved ; setting proper
(@attic) rw-rights is enough.
IHMO, it would be a lot simpler if 'project' esme could simply
move from (defunct) pmc-esme to pmc-attic ; A PMC can run more
than one project.
Not sure I follow how that would work technically with the existing
auth files.
The /dist/ svn auth file is generated (url above) ; the script could/
should be made smarter (it should know about attic'ed projects).
I don't know if there is a reliable database saying project esme
now belongs to pmc-attic.
If the only place that needs to know about them is the script, then it
could be listed there.
As is done for projects that allow non-PMC RMs.
Regards,
HPP
_
Henk P. Penning, ICT-beta R Uithof BBL-761 _/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Princetonplein 5, 3584CC Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Moving projects to the Attic
On 15 January 2014 09:01, Henk P. Penning penn...@uu.nl wrote:
On Wed, 15 Jan 2014, Henri Yandell wrote:
Date: Wed, 15 Jan 2014 04:30:02 +0100
From: Henri Yandell he...@yandell.org
To: general@attic.apache.org
Cc: Apache Infrastructure infrastruct...@apache.org
Subject: Re: Moving projects to the Attic
Sender: hyand...@gmail.com
So updating with Sebb's response:
Hi,
Can be done by Attic:
- Create page on Attic site
- Inform users
- Delete from committee-info.txt (members)
- Remove from www.apache.org navigation
- Announce on announce at apache.org
Needs permissions from Infra for Attic:
Shouldn't the (svn) permissions for 'site' and 'dist' be
transfered from project committers to attic committers ?
to freeze the web-site and dist-area, and let 'attic' do
its thing?
If Infra are happy with the idea, then updating the authn files can be
done by the following groups:
[/infrastructure/trunk/subversion/authorization]
@member = rw
@pmc-chairs = rw
@svnadmins = rw
@board = rw
@exec-officers = rw
Which should be enough for Attic to assign themselves the necessary
karma for the site, as has already been done here:
[/websites/production/esme]
@attic-pmc = rw
@esme = rw
Not sure where the dist/release permissions are defined, so I don't
know if this can be done by Attic personnel
for dist : [eg esme] https://dist.apache.org/repos/dist/release/esme
eg : svn ls -v https://dist.apache.org/repos/dist/release/esme
[ there may also be a https://dist.apache.org/repos/dist/dev/esme ]
for site : don't know how this would work for a CMS site.
- Update website with Attic notice
- Update HEADER.html in downloads
- Update the project DOAP file
- 6 months+: strip dist/project and add a .htaccess redirect
Needs to be done by Infra:
- Point SVN mails to general at attic
- Make SVN + JIRA/Bugzilla read-only
- Turn off automated builds
- Close down infrastructure resources
- 6 months+: Consider deleting the user list
With sites on the CMS, updating the website with an Attic notice is likely
to be a challenge. Typically I did a search and replace on every .html
page
and inserted a div at the top of the page. Any thoughts from anyone
CMS-knowledgable about whether it's best to try and do that in the CMS
somehow, or perhaps to have a more programmatic notion that marks a site
as
retired and inserts a header?
... or add to the site's style-sheet
body:before
{ content:This project retired ...;
background-color:yellow;
float : top ;
color:red;
font-weight:bold;
}
Hen
_
Henk P. Penning, ICT-beta R Uithof BBL-761 _/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Princetonplein 5, 3584CC Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
Re: Moving projects to the Attic
So updating with Sebb's response: Can be done by Attic: - Create page on Attic site - Inform users - Delete from committee-info.txt (members) - Remove from www.apache.org navigation - Announce on announce at apache.org Needs permissions from Infra for Attic: - Update website with Attic notice - Update HEADER.html in downloads - Update the project DOAP file - 6 months+: strip dist/project and add a .htaccess redirect Needs to be done by Infra: - Point SVN mails to general at attic - Make SVN + JIRA/Bugzilla read-only - Turn off automated builds - Close down infrastructure resources - 6 months+: Consider deleting the user list With sites on the CMS, updating the website with an Attic notice is likely to be a challenge. Typically I did a search and replace on every .html page and inserted a div at the top of the page. Any thoughts from anyone CMS-knowledgable about whether it's best to try and do that in the CMS somehow, or perhaps to have a more programmatic notion that marks a site as retired and inserts a header? Hen
