Salut,

The RSS feed for the wiki pages is available at 
http://dev.librehwdb.tuxfamily.org/tiki-wiki_rss.php?ver=2&css=y
(I've put 20 pages by default instead of 10). I use http://rss4you.com to
monitor it, you may choose any RSS browser convenient for you.

The link http://dev.librehwdb.tuxfamily.org/tiki-lastchanges.php shows by
default changes of the current day. And
http://dev.librehwdb.tuxfamily.org/tiki-listpages.php shows all pages on the 
wiki.
Articles can be done too, I have not yet identified what we'll put in it,
perhaps HowTo... as a matter of fact, the http://dev.librehwdb.tuxfamily.org
is mostly an area for developements (not yet the web-front-end I have in mind)
so that we can test and see if tikiwiki will be part of it later on. For the
time being, I think we'll mostly use the wiki part of it to document what is
to be done and how. The mailing-list is to be used for discussions (in english
as much as possible) to enable contributors to be involved later on, as they
can follow our preliminary discussions archived at
https://mail.gna.org/public/librehwdb-dev/

We have to choose a license for our work as soon as possible. 
http://dev.librehwdb.tuxfamily.org/tiki-index.php?page=License+Choice
The easiest if for tools ; though I prefer GPL v2 and later versions, I think
that BSD license is more appropriate for *BSD. This may have an impact on the
license for the content of the database as it may be used in either kind of 
tools.
Ideas are welcome, or we'll have to ask to people knowing better than us.

Our first work is the database scheme, which we can implement at
http://demo.librehwdb.tuxfamily.org (a MySQL db is available too with
phpMyAdmin access).
We can store scripts and tools at https://gna.org/projects/librehwdb/ in cvs
or svn (I've not much experience with the latter, though it seems more
promising), we can begin with cvs to share files then see if svn is more useful.
For the moment being, I've added the proposed scheme at
http://dev.librehwdb.tuxfamily.org/tiki-index.php?page=Doc%20Database%20Schema
so that we can discuss it in the other thread.

@++
Ben'. aka baud123

Reply via email to