ProjectGroup Category Proposal

ProjectGroup is an attempt to create a first small set of GatewayTopic to link all other Codev dev discussion topics. Each would be a launch point for a particular top-level subject or theme, with a summary, active core discussion, topic excerpts, and all related Codev links.

Keeping up quality Gateways can be a bit of work, but basic maintenance is simple: whenever a new Codev topic is created, the ProjectGroup category in the WebForm is checked off (one or more categories). The topic then automatically appears in the proper Group Topics lists (ex: ChangesTopics).

Of course, this set of Groups has to "make sense" to the majority here, or they won't be used. This is hardly a new idea, and several index pages already exist Codev. The difference here is that a set of only five Groups, organized from an end-user perspective, seem to handle all topics. You may not agree. So, please check 'em out - defs are below; each link goes to an early version of a launch page - and comment, here or there!

Proposed ProjectGroups:

• ChangesProject - tracking changes to topics, including: notification methods like WebNotify; diffs displays; WebChanges; personalization and customization; instant notification; author-selectable changes classifications; highlighting changes; anything else to do with alerting users to the changes they are interested in, and making those changes easy to locate...
• CollaborationProject - hands-on use of TWiki as a flexible collaboration tool, including: best practices for creating, editing and maintaining topics/discussions; site start-up, user intro and management; CollaborationSituations and user/daily admin-related buy-in requirements; core user activities; common services NOT provided (ex: group calendar; database as basic bulk list processor) and interfaces; identifying features that are both useful and consistent with Wikiness - the focus is probably more on the human factor, site org, policies & procedures, than on program features.
• InterfaceProject - basic usability issues, including: user interface - look-and-feel, toolbars & buttons, control screens, etc; navigation; ease-of-use of individual core functions; overall core feature set; accessability and quality of docs & Help; distribution package; etc - the minimum platform required to meet CollaborationProject needs.
• FeaturesProject - all new features & major enhancements, requests & discussions, including: core features; API/Plugins; integration with other products, protocols - features are divided between those that enhance Interface, Changes, and Collaboration, and those that add all-new capabilities.
• CodeBaseProject - development of the core TWiki code base: modularization, Plugin API, native language, system requirements, use of third-party add-ons, workflow - basically, a collection of dev philosophy/policy considerations (at best, extra perspective for Peter, though it's quite obviously on top of all this)
  • (a separate ModularizationProject is proposed for dev issues, once there's a jump forward in TWikiOO)

-- MikeMannix - 01 Jan 2002

I'm in the process of recording topics current linked into ProjectGroup, before removing it.

Q: Why is it being removed?
A: Most people consider it hasn't work because it is confusing.

-- JohnTalintyre - 27 Sep 2003

reformatted to make it clear that John was answering his own question -- MattWilkie - 27 Sep 2003

Thanks Matt. Ironic that I managed to make that confusing!

-- JohnTalintyre - 27 Sep 2003