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

Bug#707851: Debian Menu Systems : Implementation of the TC decision



On Tue, 2015-09-29 at 15:13:28 +0200, Didier 'OdyX' Raboud wrote:
> Le mardi, 29 septembre 2015, 14.34:35 Guillem Jover a écrit :
> > W/o anyone to implement this in the menu programs, this is just
> > wishful thinking, and might leave big chunks of our users with
> > inaccessible applications. On either side of the fence.
> 
> Yes. That's exactly the point: the work to keep the 'trad menu' relevant 
> is to be made by those who care about it.

You seem to be framing this as a XDG vs menu formats. I see it in great
part as applications showing up on WM/DE or not. The collateral damage
from the TC decision are applications, WM/DE and its users from either
format.

> > > "The TC" is not going to engage in detailed design work (or
> > > implementation work, for what is worth), although any of its members
> > > could (but I don't see this happening).
> > 
> > Exactly my point. This is the equivalent of mandating that the Debian
> > Future Team should design and implement an FTL engine, where of course
> > the TC has not engaged in any design work. This to me fails §6.3.5.
> 
> I obviously disagree, but invite you to challenge this decision in 
> forums other than the debian-policy list.

I find that such kind of formal bureaucratic move would be a waste of
time, which if I wanted to waste, I'd rather do trying to get the TC
disbanded as a toxic and polarizing institution for the project. But
I don't think the project is prepared for this, just yet.

> Second, the TC has not mandated any work to any particular team: it 
> changed the ecosystem in which the 'trad menu' programs evolve. Mind 
> you, program ecosystems evolve all the time; 'trad menu's was relying on 
> the Debian Policy mandating entries for all applications "that need not 
> be passed any special command line arguments", the TC decision drops 
> that requirement.

Err, no, the TC has explicitly made it "impossible" for the two systems
to coexist, breaking existing support, and forcing maintainers to choose
one or other ecosystems, w/o any working solution in sight for WM/DE not
supporting the XDG system. Which has made the situation even worse than
before, in a very anti social way.

And I don't see how point 3 of the TC resolution can be read otherwise,
but whatever.

Anyway this discussion in itself is a waste of time, so I'm getting out…

Regards,
Guillem


Reply to: