IdentifyingLocalUsersandGroups

Differences between revisions 2 and 3
Revision 2 as of 2007-10-29 21:39:05
Size: 3817
Editor: 12
Comment:
Revision 3 as of 2007-10-30 22:46:23
Size: 4243
Editor: pppoe-88-147-182-186
Comment:
Deletions are marked like this. Additions are marked like this.
Line 91: Line 91:
=== Comments ===

One can organize simple lookup database to map user browser settings (locale) to LoCo Team and suggest user to go Ubuntu LoCo Team site right at ubuntu.com front page. This will work even for non-ubuntu users and help to find on-line resources before trying ubuntu, which is important in some cases and will help to make decision to switch from other OS. -- -- Agafonov [[DateTime(2007-10-30T22:46:23Z)]]

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

The aim of this spec is to discuss how we can use the location of the user (gathered in the installer) to inform them of their local LoCo team and other local resources. This spec is also intended to discuss the validity of users opting in to be counted so we can get an idea of usage - this would be via a button in the installer.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.

Rationale

* Involving people in Ubuntu more - LoCo Teams / LUGs * Users can specify their location during/after install which triggers presentation of information

  • Support groups
  • Mailing lists
  • LoCo Teams (approved vs non-approved)

Use Cases

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.

Outstanding Issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

  • Menu item for "Local Community Support"
  • Detect location from values entered during installation
  • Allow overriding (people tend to move to different places Funny :))

  • Include LUGs (on an opt-in basis)
  • Firefox Plugin that sets local community resources
  • List services provided by LoCos / LUGs

  • Stuff browser bookmarks full of links to appropriate resources, and also the non-local ones
  • Big list by geographic region, showing countries, languages spoken
  • No one reads the "Welcome to Ubuntu" firefox page, so not worth linking there.
  • During installation have a "slideshow" (like the windows install does)
    • Make the Ubiquity percentage bar window bigger, with a bitmap/text area like windows installs Wink ;)

      • "Here's where you get support"
      • "Here's how you can contribute to Ubuntu"
  • Shipit - tuck in your business card into the CD sleeves before you give them away.

Typical resources linked to

  • Home page of LoCo / LUG

  • Mailing list
  • Forums
  • IRC channels
  • Meeting dates / times / locations
  • Launchpad Answers
  • Phone number of the LoCo contact Smile :)

Comments

One can organize simple lookup database to map user browser settings (locale) to LoCo Team and suggest user to go Ubuntu LoCo Team site right at ubuntu.com front page. This will work even for non-ubuntu users and help to find on-line resources before trying ubuntu, which is important in some cases and will help to make decision to switch from other OS. -- -- Agafonov DateTime(2007-10-30T22:46:23Z)


CategorySpec

IdentifyingLocalUsersandGroups (last edited 2008-08-06 16:35:49 by localhost)