Jeroen Ruigrok van der Werven kirjoitti: > -On [20071119 19:22], Erik Bray ([EMAIL PROTECTED]) wrote: >> A question about tobedeleted actually: Should it be used on tickets >> about configuration problems that have been marked invalid? Some of >> those have actual useful information in them, and also having more >> tickets about a configuration problem might increase the likelihood of >> someone searching for information about their problem to realize that >> they have a configuration problem and should ask on the mailing list >> or in IRC. > > From my point of view tobedeleted is only to be used for tickets that are > really apparent wrong tickets: people thinking t.e.o. is the trac instance for > $PROJECT_X. > > If the information in those invalid tickets is appropriate to avoid > configuration issues, I wonder why we don't add that to the documentation. > Referring to tickets for know-how seems a bit silly in my technical writing > point of view.
I agree. Since if it's know feature why it wouldn't be documented "properly". Specially, word "invalid" is defined to be something like this: "not valid: a: being without foundation or force in fact, truth, or law <an invalid assumption> <declared the will invalid> b: logically inconsequent" So actually it indicates that ticket contains something (or actually all since it's complete ticket flag) that is not right. For a first time Trac user refering to invalid ticket might be very confusing, saying "Look at ticket 123. It is invalid but it's still valid"... Huh? Of course I realize that collecting, organizing, rephrasing all that information takes resources - but isn't that something wiki is for? Trac is reaching point where complexity starts to reflect on quality of documentation. Most interesting thing that most of the time problem is not really Trac itself but things that it relies on - Apache config, Python config, Subversion libs... Maybe starting more directed "Trac Documentation Project" could be considered at some point. Make someone responsible that documentation is valid as it can be, it's structured, consistent, keep up list of "most wanted topics" lists etc. Just my 0.02... -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
