[Koha-devel] Integrating PTFS code into 3.4

Jane Wagner jwagner at ptfs.com
Wed May 12 15:01:49 CEST 2010


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
jwagner at ptfs.com


-----Original Message-----
From: koha-devel-bounces at lists.koha.org
[mailto:koha-devel-bounces at 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 at lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel



More information about the Koha-devel mailing list