On 3/20/13 10:21 PM, Henri Yandell wrote:
> Bike-shedding can be handled.
>
> Someone volunteers to RM a component. They put what they think needs
> doing for the next release into a list (next JIRA version), and on
> list we vote on which of the proposed components is top of the heap
> for a swarm
I'd apply two pithy statements here:
1) Activity begets activity. Start working on something and people
will be attracted.
2) People don't contribute in a vacuum. You have to leave them work to do.
In both cases though, you have to be noticed. People have to see the
activity and they have to see
Bike-shedding can be handled.
Someone volunteers to RM a component. They put what they think needs
doing for the next release into a list (next JIRA version), and on
list we vote on which of the proposed components is top of the heap
for a swarm. Especially useful prior to an ApacheCon. Also usefu
Hi,
thanks for your comments! I know what you mean.
I surely don't want to force people to do stuff they are (currently) not
interested in.
The problem I have experienced when requesting comments (for example for
[beanutils]) is, that there is sometimes very few feedback.
This is probably because
+1 to Gary.
personally speaking, while I would really like to be involved in
Bene's vision, I *have to* put effort where I _need_ to, ATM; I have
more work and spare time to contribute just for the joy of participate
is a benefit that I don't have ATM, so my PQ is driven by what I need
for my dail
I appreciate your intention :) I feel this could lead to bike-shedding on
the priority queue though :( It can be tough enough to agree to release a
component as it is, without adding another level.
What might work is something more informal like: "I've worked on [foo] and
I've done all I need to g
Hi Benedikt,
I like the idea. I'm sure we would all prefer to release more often.
br,
Matt
On Mon, Mar 18, 2013 at 4:43 PM, Benedikt Ritter wrote:
> Hi all,
>
> when looking through the components and the sandbox I can see that
> development activity is very different.
> We have very few co
Hi all,
when looking through the components and the sandbox I can see that
development activity is very different.
We have very few components that are been worked on constantly, most
notably [math].
Some components seem to be worked on, only by a few people. [configuration]
comes to mind, where