Last week at work I heard Geoff Harrison (madrake, enlightenment)
saying that one of the developers on E was asking to be able to take
place in the sourceforge-hosted discussion forums via email. He was
asking this of one of the sourceforge developers.
The response he got back was something to the effect that "everything
will be able to be interacted with via email" at some time in the
future.
We can take this as a(n?) blatant rumor that email interaction with
sourceforge bug tracker is already on the roadmap.
Unless anyone is opposed to this, I will commence setting up the rest
of the gnucash infrastructure on sourceforge.
This will consist of the following:
gnucash website at gnucash.sourceforge.net.
This is already done. There is an rsync client on our shell
account, so the webmaster (Jeremy, right?) can continue to
update the web site wherever they want to, and updates can be
done hourly, daily, whatever.
change the ip address of www.gnucash.org to point to 198.186.203.36.
No big deal if this doesn't happen. VA's marketing department
would be glad to absorb the bandwidth costs for this site
(like it would be noticed. :-)
adding developers to the site.
please go to sourceforge and become a developer.
https://sourceforge.net/account/register.php if you don't
already have an account. Let Jeremy or I know, and we will
make you gnucash developers. This will let you do a lot of
things to the gnucash area of sourceforge, work with bugs,
post to discussions, all of the things which require your name
to be used. Also, if you want to help with administering, we
can set you up as a gnucash admin.
Note that there are two different things mentioned here. One
is "Project Admin", and the other is "Developer". I would
hope that all who post here will become "Developer", and those
who want to help admin it will become "Admin".
moving the bugtracking over.
I can go over the open bugs at the current site and work on
getting many of them closed out right quick like. I will then
bring over the still open bugs. Will anyone have major
heartburn if we don't bring over all of the closed bugs?
moving the mailing lists over.
we can put them both there, gnucash-devel and gnucash-patches
without any trouble. The archives, I don't know. I can ask
the geocrawler people at work. They will know for sure.
evaluating sourceforge for other things.
sourceforge is trying to be a complete "toolkit" (my word,
they probably have something more marketing friendly) for
teams of people working on open source software. I see two
valuable things which they bring to the table for groups.
Bandwidth and sysadmin work. Disk space we can all do for
next to nothing. Same with computers. Bandwidth isn't free,
neither is our time. Also, they are implementing tools which
can help, even though other teams might not have implemented
them on their own. Here is a rundown on what they have for
tools, and my take on their impact on our project.
Project Homepage. Our web site. This directly translates to
bandwidth and admin time. They keep apache running, they pay
the bandwidth bills.
Public forums, which are kind of like mailing lists, but
different somehow. I am not sure how they are different, or
how we would use them. Maybe for groups who grew up with news
instead of mailing lists (but then read the mailing list
archives, I know. :-)
Bug tracking should be improved there, with us missing out on
email interaction for a while, until they implement.
Patch manager. I haven't looked too closely at this, but it
looks like it would help out with some of what we do on
gnucash-patches.
Mailing lists. The archival here is done automatically, and
it is also searchable. The search index is updated nightly.
Surveys. We haven't used them yet. Now we have the place to
do so if we want.
CVS Repository. Here we get to save linas some $$$. I don't
know if we will want to actually move the repository here, or
use rsync back to linas' repository. We should be able to
have multiple modules here, too. Also, cvsweb is already
there, waiting to be used, at
http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/?cvsroot=gnucash
Anonymous FTP space.
Release area. We can have our releases online, showing which
parts we want to release, and not showing the parts we don't
want.
News area. whoop-de-doo. ;-) with this part, I almost
wonder if they aren't trying to get us to put our web site
completely on theirs. But I suppose we could use it for
something.
The setup on there will commence immediately, beginning with rsync
schedules with jcollins to the website, setting up of mailing lists
and updating the bug trackers.
If anyone has any questions, please bring them up right away.
rob
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
