-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Ogley wrote:
>> Meanwhile it would be great to get some more opinions / comments on this 
>> topic! Everyone, don't hesitate to speak out now... ;)
> 
> Well, I'd certainly be in favour of a couple of key community members
> being part of the Core Team.  I think given that the 'brand', all

+1
I don't see active community members being that much involved up to now, 
especially on the field of
packaging (topics James and I, amongst a few others, are involved in).

> marketing issues, trademarks relating to logos, and ultimately
> entrepreneurial risk belongs to Novell::SUSE that it makes sense for the
> majority of seats on the CT be held by staffers.

Yes, obviously.

I'm not having a problem with project and product management being made 100% by 
Novell/SUSE. They
put many, many resources in it, they provide us with that fantastic, 
high-quality core distribution.
That's perfectly fine with me. People complaining about not having their word 
to say in the
product/project management have no clue about what it means, how much work is 
involed in it, how
complex it is, and how much money Novell puts into that.
To me, I prefer having less to say about the core distribution and have it done 
well,
professionally, by qualified people who are paid fulltime to work on it than 
having some mess like
Fedora.

I can only speak on the topic of packaging and package management, as that's 
where I'm involved in.
We talked already about the build servers, I addressed a number of ideas, 
directions and issues
currently faced by community packagers, and I'd like to see them addressed in a 
way or another.
Also, most of the mails and threads we had about that 2-3 months ago haven't 
been adressed nor
picked up, drown into the mass of people asking for help about hardware issues 
and similar.
That's not only lost time and efforts spending many hours writing mails and 
discussing about it,
it's also demotivating. Personally, I don't really feel like trying to discuss 
it again and again,
with not all that much coming from SUSE.

I also know that Novell took the decision of "opening up" (aka openSUSE) too 
soon, rolling over the
schedule the SUSE staff had in mind and hence, a lot of things still need some 
time to be done,
discussed, decided. That's perfectly fine as well, but I'd like to have some 
more feedback.
Not that you owe me anything lol, but it's just that building a community means 
involving it and
keeping it informed about what's happening. If you stay for weeks and months 
without showing that
something is happening (and how the progress is, even if it's not being worked 
on at the moment),
people (in the community) lose their motivation about it.

IMO, a proof is that on the opensuse-packager list, threads and ideas are only 
started by community
members, not by SUSE staff.

Christoph, I know you're very much involved into communication with the 
community, but I think there
must be some more happening, also from other people @ SUSE.

> I'd also like to see more of the CT blogging, but then, I'd like to see
> more of the developers blogging, period.

Yes, +100
Definately.

Also, this mailing-list has become almost unusable and unproductive, 
overwhelmed with trolling
(lately) and with people reporting issues that definately belong to 
suse-linux-e and not here.
During the last few weeks there have been many more threads and mails about 
hardware/driver support
issues than constructive discussions about the openSUSE community, how to 
interact and work together
(Novell and the community), etc..., what is what I was actually expecting from 
this list.
I've been really close to unsubcribe several times but then again, sometimes, 
there's a small thread
like this one popping up.

Proposal:
- - either create a new list "opensuse-community"
- - or clean this list from issues that belong to suse-linux-e

Furthermore, having users, questions and solutions to issues spread over 2 
lists is very
counter-productive: less people to help, less people to see the solutions.
I know suse-linux-e is very high traffic, but nevertheless. Personally, it 
turns me off to see this
list spoiled with "my usb stick is slow", "my modem doesn't work", etc... - 
while such mails are
perfectly fine and deserve attention and help, they don't belong on this list. 
At least that's my
very humble and personal opinion about it. Maybe I'm wrong. If I am, please 
create a new list that's
dedicated to discussing things like the openSUSE community itself.

Progress, guys, and communication. While a number of topics have been 
advertised as being currently
addressed by the core staff (*), we don't see much happening for several weeks.
(*) http://www.opensuse.org/Core_Team_Issues

Let's just pick this one: "(Official) Web forums".
Status: "On hold, waiting for new Novell support forums to be ready for beta 
test."
That's the status since.. what... one, two months ?

Maybe I sound harsh, but it's definately not my intention to bash or criticize 
(at least not without
trying to get some productive reaction out of it).
I'm deeply committed to openSUSE, been very actively involved into making SUSE 
better for everyone,
spending a huge amount of my free time to do so, and that's why I'd like to see 
it moving forward ;)

But maybe we're all just too impatient, too hungry for being involved in it, 
because some of us have
been waiting for years for this to happen. I certainly am. I should probably 
just wrap myself into
more patience.

Anyway, kudos to all the SUSE staffers, keep up the good work and.. maybe... 
communicate some more
about it ;-)

cheers
- --
  -o) Pascal Bleser     http://linux01.gwdg.de/~pbleser/
  /\\ <[EMAIL PROTECTED]>       <[EMAIL PROTECTED]>
 _\_v The more things change, the more they stay insane.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFDdgHrr3NMWliFcXcRAiNnAKCkUu9vBoHmzO+GBPiB7w80Flk6uACeNk/s
GfFGfgLPKjVitHRLHr+UDV8=
=FBk4
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to