Software
Team(s)
Security Policy Section 7 documents the Software Assessment Team with the role of the security and maintenance of the code. SecurityManual also says more, under SP.
mailing list is the current hang-out place for software people.
The Development Team (rather than the Assessors).
The teams consist of:
- Software Assessment
- under SP
- includes Application Engineers.
- Software Development
- informal, submits patches to Software Assessment
- join the maillist, write code.
- Testing
- informal
- takes patches from Dev, installs it on test server.
- returns test results, sometimes with fixes.
The SA Team appointments are currently under the Board, as Philipp Guering has not the time to devote full energies.
The Software
- Database is described:
Schema currently in use, a wip.
Location Database describes the schema and sources of location information.
- Source code
VMWare Development Image for creating your own test system
(mark the pages describing software with the CategorySoftware label, as seen at bottom)
Software-Assessment
The Software Assessment team consists of:
Philipp Gühring, long-term minder
MarkusWarg, a new Software Assessor appointed by the board in m20100222.3.
Dirk Astrath, a new Software Assessor appointed by the board in m20100618.1.
A new Software Assessment team and project is being built up:
- Status: wip
Current Team: see Software-Assessment Project team
- Objectives:
- Build Testserver + Repository Server Image(s) (VM) (Wytze, Andreas)
- Create Repository System (Markus, Michael)
- Create Testserver (Environment)
- Build + Document Software-Patches Flow Process
- Build + Document Path Software-Assessment Team / Critical Team
- Build + Document Emergency Patches Path
Development Process
Bugs Tracking System (a.k.a. Mantis) is where all changes to the software should be entered into, requested, prioritised and tracked.
AuditSystemTasks are some business tasks that should be in Bugs.
Brain/Study/COrbitCA is the renamed CCA Rollout Project?
notes on current development process (customary not standard)
Testing is part of the general Software area:
CCA Patch Testing project has now been sliced up into several mini-patches
BirdShack
One effort is the creation of a new CA in software, called BirdShack. Current situation:
Architectural work from the Innsbruck Software MiniTOP (April 2009).
- Early design notes are in the repo. Hmm, any URL for reference?
we need to rationalise all this doco stuff
The repository is part of the main Software Assessment repository system.
Team consists of MarioLipinski + Iang. Alejandro and Philipp D also contributed at the Innsbruck Software MiniTOP.
Links and references:
PKISoftware is a list of "competing" products that might fit the bill. Why re-invent the wheel?
Deprecated repository: original BirdShack wiki (cl)
Possum is a conceptual project / idea to do a signing server / secure module.
some ideas to add to BirdShack from Ted.
Software/IntegrationInterface might be new ideas for better interfaces.
Infrastructure
In support of software development, there are various systems:
Requirements for Source Code Repository. Starter page rather than a specification, comparisons.
SystemAdministration/Systems/Test is the Infrastructure group's page on the Test system. Running Test systems is a shared responsibility, and, as it is open to download and setup, it is more important that it is done and documented and shared than who does it.