[Compcomm] The Next Step

[Robert Carr]

No one will use GNOME without X and nowdays very few people will use
GNOME without the X.org reference implementation.

So should people discussing GNOME go to an X.org discussion forum?

On 4/17/07, Will Farrington <kalmwave at gmail.com> wrote:
> The entire thing will utilize the Compiz core and will need that core to
> be of any worth.
>
> No one will be Emerald unless they're using Compiz.
>
> etc, etc
>
> There are a plethora of reasons why naming the forums the Compiz Forums
> IS THE RIGHT IDEA. Listing them all would be a waste of time.
>
> On Tue, 2007-04-17 at 13:27 -0400, nesl247 wrote:
> > Hmm. Why do I get the feeling that people who were working on beryl
> > are getting the crap end of things here.. Everytime someone mentions
> > the teams, people are left out of it.
> >
> > I belonged to the Beryl Web and Release team. Being as I maintained
> > beryl for gentoo, and found a lot of the build issues because I was
> > one who doesn't have the same system as everyone else. Also, Saguratus
> > and I tended to manage the forums (administration tasks, he did more
> > moderating, I just stopped moderating because of time issues).
> >
> > And please, stop calling the merged community compiz. It's not compiz.
> > Compiz is the damn core, and nothing more. It's not "This week in
> > compiz" or compizforums.org or whatever.
> >
> > And iXce bought a domain something like opencompositing.org or
> > something. I think we should just name the project the Open
> > Compositing Window Manager. That's generic, fits the ideals, and we
> > already have the domain then. As far as a shared git repo, it can be
> > accessed at gitweb.opencompositing.org (whatever the domain is, as I
> > said, forgot what it was exactly).
> >
> > On 4/17/07, Jon Barnett <jonb at ieee.org> wrote:
> > > Hi,
> > >
> > > I'm not anyone of importance, just a user but I think it would be a
> > > "nice" thing for us users if the link to proposals and the plan forward
> > > (I assume this will be whiteboarded at Rock3D.org?) were linked to at
> > > our local hang-outs (beryl-project.org and compiz.org) until things get
> > > cut over. Just a suggestion as other than joining this group, we haven't
> > > had any feedback as to what is happening.
> > >
> > > It would also be nice to have some estimates on when things will happen
> > > - and maybe this might be a bit of a wish this early, when things are
> > > estimated to be completed. I'm not talking about hard deadlines, but
> > > just enough rough information to give users an idea of what will be
> > > happening and time-frames. And it doesn't necessarily have to be at the
> > > low-level implementation - just some medium level implementation goals
> > > for the sites and the working groups (I can see some of this is
> > > coalescing now). I think some users are scared (about losing features),
> > > some users are uncertain as to when development will get rolling again
> > > (or whether their bugs will get resolved), some will be wondering
> > > whether they should still be using the current forums or hanging off,
> > > and some, if they're like me, are just milling about bleating - :). A
> > > little re-assurance about moving forward would be wonderful.
> > >
> > > You can always revise goals and time-frames as things become better
> > > defined (so the whiteboard "action plan" is just the current, working
> > > plan at any point in time). Users just want to know what is happening
> > > with their product and community - and don't necessarily care about the
> > > technical level discussions :). The "This week in Compiz" idea would be
> > > good now. :)
> > >
> > > I hope my comments aren't out of line in any way.
> > >
> > > Cheers,
> > >
> > > JonB.
> > >
> > > _______________________________________________
> > > CompComm mailing list
> > > CompComm at Rock3d.org
> > > http://www.ubaight.com/mailman/listinfo/compcomm
> > >
> >
> >
>
> _______________________________________________
> CompComm mailing list
> CompComm at Rock3d.org
> http://www.ubaight.com/mailman/listinfo/compcomm
>