3.4 Development - Need input
Folks, we are about to start a development project in the areas of: Acquisitions: Approvals & payments Serials: Budgeting and improvements in subscriptions Article Indexing/Analytical records SDI We expect this to be between 250-350 person days of effort. Since this is our first involvement in software development, I will appreciate any input in how to proceed. We are essentially concerned about making sure that most or all of the code is accepted. And the patches are accepted into 3.4 not in later versions. We also don't want to work on stuff others are already working on. Thanks, Savitra Sirohi Nucsoft OSS Labs http://www.osslabs.biz
* savitra sirohi (savitra.sirohi@osslabs.biz) wrote:
Folks, we are about to start a development project in the areas of:
Acquisitions: Approvals & payments Serials: Budgeting and improvements in subscriptions Article Indexing/Analytical records SDI
Excellent :)
We expect this to be between 250-350 person days of effort.
Hopefully some of that is parallelisable :) 3.4 Is a short release, (6 months) primarily aimed at perfomance and clean up. Of course any new features that can be completed in that time are eligible for inclusion too.
Since this is our first involvement in software development, I will appreciate any input in how to proceed. We are essentially concerned about making sure that most or all of the code is accepted. And the patches are accepted into 3.4 not in later versions. We also don't want to work on stuff others are already working on.
The main things to do is, submit early and submit often. IE don't wait until you have finished all your work, specially big things, develop publicly if possible and make things available for QA and other testing as early as possible. The sooner it's available for Colin (as QA manager) and I (as Release Manager) to look at it, the more likely it is to make it in. The other thing is describe what you are working on in an RFC on the wiki, and make a bug in bugs.koha-community.org that links to it. Colin might have other suggestions, but from my point of view the main thing is communicate lots and develop as publicly as you can. Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
2010/8/23 Chris Cormack <chrisc@catalyst.net.nz>:
The other thing is describe what you are working on in an RFC on the wiki,
Wiki page is here: http://wiki.koha-community.org/wiki/RFCs_for_Koha_3.4 Thanks Nicole
On 23/08/10 12:59, Nicole Engard wrote:
2010/8/23 Chris Cormack <chrisc@catalyst.net.nz>:
The other thing is describe what you are working on in an RFC on the wiki,
One thing that helps greatly is to write good commit messages. The best ones don't only say what you did "Added new xyz" but give some indication of why you did it, "The new xyz allows abc", that bit of logic can help people who have to maintain or extend the code later. Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 208 366 1295 (phone) +44 (0) 7759 633626 (mobile) colin.campbell@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com
On Mon, Aug 23, 2010 at 7:14 AM, Colin Campbell <colin.campbell@ptfs-europe.com> wrote:
One thing that helps greatly is to write good commit messages. The best ones don't only say what you did "Added new xyz" but give some indication of why you did it, "The new xyz allows abc", that bit of logic can help people who have to maintain or extend the code later.
As the one who has to document your devs for users I very much appreciate those messages! Commits with explanations are easier for me to document. Nicole
savitra sirohi wrote:
Folks, we are about to start a development project in the areas of:
Acquisitions: Approvals & payments Serials: Budgeting and improvements in subscriptions Article Indexing/Analytical records SDI
As in selective dissemination of information? Cool beans!
We expect this to be between 250-350 person days of effort.
Since this is our first involvement in software development, I will appreciate any input in how to proceed. We are essentially concerned about making sure that most or all of the code is accepted. And the patches are accepted into 3.4 not in later versions. We also don't want to work on stuff others are already working on.
I'll leave it to the RM to say how he'd like it passed best, but I guess http://wiki.koha-community.org//wiki/Enhancement_Request_Guidelines will apply. Just wanted to check I'd got the right SDI, really. Regards, -- MJ Ray (slef) Webmaster and developer for hire at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op
participants (5)
-
Chris Cormack -
Colin Campbell -
MJ Ray -
Nicole Engard -
savitra sirohi