Unifying LoCo Team Resources w/Launchpad

Include(LoCoMenuHeader)

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.

• Launchpad entry: https://features.launchpad.net/distros/ubuntu/+spec/unifying-loco-resources-with-launchpad

• Created: 09 Nov 2006

• Packages affected:

Summary

This spec discusses expanding Launchpad to centralize and ease the creation and management of LoCo team frequently requested resources.

Rationale

Right now, LoCo teams need a collection of resources to work. Of course, these vary between different teams, but there is a core of resources that are commonly used by teams. This includes essential resources such as:

• Website
• Mailing list
• IRC
• Domain
• Forums

But, also includes non-essential, but useful resources such as:

• Planet
• User map

At the moment some of these resources are centralised (mailing lists, IRC, domains), but many are not and the LoCo team need to research, install and run seperate software to get up and running. In addition to this, there is the problem of commonality of resources. As an example, there is no central place for all of the LoCo team planets, they are instead interspersed across the net.

Use cases

• Joey is the lead of an approved LoCo team. He wants to be able to create common resources for his team such as mailing lists, webpages, and websites. Unfortunately he is not technical and doesn't have hosting resources available to him. He would procede to his LoCo Team's entry in Launchpad as the owner/administrator and select the resources he needs from a menu of available services. These are then created and mailed back to him and/or the members listed on the team page.

• Dick is a new/perspective member of a LoCo team. His local contact provides him with the launchpad address for his team. He signs up for launchpad, joins the team, and then from a single page adds himself to the mailing list, users list, adds his blog to the team's planet, and signs up to the team's forums. He is now fully connected with the team.

• Jono is the community leader and he wants to view details about a specific LoCo team. He heads to launchpad's master LoCo team and selects on the Colorado Loco Team. Launchpad displays the team general contacts, the education contacts, the marketing contacts, and the local CD distribution contacts. Launchpad displays the timezone, the various communication channels (web, irc, planet, forums, etc.), and a link to their wiki entry.

Scope

This spec covers feature requests for Launchpad. These are primarily data elements for better integration. Launchpad should in no way take over functions (e.g. planet.launchpad.net) but rather be the integration point for those listed in this spec.

Design

• Data elements to store inside Launchpad to LoCo team record:

  • LoCo Team flag

    • display/not hidden
    • policy=set by Jono/Launchpad admin only
  • Approved Team Flag
    • display/not hidden
    • Policy=set by Jono/Launchpad admin only

  • LoCo team primary contact flag

    • Contact links to Launchpad record
    • More than one contact allowed
    • display/not hidden
    • Policy=set by team owner/administrator only

  • LoCo timezone

    • display/not hidden
    • Policy=set by by team owner/administrator only

  • LoCo Mailing List Information

    • display/not hidden
    • Policy=list set by team owner/administrator only
    • May be Ubuntu or Non-Ubuntu Sponsored
    • Allow basic mailman automation functions
      • subscribe
        • regular
        • digest
      • unsubscribe
      • password change and advanced features should forward user to mailmain interface
    • Allow Owner/Administrator to request creation of Ubuntu mailing list
      • Policy=allowed by team owner/administrator only

  • LoCo Website Information

    • display/not hidden
    • Policy=set by team owner/administrator only
    • May be Ubuntu or Non-Ubuntu Sponsored
    • Allow creation of Ubuntu sponsored website
      • Policy=must be approved team,allowed by team owner/administrator only

  • LoCo official IRC channel

    • display/not hidden
    • Policy=list set by team owner/administrator only

  • LoCo Wiki Page

    • display/not hidden
    • Policy=list set by team owner/administrator only
  • user email alias for approved teams
    • display/not hidden
    • opt-in
    • Policy=must be approved team

Implementation

Code

Data preservation and migration

Unresolved issues

• Can we enable automatic creation of mailing list for approved LoCo?

• Can we enable automatic subscription of mailing list for any LoCo?

• Can we enable automatic creation of websute for approved LoCo?

• Can we create a type of a 'heat map' of each Country/State based on Melissa's coloured map which includes identification of approved teams?

BoF agenda and discussion

• [wiki:/BOFDetails]

CategorySpec