From: Greg KH <greg@kroah.com>
To: Preece Scott-PREECE <scott.preece@motorola.com>
Cc: "Miller, Marc" <marc.miller@amd.com>, linux-pm@lists.osdl.org
Subject: Re: OSDL Power Management call 8/24/2006 8 a.m. Pacific
Date: Wed, 23 Aug 2006 15:00:20 -0700 [thread overview]
Message-ID: <20060823220020.GA16302@kroah.com> (raw)
In-Reply-To: <ADE4D9DBCFC3A345AAA95C195F62B6DD01A4F732@de01exm64.ds.mot.com>
On Wed, Aug 23, 2006 at 05:46:25PM -0400, Preece Scott-PREECE wrote:
>
> Well, OSDL is one of several groups formed to try to encourage
> development in areas that its member companies prefer. OSDL has
> topic-specific working groups, which consist of people from member
> companies who are interested in specific technology areas. Those working
> groups meet so they can educate each other, coordinate activity,
> prioritize OSDL's activities on the specific topics, attempt to reach
> consensus on the direction the members would like to encourage, and so
> forth.
I for one, am very familiar with what OSDL does, on many levels, but
thanks for the summary :)
> I'm not sure why you think it's outside "the standard process" to issue
> an open invitation to community members to attend a WG meeting.
Because kernel development doesn't happen at WG meetings. It happens
when code is posted. To think otherwise is to not understand the kernel
development process.
> I don't think there's a lot of point to pretending that, just because
> kernel contributions come from individuals, those individuals are
> independent.
I never made such a statement.
> You think Intel and Motorola and other companies with a growing stake in
> the open source market don't have internal meetings to organize their
> activity, as well as participating in groups like OSDL, CELF, etc.?
Again, I never made such a statement.
I do however, doubt that a working group meeting is a useful thing for
any kernel developer to spend their time attending, unless it is at the
behalf of their employer. And I say this as someone who has attended
many such meetings at OSDL and other places.
Again, I will ask these simple questions:
- Why is the community being invited to such a meeting?
- Is there a proposed adgenda so that the community members can
determine if it is worth their time?
thanks,
greg k-h
next prev parent reply other threads:[~2006-08-23 22:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 1:13 OSDL Power Management call 8/24/2006 8 a.m. Pacific Miller, Marc
2006-08-22 2:09 ` Greg KH
2006-08-23 21:10 ` Greg KH
2006-08-23 21:22 ` Preece Scott-PREECE
2006-08-23 21:30 ` Greg KH
2006-08-23 21:46 ` Preece Scott-PREECE
2006-08-23 22:00 ` Greg KH [this message]
2006-08-23 22:35 ` Preece Scott-PREECE
2006-08-24 1:13 ` Greg KH
2006-08-24 14:45 ` Preece Scott-PREECE
2006-08-24 18:23 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2006-08-23 21:54 Miller, Marc
2006-08-24 3:50 ` Greg KH
2006-08-23 23:39 Miller, Marc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060823220020.GA16302@kroah.com \
--to=greg@kroah.com \
--cc=linux-pm@lists.osdl.org \
--cc=marc.miller@amd.com \
--cc=scott.preece@motorola.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox