Massimiliano Pala wrote:
> 
> Michael Bell wrote:
> >
> I have to say we should stop adding new features and start fixating
> major bugs/lacks or we will never come out with the new release...

That's ok. I'm only fixing in the last time too.
> 
> How about your work ??

I have to generate some files for the RBAC (not CBAC!!! - what is CBAC?)
the rest looks ok.

> As far as I know we need to integrate the changes you made about the
> CBAC into the DB module as well as the revoke requests.

That's correct. First we need five additional databases:
* RBAC
* PENDING_CRR
* APPROVED_CRR
* ARCHIVIED_CRR (is archivied correct?)
* DELETED_CRR

> 
> Also I need a list of the currently used modules having the SNAPs to
> install (at least this!) fine.

DBI, DBIS, RBAC

> I have taken a look at the docs/ dir into the openca main archive and
> I think we definetely have to find out a docs structure. I think we
> should remove all docs/ from there and put there man pages to be
> installed when the make install- process takes places.

listen good.

> Modules documentation will be installed by single module installation
> procedure - so the 'make install' for each module will install the POD
> documentation you can add to the end of the module source code.

I don't like to store the documentation directly in the sourcecode. Is
there another solution to store the POD-docs for the perlmodules?

> In the openca/docs directory we will put general openca man pages:
> 
>         openca (or OpenCA) - with general CA infos and links to
>                              modules docs;
> 
>         *.conf - with keywords and options for the related config
>                  file ( i.e. ca.conf, raserver.conf, public.conf,
>                  dbi.conf, etc... )
> 
> What do you think about it ???

Listen quite good. Who write it ;-D

> Just the last thing: I need all the .conf options for your modules
> (DBI, CBAC, etc... ) and the status of the signing daemon.

This will take some time to check all my conf-files.

Could you establish a second page beside the about-page where you
publish all actual developers? I was a little bit surprised about the
comment of Eric Bergeron who mails a comment to a bug that he works on
the OpenCA::OpenSSL module as an OpenCA-developer.

So it's a nice thing to have many testers and programmers but than we
must improve our organization ;-D

Did we ever announce the official usage of the bugtrackingsystem of
sourceforge?

Regards Michael

S/MIME Cryptographic Signature

Reply via email to