[sldev] Fresh new code: eventlet and mulib

[aric rubin]

Hi,

Jumping in if I may, I'd suggest that the benefits of keeping all issues 
in one place (pjira) far outweigh the difficulties of the use of the 
application. I strongly recommend simply staying with pjira for bug 
tracking. It'll save us all cycles and pain in the long run.

aric

Ryan Williams (Which) wrote:
> I asked some questions in the previous email, but I don't think they
> were very well communicated because no one responded, let's try again.
> 
> 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?
>   Currently I think "no" because there's no noise problem on sldev, and
> we don't have a community of web devs contributing to eventlet and mulib
> but not to the viewer (though I expect/hope this will happen at some point).
> --- Should we track bugs in PJIRA, or in Trac?
> --- Should we put the documentation on wiki.sl.com, or in Trac?
>   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).
> 
> Thoughts?
> 
> -RYaN
> 
> P.S. Sorry there hasn't been more developing on these lately -- I've
> been sick.
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html