The project under heavy development. It does not yet have a working demo.


The simplest explanation of purpose is likely what was discussed between two of the developers.

23:28 <doctormo> what will it be used for? 23:29 <MTecknology> Lemme draw a timeline in slow people typing... 23:37 <MTecknology>

  • 1) Asked about a LoCo Map

  • 2) I look into it
  • 3) Really irritated with wiki page format
  • 4) I start drawing up code to clean that shit-pile up
  • 5) I decide we need something better and agree with the requests
  • 6) I start working on it
  • 7) I start looking for help because the fucker is massive
  • 8) There you are...
  • 9) We work together for a while
  • 10) You take over much of the coding
  • 11) I move over to work on the UD Planet module
  • 12) You do one hell of a kick ass job [ We had our different opinions in the mix ]
  • 13) You develop another map to zoom in that is royally kick ass
  • 14) We stop while waiting to get the XML data
  • 15) Somewhere in there the LD guys thought it would be great if we finished this
  • 16) They finally give us XML output
  • 17) I try to pick this up again
  • 18) I grab code from you
  • 19) I'm swamped but have other people that want to help
  • 20) I develop specs for them to follow. .......
  • 21) Project finished.
  • 22) You developed it in a highly portable manner that we maintain
  • 23) I deliver to LoCo Directory guys

  • 24) They spend 15min making it work with the LD instead
  • 25) It exists for everyone.

The goal of this Ubuntu Drupal module is to present all of the LoCo information on a map. A model can be seen here and here.

This has been a massive project for some time in the community and nobody has yet to provide a fully functional and ready to deploy system. It's time to finally have this running in the wild.


Project Lead


Lead Developer




RTL Developer




SVG Concepts



Warning /!\ Review Needed

  1. This will exist as a Drupal module
    1. The map must be displayable as a page that is returned as content (map + theme shown) [provided it's feasible]
    2. The map must be displayable as a page that is printed (only map shown)
  2. The administrator must be able to specify dynamic options such as:
    1. The color for:
      1. Non-Existing LoCos

      2. Non-Approved LoCos

      3. Approved LoCos

      4. Defaults should be pulled from the SVG Concept
    2. The highest level map
    3. The data location (http://loco.ubuntu.com/data/xml)

    4. The images location (Unknown)
    5. A button to force retrieving of remote data
  3. Remote information should be pulled from remote location on cron()
    1. The cron function will not run more than once every 24 hours
      1. Unless forced
    2. The data will be checked fore timestamp differences before being fetched
      1. New timestamp will not be saved until the parse completes successfully
    3. After retrieving; the data will be parsed and printed to a local file
      1. This file will be formatted so no additional parsing operations need to occur
    4. No remote data will need to be pulled. Except:
      1. Current LoCo data from the LoCo Directory

    5. Any data needed will need to exist locally in a format ready for the map
  4. The map will start in a predefined "highest level map" (Ex. North America)
    1. The user Info <!> {will / will not} be able to go out beyond this level

    2. The user will be able to zoom in until data exists for a detailed overview
    3. In the detailed overview: users will see outlined areas for each LoCo.

    4. Hovering over the area will highlight the area
    5. Clicking the area will bring up a box with information about the LoCo in that highlighted area

    6. The box will contain: (if available)
      1. Flag or Image
        1. https://launchpad.net/api/beta/~<LP_TEAM>/mugshot

        2. Some method to use a link to LP Team Image would be best for this
      2. LoCo Name

        1. Info <!> Possibly a note about if they are officially approved or not

        2. Info <!> Possibly a note about if they provide local support

      3. Link to Website
      4. Link to Forums
      5. Link to Wiki
      6. Link to Mailing List
      7. Link to IRC Channel (webchat.freenode.net)
      8. Link to Launchpad Page
      9. [ Above order should likely be followed. ]
  5. The map will have RTL CSS wherever appropriate
  6. The code will be CLEAN and READABLE
    1. It will not remain as a Drupal project
    2. It will be expanded and partially absorbed into the LoCo Directory project

  8. The user must be alerted if they need to enabled javascript
  9. The user must be alerted if they need to obtain SVG support
  10. (i) Technologies to be used:

    1. OpenLayers provides an existing set of tools for working with maps

      1. The work could be somewhat reproduced on this
      2. To achieve the eye-candy already existing would make much of the existing framework pointless
    2. SVG provides all the functionality we need
      1. A large part of this work is finished by doctormo
      2. Provides very nice eye-candy
      3. The new mechanism is much nicer to older browsers with older video cards
    3. Google Maps would be best suited for "pins" which is not a part of this project

Additional Thoughts

Add additional thoughts below this line.

UbuntuDrupal/Specs/LoCoMap (last edited 2009-12-15 21:25:15 by 138)