ToDo list

This is a list of ideas which are deemed either sorely needed, useful or interesting. If you're looking for something to help out with, look no further!

Royal pains in the arse

• Publicise. Srsly, need wider exposure.
• Use Template:Backto at the foot of each page
• Hunt for links to and bypass redirects

✓

• Roll out the setlist template

✓

• Replace all instances of Image: with File:

Layout and appearance

• Hunt artefacts visible with various layout engines and fix them
• Investigate recent CSS implementation, seeing whether any could be used to improve MuseWiki's appearance
• Wade through our templates and simplify/prettify if at all possible
• Investigate, design and implement a way of laying out media verification hash tables within pages
• Typographical students and those in the know: check whether our conventions are correct
• People with Internet Explorer 8: Keep checking the wiki to make sure it displays decently with IE8. IE is notorious for its layout engine being incomplete and buggy and MuseWiki developers don't use Windows.
• Use <p> instead of <div> and tables where appropriate, instead using appropriate CSS rules.

Resources, searching and verification

• Scrape various media (anyone near a national library or a proficient human web-spider?) for press/coverage relating to Muse, add it to our reference archive
• Find circular references within MuseWiki articles, remove and provide rationale for doing so on the article's talk page.
• Get the official Muse board and Muselive to make sure topic IDs don't change. This is a real verification headache.
• Transcribe various audio and video interviews and add to our media reference archive.
• Transcribe articles which have yet to be transcribed and add to the archive.
• Add scans to archived articles for which scans are missing.
• Anyone who knows a language other than English: translate foreign-language articles and add to our media reference archive.
  • Check the accuracy of translated articles.
• Use our reference archive to write and/or expand MuseWiki articles, adding references as appropriate.
• Write comprehensive help.

Files

• Hunt authorship and source information for uploaded files, tell authors about creative commons and ask whether they'd be happy licensing under a CC licence (tres cool)
• Descriptions for files which currently have none

Gear

• Expand and clean up the gear section—particularly suited to musicians in the know.

Gigs

• For gigs you went to: add information. Please encourage others to do so as well!
• Make sure our links to recordings are up to date, add any that are missing.
• Use recordings to construct and complete speech tables.
  • Anyone who knows a language aside from English: transcribe and translate foreign speech.
• For gigs missing the venue in which they took place, find out the venue and set the Venue variable in the respective page's Gigbox.

Codemonkey bananas

• Use HTML5 audio instead of the flash player for Chrome, Firefox, Opera and Safari

Doesn't conform to old browsers, sorry but I'd like to see the day come, but it's not going to happen :( --crazybobbles 20:58, 23 September 2009 (BST)

Use CSS which old browsers don't understand to hide it from them. :P --Tene 21:19, 23 September 2009 (BST)

✓

• Make references work for people who are not logged in

Should work now i think...--crazybobbles 20:58, 23 September 2009 (BST)

Eeexcellent.... --Tene 21:19, 23 September 2009 (BST)

• TLS/SSL?

Why :( --crazybobbles 20:58, 23 September 2009 (BST)

We live in the UK foo', that shouldn't be a question that you have to ask. --Tene 21:19, 23 September 2009 (BST)

When is this gonna be implemented? Lazlo

• Set up wiki bots for admins

What kinda rules are we talking about? Would be pretty fun to experiment on this but need situations where bots are useful --crazybobbles 20:58, 23 September 2009 (BST)

One situation where it would be useful is removing unknown variables, another rolling out simple templates such as backto, another sweeping for Americanisms. :P --Tene 21:19, 23 September 2009 (BST)

• Get rid of px usage and use oooonly em

Meh they both have their uses :p --crazybobbles 20:58, 23 September 2009 (BST)

em should be preferred when it's not detrimental to do so /me rolls eyes. --Tene 21:19, 23 September 2009 (BST)

• (Really) fix titles containing ampersands

✓

• Fix titles containing plus signs

✓

• Find a way of adding a captcha box

✓

• Add standard CSS3 border rules. These are implemented in Firefox 4+ and Chrome.

Long-term

• Get each member of Muse to join and edit. Also known as "take over the world", with originality.

Go back to help