On Tuesday 20 April 2004 19:38, Kip Hampton wrote:
> Matt Sergeant wrote:
> >> Chris reports progress to the AxKit PMC at the (newly instituted)
> >> bi-weekly dev meetings.
> >>
> >> When the items on Chris' RP are knocked down and released, the process
> >> starts over.
> >
> > This seems like th
Matt Sergeant wrote:
Chris reports progress to the AxKit PMC at the (newly instituted)
bi-weekly dev meetings.
When the items on Chris' RP are knocked down and released, the process
starts over.
This seems like the Pumpking is also going to be the main developer on
the release.
Not necessaril
On 20 Apr 2004, at 16:04, Kip Hampton wrote:
Chris Commiter really want to see FeatureX happen, so s/he picks it,
and a few other items from the STATUS and makes a Release Plan.
Chris' RP is selected or rejected by a vote. If selected, Chris
becomes Pumpking for the next set of subversion releas
On April 20, 2004 08:04 am, Kip Hampton wrote:
> 1) What happens if the current Pumpking can't or won't fulfil their duties?
I think this is an instance where it's discussed & voted upon in -devel.
Maybe have it so if the Pumpking drops off the face of the earth, gets hit by
a bus, a meteorite,
Matt Sergeant wrote:
On 6 Apr 2004, at 17:13, Kip Hampton wrote:
[1] http://totalcinema.com/axkit/axkitguidelines.xml
I think this document hits the mark, and I'm +1 on moving forward with
becoming a TLP and adopting this new development approach. I've gone
over this document twice now and have
On 6 Apr 2004, at 17:13, Kip Hampton wrote:
I suggest that we take the opportunity that (potentially) becoming a
top-level project provides to take stock, put aside old baggage, and
move AxKit forward with renewed vigor. To that end, I've put together
a first draft proposal for the guidelines an
Thanks Mike,
I'll take a look this afternoon. The most important thing for me is
Apache2 since all our mp-stuff is running now on mp2.
Maybe I could spend sometime to get it run on Apache2 or at least
identify what has to changed todo so.
Tom
Mike Chamberlain wrote:
On 19 Apr 2004, at 09:29, Mike C
On 19 Apr 2004, at 09:29, Mike Chamberlain wrote:
Yeap,
First off.
* THIS IS NOT AN OFFICIAL RELEASE. **
Do not expect this to work the way the current or future axkit's will
work.
Do not take this code as in indication of what any final product will
look like.
etc etc.
**
Yeap,
First off.
* THIS IS NOT AN OFFICIAL RELEASE. **
Do not expect this to work the way the current or future axkit's will
work.
Do not take this code as in indication of what any final product will
look like.
etc etc.
*
Having said that, any
Hi Mike,
is it somehwo possible to take a look at what you've done on
pipeline/apache2 stuff?
Thx
Tom
Mike Chamberlain wrote:
[1] http://totalcinema.com/axkit/axkitguidelines.xml
+1 from me.
I like the idea of having a Pumpkin, I think the problem we've been
having recently is
no one has been
Mike Chamberlain wrote:
I like the idea of having a Pumpkin, I think the problem we've been
having recently is no one has been wanting to take charge, and at
other times too many people want to run the show / have conflicting
ideas and there isn't anyone who is willing to act as a chairman to
get
[1] http://totalcinema.com/axkit/axkitguidelines.xml
+1 from me.
I like the idea of having a Pumpkin, I think the problem we've been
having recently is
no one has been wanting to take charge, and at other times too many
people want to
run the show / have conflicting ideas and there isn't anyone
On Tue, Apr 06, 2004 at 09:13:36AM -0700, Kip Hampton wrote:
+1 (lurker)
AxKit is important to me too. I also enjoy working with it and am
happy to help and contribute to the "rebirth".
Thanks, and I'm looking forward to the book.
Wendell
I'm also a non-commiter but +1 from me too.
Michael A Nachbaur wrote:
Yeah, agreed on all points. +1 to the draft from this non-commiter as
well.
Yeah, agreed on all points. +1 to the draft from this non-commiter as well.
Kip Hampton wrote:
Specifically, I'm concerned about apparent lack of recent interest in
AxKit among what have historically been its core developers and the
general "so what" attitude that is being presented to its users.
I for one have noticed this, and have been very concerned about it. I'm
and
for placing this wake up call! I do not think the timing for this
couldn't be worse. It would have been far worse if this current state of
uncertainty about AxKit's future, which I know I am not the only one
percieving it, would have continued being undealt with. So, now, before
the bo
Howdy Folks,
This message is a long time coming and, since no one seems to want to
step up to address the issue I guess I'll be the one to drag in into the
light...
Specifically, I'm concerned about apparent lack of recent interest in
AxKit among what have historically been its core developers
18 matches
Mail list logo
