Merge lp:~flacoste/launchpad/cleanup into lp:launchpad

[Francis J. Lacoste]

Remove obsolete files in doc/ and some other classes that should have gone with CustomConfigurationMachine.

That's a cleanup branch that removes obsolete document files in doc/ and some
classes that are now unused and should have been removed at the same time than
the CustomConfigurationMachine.

= Launchpad lint =

Checking for conflicts. and issues in doctests and templates.
Running jslint, xmllint, pyflakes, and pylint.
Using normal rules.

Linting changed files:
  lib/canonical/launchpad/scripts/__init__.py

[Edwin Grubbs (edwin-grubbs)]

Looks good.

review: Approve

=== removed file 'doc/calendars.txt'
--- doc/calendars.txt	2005-10-31 18:29:12 +0000
+++ doc/calendars.txt	1970-01-01 00:00:00 +0000
@@ -1,90 +0,0 @@
-Calendars
-=========
-
-Some objects in Launchpad have calendars.  Actually, currently only persons
-(and teams) have calendars, but it is planned to add them to products and
-projects as well.
-
-Calendaring code makes use of the SchoolBell library (Python package
-`schoolbell`), which comes from the SchoolTool project (www.schooltool.org).
-
-Launchpad calendars have some additional attributes such as title and owner,
-defined in the ILaunchpadCalendar interface (that extends schoolbell's
-IEditCalendar).  Calendars are stored in the PostgreSQL database.
-
-
-Hooking up calendars to objects
--------------------------------
-
-Objects that have calendars can be adapted to ILaunchpadCalendar.
-There is an adapter registered for ICalendarOwner that returns the
-'calendar' attribute of an object, so the simplest thing for adding a
-calendar to an object is to make sure this attribute exists, and
-declare that the object provides ICalendarOwner.
-
-There is a view named '+calendar' registered for ICalendarOwner, so if
-an object (e.g. a person) that has a calendar can be reached at a
-certain URL, accessing the calendar of that object is just a matter of
-going to URL + '/+calendar'.
-
-There is also a view named 'calendar' registered for the root object.
-This view provides a merged view of the calendars the user has
-subscribed to.
-
-There is a set of views available for ICalendar, and a traverser that
-interprets URL segments as dates.
-
-
-Interoperability with calendaring clients
------------------------------------------
-
-Every calendar can be exported as an iCalendar file via HTTP.  You can
-subscribe to these calendars from Mozilla Calendar (or Sunbird), Evolution,
-KOrganizer, Apple's iCal, etc.  The get the URL for getting an iCalendar file
-just append '/calendar.ics' to the calendar URL, e.g.
-
-   http://localhost:8085/foaf/persons/test/calendar/calendar.ics
-
-The ability to upload iCalendar files (and thus modify calendars stored in
-Launchpad from these calendaring clients) is not hooked up yet.  There is
-an iCalendar parser in the schoolbell module, but the tricky part is to get
-Zope 3 traversal (which is heavily customized in Launchpad) to actually
-work for HTTP PUT requests.
-
-
-Security
---------
-
-All calendars are readable by everyone.  Write access is restricted to
-the calendar owner.  The calendar owner is taken from the calendar's
-parent:
-  * if the calendar belongs to a team, then it is owned by the team's
-    owner.
-  * if the calendar belongs to a person, then it is owned by the
-    person.
-  * project and product calendars are owned by their respective
-    owners.
-
-
-TODO
-----
-
-- Re-add recurring event support (it was disabled to make prototyping
-  easier).  SchoolBell interfaces currently define the recurrence rule
-  as a single attribute providing one of four recurrence rule
-  interfaces; perhaps it can be simulated with a property.  Or perhaps
-  SchoolBell's interfaces aren't general enough and could be changed
-  to be more convenient.  Talk to me (Marius Gedminas,
-  <[e-mail]>) if you have ideas.
-
-- Write and hook up the iCalendar upload view (HTTP PUT requests).
-  Writing it should be easy -- use
-  schoolbell.icalendar.read_icalendar().  Hooking it up is difficult
-  (see the description above).
-   * After discussion, it has been decided not to provide webcal://
-     write access.
-
-
-If you have any questions about the schoolbell library or calendaring in
-Launchpad, feel free to email Marius Gedminas <[e-mail]>.
-

