[Zope-dev] "procedures" for moving package to github and porting to Python 3

[Jan-Wijbrand Kolman]

On 3/1/13 2:23 PM, Marius Gedminas wrote:
> On Fri, Mar 01, 2013 at 11:24:31AM +0100, Jan-Wijbrand Kolman wrote:
>> On 3/1/13 10:17 AM, Marius Gedminas wrote:
>>> My attempt at this: https://gist.github.com/mgedmin/4944724
>>>
>>> AFAIK Stephan migrated most of the zope.* packages using this process.
>
> Stephan tells me there are scripts at
> https://github.com/zopefoundation/zope.githubsupport
> that can do the entire process (create repo, convert history, upload
> it), if you've the right permissions on Github (few people do).  So
> perhaps the easiest thing is to ask for the package to be converted.

I just read Stephan's reply pointing to that script.

I have no idea whether I have the right permissions.

I do see someone just created an empty grokcore.component repository on 
github (thanks whoever did that! :-)  )

I could surely ask others to do the work for me, though I had the 
impression everyone could take care of the packages he/she cares about :-)

The list that I intended to start off with is roughly:

    grok
    grokcore.annotation
    grokcore.catalog
    grokcore.chameleon
    grokcore.component
    grokcore.content
    grokcore.formlib
    grokcore.json
    grokcore.layout
    grokcore.message
    grokcore.rest
    grokcore.security
    grokcore.site
    grokcore.startup
    grokcore.traverser
    grokcore.view
    grokcore.viewlet
    grokcore.xmlrpc
    grokproject
    grokui.admin
    grokui.base
    martian
    megrok.menu
    zope.errorview
    zope.fanstatic
    z3c.autoinclude
    z3c.evalexception
    z3c.flashmessage
    zc.catalog

Since the grokcore.component repo is there now, I'll follow my initial 
plan and try to get that migrated from svn to github as a first step.

kind regards, jw