wiki

wiki@lists.fedoraproject.org

139 discussions

Draft template on the wiki
by Karsten Wade 10 Jul '10

10 Jul '10

Have you ever used {{draft}}/{Draft}} at the top of a wiki page before? I noticed today that it was set to put pages in [[Category:Draft documentation]]: https://fedoraproject.org/wiki/Category:Draft_documentation The idea behind that category is to act as a queue for people wanting to help edit documentation pages in-progress. I just switched around things a bit, and now we have this: {{Draft}} puts pages in [[Category:Drafts]] https://fedoraproject.org/wiki/Category:Drafts {{Draft documentation}} (NEW!) puts pages in [[Category:Draft documentation]] https://fedoraproject.org/wiki/Category:Draft_documentation The draft documentation category is for pages that people are writing to document something, and they i) want help, and ii) want to warn people from relying on the content yet. ** It's a queue for us to help each other with proper ** documentation. The draft category is for any page that is a draft. People using the plain draft template likely want to warn people from relying on the content yet, but may not want help. ** It's a queue for us to help each other with wiki gardening. We also had some ideas of what to do with [[Category:Documentation]], but I'll leave that to another thread. - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41

2 1

documentation category ideas
by Karsten Wade 10 Jul '10

10 Jul '10

I think this is a summary of the ideas we had on IRC on how to use [[Category:Documentation]]: 0. Pages belong in the category or a sub-category because they document something. How to do something, what something is, why Fedora uses something. 1. Mainly it is a parent-category. 2. Actual pages are usually in one or more sub-categories that are an area of documentation. Examples: Policy; Proposal; Conference; Application/Program; [[Category:Draft documentation]] is clearly a sub-category of "Documentation". A sub-project might also put documentation that covers their area of the project in their category. For example, [[Category:QA Project documentation]] would also be in the [[Category:QA Project]], just as [[Category:QA documentation]] (for the general public) would be in the general interest [[Category:QA]]. Questions: * What are some further ideas for sub-categories? * Do we want to follow a prescriptive or natural language naming scheme for the sub-categories? For example: For several years I have been putting pages in [[Category:How to]]: https://fedoraproject.org/wiki/Category:How_to Looks like others have picked that up. When I say prescriptive, we would want that to be [[Category:How to documentation]]. Natural language would leave it as "How to". How does this look for other ideas? "Policy" vs. "Policy documentation" "FUDCon" vs. "FUDCon documentation" "Application" vs. "Application documentation" or even "Koji" vs. "Koji documentation" (which could be a sub-category to "What is" and "How to" categories.) cheers - Karsten, wiki troublemaker -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41

1 0

better watched page notices
by Karsten Wade 09 Jul '10

09 Jul '10

The only thing I really miss from our old wiki is that it would notify you of a page change every single time, with an inline diff of the changes as well as the change summary. *sigh* I miss that. I _know_ MediaWiki is a different culture and the page watching tools work for that, but they don't work here. Fedora Project is a mailing list/email culture - all of our tools that do stuff send reports out via email (to lists, aliases, individuals, etc.) One of the most important tools we use, the wiki, sends out truncated reports with too little data that stop coming if you don't click through on the link. I'm discouraged because I quickly fall behind on the pages I'm watching, remain unsure of which ones are out there, etc. I'm sure I could go to some config pages and reset my watched page count or something, but my point is ... I don't want to go to any webpages for this stuff. I don't mind having to click-through on an edit to patrol it, that's a fair task to do when patrolling edits. Is there anything that we can do here? Any tool to use or adopt? Should I start my research again, or do our MediaWiki heads have some ideas? Thanks - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41

2 1

Wiki help
by Mark 05 Jul '10

05 Jul '10

Hello, I dont have lots of extra time, but, I am more than willing to help out with wiki help. Let me know what I can do. -Mark

3 4

untouched pages: delete 'em?
by Ian Weller 03 Jul '10

03 Jul '10

There's quite a few pages that haven't been touched since their import from MoinMoin, and I'm thinking about mass-deleting 'em. Process for doing so: 1) write script that finds pages that haven't been touched by anybody except ImportUser and Admin 1.5) blog loudly 2) write [[Template:Quarantine]], which will throw pages that transclude it in [[Category:Quarantine]] and explain that the page will be deleted on or after September 1 if the template is not removed 3) write script to mass-delete everything in [[Category:Quarantine]] on September 1 If somebody wants a page back and nobody did anything about the template, pages can still be restored by an admin. Thoughts? I want to make sure that we have a pretty solid consensus here before I go forth with this. -- Ian Weller <ian(a)ianweller.org> () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

