specification process

Rodney Dawes dobey.pwns at
Thu Jul 9 14:07:39 PDT 2009

I generally disagree with the idea that in order to use the
org.freedesktop namespace for DBus interfaces, you must first gain
acceptance through having multiple desktops use your interface.

This means that it will be much harder to gain acceptance (as I'm sure
that lots of KDE developers are reluctant to use org.gnome services, and
vice-versa, without there being acceptance). It also means that once
that acceptance is gained, you either don't use the new namespace, or
you are immediately required to break API compatibility. And I think
encouraging the breaking of compatibility for this is probably one of
the last things we want to do. This would be very painful for
distributions and developers to deal with.

Shouldn't we rather be encouraging people to use that namespace, and
get their interfaces accepted as standards on FreeDesktop, rather than
telling them to break API when/if they do get accepted here?

On Thu, 2009-07-09 at 22:19 +0200, Cornelius Schumacher wrote:
> Following up on the discussion about at GCDS and the 
> additional input on the mailing list, I wrote down a specification for the 
> process how to manage specifications. It's based on the 
> consensus we built at GCDS plus the input which came from Aaron and others 
> before and after the meetings.
> To bootstrap the process I wrote it down as a specification 
> following the proposed process. You can find the text at 
> Please have a look and comment.
> The next step would be to work in your comments, and when this is done to 
> merge it back to the main repository and get approval by the release teams.

More information about the xdg mailing list