CAcert Code Development list.

[Alejandro Mery Pellegrini <amery AT cacert.org>]

Dear Board,

After the conclusions reported last week [1] about the real
possibilities to keep using LibreSSL in future we moved to discuss
and document in deeper detail the requirements each kind of user we
have has and then to design the architecture we think we need and an
API.

We used an installation [2] of RedMine [3] to document this process
and it's intended to be kept as central environment for CAcert.org's
Software development community.

At this point, and after some discussions, we moved from the name
"LibreSSL2" to "BirdShack" and renamed the project in RedMine
accordingly.

Please consider this is still work in progress and open to
discussion in order to give CAcert.org the software platform it will
need to be able to handle correctly the future it's foreseen. But on
the other hand we are aware that we need to move quick to be able to
be ready on time.

A summary of the work can be found in the Work History
<https://dev.cacert.cl/wiki/birdshack/Work_History> page.

At a macro level the most important documents are:
* Principles <https://dev.cacert.cl/wiki/birdshack/Principles>
* Scope <https://dev.cacert.cl/wiki/birdshack/Scope>
* Architecture <https://dev.cacert.cl/wiki/birdshack/Architecture>

The functional requirements were collected in the Actors
<https://dev.cacert.cl/wiki/birdshack/Actors> page, and in the quest
to define a RESTful interface the resources were identified in
Resources <https://dev.cacert.cl/wiki/birdshack/Resources> page and
finally the URL Space
<https://dev.cacert.cl/wiki/birdshack/URL_Space>, that will lead to
the API and the data model, was completed and tested against the
requirements.

Please feel free to comment and to register in dev.cacert.cl which
hopefully will become dev.cacert.org soon.

[1] https://lists.cacert.org/wws/arc/cacert-board/2009-04/msg00069.html
[2] https://dev.cacert.cl/
[3] http://www.redmine.org/

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature