Upcoming emails from Nicholas
Hi All This is just a bit of a heads up. Ive asked Nick to help me with coordinating Koha work a bit more. Now we have a few ppl actively working on the code, im finding im loosing track of who is working on what, etc. So I think Nick is going to email around, find out what everyones up to, and build some kinda status report, and make some suggestions in how to move forward. A suggestion he has made already, which I think has merit, is creating a development/stable situation. So we have a stable release cvs tree , and bugfixes and tidy ups get added to that. While we work on new features in the development tree. When new features become stable and tested enuff, we shift them into the stable tree and do a new release. Also I feel we need to be doing more regular releases, so that bugfixes are getting out into the public. Any other suggestions gratefully accepted. Oh, an idea ive just had myself, playing with Roger's wiki to work on the install, I think this is a good way to work on collaborative documentation. Perhaps we could put todo list type things up there, that ppl could add/modify to? Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
On Mon, 2002-04-15 at 10:07, Chris Cormack wrote:
This is just a bit of a heads up. Ive asked Nick to help me with coordinating Koha work a bit more. Now we have a few ppl actively working on the code, im finding im loosing track of who is working on what, etc.
I was looking at this issue over the weekend, and was thinking that maybe we should make better / more efficient use of the services available through SourceForge. Especially the bug tracker, feature request and documentation facilities.
A suggestion he has made already, which I think has merit, is creating a development/stable situation.
Also I feel we need to be doing more regular releases, so that bugfixes are getting out into the public.
I agree,
Any other suggestions gratefully accepted.
One other thing that I think good be useful is that maybe we should look at something like a Weekly/Monthly summary (an example being what the Midgard team use <http://www.midgard-project.org/news/mws/>. This would allow us to increase the potential audience of the project (wider audience == more developers). Just my 0.02 cents worth (GST inc) ;) Mike
On Mon, 2002-04-15 at 10:07, Chris Cormack wrote:
[--snip--]
im finding im loosing track of who is working on what, etc.
Mike Mylonas wrote:
I was looking at this issue over the weekend, and was thinking that maybe we should make better / more efficient use of the services available through SourceForge. Especially the bug tracker, feature request and documentation facilities.
[--snip--] Maybe because I don't come from a development background - I find it hard to beat the list server (when volume is light anyhow ;^). There is a real big difference between going out to actively look for reports /requests compare with the attention they get when they arrive via email. Can sourceforge be set to auto notify by email? I must admit I've never seriously looked at at sourcefore documentation utilities - I'll try to bring myself up to speed on that over next few days. Personally, I find 'wiki' a fantastic tool for "documentation-as-you-go"... R.
On Mon, 15 Apr 2002, Roger Buck wrote:
On Mon, 2002-04-15 at 10:07, Chris Cormack wrote:
[--snip--]
im finding im loosing track of who is working on what, etc.
Mike Mylonas wrote:
I was looking at this issue over the weekend, and was thinking that maybe we should make better / more efficient use of the services available through SourceForge. Especially the bug tracker, feature request and documentation facilities.
[--snip--]
Maybe because I don't come from a development background - I find it hard to beat the list server (when volume is light anyhow ;^).
There is a real big difference between going out to actively look for reports /requests compare with the attention they get when they arrive via email. Can sourceforge be set to auto notify by email?
I must admit I've never seriously looked at at sourcefore documentation utilities - I'll try to bring myself up to speed on that over next few days. Personally, I find 'wiki' a fantastic tool for "documentation-as-you-go"...
It also seems to work well for coordinating design ideas. The inforal approach, interleaving of comments, and availability of the whole flow of conversation seem to be very helpful. -pate
R.
_______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel
On 15 Apr 2002, Mike Mylonas wrote:
On Mon, 2002-04-15 at 10:07, Chris Cormack wrote:
This is just a bit of a heads up. Ive asked Nick to help me with coordinating Koha work a bit more. Now we have a few ppl actively working on the code, im finding im loosing track of who is working on what, etc.
I was looking at this issue over the weekend, and was thinking that maybe we should make better / more efficient use of the services available through SourceForge. Especially the bug tracker, feature request and documentation facilities.
A suggestion he has made already, which I think has merit, is creating a development/stable situation.
Also I feel we need to be doing more regular releases, so that bugfixes are getting out into the public.
I agree,
Any other suggestions gratefully accepted.
One other thing that I think good be useful is that maybe we should look at something like a Weekly/Monthly summary (an example being what the Midgard team use <http://www.midgard-project.org/news/mws/>. This would allow us to increase the potential audience of the project (wider audience == more developers).
If we're going to do this (and it's a good idea, IMHO), we should start a ChangeLog file to track updates so that we can readily extract them for a weekly/monthly article. It would also be nice to get some idea of what improvements people are going to be coding on the devel tree. A related idea would be the POW/ZAP thing that abiword does. The general idea is that one (or more) POWs (projects of the week) are posted to a mailinglist/wiki/website/etc, then when people commit code to close out a POW they get some public kudos in the form of a ZAP. (hrrm, maybe you should go look at the abiword project to get a better explanation ...) In any case, both of these could be sent of to people like lwn.net, gnu-friends, and OSDN for wider publicity. -pate
Just my 0.02 cents worth (GST inc) ;)
Mike
On Mon, 15 Apr 2002, Chris Cormack wrote:
Hi All
This is just a bit of a heads up. Ive asked Nick to help me with coordinating Koha work a bit more. Now we have a few ppl actively working on the code, im finding im loosing track of who is working on what, etc.
So I think Nick is going to email around, find out what everyones up to, and build some kinda status report, and make some suggestions in how to move forward.
Great Idea.
A suggestion he has made already, which I think has merit, is creating a development/stable situation.
So we have a stable release cvs tree , and bugfixes and tidy ups get added to that. While we work on new features in the development tree. When new features become stable and tested enuff, we shift them into the stable tree and do a new release.
This sounds good. I'll have to dig back into the cvsbook to get a feel for working with multiple branches, but that's a low hurdle for the gain we should get.
Also I feel we need to be doing more regular releases, so that bugfixes are getting out into the public.
Any other suggestions gratefully accepted.
The biggest things that have bothered me as I've been digging in the code and refactoring stuff is the lack of comments/documentation and the lack of tests around things (esp. the modules). Being more rigourous about getting into the codebase will help everyone out a lot.
Oh, an idea ive just had myself, playing with Roger's wiki to work on the install, I think this is a good way to work on collaborative documentation. Perhaps we could put todo list type things up there, that ppl could add/modify to?
I'd be up for it (wikiwiki is good.) -pate
Chris
participants (4)
-
Chris Cormack -
Mike Mylonas -
Pat Eyler -
Roger Buck