[Compcomm] My ideas (for the record)

[Mike Dransfield]

Firstly, I really have lost interest in what you guys do, I suspect that 
a lot of
other people have too.  This is just a post to make my opinion clear so 
that people
know.

I have never been against creating a merged community, but I seem to have
been branded a non-cooperator because I came to these conclusions when
everyone thought we were creating 'new software'.

Promoting anything other than the compiz 'brand' will only lead to a SPLIT
community not a joined happy one.  There will always be people who will
support compiz so there will always be duplication and waste.  Its not 
just me
and RYX, I feel the entire compiz community has been left out of these
discussions.  The closest we have is this thread.

http://forum.compiz.org/viewtopic.php?t=745

Here were my ideas for what to do with this mess.  Unfortunatly, I have no
say in it whatsoever, so its down to the 'community' to do it.  For some 
reason
I stopped being part of the community and I became 'compiz' at some point.


- Drop the opencompositing.org forum, as many people have pointed out
it is just a duplication of compiz.org.  It should never have been 
rushed into
in the first place.

- Speak to David about pointing 'community' subdomains such as 
forum.compiz.org
planet.compiz.org etc to the current spare server.  Move 
forum.compiz.org over WITHOUT
DATA LOSS.  The domain ownership and www. subdomains should remain as 
they are
for obvious reasons.  Extend the menu on www.compiz.org to include these 
extra
parts.

- Create releases for the plugins (ie as tar.gz's), release to the 
fdo.org compiz
releases directory (anyone with git access to fdo can do this).  If you 
are worried
about plugins 'tarnishing' the reputation of compiz (which is probably a 
valid
concern), then label them properly, anything like compiz-plugins-* will 
do.  If you
try you could have 4-5 package names done and out within 24 hours, pick
names which describe what they are so things are clear.

- Anything which is not a plugin, package in another package.  If there 
are lots
of small apps which only work with compiz, then call it compiz-apps (or 
something
like that)

- Drop libbs/libccs/libcompizconfig and work on making a settings tool 
which
does not rely on one plugin.  Work with David to get your legitimate 
requirements
added to the existing framework.  Creating a settings manager which only 
works
for < 30% of the compiz users is not very good.  You might as well just 
access gconf
directly since thats what > 70% of the users will be using anyway.  You 
cannot
complain how awful gconf is, but then use gnome, it does not make sense.

- Promote compiz and these extra plugins.  You guys are very good at 
that, its
a shame that everyones hard work is treated with such disrespect and is 
thrown
away all the time.