Thanks for the feedback guys. The question certainly wasn't meant as a bitch and moan about the size of PMC vs people who actually sign stuff off. Clearly I am aware we all volunteer our time here unless you have a nice sponsoring company and as such people have other priorities and stuff to do. That said if you only have 4 or 5 people regularly VOTEing it increases the risk, and I don't like risk ;)
I shall take onboard the comments, and hopefully the increased release cycle will get people more involved, I'll create a wiki page for those wanting to help vote but are unsure as I can't find one and include it in the next release email. Cheers Tom On Fri, Feb 19, 2016 at 4:31 AM, Lewis John Mcgibbney < [email protected]> wrote: > Hi Tom, > > bq. When a release goes to VOTE how do we get more people involved? > > Hit Twitter, Facebook and the G+ group. I do this with every piece of > software I do RM for. It actually seems to work! > One thing we've been getting more of over on Nutch (due to this) is some > people from the community who are not committers and/or PMC but who end up > taking the time to review an RC. I think that is not only cool but also > really positive for the RC as more people have seen it and hopefully > reviewed it. > > I want to share some experienced working within the Any23 community. Any23 > is VERY quiet. I used to have to go to the IPMC to p*ss off enough people > from the Any23 PMC that they would eventually come back and review the RC. > The lesson I learned over there is that just because people don't get back > immediately, or if they don't reply within say even a week, it doesn't mean > that they don't give a toss, it's 'most likely' that they are just crammed > with 101 things to do. > > In some cases, actually in most cases I would much rather have people > review the RC in their own time and be positive that a VOTE is well placed > rather than just throwing in a +1 for the sheer hell of it. > > Good job with the RC. Pushing releases is a great thing for OODT. If you > look at the release history, it was not too long ago that OODT was > releasing once a year. Current release management strategy is looking much > better. > Lewis > > On Wed, Feb 17, 2016 at 2:32 AM, Tom Barber <[email protected]> > wrote: > > > Hello folks > > > > As some of you will be aware there has been a release VOTE sat in the > wild > > with no votes since Feb 11th, now I might have picked a bad time to > submit > > the vote but that's by the by, I have a question off of the back of this. > > > > When a release goes to VOTE how do we get more people involved? > > > > There are 43 people on the PMC who can all check the release artefacts > and > > VOTE on whether it be released or not, yet the majority of the releases > > have the same 4 or 5 people voting. So, are most of the PMC emeritus? Is > it > > a lack of clarity on what is involved in voting, or something completely > > different? > > > > Understandably the platform doesn't see a great deal of development > > activity because it does what it says on the tin, but as its an ASF > project > > it does need a cohesive PMC to make sure build and issues get resolved > > properly, so what can we do to improve it? > > > > Thanks > > > > Tom > > > > > > -- > *Lewis* >
