On Jan 10, 2013, at 14:45 , Jim Fulton <j...@zope.com> wrote: > On Thu, Jan 10, 2013 at 8:39 AM, Jens Vagelpohl <j...@dataflake.org> wrote: >> >> On Jan 10, 2013, at 14:37 , Jim Fulton <j...@zope.com> wrote: >> >>> On Thu, Jan 10, 2013 at 5:48 AM, Jens Vagelpohl <j...@dataflake.org> wrote: >>>> For those packages that are fully migrated you will have obvious markers >>>> on the package in svn.zope.org, such as the package being read-only. >>> >>> I don't think being read only is enough. Are people supposed to >>> attempt commits to find out if a project is read-only? >>> >>> We should at least leave something like a MOVED_TO_GITHUB file in the >>> project, in addition to making it read only. >> >> That's what I meant by "obvious marker, such as...". I did not imply making >> a package read-only is the only marker. > > But that's all that has been done for some projects. (Sorry, I don't > mean to be critical and I didn't raise the issue when it happened.) > OTOH, it's been argued (I disagree :) that I did too much for the ZODB > projects. I think it would be helpful if we agreed on what should > done, so we have a standard play book.
Please get in touch with Tres if you think his migrations should be improved. All other repositories (Zope, Products.*) were test migrations where I asked for feedback and never got any. They are throw-away and not final. The only finished migrations are yours and Tres'. jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org 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 )
