LoCoDjango

Differences between revisions 1 and 22 (spanning 21 versions)
Revision 1 as of 2007-10-21 15:52:48
Size: 3987
Editor: c-67-165-213-225
Comment: put up some links to related work
Revision 22 as of 2008-10-06 21:16:04
Size: 6606
Editor: c-67-165-213-225
Comment: us-ma-loco-site
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
Loco Django Development is a project aimed at developing a framework for LoCo teams to use as a website. Loco Django Development is a project aimed at defining, customizing and/or developing a Django-based CMS for LoCo teams to use as a website.
Line 26: Line 26:
First flesh out the brainstorming section below, then come up with a design and implementation plan. First flesh out the discussion/brainstorming section below, then come up with a design and implementation plan.
Line 30: Line 30:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: ''This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:''
Line 34: Line 34:
Should cover changes required to the UI, or specific UI that is required to implement this ''Should cover changes required to the UI, or specific UI that is required to implement this''
Line 38: Line 38:
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.
''Code changes should include an overview of what needs to change, and in some cases even the specific details.''
Line 49: Line 42:
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. ''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.''
Line 51: Line 44:
This need not be added or completed until the specification is nearing beta. ''This need not be added or completed until the specification is nearing beta.''
Line 55: Line 48:
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. ''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.''
Line 57: Line 50:
== BoF agenda and discussion == == Feature Discussions ==
Line 59: Line 52:
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected. All are welcome to view the current specs for each of these and provide input. If you have any other ideas for features please add them as well.
Line 61: Line 54:
https://launchpad.net/banjo/  *Local Support System - [[LoCoDjango/Features/SupportSystem|Spec & Discussion]]
  *Local Support System Map - [[LoCoDjango/Features/SupportSystem/Map|Spec & Discussion]]
 *Blog/News System - [[LoCoDjango/Features/BlogNews|Spec & Discussion]]
 *User Authentication System - [[LoCoDjango/Features/Users|Spec & Discussion]]
  *Member Roster with contact information - [[LoCoDjango/Features/Users/MemberRoster|Spec & Discussion]]
  *OpenID authentication system - [[LoCoDjango/Features/Users/OpenID|Spec & Discussion]]
 *Calendar Of Events Local & Remote - [[LoCoDjango/Features/CalendarOfEvents|Spec & Discussion]]
 *Flat-Page support - [[LoCoDjango/Features/FlatPages|Spec & Discussion]]
 *Dynamic Navigation - [[LoCoDjango/Features/Navigation|Spec & Discussion]]
 *Mapping Framework - [[LoCoDjango/Features/MappingFramework|Spec & Discussion]]
  *Local Support System Map - [[LoCoDjango/Features/SupportSystem/Map|Spec & Discussion]]
  *Loco Member Locations - [[LoCoDjango/Features/MappingFramework/Members|Spec & Discussion]]
  *Meeting Spots - [[LoCoDjango/Features/MappingFramework/MeetingSpots|Spec & Discussion]]


== Discussion ==

Here are some links to related projects and apps.

See also an interesting post by James Bennet on blogs and django:
http://www.b-list.org/weblog/2007/nov/29/django-blog/

 * Massachusetts loco website code base: https://launchpad.net/us-ma-loco-site

 * pinax: http://pinaxproject.com/ - a collection of re-usable apps, with lots of social networking components

 * https://launchpad.net/banjo/
Line 70: Line 89:
https://launchpad.net/kaleidoscope/
Kaleidoscope - CMS for Real content
 A Django CMS for Real Content
 * Blogmaker - "a full-featured, production-quality blogging application for Django. It supports trackbacks, ping and comments with moderation and honeypot spam prevention."
Line 74: Line 91:
https://launchpad.net/swing42/  http://blogcosm.com/media/blogmaker/release/README.html

 http://code.google.com/p/blogmaker/

 bzr mirror of the official svn trunk: https://edge.launchpad.net/blogmaker/trunk

 * Djog: http://dev.oebfare.com/projects/djog/ - a Django blog app

 * Byteflow: http://byteflow.su/

 * Luambo multi-user multi-blog: http://svn.luamboblog.org/

 * https://launchpad.net/kaleidoscope/
 Kaleidoscope - CMS for Real content
 "A Django CMS for Real Content", but I don't see any code....

 * https://launchpad.net/swing42/
Line 79: Line 112:
https://launchpad.net/ubuntu-nl-website/
  A django app with moinmoin backend for the homepage
  A django app for authentication
  A heavily customized PunBB forum
  A django pastebin with pygments syntax coloring and hashcash spam protection
  A wordpress-mu install for blogs
  A planetplanet blog aggregator
 
Several maintenance scripts
 * https://launchpad.net/ubuntu-nl-website/
  * A django app with moinmoin backend for the homepage
  * A django app for authentication
  * A heavily customized PunBB forum
  * A django pastebin with pygments syntax coloring and hashcash spam protection
  * A wordpress-mu install for blogs
  * A planetplanet blog aggregator
  *
Several maintenance scripts
Line 88: Line 121:
https://launchpad.net/django-forum/  * https://launchpad.net/django-forum/
Line 91: Line 124:
https://launchpad.net/django-xmlrpc/ graham.binns  * https://launchpad.net/django-xmlrpc/ graham.binns
Line 93: Line 126:
  blog posts (amongst other things) using the MetaWeblog API
Line 95: Line 127:
https://launchpad.net/django-survey/
 http://yml.alwaysdata.net/dj_survey/index/
 * blog posts (amongst other things) using the MetaWeblog API

 *
https://launchpad.net/django-survey/
 * http://yml.alwaysdata.net/dj_survey/index/
Line 100: Line 135:
KSS Django - Kinetic Style Sheets. A beautiful AJAX framework.  * KSS Django - Kinetic Style Sheets. A beautiful AJAX framework.
Line 102: Line 137:
Line 109: Line 145:
https://launchpad.net/kaplan/ Kaplan TODO  * https://launchpad.net/kaplan/ Kaplan TODO
Line 111: Line 147:
https://launchpad.net/geekgrep/  * https://launchpad.net/geekgrep/
Line 113: Line 149:
https://launchpad.net/loco-drupal/  * https://launchpad.net/loco-drupal/

 * Inyoka
 The german Loco-Team had developed a single web application (including portal, forum, wiki, blog and planet) using Python (there are only a few Django dependencies left, since Django isn't suitable for bigger things). A beta version is running on http://staging.ubuntuusers.de/ and performs well, but some things (mainly the design) are still missing. After the release on http://www.ubuntuusers.de/ we are going to translate it and publish it under the terms of the GPL.
   * It's now realeased and used productively on http://www.ubuntuusers.de/. Generalization and Translations will follow.

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

Loco Django Development is a project aimed at defining, customizing and/or developing a Django-based CMS for LoCo teams to use as a website.

Release Note

Better integration with Launchpad.

Rationale

Python for LoCo sites!

Use Cases

Assumptions

Design

First flesh out the discussion/brainstorming section below, then come up with a design and implementation plan.

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.

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.

Feature Discussions

All are welcome to view the current specs for each of these and provide input. If you have any other ideas for features please add them as well.

Discussion

Here are some links to related projects and apps.

See also an interesting post by James Bennet on blogs and django: http://www.b-list.org/weblog/2007/nov/29/django-blog/


CategorySpec

LoCoDjango (last edited 2008-10-06 21:16:04 by c-67-165-213-225)