Re: VXQuery status (Was: [Incubator Wiki] Update of "April2012" by TillWestmann)
Hi, On Tue, Apr 3, 2012 at 12:52 AM, Vinayak Borkar wrote: > We in the VXQuery trenches need some help with growing the community. We > understand the technical aspects of implementing the XQuery engine, but need > some guidance with community building. It seems like you're lacking active mentors. Any volunteers to help VXQuery? > My day-job is at a university where I meet students with various interests. > The GSoC project proposals were done with the aim of using students for the > summer (with funding by Google through GSoC), to work on bootstrapping the > VXQuery project so it gets into a functional state. OK. A big part of GSoC is giving students a chance to interact and work with an open source community, so I think it would be good if there was at least some ongoing activity beyond or in addition to the GSoC projects. ComDev people, is there anything you think you could/should do to help VXQuery on this? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Extraordinary OpenOffice security patch (Was: [Incubator Wiki] Update of "April2012" by robweir)
Hi, On Thu, Apr 5, 2012 at 7:27 PM, Apache Wiki wrote: > OpenOffice > > Out-of-Band Report Thanks the explicit report about this! > The IPMC and Board should note that this extraordinary patch was made > available, as a courtesy to the ecosystem, based on the severity of the > reported > vulnerability and the ease of exploiting it. The patch was made available > under > ALv2, and distribution was done via the Apache mirrors, although this did > not constitute an official release. This is pretty gray territory. Normally neither a podling nor a TLP should ever publish binaries for distribution without all the relevant source code and without going through the standard voting procedure. > Because of the required secrecy around the preparation of such security > patches, > a minimum number of Apache members were involved in vetting this release, > though > we did try to touch all bases by involving mentors, Infra and Legal Affairs. I'm inclined to trust the judgement of people involved here. It should be noted though that even though the /dist/incubator/ooo space was used to distribute these patches, they were and are not officially blessed by the Incubator PMC on behalf of the ASF. Should a similar case arise in the future, I'd prefer if a clearly separate area under /dist or some other place was used to prevent confusing these with official Apache releases. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Tashi status (Was: [Incubator Wiki] Update of "April2012" by MichaelStroucken)
Hi, Thanks for the report, Tashi! On Fri, Apr 6, 2012 at 8:49 PM, Apache Wiki wrote: > + In the period from January to April, the project had received permission > + to publish a release. Shortly thereafter, a further release was > + approved, incorporating several bug fixes detected during deployment > + of the first release and from Jira reports. Great! > + In the process of making our first release, contact to two of our three > + mentors was re-established. The third mentor has not been heard from > + (also in other parts of Apache) for quite a while. Good to hear that. Could you update the podling status page to drop the third mentor? More generally, I guess we at the IPMC should check whether the mentors of especially long-running podlings are still actively involved. I'll follow up about that in a separate email. > + The project has a user community, but it is small. Growth mostly has > + happened by word of mouth. To show potential users at large the > + utility of this project, the author of this report will apply some of > + the advice posted to gene...@apache.incubator.org, as well as create > + web pages demonstrating the project's utility, provide sample VM images > + and disseminate other information relating to the deployments close to him. > + He will also urge others to make similar information publically available. I'm looking forward to hearing about the results and your experience on what worked and what didn't, perhaps in time for your next report in July. Some of these ideas are quite time-consuming to implement, so it'll also be useful to know if some where dropped because of insufficient free cycles. > + One of our users has requested the creation of a private branch for his > + team to work on. Perhaps this will result in a valuable feature addition > + to the project. +1 if that helps get them more involved. Ultimately though you'll want to have everyone in the community work together on a shared codebase. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Giraph status (Was: [Incubator Wiki] Update of "April2012" by OwenOmalley)
Hi, Thanks for the report, Giraph! On Tue, Apr 3, 2012 at 7:15 AM, Apache Wiki wrote: > + Next steps: > + * Another incubator release > + * Adding new committers Looking at the report and recent project activity it looks like Giraph is doing pretty well. In fact I can't spot any obvious graduation blockers. Anything I'm missing? If not, have you already started preparing for graduation? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
JSPWiki status (Was: [Incubator Wiki] Update of "April2012" by HarryMetske)
Hi, Thanks for the report, JSPWiki! On Wed, Apr 4, 2012 at 6:43 PM, Apache Wiki wrote: > + As a result of discussing in the dev-list, the objectives > + for graduation have changed: the first Apache release > + will be based on 2.8 (package-renamed), which is > + battle-tested, being the plan to evolve from there. Sounds good. > + 4 JIRA issues were fixed since last period, and tests are > + now part of the main build. That's a fairly low level of activity, though fine if you think it's increasing or stable over time. > + The main issues blocking graduation now are resolution > + acceptance, and community and IPMC graduation vote. In addition to the first release, I assume. How far along are you with that? > + The developer list currently has ?? subscribers; and the > + user list has ??? subscribers. Without the numbers this doesn't add much, so I dropped the sentence from the report. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release ManifoldCF 0.5-incubating, RC6
Hi, Please vote on whether or not to release ManifoldCF 0.5-incubating, RC6. This RC has passed our podling vote and awaits your inspection. You can download the release candidate from http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC6/ and there is also a tag in svn under https://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.5-incubating-RC6/. It has done improvements for its distribution(bin,lib,src) and build process as to core dependencies. Thank you, Shinichiro Abe - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] CloudStack for Apache Incubator
On 10/04/2012, at 11:32 AM, Kevin Kluge wrote: > Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator. > The proposal is available at [1] and I have also included it below. Please > vote with: > +1: accept CloudStack into Incubator > +0: don't care > -1: do not accept CloudStack into Incubator (please explain the objection) > > The vote is open for at least 72 hours from now (until at least 19:00 US-PST > on April 12, 2012). +1 -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Giraph status (Was: [Incubator Wiki] Update of "April2012" by OwenOmalley)
On Wed, Apr 11, 2012 at 4:30 PM, Jukka Zitting wrote: > Hi, > > Thanks for the report, Giraph! > > On Tue, Apr 3, 2012 at 7:15 AM, Apache Wiki wrote: >> + Next steps: >> + * Another incubator release >> + * Adding new committers > > Looking at the report and recent project activity it looks like Giraph > is doing pretty well. In fact I can't spot any obvious graduation > blockers. Anything I'm missing? If not, have you already started > preparing for graduation? We haven't started yet, but I was thinking along similar lines. Should I start a vote on the dev list? Thanks, Owen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Spam on the Incubator wiki
> -Original Message- > From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] > Sent: Wednesday, 11 April 2012 3:05 AM > To: general@incubator.apache.org > Subject: Re: Spam on the Incubator wiki > > Hi Gavin, > > On Tue, Apr 10, 2012 at 11:36 AM, Gavin McDonald > wrote: > > I'm seeing more and more spam appear, just give me the nod and it'll > > be done. > > You're the man! With no objections raised, please make the change. Done, let me know if any issues. Someone should change the greeting/edit instructions On the incubator home page to state that a once off email to general@ is enough to be Granted wiki write access. HTH Gav... > > Thanks! > > BR, > > Jukka Zitting > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2126 / Virus Database: 2411/4925 - Release Date: 04/09/12 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Extraordinary OpenOffice security patch (Was: [Incubator Wiki] Update of "April2012" by robweir)
On 4/11/2012 2:36 PM, Jukka Zitting wrote: > > It should be noted though that even though the /dist/incubator/ooo > space was used to distribute these patches, they were and are not > officially blessed by the Incubator PMC on behalf of the ASF. > > Should a similar case arise in the future, I'd prefer if a clearly > separate area under /dist or some other place was used to prevent > confusing these with official Apache releases. Short of people.a.o/~luser/my-patch.tgz, I'm fairly certain that can't happen with an incubating podling. Everything under the space /dist/ must exist under a PMC. And if AOOo ever does on a broad security patch distribution, inflicting that traffic on people.a.o, infra will be taking names and kicking asses. As chair, you should have been brought into this loop, but with the change from Noel I can see how this oversight happened. Sorry about that. It's probably another example why the current infrastructure schema simply isn't plausible. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Extraordinary OpenOffice security patch (Was: [Incubator Wiki] Update of "April2012" by robweir)
On Apr 11, 2012, at 10:43 PM, William A. Rowe Jr. wrote: > On 4/11/2012 2:36 PM, Jukka Zitting wrote: >> >> It should be noted though that even though the /dist/incubator/ooo >> space was used to distribute these patches, they were and are not >> officially blessed by the Incubator PMC on behalf of the ASF. >> >> Should a similar case arise in the future, I'd prefer if a clearly >> separate area under /dist or some other place was used to prevent >> confusing these with official Apache releases. > > Short of people.a.o/~luser/my-patch.tgz, I'm fairly certain that > can't happen with an incubating podling. Everything under the space > /dist/ must exist under a PMC. And if AOOo ever does on a broad > security patch distribution, inflicting that traffic on people.a.o, > infra will be taking names and kicking asses. > > As chair, you should have been brought into this loop, but with the > change from Noel I can see how this oversight happened. Sorry about > that. It's probably another example why the current infrastructure > schema simply isn't plausible. As a member of the IPMC and also the AOO PPMC I was not very happy with the way this was held close ny a few mentors and ooo-security members. I made claims on ooo-dev that we weren't going to patch when others knew perfectly well that we were, It was truly crazy time. I think that certain people erred on the side of not trusting trustworthy people. That is extremely unfortunate. I know that I was made to feel I wasted my precious time due to this secrecy. I think it was wrong. The "inner circle" failed to properly consider Linux users when many of the PPMC were well within that rank. There were significantly false assumptions about the user base impact that were perpetuated by the secrecy that surrounded this patch, The "inner circle" that did this felt they had no choice but to exclude the PPMC from their consideration. I know that this damaged my interaction with the project, I still feel very much untrusted. Sorry, I can't remain mute, but I offended anyone, sorry, but this was wrongly done. I don't know a better way Regards, Dave > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