=== removed file 'doc/localdomain-setup.txt'
--- doc/localdomain-setup.txt	2007-03-10 18:14:09 +0000
+++ doc/localdomain-setup.txt	1970-01-01 00:00:00 +0000
@@ -1,68 +0,0 @@
-= Setting up launchpad local domains =
-
-We run Launchpad on development machines using Apache and virtual hosts,
-to simulate the production environment as far as possible, and allow
-us to use virtual hosts on our local machine.
-
-Here's how to set up your machine to do this.  You need to do these operations
-as the root user.
-
-== Modify your /etc/hosts ==
-
-Add this line to /etc/hosts:
-{{{
-127.0.0.88	launchpad.dev code.launchpad.dev answers.launchpad.dev blueprints.launchpad.dev bugs.launchpad.dev translation.launchpad.dev xmlrpc.launchpad.dev shipit.ubuntu.dev shipit.kubuntu.dev shipit.edubuntu.dev
-}}}
-
-As we add more domains, you'll need to alter this line.
-
-== Set up apache ==
-
-If you have apache version 1 installed, remove it:
-
-  sudo apt-get remove apache
-
-Install apache2:
-
-  sudo apt-get install apache2
-
-Turn on proxying:
-
-  sudo a2enmod proxy
-
-Set up virtual hosting:
-
-Create a file at /etc/apache2/sites-enabled/locallaunchpad
-
-{{{
-sudo vim /etc/apache2/sites-enabled/locallaunchpad
-}}}
-
-Put the following text in there.
-
-{{{
-<VirtualHost 127.0.0.88:80>
-  ServerName launchpad.dev
-  ServerAlias *.launchpad.dev
-  LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so
-  <Proxy *>
-    Order deny,allow
-    Allow from 127.0.0.0/255.0.0.0
-  </Proxy>
-  ProxyPreserveHost on
-  ProxyPass / http://localhost:8085/ retry=1
-</VirtualHost>
-}}}
-
-Reload apache:
-
-  sudo /etc/init.d/apache2 reload
-
-== Use Launchpad ==
-
-As your normal user, run launchpad.  You should be able to access it
-at the following URLs:
-
-  http://launchpad.dev/
-  http://blueprints.launchpad.dev/
-

=== removed file 'doc/mochikit-packed.txt'
--- doc/mochikit-packed.txt	2007-03-12 19:04:23 +0000
+++ doc/mochikit-packed.txt	1970-01-01 00:00:00 +0000
@@ -1,36 +0,0 @@
-To produce a packed MochiKit.js file:
-
-  1. Get a svn checkout of MochiKit.
-  2. Run: python scripts/pack.py
-  3. The packed MochiKit.js will be in
-     packed/MochiKit/MochiKit.js
-
-To remove top-level modules:
-
-  1. Edit the list MochiKit.MochiKit.SUBMODULES
-     that is in MochiKit/MochiKit.js
-  2. Run pack again.
-
-We're currently using a packed MochiKit.js that includes:
-
-    "Base",
-    "Iter",
-    "Logging",
-    "DateTime",
-    "Async",
-    "DOM",
-    "Style",
-    "Signal",
-
-And excludes:
-
-    "Format"
-    "Selector"
-    "LoggingPane"
-    "Color"
-    "Position"
-    "Visual"
-
-This takes the size of MochiKit.js that we serve down from 172598 bytes to
-97200 bytes.
-

