From the koha-commits mailing list:
This mailing list is an informational list to which commit descriptions for patches pushed to the public Koha Git repository (currently git://git.koha-community.org/koha.git) are posted. This list should not be used to discuss individual patches, as not all contributors will be subscribed to koha-commits. Instead, please use koha-devel, koha-patches, or bugs.koha.org for that purpose. Is this no longer the case? -----Oorspronkelijk bericht----- Van: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] Namens MJ Ray Verzonden: maandag 15 november 2010 11:10 Aan: Galen Charlton CC: koha-devel@lists.koha-community.org; koha-patches@lists.koha-community.org Onderwerp: [Koha-devel] Discussion of development topics, was: Bug 5401: WYSWYG for Koha News Galen Charlton wrote:
There is a long standing practice of discussion of individual patches
on koha-commits, however, so while koha-devel is certainly a valid
choice for discussing this issue, I do want to point out and remind
people that some relevant discussion does take place on the
koha-commits list.
I don't like that practice because:- 1. the list description "Patches submitted to Koha" gives no indication it occurs and it's different from other projects' -commit mailing lists; 2. developers have to subscribe to receive all patches even if they're only interested in their fields of activity and the occasional discussions, contributing to information overload; 3. I think the patches are carried in only one of the web forum versions of our discussions http://koha-community.org/support/forums/ 4. usually the patches relate to a bug and email discussion isn't automatically attached to the bug report - I have started work to address this, but it's still going to have some delay between the discussion and posting to the bug report, which may mean the discussion is irrelevant by the time the bug is told; 5. most importantly, many topics are wider than a single patch, such as this one about what rich editor to adopt. Can we overcome these problems, or state clearly that wider-than-one-patch discussions should be on -devel? Thanks, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Past Koha Release Manager (2.0), LMS programmer, statistician, webmaster. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/