LoCoTeamPortal

Differences between revisions 1 and 26 (spanning 25 versions)
Revision 1 as of 2009-05-07 14:32:01
Size: 1078
Editor: i59F73504
Comment:
Revision 26 as of 2011-11-12 01:57:28
Size: 3316
Editor: svwilliams
Comment: project moved from LoCoDirectory to LoCoTeamPortal
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from LoCoDirectory
#Title LoCo Directory
Line 2: Line 4:
<<TableOfContents(2)>>
Line 5: Line 7:
== 0.1 release ==
= Developers =
== Get Started ==

 1. `bzr branch lp:loco-directory`
 1. `cd loco-directory; less INSTALL`

 * '''Review our [[LoCoDirectory/ReleaseProcess|release process]].'''
 * '''General [[LoCoDirectory/Development|development tips and tricks]].'''


= Bug Importance =

 * '''Critical''': Security or major feature not working
 * '''High''': Other functionality failure or new implementation deemed necessary
 * '''Medium''': Sub-optimal functionality bug or usability improvements
 * '''Low''': Trivial problems, such as typo's, poor wording or layout optimizations
 * '''Wishlist''': New features or functionality that is desirable but not necessary

= 0.1 release =
Line 9: Line 30:
=== Working features === == Working features ==
Line 12: Line 33:
 * Overview of teams.  * Overview of teams
Line 17: Line 38:
=== TODO ===
<<Anchor(TODO)>>
== TODO ==
Line 20: Line 43:
 * `./data/` contains initial data about all LoCo teams that was mailed via `loco-contacts@lists.ubuntu.com`. This needs integration into `./loco_directory.sql`, so we can populate the database with initial data.
 * make `./loco_directory/teams/forms.py` work (used within `./loco_directory/templates/teams/team_update.html`). It currently explodes when you try to change data.
 1. (./) make `./loco_directory/teams/forms.py` work (used within `./loco_directory/templates/teams/team_update.html`). It currently explodes when you try to change data. (Efrain)
 1. (./) Ask teams to join ~locoteams (Nick and Efrain)
 1. (./) Add functionality for ~loco-council change of loco contacts, etc. (Daniel)
 1. (./) Add functionality to pull team information to Launchpad. (Daniel)
 1. Make sure that all approved teams end up in ~approved-locoteams (Nick and Efrain)
 1. (./) New view "upcoming re-approvals". (Daniel)
 1. (./) Take care of translations. (Daniel)
 1. (./) Code cleanup and general beautification. (all)
 1. (./) Import Launchpad team owner and team admins (Daniel)
 1. (./) Really let `lpupdate` script update information (Daniel)


= 0.1.x =
 1. Offer STATEful file. (Daniel)


= 0.2 release =

== TODO 0.2 ==
Branch: https://code.launchpad.net/loco-directory/trunk
Events blueprint https://blueprints.launchpad.net/loco-directory/+spec/loco-directory-event-registration

 1. Add Venues from within the TeamEvent form.
 1. Offer previous venues in the TeamEvent form.
 1. Arrange so Only Horsemen can add Global Events?
 1. Arrange so only Admins can add Team Events?
 1. On Team Details offer, last 5 events organized by the team
 1. On Event Details page, offer 5 random registered attendees (link to launchpad page) as teaser, full list available at a click distance.
 1. On Events main page offer the last 5 registered by the LoCo team Community
 1. On Event Details page, offer last 5 post in microblogging services (identi.ca, twitter)
 1. On Event Details page, pull 5 random pictures from a web album in picasa, flickr etc.
Line 25: Line 77:
...
 1. Sexy Map. (Ubuntu-Drupal, Chris)

Branch: lp:ubuntu-drupal-locomap
<<BR>>Branch: lp:~christophe.sauthier/loco-directory/0.2-map

Work is ongoing on the Loco Directory. Discussed at UDS Mountain View it's going to solve a lot of today's problems and make collaboration much much easier.

Developers

Get Started

  1. bzr branch lp:loco-directory

  2. cd loco-directory; less INSTALL

  3. Review our release process.

  4. General development tips and tricks.

Bug Importance

  • Critical: Security or major feature not working

  • High: Other functionality failure or new implementation deemed necessary

  • Medium: Sub-optimal functionality bug or usability improvements

  • Low: Trivial problems, such as typo's, poor wording or layout optimizations

  • Wishlist: New features or functionality that is desirable but not necessary

0.1 release

In its 0.1 release we plan to replace the "big list of loco teams" and make administration of that list a lot easier.

Working features

  • Log in via Launchpad OpenID.
  • Overview of teams
  • Detailed view of team data.
  • Click Update button, will check if you're admin of that team.
  • admin overview.

TODO

Branch: https://code.launchpad.net/loco-directory/trunk

  1. (./) make ./loco_directory/teams/forms.py work (used within ./loco_directory/templates/teams/team_update.html). It currently explodes when you try to change data. (Efrain)

  2. (./) Ask teams to join ~locoteams (Nick and Efrain)

  3. (./) Add functionality for ~loco-council change of loco contacts, etc. (Daniel)

  4. (./) Add functionality to pull team information to Launchpad. (Daniel)

  5. Make sure that all approved teams end up in ~approved-locoteams (Nick and Efrain)
  6. (./) New view "upcoming re-approvals". (Daniel)

  7. (./) Take care of translations. (Daniel)

  8. (./) Code cleanup and general beautification. (all)

  9. (./) Import Launchpad team owner and team admins (Daniel)

  10. (./) Really let lpupdate script update information (Daniel)

0.1.x

  1. Offer STATEful file. (Daniel)

0.2 release

TODO 0.2

Branch: https://code.launchpad.net/loco-directory/trunk Events blueprint https://blueprints.launchpad.net/loco-directory/+spec/loco-directory-event-registration

  1. Add Venues from within the TeamEvent form.

  2. Offer previous venues in the TeamEvent form.

  3. Arrange so Only Horsemen can add Global Events?
  4. Arrange so only Admins can add Team Events?
  5. On Team Details offer, last 5 events organized by the team
  6. On Event Details page, offer 5 random registered attendees (link to launchpad page) as teaser, full list available at a click distance.
  7. On Events main page offer the last 5 registered by the LoCo team Community

  8. On Event Details page, offer last 5 post in microblogging services (identi.ca, twitter)
  9. On Event Details page, pull 5 random pictures from a web album in picasa, flickr etc.

Future

  1. Sexy Map. (Ubuntu-Drupal, Chris)

Branch: lp:ubuntu-drupal-locomap
Branch: lp:~christophe.sauthier/loco-directory/0.2-map


CategoryLoco

LoCoTeamPortal (last edited 2016-02-24 22:16:18 by tsimonq2)