On Jun 4, 10:38 am, Eirik Schwenke <eirik.schwe...@nsd.uib.no> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Christian Boos skrev 03. juni 2009 23:37: > > > yoheeb wrote: > > One of the things I've found very useful in MoinMoin wikis (and > > certainly many other wikis have this feature but Trac), is the ability ...for the record, I didn't write that, so no, I can't elaborate on what I meant, but it does sound rather insightful... :D I have been misquoted! oh no, it's on the internet, it must be true!
As an observation, here's is what I think seems to of washed out of this hijacked thread so far in terms of intent.... maybe we should have an "adopt-a-wiki-page" type thing, similar to adopt-a-hack on track hacks. "someone" can adopt a page, and either be notified of changes by one of the notify type plugins, and have the chance to "moderate" the changes. Or be given "exclusive" (by that, I mean, in addition to all the people that actually maintain trac) to edit that page specifically, and the edgewall site could create "components" for each of the top level wiki pages (or a "suggest a new top level topic" as well) for the purpose of people to suggest updates to topic X, with topic "x" automatically getting a CC and choosing to "close" the ticket. If a topic doesn't have an owner, the top guys can make the stub, update the ticket so the post has the option to adopt it, or someone else can adopt it. Also, we could, for example, "standardize" on a convention for recipe naming: SomeWikiTopic/Recipes/HowtoDoSomethingCool SomeWikiTopic/Recipes/HowtoDoSomethingMoreCool SomeOtherTopic/Recipes/HowtoDoSomethingLame so each topic could have a topic specific "Recipies" TitleIndex section in it somewhere. Some top level page could collate all "*/Recipies/* pages etc. What'cha think? [note: long winded example follows:] The Recipe pages could also link to their parent, or EVEN have sub recipes: ApacheSetup/ModPython/Recipies/Windows ApacheSetup/ModPython/Recipies/Windows/Recipes/LDAP ApacheSetup/Recipies/ModPython/Windows ApacheSetup/ModPython/Recipies/Ubuntu ApacheSetup/WSGI/Recipies/VirtualServers ApacheSetup/SubversionAuth/Recipes/httauth etc. Now, for the sake of argument. Lets say we used the ticket idea mentioned above. I need some information: I find ApacheSetup I find there is a recipe for modpython on windows I find there is a sub-topic page on WSGI I see there Isn't a sub-topic page on WSGI on windows, or recipe page. I use everything I get from the main apace topic, the wsgi topic, and the modpython recipe to get close. I go to the usergroup, get some help to find out how to get the details working out. I go the the ApacheSetup/WSGI page, click the link for "request a change or correction to this page" (I am assuming we put them on all the pages in this model) I get a ticket, with ApacheSetup-WSGI as the component. somewhere I can fill in something that says RECIPE (keyword, new type, custom field, whatever) I "suggest" a new recipe: I wiki format an Apache/WSGI/Recipes/Windows page, with all that I learned. The owner of the page, (if already adopted) can moderate this info, maybe contact me, and very possibly choose to add it to the the WSGI/Recipies/Windows page. They could even offer to have ME become the owner, or "abandon" that particular sub page, letting myself, or someone else adopt just that recipe. I am on windows Or in short form, Lets have topics be parents of recipes. If there isn't an appropriate topic, there probably should one. ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
