On 9/10/2010 11:25 PM, Justin Erenkrantz wrote:
> On Thu, Sep 9, 2010 at 12:20 PM, Greg Stein wrote:
>> For reference:
>>
>> * Subversion created its dev list in April 2000.
>> * The user list was created in July 2003. 238 messages were posted that
>> month.
>>
>> As you can see, we waited a very
On 13/09/2010 14:35, Noel J. Bergman wrote:
>> So far I see 2 clear (binding) +1s for the proposal...
>> Calling out for more ;)
>
> Echoing Bertrand's comment, people may have been waiting for a [VOTE]
> thread.
A VOTE is a good idea. :)
p
0x62590808.asc
Description: application/pgp-keys
+1 from me (binding)
On Mon, Sep 13, 2010 at 9:11 AM, Jim Jagielski wrote:
> So far I see 2 clear (binding) +1s for the proposal...
>
> Calling out for more ;)
>
> On Sep 7, 2010, at 8:29 PM, Matthew Sacks wrote:
>
>> Hello, Peary Chiu and myself would like to announce the Proposal for the
>> Ki
> So far I see 2 clear (binding) +1s for the proposal...
> Calling out for more ;)
Echoing Bertrand's comment, people may have been waiting for a [VOTE]
thread.
--- Noel
-
To unsubscribe, e-mail: general-unsubscr...@in
On Mon, Sep 13, 2010 at 3:11 PM, Jim Jagielski wrote:
> So far I see 2 clear (binding) +1s for the proposal...
It's a proposal, not a vote, right?
I think it's fine to move forward with the vote if there are no
pending issues (haven't checked).
-Bertrand
> Calling out for more ;)
>
> On Sep 7
+1
sound neat - and I'm really eager to check the groovy port ;)
LieGrue,
strub
--- On Mon, 9/13/10, Jim Jagielski wrote:
> From: Jim Jagielski
> Subject: Looking for a few more votes... Re: [PROPOSAL] Kitty to Enter the
> Incubator
> To: general@incubator.apache.org
So far I see 2 clear (binding) +1s for the proposal...
Calling out for more ;)
On Sep 7, 2010, at 8:29 PM, Matthew Sacks wrote:
> Hello, Peary Chiu and myself would like to announce the Proposal for the
> Kitty, Production Tomcat utility. Our proposal is as follows (we have also
> attached a P
On Thu, Sep 9, 2010 at 12:20 PM, Greg Stein wrote:
> For reference:
>
> * Subversion created its dev list in April 2000.
> * The user list was created in July 2003. 238 messages were posted that month.
>
> As you can see, we waited a very long time before sending users to
> their own list. Our dev
9/10, James Carman wrote:
>
> > From: James Carman
> > Subject: Re: No dev-, user- lists for small podlings (was: Re: [PROPOSAL]
>Kitty to Enter the Incubator)
> > To: general@incubator.apache.org
> > Date: Thursday, September 9, 2010, 7:33 PM
> > On Thu, S
, user- lists for small podlings (was: Re: [PROPOSAL]
> Kitty to Enter the Incubator)
> To: general@incubator.apache.org
> Date: Thursday, September 9, 2010, 7:33 PM
> On Thu, Sep 9, 2010 at 3:24 PM, Greg
> Stein
> wrote:
> > The formation of your community is a BIG DEAL. N
On 9/9/10 9:33 PM, James Carman wrote:
On Thu, Sep 9, 2010 at 3:24 PM, Greg Stein wrote:
The formation of your community is a BIG DEAL. Not something to
casually sweep under the rug.
Partitioning the community between users and devs makes it very
difficult to establish a large, viable, sustai
James Carman wrote on Thu, Sep 09, 2010 at 15:33:53 -0400:
> If users are interested in the development goings-on,
> then they can subscribe to the dev list.
A standard argument against this:
Having it in the same list makes it easier to pull users in to become
developers.
> Some folks, like us
>
The dicussion of how proposals should be addressed might be a better
issue for the Wiki page on proposals.
It is off topic of this original proposal, and I vote that it be moved
to a separate thread.
We have agreed and noted to use a single mailing list for the purposes
of this proposal.
On Thu
On Thu, Sep 9, 2010 at 7:24 PM, Greg Stein wrote:
> ...It is obviously a call for each podling to make, so I'm simply
> recommending that all podlings consider the impact of dividing your
> community when you ask for separate dev/user lists. I believe it is
> rarely appropriate
I think this s
On Thu, Sep 9, 2010 at 3:24 PM, Greg Stein wrote:
> The formation of your community is a BIG DEAL. Not something to
> casually sweep under the rug.
>
> Partitioning the community between users and devs makes it very
> difficult to establish a large, viable, sustainable community.
>
> If projects a
The formation of your community is a BIG DEAL. Not something to
casually sweep under the rug.
Partitioning the community between users and devs makes it very
difficult to establish a large, viable, sustainable community.
If projects arrive at the Incubator with an already-built user
community, th
On Wed, Sep 8, 2010 at 08:11, sebb wrote:
> On 8 September 2010 12:39, dan haywood wrote:
>
>
>
>> And another benefit of putting user traffic on the dev list is that
>> it'll give the devs exposure to any probs that regular users are having with
>> actually using the framework (ie so we can mat
+1 on the mailing lists issue.
On Thu, Sep 9, 2010 at 8:29 AM, Pid wrote:
> On 09/09/2010 07:15, Greg Stein wrote:
>> Just to clarify: I'm assuming you're saying "+1 to the proposal",
>> rather than to my comment. Correct?
>
> +1 indeed, to the proposal
>
> +1 actually, to the mailing list commen
I'm with James on this one. Many good points have been made on this,
but we do have bigger things to worry about.
On Wed, 2010-09-08 at 08:06 -0400, James Carman wrote:
> On Wed, Sep 8, 2010 at 7:39 AM, dan haywood
> wrote:
> >
> > For the moment at least the dev community is more active (or at
On 09/09/2010 07:15, Greg Stein wrote:
> Just to clarify: I'm assuming you're saying "+1 to the proposal",
> rather than to my comment. Correct?
+1 indeed, to the proposal
+1 actually, to the mailing list comment, too.
The Incubator PMC might consider that establishing sufficient interest
which
Just to clarify: I'm assuming you're saying "+1 to the proposal",
rather than to my comment. Correct?
And to clarify for myself: I have no opinion on the proposal itself. I
timed out after "Java" and the next few buzzwords. Thankfully, this
proposal didn't say "framework" or I may have timed out a
+1 (non-binding)
Small point: if a Mentor must be a Member, I can't be one, because I'm not.
p
On 08/09/2010 16:00, Mohammad Nour El-Din wrote:
> +1 (Notbinding)
>
> On Wed, Sep 8, 2010 at 7:22 AM, Greg Stein wrote:
>> On Tue, Sep 7, 2010 at 20:29, Matthew Sacks wrote:
>>> ...
>>
>>> *Mailing
On Sep 8, 2010, at 1:22 AM, Greg Stein wrote:
> On Tue, Sep 7, 2010 at 20:29, Matthew Sacks wrote:
>> ...
>
>> *Mailing Lists*
>>
>> kitty-dev
>> kitty-commits
>> kitty-user
>>
>
> Is there a large user community already? If not, then splitting the
> community across dev/user does not make se
+1 (Notbinding)
On Wed, Sep 8, 2010 at 7:22 AM, Greg Stein wrote:
> On Tue, Sep 7, 2010 at 20:29, Matthew Sacks wrote:
>>...
>
>> *Mailing Lists*
>>
>> kitty-dev
>> kitty-commits
>> kitty-user
>>
>
> Is there a large user community already? If not, then splitting the
> community across dev/user d
On 8 September 2010 12:39, dan haywood wrote:
> And another benefit of putting user traffic on the dev list is that
> it'll give the devs exposure to any probs that regular users are having with
> actually using the framework (ie so we can mature its documentation etc)
In ASF projects I would
On Wed, Sep 8, 2010 at 7:39 AM, dan haywood
wrote:
>
> For the moment at least the dev community is more active (or at least more
> vocal), so their mailing list should be the main focal point. As I said in
> the other email, when we have more user traffic than dev traffic, then
> we can vote to
On 8 September 2010 12:19, Robert Matthews wrote:
> One point against this is that we have had a long-standing user list, ...
>
> ... People are used to
> the user list already.
We do, but it's going to change anyway when we make the apache mailing list
available.
> If we are going to comb
On 8 September 2010 12:16, James Carman wrote:
> Isn't Isis a different bird though? It has been around for a long time and
> is likely to actually have existing users
>
It has some, but not enough to be sustainable. Hence entry into
the incubator to build both its user and developer communiti
One point against this is that we have had a long-standing user list,
and it is the developer list that is new and growing. People are use to
the user list already. If we are going to combine the two then I
suggest we have a -user list now and let the developers grow out of
that.
Rob
On Wed, 20
Isn't Isis a different bird though? It has been around for a long time and
is likely to actually have existing users
On Sep 8, 2010 7:04 AM, "Benson Margulies" wrote:
> Well, we could neglect to tell anyone about the user list until we need
it.
>
> On Wed, Sep 8, 2010 at 3:16 AM, Dan Haywood wr
Well, we could neglect to tell anyone about the user list until we need it.
On Wed, Sep 8, 2010 at 3:16 AM, Dan Haywood wrote:
> Isis mentors:
> Given we're in the same situation and are still being bootstrapped, should
> we follow this advice, ie start off with a combined mailing list for -dev
g
> > Cc: d...@haywood-associates.co.uk
> > Subject: Re: No dev-, user- lists for small podlings (was: Re:
> > [PROPOSAL] Kitty to Enter the Incubator)
> >
> > +1 especially since incubation is about establishing a developers
> > community
> >
> > -M
&g
Wednesday, 8 September 2010 7:29 PM
> To: general@incubator.apache.org
> Cc: d...@haywood-associates.co.uk
> Subject: Re: No dev-, user- lists for small podlings (was: Re:
> [PROPOSAL] Kitty to Enter the Incubator)
>
> +1 especially since incubation is about establishing a developers
&
d do fine for
> now.
>
> LieGrue,
> strub
>
> --- On Wed, 9/8/10, Dan Haywood wrote:
>
>> From: Dan Haywood
>> Subject: Re: No dev-, user- lists for small podlings (was: Re: [PROPOSAL]
>> Kitty to Enter the Incubator)
>> To: general@incubator.apache.org
gs (was: Re: [PROPOSAL]
> Kitty to Enter the Incubator)
> To: general@incubator.apache.org
> Date: Wednesday, September 8, 2010, 7:16 AM
> Isis mentors:
> Given we're in the same situation and are still being
> bootstrapped,
> should we follow this advice, ie start off
On Wed, Sep 8, 2010 at 9:16 AM, Dan Haywood wrote:
> Isis mentors:
> Given we're in the same situation and are still being bootstrapped, should
> we follow this advice, ie start off with a combined mailing list for -dev
> and -user? ...
Like Martijn and Greg I think that's a great idea.
We ran
Isis mentors:
Given we're in the same situation and are still being bootstrapped,
should we follow this advice, ie start off with a combined mailing list
for -dev and -user?
Dan
On 08/09/2010 08:10, Martijn Dashorst wrote:
On Wed, Sep 8, 2010 at 7:22 AM, Greg Stein wrote:
On Tue, Sep 7, 20
On Wed, Sep 8, 2010 at 7:22 AM, Greg Stein wrote:
> On Tue, Sep 7, 2010 at 20:29, Matthew Sacks wrote:
>>...
>
>> *Mailing Lists*
>>
>> kitty-dev
>> kitty-commits
>> kitty-user
>>
>
> Is there a large user community already? If not, then splitting the
> community across dev/user does not make sens
On Tue, Sep 7, 2010 at 20:29, Matthew Sacks wrote:
>...
> *Mailing Lists*
>
> kitty-dev
> kitty-commits
> kitty-user
>
Is there a large user community already? If not, then splitting the
community across dev/user does not make sense. You want to keep the users
and developers on the same mailing l
39 matches
Mail list logo
