On 7/5/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
I take your point about Yet Another Role. On the other hand it takes 3
binding +1s to do a release, and projects typically have only one
mentor. It seems to me that a few people like you Robert take on a
large part of the burden of doing deta
A couple of points in relation to the discussion.
Firstly I'd like to make it clear I do not condone any "blind +1"ing.
I don't think anyone on this list does. In fact exactly the opposite.
The aim of this discussion was to come up with ways to ensure that
projects have people willing to do the h
On 7/5/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Actually this raises an interesting discussion about the Incubator PMC.
There is kind of a tricky role for Incubator PMC members. Because most
of us have no knowledge or affiliation with any given one of the tens
of incubator projects, we fin
Paul Fremantle wrote:
So here is a suggestion. Each incubator project could have nominated
two or three PMC members whose job is to pay attention to the project.
As opposed to a mentor - who is there to actively help, these PMC
members would be there to pay enough attention to have an input on
r
Actually this raises an interesting discussion about the Incubator PMC.
There is kind of a tricky role for Incubator PMC members. Because most
of us have no knowledge or affiliation with any given one of the tens
of incubator projects, we find it hard to have any say, especially
when it comes to
Shesh...what makes you think it was done lightly? As the rest of my post
indicated I'd taken the time to downloaded and try out their release, even
pointed out a problem in the readme files I'd found. And I'd looked at
things like the notice and license files that have cased problems in other
incu
