Moving source code to Github. What to do with mailing list?

Irmen de Jong <[email protected]>
Newsgroups gmane.comp.python.pyro
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I've decided to move Pyro's source code repositories from my own subversion server, to
Github.

It seems the conversions of the svn-repo of Pyro4, Pyro3 and Pyrolite to Github have
been succesful (as far as I can see: the commit history is intact). So this change is
in effect immediately. The documentation etc hasn't been updated yet to reflect the
change, but I will do that shortly.

The new (git) repositories are:

https://github.com/irmen/Pyro4
https://github.com/irmen/Pyrolite
https://github.com/irmen/Pyro3     (for the oldskoolers)


This brings us to the mailing list. It has served the Pyro project faithfully for a
LONG time: since march 2002. I'm wondering if the features of Github (gist, code
comments, issue trackers) could perhaps replace the mailing list? What are your
thoughts about this? (The mailing list is the only string that still ties Pyro to
sourceforge.net)

I will be happy hearing your feedback about these topics.

Cheers,
Irmen de Jong.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJR00TxAAoJEHC9o7RHFlf2RvkH/28WC1am7gK3xwsDxN5JI2SE
fip+nfA6Lpri7ZOWnaax+iXoihmeDGglwoa03KpjKZeT1sv4XNJjgzM7gmJC1STH
26uE6l88W9fH2zzhlZVtAKDnaBCjTxV+wbodWlKP5eP9TV4bJ6R5JvkQNQZZbh8T
rp11ZHcGsyEQHlnfCZL9P+D8gtN0TEidfX+VraBGISqN7MyyFBsbaayp4/hdz3y3
pIgHHF7IgqPculEDCi4kH59pTgqgZ21dU6fjkigVBiljXjihJNQ74CtL8DCs2a4g
twDSN11xG0Fm7KQDaEZqyB0fEqXpjuogMSk9SCbuASYTe3UkxBWo/aa7SCI3cUI=
=Hykm
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.