-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Cross-posted to trac-dev, as this thread should be moved there please reply only to trac-dev]
Olemis Lang skrev 04. juni 2009 22:29: > On Thu, Jun 4, 2009 at 2:07 PM, Eirik Schwenke > <[email protected]> wrote: >> >> I think we need to rethink (or document plainly on the wiki) the terms >> "trac user" and "trac developer". "trac end user" and "trac contributor" >> might be better labels, a contributor being anyone that submits code >> (python, javascript, html and templates) or documentation (wiki, >> newhelp) changes. >> > > Let me see if I get the idea : > > - Contributor : a contributor being anyone that submits code > (python, javascript, html and templates) or documentation (wiki, newhelp) > changes. (This one seems to be ok for me) > - Trac developer : What's the difference between a Trac dev and a contributor > that submits code ( checkin permissions ?) Yes, my thinking was that trac-dev would be someone with commit access. Apparently there should be no such thing as a trac dev, only trac commiters ... > - trac user" : ¿? > - trac end user: ¿? What's the difference No difference, "trac user" and "trac dev" are the only "old"/legacy terms that I've seen used before -- and my point was that those terms weren't all that helpful for discussion. As a side note, the term "trac dev" might be relevant as in: "trac-dev: someone that has a working knowledge of the internals of trac". These are all small details - I believe my original comments had something to do with defining the workflow, and the notion that not all contributors (eg: doc writers) are / should be trac devs. (...) >> I found: http://trac.edgewall.org/wiki/TranslationRu/TracAdmin, does >> this mean that case 4) would involve creating /TranslationJp/xx ? >> > > What about using Wiki Negotiation plugin ? Is that plugin alive/working ? I had forgotten all about it -- I assume you refer to: http://trac-hacks.org/wiki/TracWikiNegotiatorPlugin The example site appears to be down -- but that doesn't mean the plugin is dead. There's still a question of managing all this stuff, which is somewhat related to tagging/branching of documentation -- and possibly suggests some changes to the wiki in future releases of trac. An interesting project I worked with at the University of Trondheim had some useful features for managing documentation: a) each article is contained in an xml-file (analogous to a wiki page) b) each has an author/owner c) the system sends out mail to each owner after x months, asking them to verify that the article is still relevant, and either: 1) sign off (click "ok") 2) update and sign off (ie: edit, sign off) 3) delete it This is mostly workflow related, and could probably be implemented on top of either rest/sphinx and/or the wiki. The system is open, and has some multilingual content: http://infoweb.ntnu.no/about+infoweb/help/about.html (unfortunately it appears development is better maintainted than documentation, as can be seen from the warning on top of the following page): http://infoweb.ntnu.no/about+infoweb/info/technical.html - -e - -- .---. Eirik Schwenke <[email protected]> ( NSD ) Harald Hårfagresgate 29 Rom 150 '---' N-5007 Bergen tlf: (555) 889 13 GPG-key at pgp.mit.edu Id 0x8AA3392C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkos+7sACgkQxUW7FIqjOSxJ+gCgoCXQ0gjIfkF04aVx1ciLP2SI 7WwAn3dH104+1Z2HEgkKM01heVodO2KU =cIT9 -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
