We actually passed around the workflow chart you created in class today and talked about it. They were scared--very scared :)
Daniel Wang <[EMAIL PROTECTED]> wrote in message news:<b1p4q2$[EMAIL PROTECTED]>... > G. S. wrote: > > Daniel Wang: > > > > I'm teaching a technical writing class right now on "document > > management" and will be teaching other classes in the future. I'd > > like to set my students on the task of producing end-user > > documentation. I've been reading your posts, and it sounds like you > > want contributors to work on the FAQs, which will eventually be rolled > > into the mozilla builds. > > that's correct. > > > If I coordinate the student writing and edit it, then where do we go? > > I do not know. I've given up the ownership of the FAQ to the public, so > I will be fine if you coordinate the work in public or in private, as > long as the end result is accessible to the public. > > > What's up with the Zope project? > > I do not know either. You will need a multi-user account and I don't > know if Zope gives you that. And Zope's requirements on HTML (a good > format for publishing, but not for writing) would make me think twice. I > believe the people at zope read this forum, so expect some quick reply > from them on this :) > > > There are always tech writing classes and projects looking for work. > > If the submission process were more streamlined perhaps I could get a > > bunch of instructors together and get some continuing effort put > > toward this problem. > > You will have to talk with the zope people on this. > > Since you will have teams working consistantly on Mozilla documentation, > it will be nice if you collect feedbacks from your students once a while > and publish a newsletter on your documentation process. People who have > never done tech writing (including me, before the FAQ) might be > interested in reading about it.
