> Mel, what's your intention with the trac instance? Are any modules,
> etc. needed right away?
First intention with Trac is to use it as public milestone/task tracking
for:
* swag creation & delivery for upcoming TOS events (SIGCSE if it's up in
time, a POSSE curriculum dev sprint in May if not - things like "make
sure we have whiteboard markers!" and so forth)
* POSSE physical material production for specific workshop instances
("get 20 booklets printed and delivered to RIT, etc")
* POSSE administration and infrastructure for specific workshop
instances ("Find instructors for $foo, set up blog aggregator for $bar")
* PR and outreach milestones/targets (this quarter we're going to get
opensource.com/education articles on X, Y, and Z... next quarter we're
going to get PR for projects foo, bar, and baz... one sample ticket
might be "produce 60-second TOS overview video from SIGCSE footage" and
so forth.)
(I'm getting all these tasks from
http://teachingopensource.org/index.php/Red_Hat_education_strategy, but
this isn't meant to be a Red Hat Strategy Exclusive Trac Instance, I
just want to be able to do all the work I'm doing "upstream" publicly...
if people are working on conference tracks, papers, workshops, events,
textbook material, etc. that's "upstream TOS" they should be able to
make components for that too.)
I'm used to being a trac admin and can set milestones, etc. via the web
interface if given privs.
Hope this clarifies?
--Mel
_______________________________________________
tos mailing list
tos@teachingopensource.org
http://teachingopensource.org/mailman/listinfo/tos
