Contributor xiota

Many GUI configuration utilities work by modifying config files. They should tell the users what files they modify and the modifications they make because sometimes it's easier, faster, or necessary to edit configuration files for functionality the GUI tool does not support, but figuring out what files are involved can be more difficult than actually making the changes.

Even if users don't intend to edit the configuration files, knowing which files are modified and how will help users to build accurate mental models about the tools they use, which will help them to effectively use those tools to accomplish their goals.

Some pages listing ideas include a search box in the upper-right of the screen (eg, "Most popular today"), others don't (eg, "Random ideas"). They should all include a search box.

Maybe the "Search ideas" link on the left can be replaced with a search box? Searching shouldn't be a two step process.

Obvious. Self explanatory. No description needed.

Special versions of Ubuntu can be put on 3-inch/80mm mini-CDs or mini-DVDs. Then they can be packaged with the toy plushies in this idea: http://brainstorm.ubuntu.com/idea/4270/

The kids get a new toy. The grown-ups get a new operating system.

Patch GNOME to fix the following behavior: Almost anything the user does to remove or prevent the file ~/.recently-used.xbel from being used fails, including:

* deleting it
* changing permissions to 000, 444, 400, etc
* changing user to root
* changing group to root
* linking to another file like /dev/null

In each case, or combinations, GNOME resets the file user, group, and permissions and continues to use the file. If a user expends that much effort to remove or prevent a file from being used, it shouldn't be used.

Let users mark up their descriptions using Markdown. Existing descriptions would be unlikely to be negatively affected.

Here are some relevent links:

* http://daringfireball.net/projects/markdown/
* http://michelf.com/projects/php-markdown/

Some people vote against ideas, not because they're bad, but because they're not related to Ubuntu (or operating systems in general), they're out of Canonical's control, or they're likely to be a low priority for Canonical in the foreseeable future.

There should be a brainstorm sister site, or a section of brainstorm, devoted to these types of ideas. Users who want to stare at non-Ubuntu-related ideas can go to the sister site. Users who want to focus on Ubuntu-only ideas don't.

Then people can vote on ideas based on whether the idea is good or bad, not how they think the idea relates to Ubuntu or Canonical or others. Results from the sister site can periodically be forwarded to relevant developers, or can be used by Canonical some day when it decides to expand operations.

Each version of Ubuntu is named after an animal. There should be a back-story for each animal that explains why the warthog's warty, the hedgehog's hoary, the badger's breezy, etc.

Each story should also have some type of moral related to the philosophy of ubuntu. And pictures... It should be suitable bed-time reading for children.

Then the picture book can be packaged with the corresponding toy plushy from this idea: http://brainstorm.ubuntu.com/idea/4270/

And the Ubuntu distribution from this idea: http://brainstorm.ubuntu.com/idea/4590/

Make an Ubuntu game that features the mascots of each new Ubuntu version (Warthog, Hedgehog, Badger, Drake, etc). Or maybe a series of games that each features a different mascot. They should be good small time wasters that cover a variety of game types (action, arcade, educational, puzzle, etc), except for the LTS releases. The games for those should be bigger and longer (like an RPG or adventure game). They can feature characters from previous releases.

Add a default shortcut or launcher in new accounts to run a terminal. I know new users want to avoid the terminal, but it's an rite of passage that all Linux users should eventually go through.

In practice, sometimes a command-line solution is preferable to a GUI solution. For example, when the choice is between copying and pasting a single command -vs- a lot of searching for the right buttons to click and still having to type some configuration details and possibly having the new configuration not persist across reboots.

There is Ctrl+Alt+F1, but I'd expect new users to be more scared of that than the gnome-terminal.

Password delays don't actually increase security. They just make password typos more annoying. New users (coming from other OSes) already think passwords are annoying. Annoying them further will encourage them to avoid Linux or to adopt lax security measures (such as auto-login or 'asdf' passwords).

Removing password delays may result in an increase of the number of incorrect password retries users make, so the limit should be increased to prevent users from locking themselves out of their accounts.

Users should also be sent an administrative email to notify them of failed attempts to access their account so they can decide whether they should change their password.

Double clicking should only run applications that are already installed (most likely through apt). Executables should not be executed when double-clicked. This idea does not affect data files (such as pdf, png, svg, odf, mp3, ogm, mkv, avi, xyz, etc.) -- only executables, files with the +x permission set.

Clicking and double-clicking on icons is too easy. What if a user accidentally double clicks a script "wipe-out-home-directory.sh" when intending only to select for deletion? ... Good bye data. ... This might happen while tapping on a touchpad to drag to the trash. Two-taps = execute. Two-taps+slide = drag. This distinction would be difficult for people with a tremor or people in a situation that mimics a tremor, like a moving vehicle.

Executables and scripts should require a right click, possibly with additional confirmation, to decrease the chance of executing a file unintentionally. This would be equivalent to typing the path to an executable at a terminal to prevent users from running files they do not intend to run.

The 'rm' command, typed at the terminal, is dangerous and irreversible. Instead of deleting files immediately, 'rm' should send files to the Trash. This would be useful in cases where users might type something like 'rm -r temp *', when 'rm -r temp\ *' is intended. (Warning: Do not try those commands. I include them here for illustrative purposes only.)