Re: How to signal that projects have moved to github
Tres Seaver <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/10/2013 09:15 AM, Jim Fulton wrote: > I'd like us to agree on how we're going to indicate in SVN that > projects have been moved to github. > > Here's an opening bid: > > - Replace contents of trunk with a single file MOVED_TO_GITHUB > containing the URL if the project page in github > > - Copy above file to root of project. > > - Make project read only > > An argument against cleaning out trunk will break CI tools. This is > also an argument *for* cleaning out trunk. :) > > Thoughts? > > There are a lot of other details of the migration that need to be > worked out, like how folks should request migration and automating the > conversion further. I would be happy to add the 'MOVED-TO-GITHUB.txt' files to the SVN projects for the 'zope.*' packages I have already migrated. I need to have the readonly restriction relaxed, first/ Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [email protected] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDu8+UACgkQ+gerLs4ltQ78tACg0RqCvxRd269YKdcT+shih/5s y/EAn1aO1PUQamqH4sJaMVgBKH2xK2LP =YRxy -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )