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

2013-03-04 Thread Jan-Wijbrand Kolman

On 3/1/13 5:29 PM, Stephan Richter wrote:

On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote:

 megrok.menu


It's done now, but it lost its 0.1 tag due to a conversion issue.


Great! And thanks again!


regards, jw


___
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 )


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

2013-03-01 Thread Marius Gedminas
On Fri, Mar 01, 2013 at 09:51:05AM +0100, Jan-Wijbrand Kolman wrote:
 Disclaimer: it's been a while since I actively followed zope-dev and
 grok-dev. So, please forgive me my ignorance.

A single up-to-date web page sure beats reading months of list archives.

 Spurred by the recent ZTK-2.0 discussion, I'm trying to get back on
 track on the topics of 1) migrating package to github and 2) porting
 packages to Python 3.
 
 As a first step, I'd like to get the packages directly related to
 Grok moved over to github.
 
 Could someone perhaps tell me if there's a guideline document, some
 kind of recipe, or perhaps a conclusive posting on the mailinglist
 on how to proceed on this topic?

My attempt at this: https://gist.github.com/mgedmin/4944724

AFAIK Stephan migrated most of the zope.* packages using this process.

Marius Gedminas
-- 
http://pov.lt/ -- Zope 3/BlueBream consulting and development


signature.asc
Description: Digital 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 )


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

2013-03-01 Thread Jan-Wijbrand Kolman

On 3/1/13 10:17 AM, Marius Gedminas wrote:

On Fri, Mar 01, 2013 at 09:51:05AM +0100, Jan-Wijbrand Kolman wrote:

Disclaimer: it's been a while since I actively followed zope-dev and
grok-dev. So, please forgive me my ignorance.


A single up-to-date web page sure beats reading months of list archives.


:-)


Spurred by the recent ZTK-2.0 discussion, I'm trying to get back on
track on the topics of 1) migrating package to github and 2) porting
packages to Python 3.

As a first step, I'd like to get the packages directly related to
Grok moved over to github.

Could someone perhaps tell me if there's a guideline document, some
kind of recipe, or perhaps a conclusive posting on the mailinglist
on how to proceed on this topic?


My attempt at this: https://gist.github.com/mgedmin/4944724

AFAIK Stephan migrated most of the zope.* packages using this process.


Ok, thanks. I've read it, but will need to re-read it a couple of times 
more I guess :)


It seem to me the best next step would be to just pick a random 
grokcore.* package and to just try it. I'll pick, well, grokcore.component.


If I understand correctly, there's two things I need to ask someone to do:

* create a repository at https://github/zopefoundation/grokcore.component

* ask permission to use the authors.txt mapping svn usernames to real 
names and email addresses.


Again, thanks for the information.

regards, jw

___
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 )


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

2013-03-01 Thread Stephan Richter
On Friday, March 01, 2013 11:17:44 AM Marius Gedminas wrote:
  Could someone perhaps tell me if there's a guideline document, some
  kind of recipe, or perhaps a conclusive posting on the mailinglist
  on how to proceed on this topic?
 
 My attempt at this: https://gist.github.com/mgedmin/4944724
 
 AFAIK Stephan migrated most of the zope.* packages using this process.

Yes, I have, except that I use a one does it all script published here:

https://github.com/zopefoundation/zope.githubsupport

All you need to do is to create a zope.cfg that works for you. I can quickly 
create repositories for you if you send me a list of (pkg_name, pkg_title) 
tuples.

Jim will announce a secret location for the authors.txt file in the next days 
on the ZF mailing list.

Regards,
Stephan
-- 
Entrepreneur and Software Geek
Google me. Zope Stephan Richter
___
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 )


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

2013-03-01 Thread Marius Gedminas
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.

Marius Gedminas
-- 
http://pov.lt/ -- Zope 3/BlueBream consulting and development


signature.asc
Description: Digital 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 )


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

2013-03-01 Thread 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




___
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 )


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

2013-03-01 Thread Jan-Wijbrand Kolman

On 3/1/13 1:39 PM, Stephan Richter wrote:

AFAIK Stephan migrated most of the zope.* packages using this process.


Yes, I have, except that I use a one does it all script published here:

https://github.com/zopefoundation/zope.githubsupport


Aha, great!


All you need to do is to create a zope.cfg that works for you. I can quickly
create repositories for you if you send me a list of (pkg_name, pkg_title)
tuples.


I just compiled a list in another reply in this thread.


Jim will announce a secret location for the authors.txt file in the next days
on the ZF mailing list.


You mean the ZF mailinglist that only ZF members can join?

Thanks for the pointers so far!

regards, jw


___
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 )


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

2013-03-01 Thread Stephan Richter
On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote:
 I do see someone just created an empty grokcore.component repository on 
 github (thanks whoever did that! :-)  )

It is actually fully converted. :-)

I am going to adjust my script to allow mutliple conversions at once. I will 
take care of your list.

Regards,
Stephan
-- 
Entrepreneur and Software Geek
Google me. Zope Stephan Richter
___
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 )


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

2013-03-01 Thread Stephan Richter
On Friday, March 01, 2013 02:40:38 PM Jan-Wijbrand Kolman wrote:
  Jim will announce a secret location for the authors.txt file in the next
  days on the ZF mailing list.
 
 You mean the ZF mailinglist that only ZF members can join?

Yeah, but if you are a committer, you are a member. :-)

Regards,
Stephan
-- 
Entrepreneur and Software Geek
Google me. Zope Stephan Richter
___
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 )


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

2013-03-01 Thread Jan-Wijbrand Kolman

On 3/1/13 2:49 PM, Stephan Richter wrote:

On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote:

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


It is actually fully converted. :-)


LOL - cool!


I am going to adjust my script to allow mutliple conversions at once. I will
take care of your list.


Really?! Thanks!!

regards, jw

___
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 )


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

2013-03-01 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03/01/2013 08:50 AM, Stephan Richter wrote:
 On Friday, March 01, 2013 02:40:38 PM Jan-Wijbrand Kolman wrote:
 Jim will announce a secret location for the authors.txt file in
 the next days on the ZF mailing list.
 
 You mean the ZF mailinglist that only ZF members can join?
 
 Yeah, but if you are a committer, you are a member. :-)

Not so.  Foundation members are listed here:

 http://foundation.zope.org/members/nominated_members

The original group of what are now called nominated members was invited
from the then-existing set of committers, but there is no necessary tie
between the two.



Tres.
- -- 
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlEwtfMACgkQ+gerLs4ltQ66bwCfTubHRqqMv3PkZemQgXwoIx4s
n10An3Jd/08Vp8k28xPqOZta6Bbj/GRM
=vuDU
-END PGP 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 )


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

2013-03-01 Thread Stephan Richter
Everything but megrok.menu is now converted. GitHub did not like the fact that 
I tried to create 26 repos at once, so I had some startup issues.

Regards,
Stephan
On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote:
 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
-- 
Entrepreneur and Software Geek
Google me. Zope Stephan Richter
___
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 )


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

2013-03-01 Thread Stephan Richter
On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote:
 megrok.menu

It's done now, but it lost its 0.1 tag due to a conversion issue.

Regards,
Stephan
-- 
Entrepreneur and Software Geek
Google me. Zope Stephan Richter
___
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 )