7 17

Some wiki article names are ambiguous
by Aaron Faanes 30 Jun '10

30 Jun '10

I feel like there's usability issues with some articles in the Fedora Project wiki. Here's a sample of some of them: * Websites * Women * L10N * Overview I believe that these pages should be renamed to be more indicative of their content. Specifically, "Fedora" should be included for project pages, non-wiki-like titles such as "Overview" should be renamed, and esoteric abbreviations like L10N should be expanded. * Websites -> Fedora Websites * Women -> Fedora Women * L10N -> Fedora Localization * Overview -> Fedora Project (or perhaps simply Fedora) Most pages should not include Fedora, since the Fedora wiki already implies a bias towards Fedora-related information. For example, I expect a page on Red Hat contributions to contain contributions that Red Hat has made to Fedora, so I feel like this is a suitable name. I don't think this bias is a strong enough reason to exclude it from project pages. I'm not likely to assume that page called "Websites" is a project page since the name gives me no indication. The repetition of "Fedora" and the capitalization in "Fedora Websites" in the URL reinforces the fact that the page is about a group called "Fedora Websites," rather than websites in Fedora. Redirects from "Fedora *" do not sufficiently solve the problem. The title on the article page will still be without "Fedora" and so will still evoke confusion. Tooltips shown by mousing over a link will also show this ambiguous title. Ordinarily, I wouldn't think the repetition of "Fedora" is necessary. http://fedoraproject.org/docs reads much better than http://fedoraproject.org/fedora_docs. This is because I read it as "the docs page in the Fedora Project" and I am not confused. More importantly, I don't have any learned expectations about its content. Wiki pages do have learned expectations. When given a URL to a wiki page, I expect that the content will be an article, and I expect the last part of the URL is the article title. This is why URLs like http://en.wikipedia.org/wiki/Wiki do not strike me as redundant or confusing. On the other hand, I would be confused if http://en.wikipedia.org/wiki/Overview contained an overview of the Wikipedia. Our wiki sadly violates these expectations. We name some articles using a "naive" convention, so the page's subject is ambiguous. -- Aaron Faanes

2 1

Fedora wiki style guide
by Aaron Faanes 23 Jun '10

23 Jun '10

(This is a repost in order to start this thread in the wiki mailing list. Sorry for the noise.) Hey everyone, I've been working a lot with the Fedora wiki recently, and I've been accumulating some style ideas as I've been editing. I ended up writing some of my thoughts and suggestions: https://fedoraproject.org/wiki/User:Dafrito/Style_guide I'm interested in what you guys have to think about it - especially in what sections represent areas of consensus or disagreement. The guide uses a formal voice for clarity, but I intend for any guideline to be friendly, incremental, and flexible. It's not an all-or-nothing proposal. :) I mean no offense to any other editors, and I apologize in advance if I appear rude in the document. Thank you, -- Aaron Faanes

3 4

How to get *Collapsible tables* on wiki?
by He Rui 22 Jun '10

22 Jun '10

Greetings everyone, Glad to meet you here. I have a question about wiki syntax. I wanna have some Collapsible tables on my wiki pages, like http://en.wikipedia.org/wiki/Help:Collapsing But when I use the same example code as it suggested, it doesn't work on fedora wiki page, since the following js file is needed: http://en.wikipedia.org/wiki/MediaWiki:Common.js So I want to know if it is possible and allowable to have fedora wiki run this js? If yes, how to load this file? If no, is there any other way to have Collapsible tables on fedora wiki? Many thanks, Hurry (￣▽￣") -- Contacts Hurry FAS Name: Rhe Timezone: UTC+8 TEL: 86-010-62608141 IRC nick: rhe #fedora-qa #fedora-zh

2 2

Re: Fedora wiki style guide
by Karsten Wade 22 Jun '10

22 Jun '10

