[Compcomm] Let's Get Things Started

[nesl247]

Mike, there's a good reason that Beryl packages binaries for distros.
Doing so eliminates possible issues that the distros will have,
because the beryl developers themselves create the binaries.

As for "Team Web", there is no such thing. Beryl has it's people, and
Compiz has it's people. When we merge the two projects, post code,
then we can discuss who's going to have what position.

At first I really wanted the merge, because I was tired of the way
things were being duplicated (to some aspects, there was a lot of
originality with beryl, at least in terms of applications such as the
beryl settings manager, and beryl manager). But now, this merge has
become a complete mess. It has been executed improperly, and really,
both projects should just pull back to the way they were, or someone
who knows how to properly manage a project needs to step up and take
control. And I wouldn't feel comfortable with anyone on the compiz
side who is extremely emotional being this person, or anyone from the
beryl side who has complete hatrid of compiz.

On 4/16/07, Mike Dransfield <mike at blueroot.co.uk> wrote:
> Nicholas Thomas wrote:
> > Bagsies here on Team DIST; who else wants to join? ;) I'm assuming gandalfn,
> > at the very least
> >
>
> First off, its great that there are so many people willing to lend a hand.
>
> Its also a good idea to give people roles and boundaries.
>
> I would like to clear up some beryl misconceptions though.
>
> WE are not responsible for packaging (ie deb/rpm generation) We are
> only responsible for releasing the source (and maybe generic binaries).
> The distros are responsible for finding people to turn those source
> tarballs into the correct format.
>
> This way there are clear lines between responsibilities and the workload
> is kept down for everyone.  Bugs are also much easier to track down.
>
> > Team WEB is obviously imnotpc + iXce + ???
> >
>
> No problem with that, amgeex and RYX are responsible for the
> forum and wiki new look (mainly ;)), so at the moment they are
> really team WEB.
>
> > Team DEV... pretty much everyone, I guess. It can be given a structure later.
>
> Errrm... It takes a lot of time and dedication to develop software.
>
> Lumping everyone else as a developer is really not a good idea
> because people commit patches which they do not understand
> the consequences of.  Thats why David is totally in charge of his
> code and all changes must be agreed by him.  Peoples plugins
> are the same.
>
> To be honest, its fairly insulting to be told that skills you have
> taken years and years to develop are not right and anyone with
> a book can do the same thing with a bit of time.  These things are
> like anything else in life, you need practice and experience.
>
> It is only IT where we see this sort of attitude that so long
> as you can write code you are a programmer.  I'd much rather
> have limited access to stable code than unlimited access to a
> code pile.  Beryl was always a code pile and we do not want
> that even if it means short term gains and great looking
> youtube videos.
>
> _______________________________________________
> CompComm mailing list
> CompComm at Rock3d.org
> http://www.ubaight.com/mailman/listinfo/compcomm
>


-- 
Alex Heck - nesl247