Re: [Koha-devel] Integrating PTFS code into 3.4
On Wed, May 12, 2010 at 1:20 AM, Frederic Demians frede...@tamil.fr wrote: Thanks a lot to PTFS for contributing back to Koha its customer's code. Ditto from me!! It is awesome to see so many new developments made public for all to benefit from. [snip] This process would avoid having orphan functionalities without any documentation or with incomplete documentation. Better yet, this process makes it so that other developers don't start working on the same functionalities - having everything documented up front makes it so that each developer can seek sponsorship for a new feature instead of doubling the work that another developer is already doing Thanks Nicole C. Engard ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Integrating PTFS code into 3.4
Re: 1. Specifications are published on Koha wiki in RFC section. in your message. At and after Kohacon last year, the general understanding for developers was that new development should be posted in bugzilla as enhancements instead of to the wiki RFC, and that's the procedure we followed. Most of the bug reports for these features have been in bugzilla since last summer. Has there been a change/reversion in procedure? Or has this question ever been resolved? Jane Wagner Library Systems Analyst PTFS Inc. Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwag...@ptfs.com -Original Message- From: koha-devel-boun...@lists.koha.org [mailto:koha-devel-boun...@lists.koha.org] On Behalf Of Frederic Demians Sent: Wednesday, May 12, 2010 1:21 AM To: Chris Cormack Cc: koha-devel Subject: Re: [Koha-devel] Integrating PTFS code into 3.4 Thanks a lot to PTFS for contributing back to Koha its customer's code. I'm hoping that PTFS can help creating these branches, but anyone can do so at let me know where to pull from. They need to have the changes isolated if possible and be based on new_features. (Which at the moment tracks master). A very valuable and detailed documentation is available in Harley: http://github.com/ptfs/Koha-PTFS/raw/harley/HarleyReleaseNotes.pdf It would be great if PTFS technical redactor who edited this precious document could cut-and-past its content per new functionality into Koha wiki. For the future, new functionalities developments could follow this path: 1. Specifications are published on Koha wiki in RFC section. 2. Developers design, code, test and validate with sponsoring library. 3. Then a developer level documentation is published on Koha wiki at the same time the code is proposed to the RM. 4. After integration of new code to main Koha, the Documentation Manager documents the new functionality based on the wiki documentation. This process would avoid having orphan functionalities without any documentation or with incomplete documentation. -- Frédéric DEMIANS http://www.tamil.fr/u/fdemians.html ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Integrating PTFS code into 3.4
On Wed, May 12, 2010 at 9:01 AM, Jane Wagner jwag...@ptfs.com wrote: Re: 1. Specifications are published on Koha wiki in RFC section. in your message. At and after Kohacon last year, the general understanding for developers was that new development should be posted in bugzilla as enhancements instead of to the wiki RFC, and that's the procedure we followed. Most of the bug reports for these features have been in bugzilla since last summer. Jane, I do remember that now that you mention it!! That said, the 3.4 RFCs are already on the wiki - well are being moved to the wiki: http://wiki.koha-community.org/wiki/RFCs_for_Koha_3.4 So, I too ask what the procedure is - should we put them on the wiki bugzilla? or just the wiki? or just bugzilla? Nicole ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Integrating PTFS code into 3.4
Hi, On Wed, May 12, 2010 at 9:04 AM, Nicole Engard neng...@gmail.com wrote: So, I too ask what the procedure is - should we put them on the wiki bugzilla? or just the wiki? or just bugzilla? Both - the bugs database and the emailed RFCs and wiki serve slightly different purposes: * bugs database: complete database of all bugs and enhancements and (via the voting mechanism) a way of gauging interest in a new feature * RFCs - emailed announcement of major new development to solicit feedback on the feature and its design and implementation and to help find anybody who has parallel work underway * wiki - summary of RFCs, another spot to hash out architectural issues, and ideally a starting point for the release notes. This approach does have some redundancy, but that redundancy is a feature, not a bug, as it were. Regards, Galen -- Galen Charlton gmcha...@gmail.com ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Integrating PTFS code into 3.4
Okey Dokey, all of the 3.4 RFCs have been moved to the new wiki: http://wiki.koha-community.org/wiki/RFCs_for_Koha_3.4 -- please add any that are missing there. Nicole On Wed, May 12, 2010 at 9:14 AM, Galen Charlton gmcha...@gmail.com wrote: Hi, On Wed, May 12, 2010 at 9:04 AM, Nicole Engard neng...@gmail.com wrote: So, I too ask what the procedure is - should we put them on the wiki bugzilla? or just the wiki? or just bugzilla? Both - the bugs database and the emailed RFCs and wiki serve slightly different purposes: * bugs database: complete database of all bugs and enhancements and (via the voting mechanism) a way of gauging interest in a new feature * RFCs - emailed announcement of major new development to solicit feedback on the feature and its design and implementation and to help find anybody who has parallel work underway * wiki - summary of RFCs, another spot to hash out architectural issues, and ideally a starting point for the release notes. This approach does have some redundancy, but that redundancy is a feature, not a bug, as it were. Regards, Galen -- Galen Charlton gmcha...@gmail.com ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Integrating PTFS code into 3.4
Thanks a lot to PTFS for contributing back to Koha its customer's code. I'm hoping that PTFS can help creating these branches, but anyone can do so at let me know where to pull from. They need to have the changes isolated if possible and be based on new_features. (Which at the moment tracks master). A very valuable and detailed documentation is available in Harley: http://github.com/ptfs/Koha-PTFS/raw/harley/HarleyReleaseNotes.pdf It would be great if PTFS technical redactor who edited this precious document could cut-and-past its content per new functionality into Koha wiki. For the future, new functionalities developments could follow this path: 1. Specifications are published on Koha wiki in RFC section. 2. Developers design, code, test and validate with sponsoring library. 3. Then a developer level documentation is published on Koha wiki at the same time the code is proposed to the RM. 4. After integration of new code to main Koha, the Documentation Manager documents the new functionality based on the wiki documentation. This process would avoid having orphan functionalities without any documentation or with incomplete documentation. -- Frédéric DEMIANS http://www.tamil.fr/u/fdemians.html ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
