xc/programs considered harmful

[Paul Anderson]

The procedure that was developed long ago is probably too 
heavyweight a process for the current organization.  It's
something I have been wanting to revisit now that we have
a much larger organization.

The original proposal for deprecation was really targeted
more towards APIs rather than the physical location of code.
Nevertheless, the underlying premise of the deprecation process
involved ensuring that people would have a chance to review
how removing the API code affected them and potentially
other components that could depend on it.  In addition, putting
together a schedule and/or documentation for when things would
be removed from the tree was encouraged so that people would
have time to prepare and reference it in their own release
schedules, etc.

Best regards,

-paul

> Daniel -
> 
> There  is a procedure already in place for deprecating ANY code. It is part 
> of X.Org's commitment to stability of the code base.  The Architecture Group 
> is the place to start; under Paul Anderson's chairmanship they are empowered 
> to review and propose changes. You should write xorg_arch at x.org.
> 
> It is also inappropriate to propose cdhanges - much less changes of this 
> magnitude - just prior to the Christmas-New Year's holidays, which affect 
> many active members of the community.
> 
> I suggest you start by reviewing standing policies with Paul Anderson.
> 
> Leon
> 
> on Fri, 17 Dec 2004 17:45:51 +0100 Daniel Stone wrote:
> >
> >On Fri, 2004-12-17 at 11:40 -0500, Stuart Anderson wrote:
> >> On Fri, 17 Dec 2004, Daniel Stone wrote:
> >> > I understand that xeyes/xlogo/xedit/etc are all neat and whatever, but 
> I
> >> > don't see their place in the monolithic tree, and I think we can set a
> >> > great precedent by moving the maintainence of these tools to the 
> modular
> >> > tree, if they are still required, and then that can become the 
> canonical
> >> > upstream source.
> >> 
> >> I don't think your first message was explicite about adding them to the
> >> module tree, which means they are just moving, not being purged from the
> >> universe.
> >> 
> >> Which modular project would these be moving to?
> >
> >If people wanted to maintain them, fd.o has an 'xapps' repository.
> >_______________________________________________
> >xorg mailing list
> >xorg at lists.freedesktop.org
> >http://lists.freedesktop.org/mailman/listinfo/xorg
> 
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg
>