wiki July 2010

wiki@lists.fedoraproject.org

6 participants
8 discussions

Re: Broken redirects
by Sijis Aviles 31 Jul '10

31 Jul '10

On Wed, Jul 28, 2010 at 11:33 PM, Michael Price <michaelprice04(a)gmail.com> wrote: > While checking out the Broken redirects I noticed that the Category:Fedora > when searching under Categories the Fedora one has been deleted so should I > just delete Category:Fedora? Also I'm not really sure what to do with > Category:Usability because I can't even find it listed under Categories. > It looks like you were at this page on the wiki: https://fedoraproject.org/wiki/Special:BrokenRedirects The only thing i found on Usability was this page[1], however, i do not know if you can redirect a Category to a specific wiki page. Assuming we can determine how many pages are affected by these broken category links, if the number is low (less than 10) then i would probably delete it. Anyone have other ideas on how to handle this? Sijis [1] - https://fedoraproject.org/wiki/Usability

1 0

Re: Packaging page ... odd?
by Ian Weller 27 Jul '10

27 Jul '10

On Tue, Jul 27, 2010 at 05:07:22AM -0400, Michal Nowak wrote: > ----- "Dave Pawson" <dave.pawson(a)gmail.com> wrote: > > > Just been reading > > https://fedoraproject.org/wiki/Font_package_lifecycle > > and I noted that the table is cut off on the right? > > rhs cells don't show. > > Cleared by reducing the font on my screen? [Cntrl -] > > No horizontal scroll bar available to allow me to have the larger > > font > > and scroll over to see the content. > > > > there's so much CSS and js used I can't tell just what the problem > > is, > > but it is an accessibility issue for me. > > Looks like a general problem with Fedora wiki. Cc-ing webmaster. This is a problem we've had for a while -- hopefully the new website layout that's due at the release of F14 will fix the problems we've been having with tables. (On this table specifically, it shouldn't even be a table like this -- hard to read, navigate, and doesn't need to be tabular -- would be most readable if it were simply laid out in sections.. CCing wiki@ to see if somebody wants to volunteer to fix it.) :) -- Ian Weller <ian(a)ianweller.org> Where open source multiplies: http://opensource.com

1 0

Request for mentor
by Aaron Faanes 13 Jul '10

13 Jul '10

Hello all, I've already contributed a bit, but as I was reading Mike McGrath's "How to be a successful contributor" Wiki article[1], I realized that I hadn't really introduced myself. I also realized that I'd like a sponsor/mentor. This is my attempt to remedy both of those. ;) First of all, some quick facts[2]: My name is Aaron Faanes. My FAS account and IRC nick is dafrito. I live in the central timezone. I've been using *nix in some form for the past few years. I ran FreeBSD a few years ago, then Ubuntu for about a year. I saw a talk by Greg Kroah-Hartman that praised Fedora and Red Hat for their commitment to upstream, so I switched and have been using it almost exclusively ever since. I'm a jack-of-all-trades sort of person. I've got a few years of coding experience (python, java, lua, bash, javascript) working on the tooling/docs/support side of things. Consequently, I feel like I could have posted this sponsor request to the test, docs, and websites mailing lists all with similar levels of enthusiasm. However, I decided to request a wiki mentor since the wiki seems to be where I've found my groove. I've done some writing[3], some template work[4], and I'd be interested to continue that work. I've also made some suggestions (some good, some not-so-good ;) ), and I'd like to work with a sponsor to guide me towards the ideas that have consensus and interest. I've also had an interest in being an admin for the Wiki, so a sponsor could help see if I'm up for that task as well. I'd like to start small. I feel like there's a tendency, at least for myself, to dive into too much and get overwhelmed, so I feel like a sponsor would help ensure that things don't get too crazy. As far as timing is concerned, I can commit two to three afternoons (10-15 hours) a week. Thank you for your consideration, Aaron Faanes [1] https://fedoraproject.org/wiki/How_to_be_a_successful_contributor [2] For some more information: https://fedoraproject.org/wiki/User:Dafrito [3] https://fedoraproject.org/wiki/Special:Contributions/Dafrito [4] Templates that I've worked on: * https://fedoraproject.org/wiki/Template:Infobox_package * https://fedoraproject.org/wiki/Template:Infobox_group * https://fedoraproject.org/wiki/Template:Delete

4 9

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

11 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 11 Jul '10

11 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 06 Jul '10

06 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

wiki July 2010