First of all, *applause* to Matt and Allegheny for stepping up here -- I personally think it would be awesome to have TOS infrastructure distributed amongst various schools, and having them come alongside OSU and Seneca in doing this is a big step in that direction. Thanks, Matt!
> Matt and I talked somewhat, and I think the applications we need to > install on it are: > - gitosis (handles git hosting and authentication) > - redmine (handles wiki, tickets, code viewing, and more) Question -- is the intent here to quickly set up services we don't already have and are not on OSU's list of "software that is really easy for us to install" (as in gitosis), or to migrate things from OSU (as in redmine)? The first sounds like a good idea, the second not so much, but that may just be me. Things I'd like to have up for POSSE, in priority order, that this box could host: * TOS Planet (http://tickets.teachingopensource.org/issues/4) -- no fallback, which is why this is priority #1. * An IRC proxy (http://tickets.teachingopensource.org/issues/35) -- no fallback, but we have done without in the past; priority #2. * Etherpad (http://tickets.teachingopensource.org/issues/35) -- fallback is to use a public site, which is ok but not the most reliable, and also no private option, which is an important feature. * Meetbot (http://tickets.teachingopensource.org/issues/10) -- fallback is to continue using Fedora's bot. Gitosis seems lower-priority than these four to me, but I'm admittedly biased. :) I'd argue that github already allows .edu folks to make private groups and accounts at no charge. --Mel _______________________________________________ tos mailing list tos@teachingopensource.org http://lists.teachingopensource.org/mailman/listinfo/tos
