[sldev] Fresh new code: eventlet and mulib

[Boroondas Gupte]

[Oops, wrong "From" address, so here it's again for the list]

As there are probably no clear answers to this questions, here are some
> > Thoughts?
on it.

> > The main question is: how closely do we want to associate eventlet and
> > mulib development with viewer development?
> >
> > --- Should we have a separate mailing list(s) for them?
ATM this probably would be contra productive as only few would subscribe
to them and so most would miss it if someone e.g. will present some good
non-grid use for those libs. If the lib-related traffic gets too high
later, you can still create a separate list then. "SLDev" stands for
"Second Life Develop(ment|ers)" anyway so it hasn't to be limited to the
viewer if more parts get open sourced  :-)
> > --- Should we track bugs in PJIRA, or in Trac?
For people that don't know Trac, it's another new thing to learn. Though I
guess it won't be too hard and as the libs are probably more of interest
for the more technically minded residents this shouldn't be a big issue. I
can't say much more as I'm one of those who don't know Trac (yet).

If linking between JIRA issues (doesn't has to be VWR, think of SVC and
WEB, for example) and issues with those libraries are needed, it's
probably easer to have them both in JIRA.
> > --- Should we put the documentation on wiki.sl.com, or in Trac?
As crosslinks should be trivial here (yeah, you won't have the wiki link
shortcuts etc) I don't really mind.
> >   It's really tempting to make the Trac for each project be the one-stop
> > shop for all relevant information.  It's how I'd do it if I were
> > starting these from scratch.  But we do have all this existing
> > infrastructure for bug tracking and documentation.  My inclination is to
> > continue documenting on wiki.sl.com, because I prefer MediaWiki, and
> > track bugs in Trac (because things get too easily lost in JIRA, plus
> > it's heck of slow).
> >
Meta-Issues or new JIRA projects would prevent issue loss. But perhaps
Trac's got fewer quirks than JIRA? (I fear it only's got different ones,
but I'd be looking forward to try)

Maybe someone who's already used Trac can tell us a bit about it (and
compare it to JIRA) ...

Boroondas