tisonkun opened a new issue, #112:
URL: https://github.com/apache/steve/issues/112

   Follow-up to #111. The DOAP source was switched to the [document generated 
by the current website](https://steve.apache.org/doap.rdf) in [this Comdev 
change](https://github.com/apache/comdev-projects/commit/b06b3f964ee38e708f308fb0965551a1f8f5aa5a),
 but the broader SVN tree still needs a clear archival status.
   
   The [SVN tree](https://svn.apache.org/repos/asf/steve/) contains `trunk/`, 
`branches/`, `tags/`, `site/`, and `steve-web/`. Its last change was in March 
2021 (r1887525); the old DOAP file dates from June 2014 (r1602421). Active 
development and website sources now live in this Git repository, with project 
metadata maintained in `.asf.yaml`.
   
   Proposal: retain SVN as a read-only historical archive, with clear links to 
the maintained sources.
   
   - [ ] Check remaining builds, scripts, and public references for SVN 
dependencies, and confirm that `projects.apache.org` has regenerated its STeVe 
entry from the new DOAP URL. Identify any SVN-only material that still needs 
active maintenance.
   - [ ] Record project consensus on `[email protected]` for archiving the 
entire `/steve/` SVN tree.
   - [ ] Add a migration README at the SVN root and notices at relevant legacy 
entry points, linking to this repository, https://steve.apache.org/, and the 
generated DOAP.
   - [ ] Ask Infra to confirm or set `/steve/` read-only, following the 
[SVN-to-Git guidance](https://infra.apache.org/svn-to-git-migration.html). 
Preserve the existing URLs and revision history; no ongoing Git-to-SVN 
mirroring is proposed.
   
   Done when SVN is clearly marked as historical and read-only, and active 
builds and project metadata no longer depend on its contents.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to