=== removed file 'doc/poexport.txt'
--- doc/poexport.txt	2005-10-31 18:29:12 +0000
+++ doc/poexport.txt	1970-01-01 00:00:00 +0000
@@ -1,140 +0,0 @@
-Exporting PO Files From Rosetta
-===============================
-
-Last Review: 26 Aug 2004 13:50 CEST
-
-This document describes the process we should follow to export a .po file from
-Rosetta.
-
-The process here is not optimized. Perhaps there is a faster way to do it with
-less queries and less steps, but that's outside the scope of this document.
-
-We need a temporary store for a list of POMsgSet.id that are already exported.
-
-Comments
---------
-
- - What happens if we have a msgset in a POFile that is not available in the
-   POFile anymore and we see it again? Should we reuse it? For example, it
-   happens if we import a pofile with an obsolete msgset and when we import it
-   again, someone has deleted it. Also it could be interesting add as fuzzy
-   other translations from other modules (perhaps for Phase 2).
-
-The Procedure
--------------
-
-To be able to export a POFile we need to know the POFile object we want to get.
-
- 1. We get the POTemplate associated to this POFile "po" (POFile.potemplate).
-    This is the easy bit.
-
- 2. We get all POMsgSets for this POTemplate "pot" that have POMsgIDSighting
-    that were in the pot file last time we imported it::
-
-        SELECT POMsgSet.* FROM POMsgSet
-        WHERE
-            POMsgSet.potemplate = pot.id AND
-            POMsgSet.pofile IS NULL AND
-            POMsgSet.sequence > 0
-            EXISTS (SELECT * FROM POMsgIDSighting
-                WHERE
-                POMsgSet.id = POMsgIDSighting.pomsgset AND
-                POMsgIDSighting.inlastrevision = TRUE)
-            ORDER BY POMsgSet.sequence
-
- 3. For every POMsgSet "potSet" we got in #2 we look for its equivalent
-    POMsgSet "poSet" inside the POFile::
-
-        SELECT POMsgSet.* FROM POMsgSet
-        WHERE
-            POMsgSet.potemplate = pot.id AND
-            POMsgSet.pofile = po.id AND
-            POMsgSet.primemsgid = potSet.primemsgid
-
-    If we don't find a POMsgSet, we dump potSet and continue to the next messasge
-    set.
-
-    If we get a POMsgSet, we add its id (POMsgSet.id) into a temporary list,
-    and look for an active translation sighting ("translationSighting") for
-    the message set::
-
-        SELECT * FROM POTranslationSighting
-        WHERE
-            POTranslationSighting.pomsgset = poSet.id AND
-            POTranslationSighting.active = TRUE)
-
-    If we don't get any POTranslationSighting, we dump potSet along with
-    poSet.commenttext and go on to the next message.
-
-    XXX: Should we look on older translations? (Read comment #1)
-
-    If we have an active translation we need to check if it's a plural form
-    and if it's the same as the POTemplate one::
-
-        SELECT POMsgIDSighting.id FROM POMsgIDSighting
-        WHERE
-            POMsgIDSighting.pomsgset = potSet.id AND
-            POMSgIDSighting.pluralform > 0 AND
-            POMsgIDSighting.inlastrevision = TRUE
-
-    If this query returns a result (and it should only ever return one), we
-    call it "templatePluralSighting".
-
-    If this query returns no results, it's not a plural form in the template.
-    We now check whether it's a plural form in the PO file::
-
-        SELECT POMsgIDSighting.id FROM POMsgIDSighting
-        WHERE
-            POMsgIDSighting.pomsgset = poSet.id AND
-        POMSgIDSighting.pluralform > 0 AND
-        POMsgIDSighting.inlastrevision = TRUE
-
-    If this query also returns no results, (it's non-plural in the PO file
-    too) we dump potSet, with poSet.commenttext, poSet.fuzzy,
-    translationSighting.potranslation.translation, and go on to the next
-    message set.
-
-    If this query does return results (it's non-plural in the template but
-    plural in the PO file), we dump potSet with poSet.commenttext,
-    translationSighting.potranslation.translation and a fuzzy flag, then go on
-    to the next message set.
-
-    Now, the case when the message set is plural in the template.
-
-    We look to see if the same plural form exists in the PO file::
-
-        SELECT POMsgIDSighting.id FROM POMsgIDSighting
-        WHERE
-            POMsgIDSighting.pomsgid = templatePluralSighting.pomsgid AND
-            POMsgIDSighting.inlastrevision = TRUE
-
-    If the plural forms are equal, we dump potSet with poSet.commenttext,
-    poSet.fuzzy (although if poSet.iscomplete is false, the fuzzy flag is
-    set), translationSighting.potranslation.translation and go on to the next
-    message set.
-
-    If the plural forms are not equal, we dump potSet with poSet.commenttext,
-    translationSighting.potranslation.translation and set the fuzzy flag. And
-    then go to the next message set.
-
- 4. At this point we have dumped all current messag sets from the template,
-    now it's time to export the remaining message sets from the PO file.
-
-    We get the list of POMsgSets that are active::
-
-        SELECT POMsgSet.* FROM POMsgSet
-        WHERE
-            POMsgSet.potemplate = pot.id AND
-            POMsgSet.pofile = po.id AND
-            POMsgSet.sequence > 0
-            EXISTS (SELECT * FROM POMsgIDSighting
-                    WHERE
-                    POMsgSet.id = POMsgIDSighting.pomsgset AND
-                    POMsgIDSighting.inlastrevision = TRUE)
-        ORDER BY POMsgSet.sequence
-
-    And, for every POMsgSet we get, we check whether it's in our list of
-    message sets that we've looked at already. If it is, we ignore it. If it
-    isn't, we dump the message set with all its translations but without the
-    file references and source comment, and set the obsolete flag.
-

=== removed file 'doc/rosetta-cmdline.txt'
--- doc/rosetta-cmdline.txt	2005-10-31 18:29:12 +0000
+++ doc/rosetta-cmdline.txt	1970-01-01 00:00:00 +0000
@@ -1,41 +0,0 @@
-===========================
- Rosetta command line tool
-===========================
-
-We want a Rosetta command line tool, to interact with testing, importd
-and other tools we will be using in the server.
-
-Local tool
-===========
-
-The tool will run on the same machine where Rosetta (Launchpad) is
-installed, so no XML-RPC or httplib funky stuff; just import
-lib.canonical.rosetta and rock on.
-
-We will probably have to have a way of pointing it to where the source
-tree is so that it can mess with the python path and parse the zcml
-necessary to connect to the database.
-
-Command line
-=============
-
-The sanest way to tell it what to do is probably a command line scheme
-that uses subcommands, kind of similar to tla, but with two levels;
-the first argument would be a class, the second one a "command".
-
-Use cases
-==========
-
-Import PO template
--------------------
-
-command line::
-
- % rosetta pofile parse xxx.po --potemplate ptid
-
-Import PO file
----------------
-
-command line::
-
- % rosetta potemplate parse xxx.pot --new --name="name" --title=""

=== removed directory 'doc/user-manual'
=== removed file 'doc/user-manual/Makefile'
--- doc/user-manual/Makefile	2005-10-31 18:29:12 +0000
+++ doc/user-manual/Makefile	1970-01-01 00:00:00 +0000
@@ -1,7 +0,0 @@
-all: xhtml
-
-xhtml: rosetta-upstream-setup.xml
-	xmlto xhtml rosetta-upstream-setup.xml
-
-clean:
-	rm -f rosetta-upstream-setup.html

=== removed directory 'doc/user-manual/images'
=== removed file 'doc/user-manual/images/products-search-form.png'
Binary files doc/user-manual/images/products-search-form.png	2005-10-31 18:29:12 +0000 and doc/user-manual/images/products-search-form.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'doc/user-manual/rosetta-upstream-setup.xml'
--- doc/user-manual/rosetta-upstream-setup.xml	2005-10-31 18:29:12 +0000
+++ doc/user-manual/rosetta-upstream-setup.xml	1970-01-01 00:00:00 +0000
@@ -1,58 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
-    "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
-]>
-<article>
-  <articleinfo>
-    <title>How can I use Rosetta to translate my project</title>
-    <author>
-      <firstname>Carlos</firstname>
-      <surname>Perell&oacute; Mar&iacute;n</surname>
-    </author>
-  </articleinfo>
-
-  <sect1>
-    <title>Introduction</title>
-    <para>
-This document covers all steps needed to follow so you get a new resource to
-translate imported into Rosetta. It does not cover the steps to translate
-Ubuntu resources, if you have any special request or question about Ubuntu
-translations, please, send it directly to
-<ulink url="http://lists.ubuntu.com/mailman/listinfo/ubuntu-translators">
-Ubuntu translators mailing list</ulink>.
-    </para>
-  </sect1>
-
-  <sect1>
-    <title>Creating a new Product in Launchpad</title>
-    <para>
-To be able to translate anything with Rosetta you need first a product in
-Launchpad. There are already many products created already in Launchpad, so
-the first step is check if it already exists. To do it go to the
-<ulink url="https://launchpad.ubuntu.com/products">Product Search form</ulink>
-and try to find the product you are interested on.
-
-      <mediaobject>
-        <imageobject>
-          <imagedata fileref="images/products-search-form.png" format="PNG" />
-        </imageobject>
-
-        <textobject>
-          <phrase>Launchpad product search form.</phrase>
-        </textobject>
-
-        <caption>
-          <para>
-            Launchpad product search form.
-          </para>
-        </caption>
-      </mediaobject>
-
-    </para>
-
-    <para>
-If you are not able to find the product you are interested on
-    </para>
-  </sect1>
-
-</article>

