[Compcomm] Compromise

Danny Baumann dannybaumann at web.de
Fri Jun 22 07:40:03 EDT 2007


Hi,

> > > The OCO forums will stay as they are and become a "compositing hub". 
> > > 
> > > Compiz forums will get upgraded to suit the needs of compiz fusion and
> > > the growth of the community and become the community place for compiz
> > > (as they were since the early days of compiz-quinn).
> > 
> > Agree, I just would like to see some important topics imported from the
> > OCo to the Compiz forums in that case. At least if that's possible.
> That's right. We have to make sure that no useful information gets lost. 
> It should be possible on a per-post basis. However - I agree that this 
> has to be ensured.

Ok, that's fine.

> > > > 2) Compiz.org will remind people of compiz. We are NOT compiz. We are
> > > > a merge of Compiz Extras and Beryl. We should have our own domain.
> > > Wrong. We are a community using and enhancing the compiz window manager.
> > > Our community enhacements are called "Fusion" because they were brought
> > > in by our friends from the former beryl-project. The core of everything
> > > our project is about is called COMPIZ. Our primary domain is compiz.org.
> > > Where excatly is the problem?
> (Sorry for my harsh tone ... I do my best but sometimes my "urban" style
> of speech still finds its way through :D ..)

We have seen worse examples of urban style than that one ;-)

> > - As Jeff already pointed out, dev at lists.compiz.org will be
> > non-Compiz-Core related discussion - that's kind of confusing.
> Yes, I see the confusion. How about fusion-dev at lists.compiz.org ?

That would be ok with me.

> > -Same for the bugtracker - using bugs.compiz.org as URL for it will
> > bring us a lot of Compiz Core & core plugin bug reports, where core has
> > its own bugtracker at FD.o and we (as Compiz Fusion) aren't responsible
> > for (most of ;-) ) them.
> Hmm - again I understand the problem. I gotta think about it a few
> minutes :) ... .... (some minutes later) .... How about talking to David
> and try to have one bugtracker for the entire project(s)? Maybe it can
> be categorized for core/fusion? 

Exactly. It would indeed be the best solution if we could convince David
to use a bugtracker common with our one (whereever it is hosted) to
solve this user confusion problem. Who is going to ask him? ;-)

> I am pretty sure that users would also
> report core-bugs to the fusion-bugtracker, no matter what it is called.
> It would be kinda difficult to ensure that you get "the right bugs" into
> "the right tracker" if there are two of them.

Looking at bugs.opencompositing.org tells me you're perfectly right in
this assumption.

Regards,

Danny




More information about the CompComm mailing list