User talk:Bouncingmolar

Hi, regarding ampersands within an article, could you give me an example since I'm not sure what you mean? -- Barrylb 19:55, 23 May 2007 (UTC)

Re: Extension template
Please explain the rationale for changing a large number of extension pages to use a template which, so far as I can see, provides no additional benefit. Examples of this are, , and. robchurch | talk 14:27, 27 June 2007 (UTC)


 * Hi robchurch. Yes I have made a template called extension categorized which is a duplicate of the extension template. The only difference is that it does not contain the category:extension.
 * The rational behind this move is that I have been going through every single extension manually and sub categorizing them and placing them within the subcategory category:extensions by category. I created a duplicate template because it is easy to revert if my work is disputed with the trade off of having an identical duplicate template. However I hope that you can see that I am slowly making progress. Why remove the you may ask? Well the main reason is that it is extremely difficult to sub categorize the extensions because it is hard to tell which ones are already sub categorized. This way the sub categorized ones are nolonger within this category and the uncategorized ones are retained in the extension category. I was using the category convention used in wikipedia. I just assumed it applied to mediawiki as well.
 * "Articles should not usually be in both a category and its subcategory. For example Golden Gate Bridge is in Category:Suspension bridges, so it should not also be in Category:Bridges."
 * I realise this rule doesn't apply to everything so if you think I should revert them all once i've finished sub categorizing everything let me know... however sub categorizing is proving to be a very slow process.
 * -Bouncingmolar 14:48, 27 June 2007 (UTC)

In that case, please make the change to the template in use. We do not wish to encourage forking of templates with an identical purpose, as it doubles the maintenance overhead. I would suggest making a complete list of all pages which need to be processed prior to removing the categorisation from the template, and then updating these. robchurch | talk 14:57, 27 June 2007 (UTC)
 * I see what you are saying Rob; that we don't need identical templates because if a new version of the template is made we have to update both. However the templates are not identical (even if it is only a minor difference). The Main purpose of the alternative template is that it has the removed. The problem with  modifying the original template:extension is that the category:extension information is stored there!(as i mentioned on the category:extension talk page.) :If i remove the extension category from the template then un categorized extensions will not be listed in the main extension category nor the extension subcategories. Which is a problem! So what the modified template does is it allows me to retain the original template structure without removing the category from all of the uncategorized extensions. I hope that makes sense.
 * Bouncingmolar 15:06, 27 June 2007 (UTC)

No, the categorisation difference is trivial. As I suggested above, use a list to store current categorisations and update the pages with them, or keep a list of extension pages which have been updated.

The current behaviour, introducing a useless extra template that will need to be changed back later is disruptive and redundant. You also provided no justification in the form of edit summaries, which is considered courteous in the least. robchurch | talk 15:13, 27 June 2007 (UTC)
 * this discussion will be continued on the category:extension talk page Bouncingmolar 15:17, 27 June 2007 (UTC)


 * Okay, just stop it. If you want to categorize extensions, fine. Just don't use that forked template, template:extension categorized. It was never meant to be used. Use template:extension instead. Thanks. -- Sayuri 08:07, 11 July 2007 (UTC)
 * discussion continued on category:extension talk page Bouncingmolar 05:10, 14 July 2007 (UTC)

Stuff to do
Hi, I've run out of stuff to do with the extensions. Maybe while i wait I can help with the extensions on meta somehow? or if you have another job? Bouncingmolar 14:29, 16 July 2007 (UTC)
 * OK - how's this one for size! :-) Category talk:Extensions --HappyDog 20:45, 16 July 2007 (UTC)

Your visit on Bluecortex.com
Hi - just to let you know I will be focusing my efforts on from now on. Pretty much all extensions I have on [http:bluecortex.com] will make their way to BizzWiki. Jean-Lou Dupont 15:16, 26 July 2007 (UTC)

What about JS code?
I'll be coming out with some JS code for handling forms. This will be part of BizzWiki. Can I post the code in the 'extension' namespace? Jean-Lou Dupont 15:58, 26 July 2007 (UTC)
 * Yes. The extension namespace is a place for all third-party extensions, whether they are installed via the built-in extension mechanism, by code modifications (hacks) or as custom javascript. --HappyDog 22:13, 26 July 2007 (UTC)

Proposed Extension subcategory tree

 * Authentication and Authorization Extensions
 * Authentication and Login
 * Page Access Control Extensions
 * Advertising extension
 * Ajax extensions
 * Calculation
 * Calendar extensions
 * Category extensions
 * Chat extensions
 * Data extraction extensions
 * Discussion and Forum Extensions
 * Edit extensions
 * Email extensions
 * Feed generator extensions
 * Firefox Extensions
 * Form extensions
 * Extensions GIS
 * Google extensions
 * Graph extensions
 * Integration
 * Internationalization Extensions
 * Interwiki extensions
 * List extensions
 * Log extensions
 * Map extensions
 * Media handling extensions
 * MediaWiki authentication
 * MediaWiki tools
 * Namespace extensions
 * Page Access Control Extensions
 * Navigation extensions
 * Category extensions
 * Output extensions
 * Page management extensions
 * RSS Extensions
 * Redirect extensions
 * Referencing extensions
 * Script embedding extensions
 * Search extensions
 * Google extensions
 * Sort extensions
 * Subpage extensions
 * Syntax highlighting
 * Template extensions
 * Parser function extensions
 * Uncategorized extension
 * User management extensions
 * User notification
 * Variables extensions
 * WYSIWYG extensions

Yes, yes, and yes
I'd be delighted for your help. There is so much to do and your perspective as an administrator of a small office wiki is especially valuable. There are lots of things that don't need coding skill. However, to encourage you to Be Bold!, I've also added Template:CodeReviewNeeded.

Things that need to be done:
 * extensions by visual element/audio element/integration target/content source don't need coding expertise. There are a lot of extensions that need to be categorized under one or more of these.  You might try reading through Category:Tag extensions or Category:Parser function extensions or Category:Special page extensions to see if you can find extensions that are missing categories.  I also sometimes search for a keyword, e.g. YouTube or Google to find all extensions that might require a particular integration target/have a particular visual element, etc.
 * monitor new extension creation to clean up template, categorization, readability of documentation, etc. Your judgements of readability I think are particularly valuable, precisely because you aren't a coding expert.  Documentation needs to be understandable without the code.
 * clean-up: e.g. nix the off-site extension category (it seems like there is a consensus for that)
 * extensions requiring patches - I've been adding a Template:Extension by patch warning to these so that administrators know what they are getting into

Also check the to-do list on my user page for more ideas. Cheers, Egfrank 06:58, 25 September 2007 (UTC)

PS. If you think any of the above belongs on the Category_talk:Extensions page or some other suitable place, please feel free to move it.