[Pkg-exppsy-maintainers] Gearing up for PyEPL release

Wed Aug 6 17:39:58 UTC 2008

Hi Yarik:

Thanks for the input!  The problem with alioth, and please correct me
if I'm wrong about any of this, is that, by being debian-centric, they
are prohibitive about what packages are allowed to be hosted there.
For now, pyepl source is under git under the pkg-exppsy heading, which
was only possible because you already had the general project set up.

I tried to start a new project there awhile back and was turned down
because I did not prove that it was specifically designed to promote
debian.  PyEPL is not specifically designed to support debian,
however, packaging PyEPL for debian is.

I don't like having a handful of larger projects under the pkg-exppsy
heading in alioth.  Outside us, no one really knows about alioth or
has accounts on it (obviously, it's easy to get an account.)  Every
online hosting site forces you to have an account on their system to
use it, so that's not a big issue.

My goal is to have an easy-to-use, visible, online site for source,
wiki, bug/issue tracking, announcements, mailing list, and releases.
Nothing has all of what I want without rolling my own.

GoogleCode has everything except only does svn (git-svn is not really
that bad if we had to use it) and, for better or worse, it's google.
Also, Greg recently started a pyepl blog there:
http://pyepl.blogspot.com/

Alioth has git hosting, but no wiki and it doesn't really seem that
PyEPL fits under the main goals of Alioth.

Sourceforge has no git and an annoying interface

GitHub has a wiki, but no issue tracking.

To be honest, I'm currently leaning towards using GoogleCode and I'm
looking for someone to talk me out of it.  I would likely still keep
the source at alioth for the git excitement.  If alioth is going to
work in the long run, pyepl would likely need its own project and I'm
not sure that will fly with the admins.  Also, the main impetus for
this move is to have a wiki, which alioth can't supply.

Thanks for any thoughts,
Per

On Wed, Aug 6, 2008 at 11:49 AM, Yaroslav Halchenko
<debian at onerussian.com> wrote:
> Hi Per
>
> sorry for being salient.
> so, alioth could provide you with everything besides wiki, right? so may
> be it would be a good place? and then host wiki elsewhere? there are
> free wiki hosts available but I am not sure if you would like to take
> the risk to use any of those ;-)
>
> well... I could install and make available a host with anything we like
> to have on it but then we would need to take a burden of maintaining it
> (shouldn't be too much but if you like to have public wiki it might be
> some burden). what do you think?
>
> On Wed, 06 Aug 2008, Per B. Sederberg wrote:
>
>> Does anyone receiving this email have any thoughts on where/how to
>> host PyEPL?  The goal is to have centralized source, issue tracking,
>> mailing list, wiki, ...
>
>> I hope all is well around the world :)
>
>> Talk to you soon,
>> Per
>
>> On Tue, Jul 22, 2008 at 12:08 PM, Per B. Sederberg <persed at princeton.edu> wrote:
>> > Hi Folks:
>
>> > I'm gearing up for a PyEPL release.  The last before a larger overhaul
>> > that will include a major refactor and, hopefully, Windows support.
>> > This release actually has a load of very important changes (we now
>> > have a changelog in there, for one.)
>
>> > I'd like your input on some issues going forward.  Greg has been
>> > pushing for a long time (and he is absolutely right and we are remiss
>> > for not doing this earlier) that we need a wiki to help build a
>> > community of users pushing sample code and other exciting tidbits.  We
>> > currently have a mailing list / forum on sourceforge and that's where
>> > we post our releases.  I'm not blown away by their wiki and I'm
>> > getting more and more annoyed by the massive amount of distracting ads
>> > (I realize they are providing a great service and must pay for what
>> > they are providing.)
>
>> > As you know, the PyEPL source is now hosted under git at alioth, which
>> > I'm happy to keep.  I personally like the mailing list and issue
>> > tracking provided by google code far more than what I've seen us use
>> > on alioth.  Google code also has a minimal wiki that would suffice.  I
>> > certainly don't want to move over to svn (even as git-svn), so that is
>> > not a big worry in any way.
>
>> > So, here's one proposal: We move the forum/mailing list over to google
>> > code and start using their wiki, too.  We would still need to figure
>> > out where to put a pyepl website, which is currently also hosted on
>> > sourceforge.  We would then post tarballs and installs there, as well.
>
>> > The good would be that it's more centralized, the bad is that we would
>> > not be completely centralized and there may be complaints about using
>> > google code.
>
>> > If you have the chance, please chime in with opinions about this along
>> > with alternatives that we have not fully explored (such as
>> > github.com)...  I'd love to know how close we can get with alioth,
>> > too.  The basic desire is to get a more unified home for the PyEPL
>> > with a website, wiki, forum/mailing list, bug/issue tracking,
>> > releases, ...
>
>> > Thanks,
>> > Per
>
>
>> _______________________________________________
>> Pkg-exppsy-maintainers mailing list
>> Pkg-exppsy-maintainers at lists.alioth.debian.org
>> http://lists.alioth.debian.org/mailman/listinfo/pkg-exppsy-maintainers
>
>
> --
> Yaroslav Halchenko
> Research Assistant, Psychology Department, Rutgers-Newark
> Student  Ph.D. @ CS Dept. NJIT
> Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
>        101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
> WWW:     http://www.linkedin.com/in/yarik
>
> _______________________________________________
> Pkg-exppsy-maintainers mailing list
> Pkg-exppsy-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-exppsy-maintainers
>