Topic Classification
The Codev web categorizes topics by type of form used:
Topic Classification for BasicForm
The
BasicForm has these Topic Classification items:
AdminTopic,
BrainstormingIdea,
DefineTerm,
GatewayTopic,
NextGeneration,
TWikiAddOnProduct,
TWikiCommunity,
TWikiAdvocacy,
TWikiDeployment,
TWikiDevDoc,
TWikiDevQuestion,
TWikiVsOtherProducts
Older WebForm-based Topic Classification
Each topic in the TWiki.Codev has a classification. Set it using the
WebForm when you edit a topic. Click on a classification below to generate a list of all Codev topics currently listed in that category (Dec-2001 - most topics have NOT yet been categorized - go for it whenever you get a chance!):
Name |
Type |
Tooltip Message |
Select one... |
option |
|
TWikiCommunity |
option |
Any subject to do with the TWiki community |
TWikiDeployment |
option |
Any subject to do with TWiki in action |
TWikiVsOtherProducts |
option |
Discussion of any type of relevant software |
TWikiAddOnProduct |
option |
Programs, protocols, modules...anything that can be used with TWiki |
TWikiDevQuestion |
option |
Specific queries about TWiki development |
FeatureBrainstorming |
option |
Wide open future dev discussion |
FeatureEnhancementRequest |
option |
Specific requests for new and improved features |
FeatureToDo |
option |
Features accepted into the dev queue |
FeatureHack |
option |
Unofficial core code modifications (in dev or done) |
FeatureUnderConstruction |
option |
Approved feature in active dev (see also FeatureHack) |
FeatureDone |
option |
Implemented in Beta |
FeatureNotSuitable |
option |
Down but not necessarily out |
PatchProposal |
option |
Request for CoreTeam to evaluate a patch for integration into the core. |
PatchAdjustmentRequired |
option |
CoreTeam requests specific changes from patch author before inclusion. |
PatchReadyForCVS |
option |
Patch ready to be included into TWiki by core team |
PatchAccepted |
option |
Patch accepted and integrated into core TWiki code, available in CVS. |
PatchNotSuitable |
option |
Patch deemed unsuitable for inclusion into the core. Perhaps change to FeatureHack? |
BugReport |
option |
|
BugAssigned |
option |
|
BugResolved |
option |
|
BugDuplicate |
option |
|
BugRejected |
option |
|
DocRequest |
option |
TWiki features in need of new or improved documentation |
DocsToDo |
option |
Pending docs for FeatureDone and approved DocRequests |
FeatureDocumented |
option |
Stable, documented feature |
DefineTerm |
option |
A basic definition/external link for specialized term, protocol, product, company, person,... |
AdminTopic |
option |
TWiki/Codev functional and/or descriptive topic (ex: WebForm, ActiveTopic; includes placeholders linking to same-named topics in other webs) |
GatewayTopic |
option |
A top-level launch-point topic, linking all other Codev topics and threads related to a broad main area of TWiki development: overview, active core discussion, sub-topic excerpts, links to SummaryTopics for specific features and ideas. |
NextGeneration |
option |
Ideas, possible far out, for future TWiki architecture and development |
This category was mentioned, but doesn't seem to exist
--
MikeMannix - 19 May 2002
--
JohnTalintyre - 12 Sep 2003
Are these categories going to be updated? Is there a need to reorganize again?
Related:
CodevFields and the now defunct
MasterRefactor
--
GrantBow - 09 Jan 2003
Add forms table above, put descriptions of categories in there.
--
JohnTalintyre - 12 Sep 2003
I think that there is an issue defining the classification in this topic here vs in the form definition topics: An incorrect classification can be selected for a form.
For example, lets assume that we have one bug and feature tracking form with many fields and one
BasicForm for other types of topics. It is possible to select
BugReport for the basic form and vice versa.
It is better to prevent that, e.g. each form definition has only allowed classification field values. That is, the
TopicClassification options are defined in the form topics. That way a user needs to change the form in order to switch from one type of typic to another.
--
PeterThoeny - 12 Sep 2003
That's exactly what will happen with the
ProposedNewFormsInCodev.
--
SamHasler - 10 Nov 2004