Consequences of this narrow interpretation of responsibility are that one is only responsible for code voted on when one had voting rights and possibly that one cannot leave the community to pursue other interests.
This interpretation leads to stasis in and of the community and should therefore be shedded. -cjr -----Oorspronkelijk bericht----- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Pierre van Rooden Verzonden: Friday, November 11, 2005 3:02 PM Aan: Discussion list for developers Onderwerp: Re: [Developers] HACK: New cache implementation based on oscache Johannes Verelst wrote: >For now, we are voting on this hack to give the code the status of >'application', which means it has the same status as the other >applications. What that status MEANS is not under discussion now, we >could discuss that in another thread. > > Possibly, but if we decide that my interpretation of applications is the way to go, and it then turns out that not enough people want to maintain oscache code then what? Does it suddenly turn into a contribution? I would rather have people commit themselves now than have a discussion later on and having to reverse earlier decisions. Gomez _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
