[FM Discuss] FM Upstream

[Anne Gentle]

In my other work as a tech writer, it's often easiest to just be tracking
doc in the trac system with all the dev folks (which is what I meant
previously when I said def, woops). Are typos far more embarrassing as a
writer? :)

That said, is it possible to mark bugs as "doc request" or "doc change" in
trac? I'll have to poke around a little bit myself to see if it appears
do-able. I don't expect doc fixes to take up a lot of room or make reporting
more difficult for dev bugs, but I'll take that potential tradeoff into
consideration as well. Once I get a feel for what might work well, I'll
write up a proposal (brief!). I do like Adam's idea of a "manual planner,"
in FM, though.

Are SugarLabs tracked in OLPC's trac? I have an account there, but if I need
another one, let me know.

I've also taken a look at the link you've sent, David, and the only
organization I'd add on top of the nice start you have is to separate out
"end user" docs from "programmers" docs, if that makes sense to you guys.

And a fall book sprint would be awesome to start planning now. Let me know
how I can help.
Thanks!
Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.flossmanuals.net/pipermail/discuss-flossmanuals.net/attachments/20080628/696175de/attachment.htm>