This Web

Other Webs

Schematics

RSS

Scheme Links

Cookbook Administration Issues

This is a laundry list of things to think about, plan for, and/or do. Expand any significant points below into their own topics, as necessary, and link to them from here.

Project Management

• What is the desired progress of this project?
• How can we measure that?
• What measurements do we expect if everything is running as desired?
• What do we expect to see if one of the alternative suggested development models is more appropriate?

Security

• Signup
  • Consider providing a more stripped-down sign-up page than TWikiRegistration. Include copyright permission notice on the signup page.
  • Validation of signups
    • Require email confirmation - TWiki sends email to new signups, but does not require user response by default. May be configurable.
    • Captcha - could protect against bogus signups, but requires some setup (not a TWiki feature).
• Access controls - see TWikiAccessControl, particularly notes about "An Important Control Consideration"
  • Per topic control is possible - topics can be protected, e.g. when they reach a point where they are considered worth protecting against edits.
  • See also Annotations below.

Legal

• License - LGPL
• Copyright - contributors must provide permission

Content Management

• Annotations - see AdminAnnotationProposal
• Moderation of recipes or annotation (possible future idea)
• Source code management - see IncludingSourceCode
  • Using separate files for source
    • Naming convention
• Releases
  • Static HTML distribution - use wget with link rewriting? Probably inadequate, leaving content editing links in place and not able to rewrite links in all file formats.
    • Note: some of this inadequacy could be addressed with a TWiki skin, which can be used to eliminate the editing links. Try appending ?skin=plain to a topic url to see an example. Custom skins are also possible - the Cookbook site uses a non-standard skin called VoidSkin, for example.
  • Source code distribution - see Source code management above. Can fairly trivially zip up contents of Scm web to make a source distribution. Only works if all significant source code snippets are actually stored there. See IncludingSourceCode.
  • Book-style printable document distribution
    • See TWiki:Codev.TWikiForBookAuthoring, TWiki:Codev.PrintUsingPDF
    • AdminCookbookViews may help (see below)

Structure and Presentation

• AdminCookbookViews could help support multiple views of the same recipes
• URL structure - use Apache's mod_rewrite to make URL's friendlier. See TWiki:Codev.ShorterURLs
• Come up with & register good Schematics domain name? Some suggestions include:
  • schematician and plt-?schematics - MJRay
  • SchemeWiki.org, SchemeRecipes.org, SchemeSolutions.org - JensAxelSoegaard

Known Limitations

• We ran into TWiki:Codev.IncludeUrlIsSuperSlow with an earlier code inclusion technique (document this).

Completed Items

• The login box suggests that pressing cancel will take one to the registration page. Instead one is taken to a 404 page. This has been corrected.

-- AntonVanStraaten - 20 Apr 2004