Thread: Need wiki help: Advocacy TODO page
WWW, I'd like to set up an Advocacy TODO page. So, first thing, I'd like to be able to re-use the TODO list template; how do I create a new page which uses those templates (assume no Mediawiki internals knowledge). Second, I'd like to extend the template (this is less important), to support adding a list of people "claiming" a TODO item. Each claim should include a message link. I think this would be valuable for the hacking TODO as well. -- Josh Berkus PostgreSQL Experts Inc. www.pgexperts.com
Isn't this a wiki thing? gb.- On Thu, Aug 20, 2009 at 2:15 PM, Josh Berkus<josh@agliodbs.com> wrote: > WWW, > > I'd like to set up an Advocacy TODO page. So, first thing, I'd like to > be able to re-use the TODO list template; how do I create a new page > which uses those templates (assume no Mediawiki internals knowledge). > > Second, I'd like to extend the template (this is less important), to > support adding a list of people "claiming" a TODO item. Each claim > should include a message link. I think this would be valuable for the > hacking TODO as well. > > -- > Josh Berkus > PostgreSQL Experts Inc. > www.pgexperts.com > > -- > Sent via pgsql-www mailing list (pgsql-www@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-www >
> Why not reuse the commitfest app for this? Mostly because I'd need several changes to it, and I don't want to mess with Robert's development of the app for CFs. -- Josh Berkus PostgreSQL Experts Inc. www.pgexperts.com
On 8/20/09 10:55 AM, Guido Barosio wrote: > Isn't this a wiki thing? Yes, that's why I asked for wiki help. See subject line. -- Josh Berkus PostgreSQL Experts Inc. www.pgexperts.com
LMAO, still waking up :/ On Thu, Aug 20, 2009 at 3:04 PM, Josh Berkus<josh@agliodbs.com> wrote: > On 8/20/09 10:55 AM, Guido Barosio wrote: >> Isn't this a wiki thing? > > Yes, that's why I asked for wiki help. See subject line. > > > -- > Josh Berkus > PostgreSQL Experts Inc. > www.pgexperts.com >
2009/8/21 Josh Berkus <josh@agliodbs.com>: > I'd like to set up an Advocacy TODO page. So, first thing, I'd like to > be able to re-use the TODO list template; how do I create a new page > which uses those templates (assume no Mediawiki internals knowledge). There's really nothing to it. Those templates will work on any page, there are no special requirements or configurations needed. The commitfest templates were a bit of a special case -- getting the layout working the way we wanted required some sorcery. The Todo is a lot more straightforward. I have created a basic todo page at http://wiki.postgresql.org/wiki/Advocacy_Todo, with an example TodoItem. Feel free to replace it with genuine items, using the TodoItem templates just as you would on the dev Todo. Feel free to change the wording in the intro paragraph, and if you don't like the section headings or the TOC, just delete/change them. > > Second, I'd like to extend the template (this is less important), to > support adding a list of people "claiming" a TODO item. Each claim > should include a message link. I think this would be valuable for the > hacking TODO as well. > I'm not sure how valuable it would be to complicate the TodoItem templates the way you describe. The template includes a free-text entry area after the short name for the item, and that's where we have (so far) been keeping links to relevant messages and commentary. There's nothing stopping you from putting e.g. "Claimed by Josh Berkus (see {{messageLink|...}})" in there, and adding parameters for this to the template is unlikely to save you a significant number of keystrokes. The real value of templates is in factoring out the wiki formatting and layout stuff, but I don't think a "claimed by" list really warrants its own special layout. In particular, I wouldn't want to try to put the todo items into a table, since tables were what made the CF templates so fragile and stopped the per-section edit links from working. Cheers, BJ
> I'm not sure how valuable it would be to complicate the TodoItem
> templates the way you describe. The template includes a free-text
> entry area after the short name for the item, and that's where we have
> (so far) been keeping links to relevant messages and commentary.
> There's nothing stopping you from putting e.g. "Claimed by Josh Berkus
> (see {{messageLink|...}})" in there, and adding parameters for this to
> the template is unlikely to save you a significant number of
> keystrokes.
If messagelinks already work, that's at least half the battle. I'll try
it as-is and ask for more help if more is needed.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
Brendan Jurd escribió: > I have created a basic todo page at > http://wiki.postgresql.org/wiki/Advocacy_Todo, with an example > TodoItem. Feel free to replace it with genuine items, using the > TodoItem templates just as you would on the dev Todo. Why not follow Selena's lead and name the page Advocacy/Todo? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
2009/8/22 Alvaro Herrera <alvherre@commandprompt.com>: > > Why not follow Selena's lead and name the page Advocacy/Todo? Well, I put the content under Advocacy_Todo because that page already existed (albeit empty) and it seemed a logical naming, consistent with our approach elsewhere on the wiki. We *could* use subpages for Advocacy, sure. Buta) I don't know all the implications of using subpages versus the standard scheme.b) We don't do that anywhere else in the wiki, so it's kinda out of left field.c) Wikipedia specificallydisallows the use of subpages in the main namespace, because trying to organise things into a topical hierarchy proved counterproductive. I'm not suggesting we have to do whatever Wikipedia does, but they are the organisation with the most field experience using mediawiki, so it might be useful to take advantage of their lessons learned. Personally I'd be more inclined to just put all of the Advocacy-related pages into Category:Advocacy. Cheers, BJ
Brendan Jurd a écrit : > 2009/8/22 Alvaro Herrera <alvherre@commandprompt.com>: >> Why not follow Selena's lead and name the page Advocacy/Todo? > > Well, I put the content under Advocacy_Todo because that page already > existed (albeit empty) and it seemed a logical naming, consistent with > our approach elsewhere on the wiki. > > We *could* use subpages for Advocacy, sure. But > a) I don't know all the implications of using subpages versus the > standard scheme. > b) We don't do that anywhere else in the wiki, so it's kinda out of left field. > c) Wikipedia specifically disallows the use of subpages in the main > namespace, because trying to organise things into a topical hierarchy > proved counterproductive. I'm not suggesting we have to do whatever > Wikipedia does, but they are the organisation with the most field > experience using mediawiki, so it might be useful to take advantage of > their lessons learned. > > Personally I'd be more inclined to just put all of the > Advocacy-related pages into Category:Advocacy. > i totally agree on this. i see at least two other categories in the wiki that could be "knowledge base" and "developpers", something like that... Anyway the first good thing about using an advocacy category is that we will have to go through all the wiki pages and check for orphans pages. I'm volunteer to start this category and add pages into it !
Alvaro Herrera a écrit : > damien clochard escribió: > >> i totally agree on this. i see at least two other categories in the wiki >> that could be "knowledge base" and "developpers", something like that... >> >> Anyway the first good thing about using an advocacy category is that we >> will have to go through all the wiki pages and check for orphans pages. >> >> I'm volunteer to start this category and add pages into it ! > > Please go ahead :-) > http://wiki.postgresql.org/wiki/Category:Advocacy done :) From now on, if you create an Advocacy related page, please add the following tag wherever you want inside the page : [[Category:Advocacy]]