[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Re: Re: [CTTE #614907] Resolution of node/nodejs conflict

Hi Lars,

Lars Wirzenius wrote:

On Sat, Jul 21, 2012 at 04:38:21PM -0400, Filipus Klutiero wrote:
>  Hi Stefano,
>  Stefano Zacchiroli wrote:
>  >On Tue, Jul 17, 2012 at 08:07:15PM -0400, Filipus Klutiero wrote:
>  >>   Thank you, but I would appreciate if debian-devel-announce would
>  >>   stay dedicated to important announcements which may be useful for a
>  >>   wide range of developers.
>  >
>  >tech-ctte resolutions do fit that bill. The tech-ctte is the highest
>  >dispute resolution body we have in Debian, and I think their doings
>  >deserve this level of awareness in the project.
>  although publicity of some resolutions may indeed be useful for a
>  wide range of developers, I fail to see many who would be interested
>  in the resolution on node.

You're complaining about the posting volume of a list that has 13 +
17 + 16 + 7 + 8 + 10 + 4 = 75 messages this year, or about 2.6 days
between posts.

No, I simply explained it would have been better to send the message in question elsewhere, avoiding debian-devel-announce. It may be that there are few messages in this situation, and that more messages were in the opposite situation and should have been sent to debian-devel-announce.

In my opinion, _every_ technical committee decision should be posted
to debian-devel-announce. Any time that the TC needs to make a decision,
it's already an unusual circumstance, and usually something's gone wrong.

Conflicts are intrinsic in projects divided into thousands of inter-dependent sub-projects with private decision-making processes... I would be more worried to see no conflicts in our system.

Reply to: