NOTA BENE - WORK IN PROGRESS - Your Inputs & Thoughts
To comma Workbench - To comma Workbench - Overview Projects - To Technology Laboratory CAcert.org Wiki - Certificate Login & Technical Support - To comma Arsenal Wiki - To comma Arsenal - Development & Design Team Current Projects
Contents
- CAcert.org Wiki Certificate Login & Know-How Management Tool - comma Project Background
- comma Purpose
- Know-How Management Tool
- Wiki Pages - Overall Organization Structure
- Competence (Functional / Professional) Areas and Focus Area(s)
- Wiki Categories
- Wiki Access Rights
- Temporary Wiki Templates
- Procedure for Reorganizing Wiki Pages & Community Involvement
- Wiki Reorganizing Team
- Inputs & Thoughts
CAcert.org Wiki Certificate Login & Know-How Management Tool - comma Project Background
User - CAcert.org Newbies & Wiki Authors / Editors
- CAcert.org Community Members want Certificate Login to other CAcert.org web applications, beside of blog, means wiki and future application as forum as well.
- Today CAcert.org wiki is used the usual way, means by adding somewhere a Wiki page with Wiki title, headline, content and links, respecting more or less Wiki relevant technical rules only. User looking for information about CAcert.org related topics, have to use search functionality to find the desired information hopefully.
For technically interested Users
more about Wiki - source: en.wikipedia.org
more about Knowledge Management - source: en.wikipedia.org
comma Purpose
- To become a Know-How Management Tool, somehow an interactive book, for CAcert.org Community
- Make CAcert.org Newbies Community contribution as easy as possible, as they can find information desired in various ways and still have the overview
Know-How Management Tool
- CAcert.org wiki to become the place to find in various ways the information or know-how needed.
Wiki Search is offered by several ways as: Search by Title; Search by Text Keyword; Search by Category and Search by Competence Areas Index, e.g. for Brain, Technology and comma
- Certain wiki pages may be protected for reasons as, e.g. important content, key for cross-linked structure, et cetera
CAcert.org Visual Identity applies or is even mandatory for CAcert.org Wiki as well. - If not respected quite disciplined, it becomes superfluous and is waste of time and energy.
Wiki Pages - Overall Organization Structure
- Today is no overall project structure, beside attempts for certain sections, related to wiki Categories. Consequences are, that everything is more or less available, but quite hard to be found for new CAcert.org committers and practically impossible to get an overview for Mr. or Mrs everybody.
Thus, leading thought is, Usability & Look of Cacert.org Wiki for the Internet User, with other word, when it is presented to the Community and the public.
- The structure of the Wiki or the tree structure path to the residence of your Wiki page has nothing to do with the importance of "your" wiki page(s) or the value you add to CAcert.org. It is just an organizational measure, to make this structure clearly arranged and usable for all CAcert.org Community Members.
To map the overall project structure 3 Competence Areas, divided in Sections might make sense. These 3 areas have Functional or Professional Focus. Areas and Sections are networked, in order to be used as an interactive book or work of reference. - Rough basis of idea is somehow, the organization structure of a (commercial CA) company, means not the CA or PKI organization as such, but the simple and generalized company structure, with divisions like: software development & production, finance & administration and marketing & sales. - This actual structuring attempt is a proof of concept and aims not to interfere with existing Wiki pages.
Additional to the 3 functional or professional areas called Competence Areas. It is possible, that Focus Areas as CAcert.org Community or Quality Management can be added, simply by adding 1 new Wiki page what serves mainly as filter or link page.
It is clearly understood, that Competence Area or Focus Area / Section / Sub-Section are mainly serving as directory or table of contents with explanatory content to give a better overview and understanding, thus to allow newbies quickly to understand, what CAcert.org is all about and find their way to contribute at best.
Competence (Functional / Professional) Areas and Focus Area(s)
Brain Competence Area contents to everything related to administration and evolution of the CAcert "(direct) democracy", as CCA (Analogy: Constitution), Policies (Analogy: Laws), Arbitration & Dispute Resolution (Analogy: Supreme Court), Education & Training, Management & Quality Audit, CAcert Inc. and Study, the project Section of Brain.
Tree Structure Path Layout is Competence Area / Section / Sub-Section. Upon demand, more might be added.
- Brain
- Brain/PoliciesAndSignificantTechnicalStandards
- Brain/ArbitrationDisputeResolution
- Brain/EducationTraining
- Brain/CryptographyLibrary
- Brain/MgmtQualityAudit
- Brain/CAcertInc
- Brain/Study
- Note: There are technically 6 Sub-Sections, but on the Internet you see 7, as CCA is prominently promoted, but linked to official versions place.
- Sections Wiki pages usually provide an overview and links to detailed know-how or detailed content.
more about Direct Democracy source: en.wikipedia.org
more about Constitution source: en.wikipedia.org
more about Law source: en.wikipedia.org
more about Supreme Court source: en.wikipedia.org
Technology Competence Area contents relates to all technical matters, as infrastructure, systems administration, technical support and to technical knowledge / how-to's and the Technology project Section, Laboratory.
Tree Structure Path Layout is Competence Area / Section / Sub-Section. Upon demand, more might be added.
- Technology
- Technology/TechnicalInfrastructure
- Technology/CriticalSystemAdmin
- Technology/NonCriticalSystemAdmin
- Technology/TechnicalSupport
- Technology/KnowledgeBase
- Technology/Laboratory
- Note: Sections Technology/TechnicalInfrastructure, Technology/CriticalSystemAdmin and Technology/NonCriticalSystemAdmin do not exist yet, due to lack of technical know-how. Support is accessible through comma/Community as well.
comma Competence Area contents relates to all CAcert.org Community communication and marketing aspects, the offerings to the Community, the arsenal of communication and marketing weapons, all event related activities and the Workbench, as the project Section of comma.
Tree Structure Path Layout is Competence Area / Section / Sub-Section. Upon demand, more might be added.
- comma
comma/Community -> could also be just Community as a Focus Area
- comma/Offering
- comma/Identity
- comma/Arsenal
- comma/RegularCampaigns
- comma/SpecialCampaigns
- comma/Workbench
- Note: There are technically 7 Sub-Sections, but on the Internet you see 6, as Campaigns is on the Internet visible as 1 Section divided in 2 Sub-Sections.
Alternatively the CAcert.org Community could be separated as a special Focus Area, it's contents relates to all CAcert.org Community facets.
CAcert.org Wiki Main page (content to be defined) will be the final keyhole to access the 3 Competence Areas and as well access to specific and important Sections , e.g. Community or Support. But can still be accessed by Category or keyword search.
Wiki Categories
- Purpose of Categories is to allow search by relevant CAcert.org Wiki categories. Each wiki page is tagged with at least one or more Category.
- List of all significant Categories you find with search function and keyword:
Actual Search with Keyword "CategoryCategory"
#
Description / Purpose
01.
02.
03.
04.
05.
06.
07.
08.
ContentReviewTeam/case0030
09.
OpenID
10.
SystemAdministration/Systems
Actual Search with Keyword "Category"
#
Category
Description / Purpose
01.
02.
03.
04.
05.
06.
07.
08.
09.
10.
11.
12.
13.
14.
15.
Objective: One reviced / reassessed, meaningful list with description. Proposal: Take each Competence Area as a Category, add titles within an Area as Category and supplement with additional Categories if helpfull
Search with Revised / Cleand-Up Keyword
#
CategoryCategory? or Category?
Description / Purpose
01.
02.
03.
04.
05.
06.
07.
08.
09.
10.
11.
12.
13.
14.
15.
- more significant Categories?
Wiki Access Rights
- Every CAcert.org Community Member is allowed and is expected to add content
- Today - User password
- Tomorrow - Certificate Login Only
Temporary Wiki Templates
Procedure for Reorganizing Wiki Pages & Community Involvement
- In case of a new CAcert.org Wiki page, try if ever possible to add it in the relevant Competence Area and the most appropriate section. This is visible in the path, as a classical tree structure.
- In case of an existing CAcert.org Wiki page to change place within Wiki, define final place and proceed as follows:
- Add on existing site on left top (path/path/path/newsite serves as example only):
#REDIRECT <path/path/path/newsite
- Add on exixting site on left bottom:
CategoryRedir
Copy & Paste content of depreciated wiki page in new wiki site.
- Add on existing site on left top (path/path/path/newsite serves as example only):
Announcement and invitation for comments on Main E-Mail List: cacert@lists.cacert.org
Wiki Reorganizing Team
For active contribution join comma Arsenal Development & Design Team
Inputs & Thoughts
20090910-UlrichSchroeter - some notes from IRC, email discussions
* add default permissions: Admin Full, Everyone Read (done) * Structure by ... * folders (comma project) * Category's (Tags) * Heading * Design modifications from bordeaux red to CAcert blue, CAcert.org Visual Design, relates to /comma/Identity/VisualDesign -> CAcert.org Colors, Blue - HTML #11568C, see also [[/comma/Identity/VisualIdentity|Visual Identity]] * proposal: for Email posts use { { { and } } } (but links doesn't works) * how to escape special chars in the wiki ? more ... [[HilfeZumFormatieren|Help formatting]] * how to add global images to a wiki image shared folder ?
20090911-hugi
Wiki as such was basically intended to be used for quick idea writing, thus "chaos" is a consequence. But, Wiki has by far much more potential, e.g. to become a "Know-How Management Tool" in a long term run for CAcert.org, without loosing it's original purpose or "roots". - That's the beauty! :-) - So, "chaos" relates more to comma, than to Technology, except certain technological implementations / modifications, e.g. Categories, Template building once Structure is more clear (-> Relates to Page Layout -> CAcert.org Design, more to come). - BUT, it will NEVER be a mandatory, how to use the Wiki, everybody decides him / herself, how to use it, in terms of content. - [[comma/Identity/VisualDesign|CAceret.org Visual Design]], in marketing theory - Corporate Design, short CD - is an other story, but can be solved by offering a range of templates, thus Wiki users have still the freedom of content. Sounds like a fair deal?
20091012-UlrichSchroeter
http://wiki.cacert.org/CategoryDepreciated The pages in this category are depreciated and outdated. Please do not trust on them. They are kept for archiving reasons and might be deleted in future. List of pages in this category: soll heissen ... wenn du Seiten am umstellen bist, waere es m.E. sinnvoll bei den "alten" Seiten ein #REDIRECT <neue seite> am Anfang und ein !CategoryDepreciated ans Ende einzufuegen ,-) dann koennte man diese Seiten dann irgendwann man gezielt loeschen, wenn saemtliche 'alten' Links irgendwann einmal aktuallisiert sein sollten ...
20100819-UlrichSchroeter
!CategoryDepreciated on redirection pages results on a listing of active pages as Depreciated. So therefor, I've added a 2nd Category for those pages, that redirects from old pages to new pages: !CategoryRedir So real depreciated pages should be tagged with !CategoryDepreciated if they'll never be used. But on most redirected pages, users knowing the short tags will be redirected to the new page with a long path, that nowbody will remind. So the redirection pages should be as they are, as redirection pages and therefor needs their own Category: !CategoryRedir and not to be Depreciated
YYYYMMDD-YourName
Text / Your Statements, thoughts and e-mail snippets, Please
Category or Categories