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

[Yaroslav Halchenko]

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