. '''To CAcert.org [[ProposalFutureWikiMainPage| Wiki Temporary Start Page]]''' - '''To CAcert.org [[Community]]''' - '''To CAcert.org [[Brain]] Area''' - '''To CAcert.org [[comma]] Area'''
----
== CAcert.org Technology Area ==
. Is short for all technological matters.
. PKI, CA, RA etc
.'''Technology''' is a interlaced part of '''CAcert.org Areas''' networked as - '''[[Brain]]''', '''Technology''' and '''[[comma]]'''
. {{attachment:CAcert.org_CompetenceAreas.jpg}}
. CAcert.org
. Competence Areas
. [[attachment:CAcert.org_CompetenceAreas_Big.jpg|CAcert.org Competence Areas - Big ]]
<
>
== Technology Mission ==
. Text
<
>
== Technology Area ==
. Intro / Reason Why / Overview Technology Sections
<
>
. '''CAcert.org''' '''[[Technology#CAcert.org_Technical_Infrastructure| Technical Infrastructure]]'''
. ''' [[Technology#Critical_Systems_Administration|Critical Systems Administration]]'''
. ''' [[Technology#Non-Critical_Systems_Administration|Non-Critical Systems Administration]]'''
. ''' [[Technology#Technical_Support_for_CAcert.org_Community|Technical Support for CAcert.org Community]]'''
. ''' [[Technology#Technology_Knowledge_Base| Technology Knowledge Base]]'''
. ''' [[Technology#Technology_Laboratory| Technology Laboratory]]''' - Software / Hardware Development & Testing Space
<
>
== CAcert.org Technical Infrastructure ==
. Description / Elements
. Critical Systems
. Non-Critical Systems
<
>
== Critical Systems Administration ==
. Desription / Elements / Roles & Missions
. System Administrators
. Technical Infrastructure
<
>
== Non-Critical Systems Administration ==
. Description / Elements / Roles & Missions
. System Administrators
. Technical Infrastructure
<
>
== Technical Support for CAcert.org Community ==
. Description / Elements, e.g. Manuals, How-To's / Roles & Missions / by E-Mail
. '''CAcert.org''' '''[[Technology/TechnicalSupport| Support Overview]]'''
. '''Support''' for '''[[Technology/TechnicalSupport/EndUserSupport| End Users]]'''
. '''Support''' for '''[[Technology/TechnicalSupport/SysAdmin| System Administrators]]'''
. '''Support''' for '''[[Technology/TechnicalSupport/Developers| Software & Application Developers]]'''
. '''CAcert.org''' '''[[Technology/TechnicalSupport/SupportTeam| Support Team]]'''
<
>
== Technology Knowledge Base ==
. Structured Theory and Practice about Cryptography, Certificates, X.509 etc. from a Tec point of view, maybe linked with Brain for Standards, etc./ Tec Documents / Tec Presentations / From CAcert.org Community Members / Links to relevant Tec Sites...more?
. Technology '''[[Technology/KnowledgeBase| Knowledge Base - Overview]]'''
. '''[[Technology/KnowledgeBase/SignificantTechnicalStandards| Significant Technical Standards]]'''
. '''[[Technology/KnowledgeBase/Server| Server Certificates]]'''
. '''[[Technology/KnowledgeBase/ClientCerts| Client Certificates FAQ]]'''
. '''[[Technology/KnowledgeBase/WebAppCertLogin| Web Application Certificate Login]]'''
.?
<
>
== Technology Laboratory ==
. In Technology Laboratory various Software or even Hardware related Projects are under Development and / or Testing. What else?
. Technology '''[[Technology/Laboratory| Laboratory - Overview Projects]]'''
. Technology '''[[Technology/Laboratory#Technology_Projects_-_Improvement_EXISTING_Software| Projects - Improvement EXISTING Software]]'''
. Technology '''[[Technology/Laboratory#Technology_Projects_-_Design_&_Development_of_NEW_Software| Projects - Design & Development of NEW Software]]'''
. Technology '''[[Technology/Laboratory#Technology_Projects_-_Design_&_Development_of_NEW_Hardware| Projects - Design & Development of NEW Hardware]]'''
. Technology '''[[Technology/Laboratory#Technology_Projects_-_Evaluation_&_Testing_of_NEW_/_EXISTING_Software| Projects - Evaluation & Testing of NEW / EXISTING Software]]'''
<
>
----
== Inputs & Thoughts ==
. 20090922-[[Iang]]
. {{{
the naming based on development / testing etc is not IMHO a good idea. What happens when the project is finished? Do we have to change all the names of the pages? I think we may be better off just linking from this page as an index to the various laboratory ideas... what do you think?
}}}
----
. 20090922-[[hugi]]
. {{{
The idea behind Technology Laboratory is, to have a Section for Project Development work. - Same as for Brain Study or comma Workbench. - Once a Project is finished, means is implemented in CAcert.org technological system, it can be moved (e.g. page re-name) to e.g. Technology Knowledge Base, if its worth to be documented or goes to the section it was intended - And why here on Technology Laboratory all Projects listed? I had at the time then I started no better idea and I didn't wanted to make too long paths. But it can be done as well like for Technology Knowledge Base, with link to Overview and listing of main categories. Finally, what is important for us in terms of Laboratory, is to have a clear view of workload.
}}}
----
. 20091029-[[UlrichSchroeter]]
. Lists with actual Sys Admins / contacts
. [[SystemAdministration|System Administration Overview]]
. [[SystemAdministration#Systems|System Administration Individual Systems Overview]] Each listed individual page includes the related System contacts
. [[https://community.cacert.org/staff.php|SysAdmins Overview]]
----
. 20100218-[[Iang]]
. {{{
The term "technology" has to be treated with care in a tech-heavy environment. One thing that does not sit well in "technology" is the "RAs". Our RAs are assurers, and around 98% of their process and daily activity is non-technological. Meetings face-to-face, events, co-auditing, training, 7 years of paper storage, ball-point pens, etc. The only part where they hit technology is when they enter a number from 10 to 35 against an email address, and when they turn a UV lamp against paper dox.
I see the Assurers as the backbone of our community.
The same thing can be said of the Support group, although to a lesser extent, because they do have daily interaction with email and tracking systems. But to call use-of-email a "technology" is like calling a ball-point pen a technology. That misses the real society point, a ball-point pen is just a better pen; and an email is a better letter or a better phone call.
To go blue sky and speculate more ... what I would like to do is integrate the Triage concept even further into the Assurers, our backbone-of-community. Not now, but sometime in the future; I envy the ability of (say) slashdot to deputise faithful readers to do a week's service for the community, marking posts up & down. They know how to tap their community, we can do so as well.
}}}
----
<
>
'''Category''' or '''Categories'''<
>
CategoryCustom