On Aug 15, 2006, at 5:23 PM, Noel J. Bergman wrote:
Yoav Shapira wrote:
Noel J. Bergman wrote:
I would put forth a strawman that the "Editor" role is at least
somewhat analogous to the "Release Manager" for code.
there's a big difference: a release manager does not modify other
people's w
Yoav Shapira wrote:
> Noel J. Bergman wrote:
> > I would put forth a strawman that the "Editor" role is at least
> > somewhat analogous to the "Release Manager" for code.
> there's a big difference: a release manager does not modify other
> people's work (e.g. the code), only packages it.
The Re
Hi,
On 8/15/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
dictates. I would put forth a strawman that the "Editor" role is at least
somewhat analogous to the "Release Manager" for code. Either way, the
deliverable still needs to be approved by the PMC.
Yes, either way the deliverable still
Craig Russell wrote:
> Granqvist, Hans wrote:
>> Just a few thoughts on the process: How do you envision editorship
>> of the spec? Would all committers be editors?
> In successful spec writing projects that I've been involved in, there
> has been an editor for the entire specification or an edit
Alan Conway wrote:
> Idiotic question from complete Apache newbie: is the proposal that
> Apache should start hosting specs but would still host projects
> implementing foreign specs, or that Apache should stop hosting projects
> implementing non-Apache specs?
Twofold answer IMHO...
if we host a
On Aug 15, 2006, at 6:57 AM, Alan Conway wrote:
Idiotic question from complete Apache newbie: is the proposal that
Apache should start hosting specs but would still host projects
implementing foreign specs, or that Apache should stop hosting
projects
implementing non-Apache specs?
I haven'
Idiotic question from complete Apache newbie: is the proposal that
Apache should start hosting specs but would still host projects
implementing foreign specs, or that Apache should stop hosting projects
implementing non-Apache specs?
On Mon, 2006-08-14 at 08:34 +0100, James Strachan wrote:
> On 8/
On Aug 14, 2006, at 9:56 AM, Granqvist, Hans wrote:
...
I would be in favor of such an approach. Honestly, I would
vastly prefer to have Open Specifications managed under ASF
processes than under the JCP, OASIS, etc.
Yea, I think it could be a good idea.
I agree.
Just a few thoughts on t
> ...
> I would be in favor of such an approach. Honestly, I would
> vastly prefer to have Open Specifications managed under ASF
> processes than under the JCP, OASIS, etc.
Yea, I think it could be a good idea.
Just a few thoughts on the process: How do you envision editorship
of the spec?
On 8/13/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Carl Trieloff wrote:
> -> Is Apache in the business of writing and publishing specifications? <-
> As long as Apache is not in the business of also creating
> specifications, there will be by definition some separation
> between code and sp
What broken mail client are you using?
inline...
Noel J. Bergman wrote:
> Carl Trieloff wrote:
>
>> -> Is Apache in the business of writing and publishing specifications? <-
>
>> As long as Apache is not in the business of also creating
>> specifications, there will be by definition some separ
On Aug 13, 2006, at 10:49 AM, Noel J. Bergman wrote:
Carl Trieloff wrote:
-> Is Apache in the business of writing and publishing
specifications? <-
As long as Apache is not in the business of also creating
specifications, there will be by definition some separation
between code and spec p
Carl Trieloff wrote:
> -> Is Apache in the business of writing and publishing specifications? <-
> As long as Apache is not in the business of also creating
> specifications, there will be by definition some separation
> between code and spec processes, and I would like to work
> with the ASF to
13 matches
Mail list logo