Re: PEAR Meeting - Summary online

Hi! Lukas Smith wrote:

You may be misinterpreting things here or putting too much into it though and finally we might not have been clear enough. A "veto" in this case could have also affected IT[X] development as in: "Alex go ahead commit this stuff" or rather "Pierre, its ok for him to commit". However this is not something we would like to have happen. At the meeting it was pretty much decided that redundant and even worse forks are not something we want in PEAR and that we need to build up structures and mechanisms to prevent this. The idea of "veto" in this context is to prevent things to get so out of hand that developers cannot effectively work together anymore.

I don't quite buy your "explanation". Looking up the word "veto" in Webster's dictionary (http://www.webster.com) yields the following: ---------- ... Etymology: Latin, I forbid, from vetare to forbid ... 1 : an authoritative prohibition : INTERDICTION 2 a : a power of one department or branch of a government to forbid or prohibit finally or provisionally the carrying out of projects attempted by another department; especially : a power vested in a chief executive to prevent permanently or temporarily the enactment of measures passed by a legislature b (1) : the exercise of such authority ---------- And the passage in question on PEAR website ---------- The Group can apply a veto on a package proposal. The veto should remain until the issues are solved. For example the latest discussion on pear-dev about IT[X] vs. Sigma could have resulted in a veto by the PEAR Group. ---------- There are no different meanings possible, unless you begin to redefine the words. The passage means "The Group can prohibit adding a new package and Sigma could be thus prohibited". No less, no more.

I will revisit the wording to make this more clear. But again this was an example who's purpose was not to illustrate a conflict where the PEAR group would act and on what scope. It was not meant was an example of what the exact decision would be. This is not something we discussed.

Please do so. BTW, did the community decide what to do with abandoned/unmaintained packages?