=== removed file 'doc/zope3sins.txt'
--- doc/zope3sins.txt	2005-10-31 18:29:12 +0000
+++ doc/zope3sins.txt	1970-01-01 00:00:00 +0000
@@ -1,7 +0,0 @@
-===========
-Zope 3 Sins
-===========
-
-This document is for collecting those areas of Zope 3 that depend on the
-ZODB, object graph<->URLs or make other assumptions that make it difficult to
-use in ways that diverge from those assumptions.

=== removed directory 'lib/canonical/launchpad/apidoc'
=== modified file 'lib/canonical/launchpad/scripts/__init__.py'
--- lib/canonical/launchpad/scripts/__init__.py	2010-04-27 22:33:21 +0000
+++ lib/canonical/launchpad/scripts/__init__.py	2010-05-14 14:41:10 +0000
@@ -24,11 +24,9 @@
 from textwrap import dedent
 import threading
 
-import zope.app.appsetup
 import zope.sendmail.delivery
 import zope.site.hooks
 from zope.configuration.config import ConfigurationMachine
-from zope.configuration.config import GroupingContextDecorator
 from zope.security.management import setSecurityPolicy
 from zope.security.simplepolicies import PermissiveSecurityPolicy
 
@@ -45,29 +43,6 @@
 # Intentional re-export, following along the lines of the logger module.
 from canonical.launchpad.scripts.loghandlers import WatchedFileHandler
 
-# XXX StuartBishop 2005-06-02:
-# We should probably split out all the stuff in this directory that
-# doesn't rely on Zope and migrate it to canonical/scripts.
-
-class NullItem:
-    def __init__(self, context, handler, info, *argdata):
-        newcontext = GroupingContextDecorator(context)
-        newcontext.info = info
-        self.context = newcontext
-        self.handler = handler
-        self.argdata = argdata
-
-    def contained(self, name, data, info):
-        return NullItem(self.context, None, None)
-
-    def finish(self):
-        pass
-
-
-def NullFactory(context, data, info):
-    return NullItem(context, data, info)
-
-
 def execute_zcml_for_scripts(use_web_security=False):
     """Execute the zcml rooted at launchpad/script.zcml