On Apr 19, 2006, at 7:18 AM, Stephen Hahn wrote:
Given the circular nature of this particular proposal, I will at
this
point suggest that we either
- repurpose opensolaris-code
Yeah, go for this one, the name is pretty good.
Kaiser Jasse -- Authorized Stealth Oracle
The
If this is still open for discussion, I also agree for repurposing opensolaris-code.-MoazamOn Apr 19, 2006, at 7:18 AM, Stephen Hahn wrote: Given the circular nature of this particular proposal, I will at this point suggest that we either - repurpose opensolaris-code
On Tue 18 Apr 2006 at 04:12PM, Eric Lowe wrote:
Dan Price wrote:
On Tue 18 Apr 2006 at 08:32AM, Eric Lowe wrote:
As for the technical discussion list, as I've said before, I don't care
about the means as long as we accomplish the ends. For all I care we can
call it [EMAIL PROTECTED], and as
Dan Price wrote:
You said: as long as everybody knows to go there for technical
questions, spec posts, and RFC submissions. That sounds like you're
spreading your project's wings out over the charter of other
communities and projects.
That certainly wasn't the intent. I haven't seen
I guess the reference to "[EMAIL PROTECTED]" in the announcement left some people confused and thinking that this was the new list previously being discussed in this thread. Wow...even that sounds confusing.-MoazamOn Apr 19, 2006, at 7:58 PM, Eric Lowe wrote:As you'll see we have removed the
Moazam Raja wrote:
I guess the reference to [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] in the announcement left some
people confused and thinking that this was the new list previously being
discussed in this thread. Wow...even that sounds confusing.
I suppose the confusion isn't surprising,
Shawn Walker wrote:
I thought the same thing. The first thing I did when I saw the name muskoka being thrown around
was to search for it on wikipedia. While it's cute and all, I relaly think that mailing lists
should have a blindingly obvious title :) The suggested name of, Solaris Kernel
There is no hidden meaning. I picked muskoka for the project because there
is an internal machine within Sun which serves a similar purpose for
engineering, it has slideware, home pages, etc. - various random things -
hosted there. The name is purposely obscure. It's just meant to be a
[EMAIL PROTECTED] wrote:
I believe it adds a barrier to entry for those willin gto participate
and not knowing where to look. It seems as if a lot of high technical,
interesting, content may be hidden under the muskoka cloak.
A name is just a name; we could change it to something less hidden
A name is just a name; we could change it to something less hidden like
techlib. There are so many projects with codenames already, are we just
fighting the tide?
I have raised the objections elsewhere also.
Perhaps we should have a meta discussion on project and community names.
Casper
[EMAIL PROTECTED] wrote:
There is no hidden meaning. I picked muskoka for the project because there
is an internal machine within Sun which serves a similar purpose for
engineering, it has slideware, home pages, etc. - various random things -
hosted there. The name is purposely obscure. It's
On Tue 18 Apr 2006 at 08:32AM, Eric Lowe wrote:
As for the technical discussion list, as I've said before, I don't care
about the means as long as we accomplish the ends. For all I care we can
call it [EMAIL PROTECTED], and as long as everybody knows to go there
for technical questions,
Now I'm really confused. This last statement sounds like you're
inventing new process. Are project teams now expected to cross-post
things like PSARC cases and design documents to muskoka-discuss?
This doesn't sound very good to me, from an outside-of-sun perspective. I'm in
agreement with
On 4/18/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
A name is just a name; we could change it to something less hidden like
techlib. There are so many projects with codenames already, are we just
fighting the tide?
I have raised the objections elsewhere also.
Perhaps we should have a
On Mon 17 Apr 2006 at 05:28PM, Daniel B. Price wrote:
Can I ask a dumb question: why are we calling this
the muskoka
project?
Naming a mailing list filled with technical kernel
content after an obscure
lake in Canada seems maximally confusing to me, and
would seem to make
it harder for
15 matches
Mail list logo
