To the Koha development community, I am in the process of writing a news story about the recent grant from EBSCO Information Services to support some major development initiatives for Koha. This seems to be an important opportunity for the Koha community to accelerate development that might have otherwise taken longer to accomplish.
As part of the context for this article, and for other reports and presentations that I make that include Koha, I would like to be able to provide a quantitative measure of the total amount of personnel resources contributed globally towards the development of Koha. I understand that several firms dedicate specific amounts of personnel to Koha development and that there are dozens of individuals that make commits to the code, write documentation, or perform quality assurance. I would appreciate it members of this list would help me compile a current figure on the number of FTE involved in Koha development. To end up with a consistent quantifiable measure, the following definitions would apply: 1 FTE (full time equivalent) = 1 person working full time for 1 year. Full time = 40 hours per week 50 weeks/year. An individual that contributes 20 hours per week on Koha for the whole year= (20 hours per week * 50 weeks per year) / 2000 hours per year = .5 FTE An individual that contributes 20 hours total for the year: (20 / 2000) * 100 = 0.01 FTE Could each of the support firms or individuals involved in Koha development please either post to this list or send to me individually the FTE that you or your organization contributes for each of the major categories of activity? For example: Company XYZ: 5 FTE development, 1 FTE Documentation, 1.5 FTE Quality Assurance. Alternatively, the number of hours per year contributed could be given instead of FTE and I'll perform the calculations. If there is a better way to quantify the resources devoted to Koha, I would be interested in your suggestions. I believe that documenting the development resources involved in Koha will help those outside the community have a better understanding of Koha's potential to continue to be enhanced to meet the needs of libraries. I need to get this article to the publisher (ALA TechSource) in the next day or two, it would be great to hear from you soon. Thanks very much for your help with this request. -marshall Marshall Breeding marshall.breed...@librarytechnology.org<mailto:marshall.breed...@librarytechnology.org> www.librarytechnology.org/<http://www.librarytechnology.org/> twitter.com/mbreeding http://www.linkedin.com/in/breeding http://scholar.google.com/citations?user=NnvfJ5cAAAAJ _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
