The plan:

1a) Harmonize Fedora and Suse's packaging guidelines
1b) Add virtual provides to Fedora / Suse -devel packages so that they
    provide their other distro counterpart -devel package
1c) Harmonize rpm macros like the ones used for make -j# invocation, update
    icon cache scriptlets etc.

The end result of step 1 should be that one can take an application srpm
from Suse and build it on Fedora and the otherway around.

2) Get a website setup where interested Fedora and Suse contributers can
enrol and co-maintain specfiles + patches for highlevel applications like for
example games. This website should offer a way of enrolling, claiming /
suggesting packages and a VCS where the specfiles and patches are hosted.
For now its up to the maintainers to manually sync any changes between this
sites VCS and the Fedora / Suse VCS.


The end result, shared packages for Fedora and (open)Suse and hopefully in
the Future also other rpm based distro's like pld and mandriva, and through
this sharing the removal of a lot of duplicate effort.

Through this whole process there will ofcourse be a lot of diplomatic
hurdles to overcome, besides the technical ones, but if we manage to pull this
of this could be a big win.


Some last notes:

1) I'm currently already sharing quite a bit of work with the people from
packman, but it would be great if we could build from the exact same
sources, so that we can just copy changes from eachother instead of
maintaining Fedora and Suse forks of the packages indefinitely.

2) This is intended for things higher up in the application stack, like
applications and some not widely used libraries. Things like the kernel /
init systen, glibc etc, will always stay distro specific, or atleast for a
long time to go.