On Tue, Jun 22, 2010 at 05:31:46PM -0400, Ian Weller wrote: > On Tue, Jun 22, 2010 at 01:12:03PM -0500, Aaron Faanes wrote: > > I've been working a lot with the Fedora wiki recently, and I've been > > accumulating some style ideas as I've been editing. I ended up writing > > some of my thoughts and suggestions: > > > > https://fedoraproject.org/wiki/User:Dafrito/Style_guide > > > > I'm interested in what you guys have to think about it - especially in > > what sections represent areas of consensus or disagreement. > > > > The guide uses a formal voice for clarity, but I intend for any > > guideline to be friendly, incremental, and flexible. It's not an > > all-or-nothing proposal. :) I mean no offense to any other editors, > > and I apologize in advance if I appear rude in the document. > > This is very good. There's a few things that I'm going to change on it. > Would you mind subscribing to the wiki list and posting this there, too? > > https://admin.fedoraproject.org/mailman/listinfo/wiki Oh, yes, definitely, bring it over. (I'm switching my Cc: and will join the thread later, too.) Aaron, you are very much on the mark here. There is desire to adopt exactly the sort of conventions you write down. There is some inertia to deal with, but we can work through that. We've long stated that our *goal* is to be "do it like Wikipedia says to do it, except in these ways ..." and have a few, reasoned exceptions if necessary. For example, this page is specifically useful if you are writing in a MediaWiki syntax and want to convert later to DocBook XML: http://fedoraproject.org/wiki/Help:Wiki_syntax_and_markup#Marking_Technical… Those I would call guidelines on top of how to do things the Wikipedia way, and really most useful in the DocBook situation. However, having matching technical markup usage across the site would be a good thing anyway ... - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41

1 0

Re: Wiki question
by Eric Christensen 22 Jun '10

22 Jun '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/06/2010 04:27 PM, Rui Gouveia wrote: > Hi, > > I'm reorganizing the wiki pages for the pt_PT language. And I have some > doubts. I have browsed the help pages, but still, can't find the answers > I need. > > Should I create all the pt_PT pages like this? > > Original: https://fedoraproject.org/wiki/<PAGE> > Translated: https://fedoraproject.org/wiki/Pt_PT/<PAGE> > > or should I create the pages, like the one I'm translating now: > > https://fedoraproject.org/wiki/F13_one_page_release_notes/Pt_PT > > What's your preferred method? > > I looked at what other teams are doing and I find examples for both > ways. The Brasilean team alone uses them both. > > IMHO the Wiki is very "free style" and there's no specific rules for > translations. > > I would appreciate your advice. > > > Thanks for your time. > > Rui Gouveia > Portuguese translation team Good question. Ian, I think we need to have some sort of solution for translating the wiki. Any thoughts? How does Wikipedia do it? - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMFV/AAAoJEDbiLlqcYamx1KcQAIwHHWu791cjiNsF4mriEzYG XlB5ZA9MJ53qeR2UFchZSVll1ZjZCllbMC43gLUV5OUdNw6UMQNlKBpH1ef3b2Ob TG6KGaOOGFvjZbDZcZikgwKKmn0BnsFwRK+rwge+/KeLWSr21cvif11P4CueibiP bE/o/cr+8uaIsk6+zMpk1BmzfqZvj5bgQkQAipZF0kAmap/BzDJKTNHYx/LHC5RG qf0l9xxxmqmA0oHq5kpFcVbNQXFwCKulSM+1YRHn4zKfkgONt/VVdOJSES4fQgh9 KUfYlM+AapgMbur+fCwvoZMy3a9HuJ3EPIR7LrFNBVkKtf5Z43BihfZSKdeODeen AHXRrPE6iJ0gcKNo/dEGXOikjx0hj2d0RnKIhGAFv91gAp647nDjIZpVtujEEDVr VwRHnIfJ3CDxtwbvW7v5zj1IEnTm5OqfMdvIkqmsAdGqqJ1B3/denBhM26Ywr/PC 5X6N8VFvVXAzFmYENZWU8ejVQUrKbqpb45Wk6hRuF+HyMV9UIT+Ug8ayGxlD0g0a 4gntsv63mZU5ouZwa966WuJBynY/NABU28p0czoYleg9IgDjHzFY27MSZDh0Og8Y DpmlMG7kAmM2/hBBoEsnjxvnaBsqwigTeasuJLSD+O3UxUCMfHF3NGbMCT3AIylB 42O2Ritc/k10xLlo8uIb =HO+j -----END PGP SIGNATURE-----

3 5

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

wiki