[Koha-devel] FW: Code simplicity document

David Schuster dschust1 at gmail.com
Wed May 11 14:55:34 CEST 2011


I too enjoyed this article and took note of this and saw during the IRC
meeting a comment about after a release how the community drops off.

"In the past, before a major release, we would “freeze” the trunk. This
meant that no new features could be developed for several weeks or months
until we felt that trunk was stable enough to call a “release candidate.”
Then we would create a new stable branch from the trunk and re-open the
main-line trunk for features. However, while trunk was frozen, there was no
feature development happening *anywhere* in the Bugzilla Project.

Graph analysis showed *very clearly* that every time we would freeze, the
community would shrink drastically and it would take *several months* after
we un-froze for the size of the community to recover. It happened uniformly,
every single time we would freeze, over many years and many releases." -
Quote from "Open source simplified, read today 05/11/2011 - at URL -
http://www.codesimplicity.com/post/open-source-community-simplified/
David Schuster

On Wed, May 11, 2011 at 7:19 AM, Marcel de Rooy <M.de.Rooy at rijksmuseum.nl>wrote:

> Liked that article!
> As relative new member of the community, I am wondering if the current
> signoff/passed_qa procedure really encourages new members to keep sending
> patches.
> It could happen easily now that a patch does not get any attention. What
> makes someone now select a patch for signoff? Coincidence, contacts,
> application feature?
> imo we need some more structure at the signoff side. We have the Bugzilla
> categories that define the default assignment for a new bug. Would it be
> useful to assign a default signer per category too? Such assignments could
> be evaluated regularly to see if they still work.
>
> Marcel
> ________________________________________
> Van: koha-devel-bounces at lists.koha-community.org [
> koha-devel-bounces at lists.koha-community.org] namens Paul Poulain [
> paul.poulain at biblibre.com]
> Verzonden: maandag 9 mei 2011 15:46
> Aan: koha-devel at lists.koha-community.org
> Onderwerp: [Koha-devel] Document to read
>
> Hello,
>
> chris gave this url on IRC, I think it's worth sharing :
> http://www.codesimplicity.com/post/open-source-community-simplified/
>
> it's a great document. I think it's worth asking ourself : "what are we
> doing well, what could we improve"
>
> This question is specifically sent to new contributors: what did we
> well, what could be improve for new/future newbies ?
>
> --
> Paul POULAIN
> http://www.biblibre.com
> Expert en Logiciels Libres pour l'info-doc
> Tel : (33) 4 91 81 35 08
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at 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/
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at 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/
>



-- 
David Schuster
Plano ISD
Library Technology Coordinator
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110511/3cfb11ff/attachment.htm>


More information about the Koha-devel mailing list