Re: [VOTE] [DISCUSS] Recommend to the Board to establish the Apache OpenOffice Project
On 10/10/2012 Andrea Pescetti wrote: Please cast your vote: [ ] +1, recommend the resolution to the Board [ ] +0, abstain/don't care [ ] -1, do not recommend the resolution to the Board, because... This vote will be open for 72 hours from now; only votes from the Incubator PMC are binding. Heads-up: the voting period will finish in about 6 hours. Shortly after it finishes, I plan to send the tally to this list and (upon successful outcome of the vote) send an email to the Board asking to include the resolution in the agenda for the next Board meeting. I'm just following the guidelines at http://incubator.apache.org/guides/graduation.html#process but if there is anything that should be done differently please share it here, since we are on a tight schedule to make it in time for next Board meeting. Regards, Andrea. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Recommend to the Board to establish the Apache OpenOffice Project
+1 Yegor On Wed, Oct 10, 2012 at 11:00 PM, Andrea Pescetti wrote: > Seeing no objections to my last message, and keeping into account that this > list had been regularly informed about the steps Apache OpenOffice was > taking towards graduation, I'm hereby asking the IPMC to recommend the > following resolution to the Board. Aim of the resolution is to establish the > Apache OpenOffice Project as a Top Level Project. > > Please cast your vote: > > [ ] +1, recommend the resolution to the Board > [ ] +0, abstain/don't care > [ ] -1, do not recommend the resolution to the Board, because... > > This vote will be open for 72 hours from now; only votes from the Incubator > PMC are binding. > > Resolution text: > --- > WHEREAS, the Board of Directors deems it to be in the best interests of the > Foundation and consistent with the Foundation's purpose to establish a > Project Management Committee charged with the creation and maintenance of > open-source software related to the OpenOffice personal productivity > applications, for distribution at no charge to the public. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), > to be known as the "Apache OpenOffice Project", be and hereby is established > pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache OpenOffice Project be and hereby is responsible > for the creation and maintenance of software related to the OpenOffice > personal productivity applications; and be it further > > RESOLVED, that the office of "Vice President, OpenOffice" be and hereby is > created, the person holding such office to serve at the direction of the > Board of Directors as the chair of the Apache OpenOffice Project, and to > have primary responsibility for management of the projects within the scope > of responsibility of the Apache OpenOffice Project; and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed to serve as the initial members of the Apache OpenOffice Project: > > * Andre Fischer (af) > * Andrea Pescetti (pescetti) > * Andrew Rist (arist) > * Ariel Constenla-Haile (arielch) > * Armin Le Grand (alg) > * Dave Fisher (wave) > * Donald Harbison (dpharbison) > * Drew Jensen (atjensen) > * Ian Lynch (ingotian) > * Jürgen Schmidt (jsc) > * Kay Schenk (kschenk) > * Kazunari Hirano (khirano) > * Louis Suarez-Potts (louis) > * Marcus Lange (marcus) > * Oliver-Rainer Wittmann (orw) > * Pedro Giffuni (pfg) > * Peter Junge (pj) > * Raphael Bircher (rbircher) > * Regina Henschel (regina) > * RGB.ES (rgb-es) > * Roberto Galoppini (galoppini) > * Yang Shih-Ching (imacat) > * Yong Lin Ma (mayongl) > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrea Pescetti be appointed to > the office of Vice President, OpenOffice, to serve in accordance with and > subject to the direction of the Board of Directors and the Bylaws of the > Foundation until death, resignation, retirement, removal or > disqualification, or until a successor is appointed; and be it further > > RESOLVED, that the initial Apache OpenOffice Project be and hereby is tasked > with the creation of a set of bylaws intended to encourage open development > and increased participation in the OpenOffice Project; and be it further > > RESOLVED, that the Apache OpenOffice Project be and hereby is tasked with > the migration and rationalization of the Apache OpenOffice.org podling; and > be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > OpenOffice.org podling encumbered upon the Apache Incubator Project are > hereafter discharged. > --- > Best regards, > Andrea Pescetti - Apache OpenOffice PPMC. > > - > 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
DeviceMap status (Was: [Incubator Wiki] Update of "October2012" by BertrandDelacretaz)
Hi, Thanks for the report, DeviceMap! On Fri, Oct 5, 2012 at 11:52 AM, Apache Wiki wrote: > No new committers or PPMC members, and very low activity so far, but > the OpenDDR code that was mentioned in the incubation proposal has just > been donated, which should help motivate people to become more active. OK, let's keep an eye on the situation. Hopefully the newly arrived code and perhaps a release based on that can bring in more activity. > The donation included a data file with had been subject to a DMCA takedown > request while hosted at Github. After some discussion we decided to exclude > that file from the donation, as the ownership of part of that data is hard to > establish. Details at https://issues.apache.org/jira/browse/DMAP-11 which > also links to threads on general@incubator.a.o. I'm not sure if this was brought up yet (or already implemented), but would it make sense for DeviceMap to treat this data file as an optional third party dependency, i.e. be able to use the contained information when this file is made available by the user or deployer? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Helix into Apache Incubator
+1 (binding). Looks very interesting. Let me know if you need an other mentor for the incubation. 2012/10/10 kishore g : > Hi, > > I would like to call a vote for accepting Helix for incubation in the > Apache Incubator. I have pasted the full proposal below. > > Please cast your vote: > > [ ] +1, bring Helix into Incubator > [ ] +0, I don't care either way, > [ ] -1, do not bring Helix into Incubator, because ... > > This vote will be open for 72 hours and only votes from the Incubator > PMC are binding. > > Thanks, > Kishore G > > > == Abstract == > Helix is a cluster management system for managing partitioned and > replicated resources in distributed data systems. > > == Proposal == > Helix provides an abstraction that separates coordination and > management tasks from functional tasks of a distributed system. The > developer defines the system behavior via a state machine, the > transitions between those states, and constraints on states and > transitions that govern the system’s valid settings. Helix ensures the > distributed system satisfies the state machine, controlling state > changes as appropriate during common operational activities such as > upgrades, component failures, bootstrapping, running maintenance > tasks, and adding capacity. > > == Background == > Helix was developed at LinkedIn to manage large clusters for several > diverse applications, including a distributed, partitioned, > replicated, highly available document store with a master-slave model, > a search service with multiple replicas that are updated atomically > and in near real-time, and a change data capture service for reliably > transporting database changes to caches, other dependent databases and > indexes. > > These services use Helix to reliably manage dozens of clusters in > multiple data centers. These services meet stringent SLAs at large > scale for mission-critical production applications such as search, > social gestures, and profiles. > Helix has proven to be flexible for a wide variety of system > configurations and operational patterns, is easy to integrate, with > pluggable interfaces enabling custom behavior. It depends on Apache > Zookeeper for coordination and tracking of system state across the > cluster, as well as providing fault tolerance. > Helix is written in Java. It was developed internally at LinkedIn to > meet our particular use cases, but will be useful to many > organizations facing a similar need to manage large clusters. > Therefore, we would like to share it the ASF and begin developing a > community of developers and users within Apache. > > == Rationale == > Many organizations can benefit from a generalized cluster management > system such as Helix. While our distributed data systems use-cases for > a very large website like LinkedIn has driven the design of Helix, its > uses are varied and we expect many new use cases to emerge. > > == Current Status == > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Helix following the Apache meritocracy > model. Since Helix was initially developed in late 2011, we have had > fast adoption and contributions by multiple teams at LinkedIn. > We plan to continue support for new contributors and work with those > who contribute significantly to the project to make them committers. > > === Community === > Helix is currently being used internally at LinkedIn and is in > production in that company for customer-facing features. Recent public > presentations of Helix and its goals garnered much interest from > potential contributors. We hope to extend our contributor base > significantly and invite all those who are interested in building > large-scale distributed systems to participate. > To further this goal, we use GitHub issue tracking and branching facilities. > > === Core Developers === > Helix is currently being developed by three engineers at LinkedIn: > Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, > an engineer at Trifacta. Kishore, the lead developer and architect, > has experience within Apache as an S4 committer. Shi developed the > partition to node mapping and rebalancing algorithm, cluster admin > APIs, and the health check framework. Jason developed the cluster > controller and most of the test framework. Adam developed the rich > alerting framework that enables cluster-wide, “intelligent“ alerts. > > === Alignment === > The ASF is the natural choice to host the Helix project as its goal of > encouraging community-driven open-source projects fits with our vision > for Helix. Many projects that can benefit from Helix will rely on > Apache ZooKeeper for cluster state management, and can far more easily > achieve their operational goals by using Helix. > > == Known Risks == > === Orphaned Products === > The core developers plan to work full time on the project. There is > very little risk of Helix being abandoned as it is a critical part of > Link
JSPWiki status (Was: jspwiki)
Hi, On Tue, Oct 9, 2012 at 1:05 AM, Jukka Zitting wrote: > JSPWiki has been troubled for quite some time. Following up on this and since JSPWiki is by far our oldest podling, I felt it appropriate to summarize its status and outlook from the IPMC perspective in this months board report. Here's my summary: JSPWiki is our oldest podling with over five years in the Incubator. Activity in JSPWiki was very low for a few years and they've yet to create their first Apache release. Earlier this year they discussed leaving the Incubator and the ASF since they clearly weren't making much progress. That discussion led to some revival of activity and the decision to continue in the Incubator. Unfortunately the podling no longer has enough active mentors, which has led to some trouble with premature attempts at cutting releases or graduating. Despite these troubles the podling is making progress, and with sufficient help from the IPMC they might well become ready to graduate within a few quarters. JSPWiki committers/mentors, does this sound like an accurate summary? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Recommend to the Board to establish the Apache OpenOffice Project
On 10/10/2012 3:00 PM, Andrea Pescetti wrote: Seeing no objections to my last message, and keeping into account that this list had been regularly informed about the steps Apache OpenOffice was taking towards graduation, I'm hereby asking the IPMC to recommend the following resolution to the Board. Aim of the resolution is to establish the Apache OpenOffice Project as a Top Level Project. Please cast your vote: [ ] +1, recommend the resolution to the Board [ ] +0, abstain/don't care [ ] -1, do not recommend the resolution to the Board, because... +1, (binding) IPMC & mentor. This vote will be open for 72 hours from now; only votes from the Incubator PMC are binding. If this were happening even a month ago, I would have commented earlier on the 72 hour period. 72 hours is a *minimum* period for [VOTE] threads; allowing a longer period for major decisions is often helpful, especially when you see there are fairly few comments here on general@. But the AOO community has come a looong way in the past few months, and it's clear on the AOO lists that the community and proposed PMC members have been making excellent progress both on the code and especially on improving positive community engagement and informed consensus driven work and decisions. Bertrand has a point that there is only a single ASF Member on the PMC list - normally this wouldn't be a significant issue, but given the scope and impact of the AOO project, it would indeed be good to ensure that we have more well-versed Members or long-term committers from other projects keeping abreast of AOO to help out. Besides the new amount of freely downloadable software for the public good that the AOO project provides, we should not underestimate the positive impacts that the next few major releases of Apache OpenOffice will have on both the office suite world and on awareness of the Apache brand. - Shane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: JSPWiki status (Was: jspwiki)
Hi Jukka, On Oct 13, 2012, at 7:49 AM, Jukka Zitting wrote: Hi, On Tue, Oct 9, 2012 at 1:05 AM, Jukka Zitting wrote: JSPWiki has been troubled for quite some time. Following up on this and since JSPWiki is by far our oldest podling, I felt it appropriate to summarize its status and outlook from the IPMC perspective in this months board report. Here's my summary: JSPWiki is our oldest podling with over five years in the Incubator. Activity in JSPWiki was very low for a few years and they've yet to create their first Apache release. Earlier this year they discussed leaving the Incubator and the ASF since they clearly weren't making much progress. That discussion led to some revival of activity and the decision to continue in the Incubator. Unfortunately the podling no longer has enough active mentors, which has led to some trouble with premature attempts at cutting releases or graduating. Despite these troubles the podling is making progress, and with sufficient help from the IPMC they might well become ready to graduate within a few quarters. JSPWiki committers/mentors, does this sound like an accurate summary? Sounds fair enough. I'm still actively mentoring the project but could it use some more mentors. The project is in the middle of cutting their first release, and we all know that the first time is the hardest. The biggest issue regarding the release was the decision to *not* release the 3.0 code base that had been the focus of previous efforts. If everyone stays focused, I believe that the project can graduate within a few months after release. Craig BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: JSPWiki status (Was: jspwiki)
On Oct 13, 2012, at 8:19 AM, Craig L Russell wrote: Hi Jukka, On Oct 13, 2012, at 7:49 AM, Jukka Zitting wrote: Hi, On Tue, Oct 9, 2012 at 1:05 AM, Jukka Zitting > wrote: JSPWiki has been troubled for quite some time. Following up on this and since JSPWiki is by far our oldest podling, I felt it appropriate to summarize its status and outlook from the IPMC perspective in this months board report. Here's my summary: JSPWiki is our oldest podling with over five years in the Incubator. Activity in JSPWiki was very low for a few years and they've yet to create their first Apache release. Earlier this year they discussed leaving the Incubator and the ASF since they clearly weren't making much progress. That discussion led to some revival of activity and the decision to continue in the Incubator. Unfortunately the podling no longer has enough active mentors, which has led to some trouble with premature attempts at cutting releases or graduating. Despite these troubles the podling is making progress, and with sufficient help from the IPMC they might well become ready to graduate within a few quarters. JSPWiki committers/mentors, does this sound like an accurate summary? Sounds fair enough. I'm still actively mentoring the project but could it use some more mentors. Correction: It could use some more mentors. The project is in the middle of cutting their first release, and we all know that the first time is the hardest. The biggest issue regarding the release was the decision to *not* release the 3.0 code base that had been the focus of previous efforts. If everyone stays focused, I believe that the project can graduate within a few months after release. Craig BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Celix status (Was: [Incubator Wiki] Update of "October2012" by PepijnNoltes)
On Oct 12, 2012, at 2:56 PM, Jukka Zitting wrote: > Hi, > > Thanks for the report, Celix! > > On Wed, Oct 3, 2012 at 4:36 PM, Apache Wiki wrote: >> We have prepared the code base and website for release and we are >> very close to making a release. > > Great stuff! Hopefully the release process works smoothly for you. > >> There has been a small decrease on activity on the mailing list, >> hopefully this is a temporary decrease due to the holidays. > > OK. Such drops happen every now and then for all projects. It's good > if you pay attention to the situation and are able to identify root > causes and take corrective action if activity doesn't bounce back on > it's own. Getting a release out is often a good way to revive interest > in a project. I looked in as well and wish Celix success. Regards, Dave > > BR, > > Jukka Zitting > > - > 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
Re: Kitty status (Was: [Incubator Wiki] Update of "April2012" by AlessandroNovarini)
It looks like the VOTE thread is +3 for retirement. And has digressed into what will happen with the code. Would someone care to call the RESULT, or should the IPMC declare it done and proceed with retirement? Regards, Dave On Sep 24, 2012, at 12:57 PM, Jukka Zitting wrote: > Hi, > > On Mon, Sep 17, 2012 at 1:18 AM, Ted Dunning wrote: >> Perhaps the kitty community can replay the vote with a definitive outcome. > > With no reaction within a week and no report since April, I think it's > safe to say that the community is no longer active and should be > retired. It doesn't look like the community has enough energy left to > do that by itself. > > Kevan, since you ran the community vote on retirement, would you mind > repeating the vote on general@ for the IPMC? > > BR, > > Jukka Zitting > > - > 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
Re: [DISCUSS] Jr. Mentor role
Sent from my tablet On Oct 13, 2012 2:59 AM, "Marvin Humphrey" wrote: > > On Fri, Oct 12, 2012 at 1:06 AM, Ross Gardler > wrote: > > Nobody, in my opinion, sh8old be voting on a release without having > > conducted the appropriate verifications themselves. > > -0 > > I agree -- but that's not going far enough. > > In my view, no one should vote on a release unless they're subscribed to the > podling's dev list. > Agreed. > That the Incubator's release process would grind to a halt without "freelance" > IPMC votes exposes a systemic flaw. > Also agreed. I think Jukka's release taskforce idea is a good way to address this. With respect to the rest of the thread, all very valid but I think the above points are the important ones. Ross > >> The first AOO release got my freelance IPMC vote because it was clear that > >> they knew what they were doing and were taking their role as IP stewards > > > > (As a mentor I also voted +1 so don't take my next comments personally) > > > > This is a perfect example of why proper reviews are necessary. In the > > second AOO release a problem was discovered (that was present in the first > > release). > > After reviewing the thread at < http://markmail.org/message/2penzb453qzo55rz> > and seeing people competently and earnestly work through a thorny issue, I'm > inclined to draw the opposite conclusion. Rather than a failure of oversight, > this seems like an example of successful empowerment and self-policing. > > In the real world, IP bugs happen. (Just look at all the slop we see in > LICENSE and NOTICE files.) To my mind, what matters most is not whether a > project can avoid all IP bugs forever, but whether the team possesses both the > capacity and the will to detect and dispatch IP bugs efficiently. > > >> , it is much more important that the community members own the task of IP > >> management themselves than that they pass any sort of superficial > >> documentation review. > > > > Isn't that a contradiction? If you voted +1 on the grounds of the PPMC > > knowing what they we doing isn't that a the most "superficial of > > documentation reviews"? > > My position is that the oversight mechanisms generally employed by the > Incubator, such as license header scans, are inherently superficial even when > executed conscientiously. A truly rigorous IP audit would proceed either > line-by-line, or commit-by-commit to match up with the standard of an Apache > PMC scrutinizing individual messages to a commits list. > > For the record, my review of the first AOO release candidate was considerably > more thorough than the norm. In fact, I doubt you will find a more thorough > review of an incubating release by a non-Mentor in the last two years, and > perhaps not for a long time before that. > > Here are links to the review thread and to my final VOTE: > > http://markmail.org/thread/b4wdzilemtu36i4a > http://markmail.org/message/ejs6qw6kpr22o3ps > > > It seems all you reviewed was some mailing list traffic. > > That's completely inaccurate. > > Please review the review thread. I went several rounds with Jürgen Schmidt, > though the work was spread out across multiple people and multiple lists. > LICENSE and NOTICE were reformulated and we built consensus for the new > approach both here and on legal-discuss. We pored over the rat-excludes file > and got RAT passing. When I found that the svn tag and the release archive > did not match, we had a discussion about scripting release builds. We > discussed why the file name had to include the string "incubating", file > formats for sums and sigs, etc, etc... > > > I encourage us to empower more people who do the work so their vot3s are > > binding. > > In my opinion, it's ridiculous that Jürgen Schmidt's heroics on the first AOO > release did not earn him a binding vote on the second. > > When it comes to release voting, the Incubator does not recognize merit, and > the Incubator does not encourage self-government. The miserable experience of > podlings as they twist in the wind for weeks awaiting "freelance" votes from > disintested IPMC members is the inevitable result. > > I'm glad that Roman wants to do his part to spare Helix from that fate, and I > wish him the best of luck. Personally, I have made a decision not to perform > any more freelance reviews. It is difficult to do them well, and each +1 > serves to perpetuate a rotten system. > > Marvin Humphrey > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: jspwiki
Hi Jukka, basically yes. Maybe important to explain that the slowdown of activity was due to big changes in the codebase (3.0 branch), which had been planned and started mainly by two committers who then hadn't that much time anymore to finish them (That's life!). It took some time to realize this, but finally we decided to adapt our plans to the new situation, which means continuing with the 2.x codebase and concentrate on graduating asap. Best regards Florian Am 13.10.2012 16:49, schrieb Jukka Zitting: > Hi, > > On Tue, Oct 9, 2012 at 1:05 AM, Jukka Zitting wrote: >> JSPWiki has been troubled for quite some time. > > Following up on this and since JSPWiki is by far our oldest podling, I > felt it appropriate to summarize its status and outlook from the IPMC > perspective in this months board report. Here's my summary: > > JSPWiki is our oldest podling with over five years in the Incubator. > Activity in JSPWiki was very low for a few years and they've yet to > create their first Apache release. Earlier this year they discussed > leaving the Incubator and the ASF since they clearly weren't making > much progress. That discussion led to some revival of activity and > the decision to continue in the Incubator. Unfortunately the podling > no longer has enough active mentors, which has led to some trouble > with premature attempts at cutting releases or graduating. Despite > these troubles the podling is making progress, and with sufficient > help from the IPMC they might well become ready to graduate within > a few quarters. > > JSPWiki committers/mentors, does this sound like an accurate summary? > > BR, > > Jukka Zitting > > - > 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
[RESULT] Re: [VOTE] Recommend to the Board to establish the Apache OpenOffice Project
On 10/10/2012 Andrea Pescetti wrote: I'm hereby asking the IPMC to recommend the following resolution to the Board. Aim of the resolution is to establish the Apache OpenOffice Project as a Top Level Project. ... This vote will be open for 72 hours from now; only votes from the Incubator PMC are binding. The Vote started on 2012-10-10 has ended. Results: +1 Jukka Zitting (IPMC) +1 Chris Mattmann (IPMC) +1 Ross Gardler (IPMC) +1 Mark Struberg (IPMC) +1 Dave Fisher (IPMC) +1 Christian Grobmeier (IPMC) +1 Suresh Marru (IPMC) +1 Leif Hedstrom (IPMC) +1 Joe Schaefer (IPMC) +1 Yegor Kozlov (IPMC) +1 Shane Curcuru (IPMC) +1 Andrew Rist +1 Alexei Fedotov There were no other votes cast. Tally (IMPC): 11 "+1" votes, no "0" votes, no "-1" votes. The IPMC has approved the proposal to recommend the resolution to the Board. I'll now proceed and send an email to the Board asking to include the resolution in the agenda for the next Board meeting. Regards, Andrea Pescetti - Apache OpenOffice PPMC. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Fwd: [ANNOUNCE] Apache log4php 2.1.0 released
FYI :-) @Ivan: we should add gene...@logging.apache.org to our default recipients... the others may want to know about our little milestones without subscribing to log4php-dev Cheers! -- Forwarded message -- From: Ivan Habunek Date: Sat, Oct 13, 2012 at 1:01 PM Subject: [ANNOUNCE] Apache log4php 2.1.0 released To: Log4php Dev , Log4php User , annou...@apache.org Dear all, The Apache log4php team is pleased to announce the release of Apache log4php 2.3.0. Significant changes in this release include: * Ability to override the default renderer. * New experimental appender: FirePHP * Many improvemetns to LoggerLayoutPatern (support for long conversion words, many new conversion words) * Various improvements to appenders * Several bugfixes Release notes, including the full change, log can be found here: http://logging.apache.org/log4php/changelog.html The release is available from: http://logging.apache.org/log4php/download.html The PEAR package will be available in a couple of days from our PEAR channel: http://pear.apache.org/log4php/ Thanks to everyone who participated in the making of this release. Best regards, The Apache log4php team -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
