Hi Everybody,
I've made a couple infrastructure additions to the gEDA project.
A while ago I had two mailing lists created (thanks Roger) for gEDA to use:
geda-bug and geda-cvs
The first one is called 'geda-bug' and is the gEDA jitterbug
<-> mailing list gateway. When somebody submits a bug via jitterbug,
the bug report is forward to the mailing list and then further discussions
can occur on the mailing list. Also, people can post bug reports to the
mailing list (though I haven't figure out how to get them into jitterbug
without cluttering up the database with dicussions). You can also submit
a bug directly into the gEDA jitterbug database by sending e-mail to
geda-bugs AT seul.org Be sure to include the gEDA version, OS as
well as a valid e-mail address. Note: I think I have this gateway working,
however, there might be some problems. Please e-mail if you see anything
wrong.
If you submit a bug report via the web
(http://geda.seul.org/bugs.html) or e-mail by using geda-bugs AT seul.org,
you will be sent a challange-response. This is necessary to keep spam
out of the jitterbug database. In the past you did not have to do this,
but now that I am encouraging the sending of bug report e-mail directly
into the database, I do not have any choice. Once you respond to one
challange, your e-mail address will be whitelisted and you won't have
to respond to another challange (for that e-mail address).
The other new mailing list is 'geda-cvs'. geda-cvs is just
a mailing list which gets a copy of the gEDA cvs commit log messages.
This is handy if you are following the cvs version of gEDA. This way
you don't have to do any cvs updates, unless somebody checks something in.
For information on subscribing and the mailing list archives to
these lists please see: http://geda.seul.org/mailinglist/index.html
Also a couple reminders: geda-user is for user related
questions or experiences. For development related discussions, please
use geda-dev. Also avoid sending messages to both lists (like this
message; sorry :-), unless absolutely necessary. New software release
announcements can be sent to both lists (and welcomed) and at some point
I will get a geda-announce mailing list working.
As usual, send all questions/complaints my way. Thank you.
-Ales
