Re: apache binary distributions
On Thu, Aug 13, 2015 at 8:58 PM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, Aug 13, 2015 at 8:35 PM, Luke Han luke...@gmail.com wrote: There's one discussion in Kylin community about to add binary package in release, people are really would like to have one: http://mail-archives.apache.org/mod_mbox/incubator-kylin-dev/201508.mbox/%3CCAKmQrOZ_MFUyF_y7HXE7iVMCfJHuuOFuU4T8ibsPWfnw0z2Opw%40mail.gmail.com%3E For some reason, people (especially in China) is not easy to build from source, since there are many library hosted on some services which can't be access directly. Beyond that, the first impression of a project is how to setup correctly and successfully, it not make sense to have everyone to build from source. And the reality is many projects already DO binary package for convenience purpose. After read so long mail thread here, I have a little bit confusion:-( there are too many messages...should we have some clear guide or practices for such binary release ? Apache produces open source software, and official Apache releases consist of source code. Alongside such official releases, projects may offer binary packages supplied by volunteers which meet certain criteria: http://www.apache.org/dev/release#what In some cases, binary/bytecode packages are also produced as a convenience to users that might not have the appropriate tools to build a compiled version of the source. In all such cases, the binary/bytecode package must have the same version number as the source release and may only add binary/bytecode files that are the result of compiling that version of the source code release. I've always wondered about the official Apache releases consist of source code. So what if a project (members) does not vote but unofficially releases binary executable packages, perhaps along with source to some other location than /dist/? Clearly, it's not an official release by Apache policy but there the bits are in the wild anyway. I'm asking since at least for many of the Java/Maven based projects it's very easy and inexpensive to distribute software through Maven Central. NPM also happily uses Github as their central repository so you could technically make lots and lots of convenience artifacts available without ever officially releasing anything. Kalle
Re: [VOTE] Graduate Apache Bloodhound from Incubator
Was the potential trademark conflict discussed somewhere? See http://mail-archives.apache.org/mod_mbox/incubator-general/201212.mbox/%3c50ca29ad.6000...@apache.org%3E- if so, just linking to the discussion is fine. Kalle On Sun, Mar 10, 2013 at 4:29 PM, Joachim Dreimann jdreim...@apache.orgwrote: +1 (non-binding) - Joe On 10 March 2013 02:30, Greg Stein gst...@gmail.com wrote: +1 (binding) On Mar 9, 2013 6:32 PM, Gary Martin gary.mar...@wandisco.com wrote: Hi, Following the community graduation vote result announcement on the bloodhound-dev@i.a.o mailing list [1] and the conclusion of the podling name search [2], I would like to invite Apache Incubator to vote on recommending Apache Bloodhound for graduation. Please vote: [ ] +1 Graduate Apache Bloodhound podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache Bloodhound podling [ ] -1 Reject graduation of Apache Bloodhound podling from Apache Incubator because ... The vote will run for at least 72 hours. The proposed graduation resolution is below. Cheers, Gary [1] http://markmail.org/message/**k6q7l4gvdtuhu6z2 http://markmail.org/message/k6q7l4gvdtuhu6z2 [2] https://issues.apache.org/**jira/browse/PODLINGNAMESEARCH-**22 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-22 --- X. Establish the Apache Bloodhound Project 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, for distribution at no charge to the public, related to a software development collaboration tool, including issue tracking, wiki and repository browsing. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Bloodhound Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Bloodhound Project be and hereby is responsible for the creation and maintenance of software related to a software development collaboration tool, including issue tracking, wiki and repository browsing; and be it further RESOLVED, that the office of Vice President, Apache Bloodhound 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 Bloodhound Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Bloodhound 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 Bloodhound Project: * Mat Booth mbo...@apache.org * Matevž Bradač mat...@apache.org * John Chambers cham...@apache.org * Branko Čibej br...@apache.org * Joachim Dreimann jdreim...@apache.org * Andrej Golcov and...@apache.org * Peter Koželj pe...@apache.org * Gary Martin g...@apache.org * Gavin McDonald gmcdon...@apache.org * Ryan Ollos rjol...@apache.org * Mark Poole mpo...@apache.org * Greg Stein gst...@apache.org * Hyrum K. Wright hwri...@apache.org * Jure Žitnik j...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gary Martin be appointed to the office of Vice President, Apache Bloodhound, 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 Bloodhound PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Bloodhound Project; and be it further RESOLVED, that the Apache Bloodhound Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Bloodhound podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Bloodhound podling encumbered upon the Apache Incubator Project are hereafter discharged.
Re: Bloodhound status (Was: Shepherd assignments, December 2012, first pass)
Also - there's a fairly new startup in San Francisco area going by the same name Bloodhound (see http://bloodhound.com/). I'm not associated with them, just happened to hear about them. It's obviously not in the same business but given how Apache projects have traditionally been rather cautious with branding and trademark conflicts, name change is perhaps something the project may want to consider. Kalle On Tue, Dec 11, 2012 at 2:21 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: ything has worked out fairly well. This might be a useful example to keep in mind when similar cases come up
Re: [VOTE] Apache OpenMeetings 2.0 Incubating Release Candidate 3
On Tue, Jul 3, 2012 at 12:02 PM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: is this the only concern or are there any other objections that will only be checked in the next round? A vote is a vote. You can express general concerns but if nobody's voting against, take the comments and fix them in the next version. It's a majority vote with a minimum quorum of three binding yays and up to the release manager to disregard the disapprovals or stop the release for any reason. For incubating projects, I'd personally try to go ahead with a release if at all possible but the more negatives you get, the more difficult it is to garner the required approval. Kalle 2012/7/3 sebb seb...@gmail.com On 3 July 2012 19:02, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Dear Incubator Members, this is the 3th Release Candidate (the second Candidate was voted negative by the IPMC because of missing exact JAR filenames in LICENSE file and missing sources as ZIP not only as .tar.gz) There was already a positive vote at OpenMeetings Dev mailing list. Results: 6 PPMC +1: aaf, solomax, smoeker, alvaro, german, sebawagner 3 Wider Community +1: Irina, Denis, Jaime The Vote Thread is here: http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201206.mbox/%3CCACeMiA-Y5qwVEGbybqKdeidx%2BFbJbGAa%2B7PZsEKtH25Y-s35JQ%40mail.gmail.com%3E The Result Vote Thread is here: http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201207.mbox/%3CCACeMiA-ibo6fGCbnLjJX9H5H2kFGDVJRMfxPyMtzWzCWNi%2BpOg%40mail.gmail.com%3E Main changes are covered in the Readme: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0RC3/README Full Changelog: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0RC3/CHANGELOG Release artefacts: http://people.apache.org/~sebawagner/rc3/ Tag: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0RC3/ Sorry, but the NOTICE file contains unnecessary information; it is for *required* notices only. That means it should only refer to items which are actually included in the relevent artifact. Also, for such included items it must only include whatever is the *required* notice; this is generally a short copyright paragraph, but may sometimes be nothing. That depends on the license. PGP release keys (signed using 93A30395): http://svn.apache.org/repos/asf/incubator/openmeetings/project/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Sebastian -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] Third Party source
On Thu, Jun 7, 2012 at 11:06 PM, Roy T. Fielding field...@gbiv.com wrote: I fear we are miscommunicating again. Only the copyright owner is allowed to (re)move copyright notices or permit others to (re)move them on the owner's behalf. Interesting, why is that? Is it so by the law? Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Q. Forks without concensus?; A. anytime / depends / never without agreement
On Mon, Jan 9, 2012 at 9:42 AM, Hyrum K Wright hyrum.wri...@wandisco.com wrote: I think the Trac community sees this as a zero-sum game: if people are contributing to Bloodhound, they *aren't* contributing to Trac. Instead, we should try to convince the Bloodhound people that our philosophy is best, and they should just come over here. Resolving such philosophical differences and technical goals is difficult at best, and I don't see it happening soon. But that's okay, there isn't a globally optimal solution to issue tracking, and we can agree to experiment with different paths. But I've probably said too much already. There isn't much more I can add here, and the last think I want to do at this point is prolong the agony of this discussion. Where's the agony? I see the general discussion about forks without consensus as very healthy, and I think it should continue to be discussed till all voices are heard. [1] Indeed, I know of at least one private proprietary derivative of Trac, but since it's proprietary, nobody knows about it and nobody complains. It's the fact that Bloodhound is proposed as open source which is causing the hullaballoo in the first place. But dear Sir, I don't believe that to be true if I may say so. Had the original proposal been worded as a derivative intended to keep Trac as the foundation, rather than a take-over there wouldn't have been any hullaballoo. I still don't understand why Bloodhound needs to start by forking Trac, without a single line written yet. The architecture with a small core and many plugins versus a complete installable package are not contradicting in any way. Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Q. Forks without concensus?; A. anytime / depends / never without agreement
On Tue, Jan 3, 2012 at 10:33 AM, Greg Stein gst...@gmail.com wrote: On Jan 3, 2012 1:28 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Tue, Jan 3, 2012 at 9:57 AM, Leo Simons m...@leosimons.com wrote: So the generic policy is there is no generic policy, and instead there is appropriate application of judgement to specific cases. Generic policy doesn't mean you couldn't use judgement or make exceptions. In principle, if the ASF's mission is to build communities around source code, we should not accept forks of open source projects if that's not the (consensus) will of the original community. And what happens when the arriving community has a different vision than the original community? Do you tell them to go pound sand? Tell them the two communities are not allowed to diverge or separate? You tell the arriving community that you need to work with the original community and that forking an existing open source project with an existing community is your last option, not your first one. I think it's just plain common sense that you have to be respectful of others, just like in the real world. Specifically regarding Bloodhound, much of the issues would likely have been avoided if the proposal hadn't dismissed the original community and hadn't stated as its primary intention to fork the existing Trac project (see quotes below). If the stated goal had been to provide a packager and installers and work closely with the existing community, I bet the tone of all stakeholders would have been very different. Kalle --- From the proposal: By it's own recognition, however, the development community surrounding Trac has largely dissipated. As discussed earlier, the current Trac development community is small and reluctant to accept outside contributions. Given the Foundation’s reputation for building and maintaining communities, we feel a new project, based on Trac but incubated under the Apache umbrella, would help re-build the developer community, jump started by developer time donated by WANdisco. The initial goals for Bloodhound primarily revolve around migrating the existing code base and integrating external features to make the project easy to deploy. Some of the initial goals include: * Migrate the existing BSD-licensed Trac code base to the ASF. Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Flex for Apache Incubator
On Mon, Dec 19, 2011 at 6:09 PM, Greg Stein gst...@gmail.com wrote: Agreed. That is/was my read, too. Even still, companies don't participate in ASF projects, individuals do. To me, the proposal implies Adobe is a participating entity. The sentence in question would read better as To that end, employees of Adobe will only have minority representation on the initial committers list. Kalle On Dec 19, 2011 6:48 PM, ralph.goers @dslextreme.com ralph.go...@dslextreme.com wrote: I don't read it that way. Yes, ASF projects only contain individuals, but most of those individuals are employed and are in some way influenced by their employer. Calling out that the initial set of committers will be diverse and that a majority of those committers will be coming from places other than the company donating the code is very good to know. Perhaps the sentence should be reworded to simply reflect that. Ralph On Mon, Dec 19, 2011 at 12:46 PM, Donald Whytock dwhyt...@gmail.com wrote: A minor comment on one sentence... To that end, Adobe will only have minority representation on the initial committers list. As I understand it, companies don't have representation in Apache projects. Individuals do, that may or may not belong to a given company, and that may or may not be operating with their employer's backing. It'll be good to have participation by people with access to the resources of the original contributors. But it's participation by people. Whether or not those people represent Adobe is between Adobe and them. Just so Adobe understands that's a consequence of the code grant. Looks interesting, though. Given AOO, is this suggesting a trend of major companies transferring code and communities to Apache? Don On Mon, Dec 19, 2011 at 3:20 PM, Alex Harui aha...@adobe.com wrote: Hi everyone, I would like to propose Flex to be an Apache Incubator project. Here's a link to the proposal: http://wiki.apache.org/incubator/FlexProposal Thank you, Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [OT] Hoover is not an adjective, was: Re: [VOTE] Release Apache opennlp-1.5.2-incubating-rc5
On Wed, Nov 16, 2011 at 7:39 AM, sebb seb...@gmail.com wrote: On 16 November 2011 14:32, Thilo Goetz twgo...@gmx.de wrote: On 15/11/11 03:22, Benson Margulies wrote: On Mon, Nov 14, 2011 at 9:20 PM, sebb seb...@gmail.com wrote: On 15 November 2011 02:12, Benson Margulies bimargul...@gmail.com wrote: That page is very misleading, and there was a long discussion of this topic elsewhere. Look at the example just above the requirement: The Apache Xerces XML parsing library is easily configurable and compliant with current standards Yes, in some sense, Xerces is an adjective there, but really what the senator is trying to say is to construct a particular noun phrase. AIUI, trademarks need to be used as if they are adjectives. Not sure possible word order is relevant/conclusive. This might explain why people in a project like OpenNLP are confused by that sentence on the trademarks page. The point is that the mark must be *used as* an adjective. I think this was previously called an adjectival noun, it now seems to be called noun adjunct: http://en.wikipedia.org/wiki/Noun_adjunct What do you suggest the trademarks page should say in order to make it clearer? I'm glad that Thilo brought this up because talking about an adjective is clearly incorrect and confusing. Indeed, the Wikipedia source you linked to clearly specifies it's a noun, not an adjective. As to what the trademarks page should say, first of all the used as an adjective needs to be removed and replaced with the correct term, noun adjust or attributive noun; the latter may be intuitively more clear. Instead of: Project and product names should always be referred to in a consistent casing and used as an adjective, and never as a noun or verb, like any trademark should be used. How about: Project and product names should always be referred to in a consistent casing and can not be used alone to specify the project or the product, but only as attributive nouns to the specific term (e.g. project, product, library, etc.) to indicate trademarks associated with it. Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Openmeetings to Apache Incubator
+1 (non-binding) On Mon, Nov 7, 2011 at 10:53 PM, Andrus Adamchik and...@objectstyle.org wrote: Opemeetings proposal has been discussed a few times here before. The group of developers behind it worked hard (and succeeded) to address all potential obstacles to the Incubator acceptance and to the following incubation. They even went an extra mile and collected all ICLAs in adbvance. So now I am starting the vote to accept Openmeetings to Apache Incubator. The proposal is also available at: http://wiki.apache.org/incubator/OpenmeetingsProposal Please cast your votes: [ ] +1 Accept Openmeetings for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Andrus --- Andrus Adamchik Apache Cayenne ORM: http://cayenne.apache.org/ Twitter: http://twitter.com/andrus_a --- == OpenMeetings Project Proposal == == Abstract == Openmeetings is a web conferencing solution. == Proposal == Openmeetings provides video conferencing, instant messaging, white board, collaborative document editing and other groupware tools using API functions of the Red5 Streaming Server for Remoting and Streaming. == Background == Openmeetings was developed since 2007 by Sebastian Wagner and willing developers. The project ships a release approximately once per quarter. It was developed using LGPL license, and developers are currently thinking of re-licensing it under Apache License 2.0. The project started as module by Sebastian Wagner for an ELearning platform (Dokeos) and was then split into a separated project. That is the reason why there is a strong relation to educational institutions that are using OpenMeetings and there are integrations for platforms like Moodle, ATutor, Sakai, STudIP or ILias available (http://code.google.com/p/openmeetings/wiki/MoodlePlugins). The relation to educational institutions also subsequently lead to some projects funded by the EU where OpenMeetings was involved, for example by the Swedish/Finnish Centre of Open-Source !OpenKarken (Case-Study about the EU project at OSOR.eu: http://www.osor.eu/studies/finland-and-sweden-collaborate-using-oss ) The integration and internationalization of the project was a primary focus right from the start of the project. Since Version 0.5 there is a Language-Editor (http://code.google.com/p/openmeetings/wiki/LanguageEditor) to edit labels, export and import them as XML and you can use those XML files for future installations (or contribute it to the community). There are currently around 30 languages available. Since version 0.5.1 there is also a SOAP API to integrate !OpenMeetings. We constantly improve this SOAP/REST API (http://code.google.com/p/openmeetings/wiki/SoapMethods) with new functionality with a strong focus on security and usability. The auth-mechnism is quite similar to OAuth, you create some token and then assign rights to the token. (Documentation for Single Sign On: http://code.google.com/p/openmeetings/wiki/DirectLoginSoapGeneralFlow) The project name !OpenMeetings and logos are inspired by Ludovic Gasc who has been the project manager at Dokeos at the time Sebastian split !OpenMeetings as separated project. Red5 Server provides an Edge-Orion-Clustering (http://trac.red5.org/wiki/Documentation/Tutorials/EdgeOriginClusteringConfiguration). We hope to extend this clustering solution with support for rtmpt and rtmps and integrate that into our application as native clustering option. == Rationale == Last year most major vendors started commercial web conferencing solutions. This is an important part of software ecosystem, and there is an urge to consolidate open source development efforts in this direction. According to several studies demand for synchronous Communication, in opposite to asynchronous Communication like wiki's or email, will raise the upcoming years. For example Gartner promises that 2011 the market will grow 20% according to their Magic Quadrant report 2010 ( http://www.gartner.com/DisplayDocument?doc_cd=205941 ). Openmeetings is a unique solution in terms of patent purity and potentially can grow into solution built on top of the fully open source stack. That is why it is a good candidate for consolidating web conferencing community efforts. == Initial Goals == Each of project committers has their own set of goals, but we all share the following. * Move to Apache. * Become popular. To become popular we plan to do the following. * Improve ecosystem around the project. * Improve release process. * Improve project testing and stability. * Apply modular architecture/SOA for better integration with other projects. == Current Status == We have agreed on applying for the Apache Foundation and preparing our proposal for the vote. Technical status of the project is: Current stable tree is 1.8.x, Trunk is 1.9. ===
Re: Trademark Kill Searches...
On Sun, Oct 30, 2011 at 1:19 PM, Robert Burrell Donkin robertburrelldon...@gmail.com wrote: robertburrelldon...@gmail.com wrote: But yes, I agree that using kill search is probably a bad idea. What podlings needs to do is essentially fact finding (not interpretation). Perhaps someone could come up with something along this line of thinking... Podling Name Filter...? Podling Name Hunt...? Podling Name Elimination...? That Trademark Stuff Podlings Need To Do...? (Or someone could just suggest a cool name) Ideas? Not sure this action item needs to have a single, well-defined name, but I think you are approaching it from the wrong angle. Instead of eliminating, the projects need to do something like name availability search, or even confirming availability of a trademark, although it's difficult to get a 100% confirmation. It should be enough just to verify the availability to the best of your ability using common, best-practice guidance. Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache OpenMeetings incubator for Web Conferencing
2011/8/11 seba.wag...@gmail.com seba.wag...@gmail.com: I have updated the Proposal to be more clear on the external dependencies and possibilities to move away from them: http://wiki.apache.org/incubator/OpenmeetingsProposal#External_Dependencies From the sidelines, WebSockets would seem like a strong contender to replace RTMP. GlassFish's Atmosphere is under CDDL (which is allowed as appropriately labeled). Kalle 2011/8/11 Jim Jagielski j...@jagunet.com I've signed up for Mentor, in case we go ahead... On Jul 29, 2011, at 5:46 AM, dsh wrote: Sebastian and Alexei, your are welcome! Btw, here is my +1 On Fri, Jul 29, 2011 at 9:47 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: Daniel, Thank you for an excellent report! -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Thu, Jul 28, 2011 at 10:20 PM, dsh daniel.hais...@googlemail.com wrote: Hi, please find my feedback below: OS X Lion: * tested with: ** Firefox 5.0.1 and Adobe Flash Player 10.3 ** Safari 5.1 and Adobe Flash Player 10.3 * Observations: ** Openmeetings did not work with Firefox/Safari if using a webcam/mic cause on the adobe flash player settings dialog it was not possible to click allow nor deny ** In Safari clicking the share/record screen button N times did open the screen sharing app N times (maybe you want to check whether an instance of the app is already running) ** I understand if sharing screens everybody has control over your screen. you may consider adding a view only mode too. ** you might check while signing up whether popup blockers are active. if yes you could prompt the user to disable popup blockers first before signing in. ** pressing the share/record screen button opens a new, blank window just to download the JNLP app. maybe you want to change that to not open a separate window that needs to be closed after starting the JNLP app ** It looks like after stopping screen sharing the shared screen still remains on each participants screen. Maybe it would make sense to provide a message to each participant that the host stopped sharing its screen. OS X Snow Leopard: * tested with: ** Firefox 5.0.1 and Adobe Flash Player 10.3 ** Safari 5.1 and Adobe Flash Player 10.3 * Observations: ** Openmeetings did not work with Firefox cause the initial screen did not load after signing up ** In Safari clicking the share/record screen button N times did open the screen sharing app N times (maybe you want to check whether an instance of the app is already running) ** I understand if sharing screens everybody has control over your screen. you may consider adding a view only mode too. ** you might check while signing up whether popup blockers are active. if yes you could prompt the user to disable popup blockers first before signing in. ** pressing the share/record screen button opens a new, blank window just to download the JNLP app. maybe you want to change that to not open a separate window that needs to be closed after starting the JNLP app ** It looks like after stopping screen sharing the shared screen still remains on each participants screen. Maybe it would make sense to provide a message to each participant that the host stopped sharing its screen. Windows 7 Ultimate: * tested with: ** Firefox 4.0.1 and Adobe Flash Player 10.3 ** Firefox 5.0.1 and Adobe Flash Player 10.3 ** Safari 5.1 and Adobe Flash Player 10.3 * Observations: ** In Firefox clicking the share/record screen button N times did open the screen sharing app N times (maybe you want to check whether an instance of the app is already running) ** I understand if sharing screens everybody has control over your screen. you may consider adding a view only mode too. ** you might check while signing up whether popup blockers are active. if yes you could prompt the user to disable popup blockers first before signing in. ** In Safari signing up did open a new window instead of opening a new tab which is different to Firefoxs behaviour (maybe this can be changed in the Safari prefs) ** pressing the share/record screen button opens a new, blank window just to download the JNLP app. maybe you want to change that to not open a separate window that needs to be closed after starting the JNLP app ** It looks like after stopping screen sharing the shared screen still remains on each participants screen. Maybe it would make sense to provide a message to each participant that the host stopped sharing its screen. Fedora Core 15 Gnome Edition: * tested with: ** Firefox 4.0.1 and Adobe Flash Player 11 * Observations: * I had to download the JNLP file and execute it using javaws on the command line. Did expect it would be run more seamlessly cause the IcedTea-Web plug-in is installed ** In Firefox
Re: Apache Rat TLP...?
Agree that the scope of Rat alone is limited. You mean if Rat proposed to graduate as Apache Tools (or even Apache Infrastructure Tools)? Rat could start as the TLP and later become a sub project once other tools graduate and join Apache Tools as sub projects. Makes sense to me as there are a lot of other internally developed tools that are not run as projects. Kalle On Fri, Aug 5, 2011 at 10:44 AM, Robert Burrell Donkin robertburrelldon...@gmail.com wrote: Rat is (now) one of the oldest podlings, and has an unusually high proportion of experience Apache contributors. The community and code are small (perhaps too small) for a top level project (TLP). Rat tools conceptually run downstream from the build in the continuous delivery space, assisting comprehension and verification of assembled source and binary artifacts but. It is natural also to include bindings for various build systems (to catch problems early) and generative repair tools within scope. No suitable TLP exists which is build system and language agnostic. So Rat is in limbo. There seems to be quite a number of existing unsatisfied related use cases eg [1][2] here at Apache. I suspect that with the arrival of OOo, automation is going to become essential and new tools will need to be developed in a variety of languages. In the podling, there is now a rough consensus that graduating to a new TLP would be the right path. Though the community is currently small, it could act as a seed for efforts to address these problems and grow as a home for these tools. But before we start to draw up more detailed proposals, I'd like to take some soundings... Opinions? Robert [1] http://mail-archives.apache.org/mod_mbox/incubator-rat-dev/201106.mbox/%3CBANLkTikiWPDsipDV9wCG8bGFnW=qwbw...@mail.gmail.com%3E [2] http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201107.mbox/%3c4e2f098b.7080...@schor.com%3E - 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: [VOTE] Retire Bluesky Podling
+1 (non-binding) for the retirement proposal. Chen, the vote has nothing to do with whether you manage to release the 4th version or not, and the failure to see that and the failure to understand what Apache and the incubator is about is a testament to why the project should be retired, in my mind. On the other hand, I don't see why Apache is relevant to your release; you can merrily go ahead with releasing it without Apache at all. Kalle On Fri, Jul 1, 2011 at 6:10 PM, Chen Liu liuchen0...@gmail.com wrote: We've already known our failure in ASF. We would not find any excuses for this bed situation. But we just hope one more month to release the 4th version work. We've been advancing Bluesky project and now the 4th version is an integtared system including something about commercial. We're aware of how to advance our development via ASF . Just give us one more month to finish the rest of work. If our work is not very well, pl vote us to retire. 2011/7/2 Craig L Russell craig.russ...@oracle.com +1 for retiring Bluesky I believe that the Bluesky project is well-intentioned but just doesn't belong at Apache. The coders do not use mail lists for discussions of design, code, infrastructure, or other aspects of project management that Apache projects must do. If it didn't happen on the mail lists, it didn't happen. This would tell me that nothing is happening, yet code appears out of thin air. The coders are not committers. There is no path for coders to become committers. Coders appear this year and disappear the next. Despite multiple attempts to teach Bluesky members what it means to be an Apache project, no progress has been made. I think we should wish them well in their new home, wherever that happens to be. Craig On Jul 1, 2011, at 4:14 PM, Benson Margulies wrote: +1 (Binding) On Fri, Jul 1, 2011 at 6:58 PM, Ross Gardler rgard...@opendirective.com wrote: +1 to retire Bluesky (binding) I see no reason for suspending the vote. We've been round this particular merry-go-round many times already. Each time we're told we'll do better. The votes been called lets just move on, the ASF is not the right home for this project for the reasons already discussed. Ross On 28 June 2011 06:49, berndf ber...@apache.org wrote: Hi everyone, this is a vote to retire the Bluesky podling. 3.5 years into incubation, the podling has not made progress in terms of becoming an Apache project. Dev is still done behind closed doors, and developers are changing frequently without notifications on the public lists. Mentors are M.I.A. Reports are often late. No Apache release was every made. There were multiple attempts to reboot the podling (Thanks Luciano!) without much success. So now I'm calling a vote to end Incubation for Bluesky. The vote is open at least until 2011-07-02 12:00 UTC. [] +1, retire Bluesky for the time being [] -0/+0, I'm undecided [] -1, I will step up as a mentor, so let's give it another try Thanks for voting, Bernd --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com --**--** - To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org Craig L Russell Secretary, Apache Software Foundation Chair, OpenJPA PMC c...@apache.org http://db.apache.org/jdo --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Role of Incubator PMC Votes
On Thu, Sep 9, 2010 at 10:51 AM, Greg Stein gst...@gmail.com wrote: On Thu, Sep 9, 2010 at 08:47, James Carman ja...@carmanconsulting.com wrote: I haven't followed this particular issue because it seems like a slamdunk easy thing. If the podling wants to change their name, then fine. Sounds easy enough. I would see no reason for anybody outside the podling to -1 that choice, and might even say that I'd be upset if they did... Sure, the podling can change the name and it can be completely dealt with an internal matter. However, in this case, the name change was put up for a procedural/opinion vote on the incubator general list. As such, I might be upset if people are criticized for giving the wrong vote. Most non-positive votes in the thread are non-binding so the project can ignore them if they like, but if you don't want the opinion, don't put it up for a vote. Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Change name of Lucene Connectors Framework to Apache Connectors Framework
-0.5 (non-binding), I find the proposed name rather confusing Kalle On Wed, Sep 8, 2010 at 5:18 AM, Grant Ingersoll gsing...@apache.org wrote: Hi, After much debate both here and on the connectors mailing list, the LCF community has voted (see http://mail-archives.apache.org/mod_mbox/incubator-connectors-dev/201008.mbox/browser) and would like to officially change our name to be the Apache Connectors Framework. We would like the Incubator PMC to vote to make this official. [] +1 Change the Lucene Connector Framework to the Apache Connector Framework [] 0 Don't care [] -1 Don't change it Since this is a procedural vote (http://www.apache.org/foundation/voting.html), it is a majority rule vote with binding votes coming from IPMC members. The vote is open for 72 hours. Here's my +1 (binding). Thanks, Grant - 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: [VOTE] Apache Shiro graduation as TLP
The vote is now closed and succeeded with 11 binding +1 votes, one non-binding +1 vote and no negative or neutral votes. Binding votes: Chris A. Mattman Craig Russell Martijn Dashorst Gavin McDonald Emmanuel Lecharny Kevan Miller Joe Schaefer J. Daniel Kulp Alan Cabrera Niall Pemberton Noel Bergman Non-binding vote: David Jencks Thank you all, we'll take the result to the Board! Kalle On Mon, Aug 16, 2010 at 11:18 AM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: The Apache Shiro community and the mentors of the project think the project is ready to graduate and is asking for IPMC's recommendation to present the project resolution to the board. The community graduation vote was held and resulted in 27 positive votes with no neutral or negatives (see http://mail-archives.apache.org/mod_mbox/incubator-shiro-user/201008.mbox/%3caanlktinqpvrhjxzjhjbyxpyhovzbyl1wqyw=hjln9...@mail.gmail.com%3e). The proposed resolution is attached to the end of this post and is also available at https://cwiki.apache.org/confluence/display/SHIRO/Graduation+Resolution. See the discussion on the project scope and resolution wording at http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201008.mbox/browser (linking to the index view, see the [DISCUSS] Graduation Resolution thread). For other supporting information, see all of the completed action items at http://svn.apache.org/repos/asf/incubator/shiro/STATUS and clutch status at http://incubator.apache.org/clutch.html. This is a binding IPMC vote for recommending graduation of Apache Shiro with the proposed resolution. [ ] +1 - Recommend graduation of Apache Shiro as a TLP [ ] -1 - Oppose graduation of Apache Shiro as a TLP (if it's the wording in the resolution, we may refine during the vote) This vote will remain open for at least 72 hours. === Establish Apache Shiro Project 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 application security, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Shiro Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Shiro Project be and hereby is responsible for the creation and maintenance of a software project related to application security; and be it further RESOLVED, that the office of Vice President, Shiro 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 Shiro Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Shiro 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 Shiro Project: * Les Hazlewood (lhazlew...@apache.org) * Kalle Korhonen (kao...@apache.org) * Peter Ledbrook (pledbr...@apache.org) * Jeremy Haile (jha...@apache.org) * Craig L Russell (craig.russ...@oracle.com) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Les Hazlewood be and hereby is appointed to the office of Vice President, Shiro, 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 Shiro Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Shiro podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Shiro podling encumbered upon the Apache Incubator PMC are hereafter discharged. === - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Shiro graduation as TLP
Fixed both issues Sebb raised. I doubt either was an impediment to graduation, but keep 'em coming. Oh and the votes too! (I fear our little vote will get lost in experiment/radical chat). Kalle On Tue, Aug 17, 2010 at 4:57 AM, Alan D. Cabrera l...@toolazydogs.com wrote: On Aug 17, 2010, at 4:29 AM, sebb wrote: On 16 August 2010 19:18, Kalle Korhonen kalle.o.korho...@gmail.com wrote: The Apache Shiro community and the mentors of the project think the project is ready to graduate and is asking for IPMC's recommendation to present the project resolution to the board. The community graduation vote was held and resulted in 27 positive votes with no neutral or negatives (see http://mail-archives.apache.org/mod_mbox/incubator-shiro-user/201008.mbox/%3caanlktinqpvrhjxzjhjbyxpyhovzbyl1wqyw=hjln9...@mail.gmail.com%3e). The proposed resolution is attached to the end of this post and is also available at https://cwiki.apache.org/confluence/display/SHIRO/Graduation+Resolution. See the discussion on the project scope and resolution wording at http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201008.mbox/browser (linking to the index view, see the [DISCUSS] Graduation Resolution thread). For other supporting information, see all of the completed action items at http://svn.apache.org/repos/asf/incubator/shiro/STATUS and clutch status at http://incubator.apache.org/clutch.html. This is a binding IPMC vote for recommending graduation of Apache Shiro with the proposed resolution. [ ] +1 - Recommend graduation of Apache Shiro as a TLP [ ] -1 - Oppose graduation of Apache Shiro as a TLP (if it's the wording in the resolution, we may refine during the vote) This vote will remain open for at least 72 hours. Just spotted another issue. The download for Shiro source points to https://repository.apache.org/content/repositories/releases/org/apache/shiro/shiro-root/1.0.0-incubating/ The way I read [1], non-Maven downloads should only be published from the mirrors. [1] http://www.apache.org/dev/release-publishing.html#distribution AIUI, repository.apache.org is the staging area for the official Maven repo at http://repo1.maven.org/maven2/, and is not intended to be used directly for distribution. Good point. Not sure that this is an impediment to graduation. Maybe this point, and others of the same ilk, can have their own threads on the Shiro dev list. Regards, Alan - 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: [VOTE] Apache Shiro graduation as TLP
On Tue, Aug 17, 2010 at 2:09 PM, David Jencks david_jen...@yahoo.com wrote: Dunno if it's exactly documentation but see this from Roy Fielding https://issues.apache.org/jira/browse/LEGAL-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12732740#action_12732740 Based on this I've been advising projects to put the apache LICENSE and and a NOTICE file that covers the actual contents of svn (i.e. not including stuff that is added to binaries as part of the build process) at expected svn checkout roots such as, here, http://svn.apache.org/repos/asf/incubator/shiro/trunk. I don't consider this a barrier to graduation.. +1 Thanks (and for voting too!). Seems that I'm not only one who's been pondering about this. With 17 Maven sub-modules of Shiro seems that we'd need 17 copies of the license files scattered around our source tree. I'm with Stefano there: I do contest the view that svn is the release, but let's leave that for another thread. I'm watching the issue and perhaps I'll restore the LICENSE file on top of the tree. Kalle On Aug 16, 2010, at 12:59 PM, Kalle Korhonen wrote: On Mon, Aug 16, 2010 at 11:43 AM, sebb seb...@gmail.com wrote: Also, just noticed that the SVN tree does not appear to have a copy of the LICENSE file. Normally this is stored alongside the NOTICE file at the top-level, i.e. in http://svn.apache.org/repos/asf/incubator/shiro/trunk/ Looks like the file was deleted in the following commit: r979180 | kaosko | 2010-07-26 07:45:44 +0100 (Mon, 26 Jul 2010) | 1 line Was this intentional? Yes, that was intentional, see the commit message: Follow through on the suggestions given when 1.0.0 release was made. Removed LICENSE.txt as that is added to the source distro via Apache parent pom and its remote resource plugin configuration. Renamed NOTICE.txt to NOTICE so it'll replace the default one. Note that http://www.apache.org/legal/src-headers.html#notice indicates that the LICENSE file needs to be present only in the source distro (and not in svn as Sebb claimed) so we are ok. Also note that ant suggested removing the SoftHashMap and Spring related comments completely from NOTICE file but they are regarding copyrights so look fine to me, will confirm on dev list. If you can point out any documentation that says LICENSE will is required in svn, I'll put it in otherwise I'll avoid the redundancy. In any case, thanks for taking a look! More recently, I also integrated apache-rat (the maven plugin) to our build process. Kalle - 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: [VOTE] Apache Shiro graduation as TLP
While inconclusive, based on the discussion I've restored the LICENSE file at the top of our svn trunk. Please refrain yourself from further comments regarding the LICENSE file in this thread, this is a vote (my fault; I know I should have kept my mouth shut). Kalle On Tue, Aug 17, 2010 at 4:03 PM, David Jencks david_jen...@yahoo.com wrote: On Aug 17, 2010, at 3:24 PM, Kalle Korhonen wrote: On Tue, Aug 17, 2010 at 2:09 PM, David Jencks david_jen...@yahoo.com wrote: Dunno if it's exactly documentation but see this from Roy Fielding https://issues.apache.org/jira/browse/LEGAL-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12732740#action_12732740 Based on this I've been advising projects to put the apache LICENSE and and a NOTICE file that covers the actual contents of svn (i.e. not including stuff that is added to binaries as part of the build process) at expected svn checkout roots such as, here, http://svn.apache.org/repos/asf/incubator/shiro/trunk. I don't consider this a barrier to graduation.. +1 Thanks (and for voting too!). Seems that I'm not only one who's been pondering about this. With 17 Maven sub-modules of Shiro seems that we'd need 17 copies of the license files scattered around our source tree. I'm with Stefano there: I do contest the view that svn is the release, but let's leave that for another thread. Unless your 17 sub-modules are under separate release cycles I wouldn't consider them expected svn checkout roots so one copy of the license at the root would be sufficient. I have somewhat mixed feelings about this policy. On the one hand it's a nuisance to include a LICENSE file in svn where it isn't part of an official apache release, thus possibly not legally required, On the other hand I think that for most projects where there only a few expected svn checkout roots it serves to greatly increase clarity and convenience for non-asf-pros who happen to check out the source tree to have a quick look. So on balance I think its a good idea. If you really want to torture yourself you can look up the discussion of this and related issues on legal-discuss :-) thanks david jencks I'm watching the issue and perhaps I'll restore the LICENSE file on top of the tree. Kalle On Aug 16, 2010, at 12:59 PM, Kalle Korhonen wrote: On Mon, Aug 16, 2010 at 11:43 AM, sebb seb...@gmail.com wrote: Also, just noticed that the SVN tree does not appear to have a copy of the LICENSE file. Normally this is stored alongside the NOTICE file at the top-level, i.e. in http://svn.apache.org/repos/asf/incubator/shiro/trunk/ Looks like the file was deleted in the following commit: r979180 | kaosko | 2010-07-26 07:45:44 +0100 (Mon, 26 Jul 2010) | 1 line Was this intentional? Yes, that was intentional, see the commit message: Follow through on the suggestions given when 1.0.0 release was made. Removed LICENSE.txt as that is added to the source distro via Apache parent pom and its remote resource plugin configuration. Renamed NOTICE.txt to NOTICE so it'll replace the default one. Note that http://www.apache.org/legal/src-headers.html#notice indicates that the LICENSE file needs to be present only in the source distro (and not in svn as Sebb claimed) so we are ok. Also note that ant suggested removing the SoftHashMap and Spring related comments completely from NOTICE file but they are regarding copyrights so look fine to me, will confirm on dev list. If you can point out any documentation that says LICENSE will is required in svn, I'll put it in otherwise I'll avoid the redundancy. In any case, thanks for taking a look! More recently, I also integrated apache-rat (the maven plugin) to our build process. Kalle - 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 - 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
[VOTE] Apache Shiro graduation as TLP
The Apache Shiro community and the mentors of the project think the project is ready to graduate and is asking for IPMC's recommendation to present the project resolution to the board. The community graduation vote was held and resulted in 27 positive votes with no neutral or negatives (see http://mail-archives.apache.org/mod_mbox/incubator-shiro-user/201008.mbox/%3caanlktinqpvrhjxzjhjbyxpyhovzbyl1wqyw=hjln9...@mail.gmail.com%3e). The proposed resolution is attached to the end of this post and is also available at https://cwiki.apache.org/confluence/display/SHIRO/Graduation+Resolution. See the discussion on the project scope and resolution wording at http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201008.mbox/browser (linking to the index view, see the [DISCUSS] Graduation Resolution thread). For other supporting information, see all of the completed action items at http://svn.apache.org/repos/asf/incubator/shiro/STATUS and clutch status at http://incubator.apache.org/clutch.html. This is a binding IPMC vote for recommending graduation of Apache Shiro with the proposed resolution. [ ] +1 - Recommend graduation of Apache Shiro as a TLP [ ] -1 - Oppose graduation of Apache Shiro as a TLP (if it's the wording in the resolution, we may refine during the vote) This vote will remain open for at least 72 hours. === Establish Apache Shiro Project 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 application security, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Shiro Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Shiro Project be and hereby is responsible for the creation and maintenance of a software project related to application security; and be it further RESOLVED, that the office of Vice President, Shiro 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 Shiro Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Shiro 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 Shiro Project: * Les Hazlewood (lhazlew...@apache.org) * Kalle Korhonen (kao...@apache.org) * Peter Ledbrook (pledbr...@apache.org) * Jeremy Haile(jha...@apache.org) * Craig L Russell (craig.russ...@oracle.com) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Les Hazlewood be and hereby is appointed to the office of Vice President, Shiro, 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 Shiro Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Shiro podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Shiro podling encumbered upon the Apache Incubator PMC are hereafter discharged. === - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Shiro graduation as TLP
On Mon, Aug 16, 2010 at 11:33 AM, sebb seb...@gmail.com wrote: On 16 August 2010 19:18, Kalle Korhonen kalle.o.korho...@gmail.com wrote: Some of the incubation stages don't seem to have been completed, at least according to the page: http://incubator.apache.org/projects/shiro.html Perhaps these items have been completed, in which case please could the page be updated accordingly? Uh sorry, we've forgotten the existence of that page - will update. Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Shiro graduation as TLP
On Mon, Aug 16, 2010 at 11:43 AM, sebb seb...@gmail.com wrote: Also, just noticed that the SVN tree does not appear to have a copy of the LICENSE file. Normally this is stored alongside the NOTICE file at the top-level, i.e. in http://svn.apache.org/repos/asf/incubator/shiro/trunk/ Looks like the file was deleted in the following commit: r979180 | kaosko | 2010-07-26 07:45:44 +0100 (Mon, 26 Jul 2010) | 1 line Was this intentional? Yes, that was intentional, see the commit message: Follow through on the suggestions given when 1.0.0 release was made. Removed LICENSE.txt as that is added to the source distro via Apache parent pom and its remote resource plugin configuration. Renamed NOTICE.txt to NOTICE so it'll replace the default one. Note that http://www.apache.org/legal/src-headers.html#notice indicates that the LICENSE file needs to be present only in the source distro (and not in svn as Sebb claimed) so we are ok. Also note that ant suggested removing the SoftHashMap and Spring related comments completely from NOTICE file but they are regarding copyrights so look fine to me, will confirm on dev list. If you can point out any documentation that says LICENSE will is required in svn, I'll put it in otherwise I'll avoid the redundancy. In any case, thanks for taking a look! More recently, I also integrated apache-rat (the maven plugin) to our build process. Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: an experiment
On Mon, Aug 16, 2010 at 6:05 PM, Greg Stein gst...@gmail.com wrote: Your head is in the sand. The Incubator is a broken process. Everybody hates it. Everybody wants to get out of it. Subversion was fortunate in that we had enough support to bully our way through, to route around damage, and to check everything off the list rapidly. Whoever said it before: if we *didn't* have that fortunate fact behind us, then our approach to the ASF would have been very very different. Perhaps it's useful to have some other experiences heard from those who are currently going through the incubation process. Apache Shiro is on the verge of graduation (voting going on right now), I'm a new member of Apache (i.e. not one of the people in the original project proposal) and I don't see much wrong in the current process. We have a small PPMC and there have been a few cases where we've needed to prod the interest of the mentors to gain enough votes but I don't think there's anything broken in that. For the more important votes, we've gotten some -1s from some Apache members we've never heard of before, but negatives need to be and are justified and are typically given for reasons we as new members had missed or hadn't considered at all. I recognize there's a lot of history before our project so I for would give a benefit of doubt for any random drive-bys from disinterested third parties :) I mean, after all, the incubator process is about teaching the Apache way and whatever it is, it's probably not about changing the process to your liking. If I have to beg for a few +1s or reason my way out of -1s, I'll be happy to do that, and hopefully demonstrate our willingness and ability to self govern along way. Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANN] Apache Shiro 1.0.0-incubating Released!
On Tue, Jun 1, 2010 at 4:42 PM, sebb seb...@gmail.com wrote: On 01/06/2010, Les Hazlewood lhazlew...@apache.org wrote: Otherwise we assume the release would have been voted against. The lack of a DISCLAIMER was reported as part of the vote. I don't know why it was not considered blocking. Either you vote or you don't, everything else is considered advisory, you know that. The release packages that most people in practice will use contain -incubating in the file name. I don't know what could be any more explicit. Anyhow, we'll add a file for the next release. Why isn't there a no-frills step-by-step, no room-for-error release checklist that podlings can follow to guarantee that all required criteria are met? It seems like such a checklist would be of the highest priority for the Incubator to ensure that personal interpretation is minimized or eliminated from the release process. Maven (the project) has super clear step-by-step instructions at http://maven.apache.org/developers/release/apache-release.html for releasing with Maven (kudos to Maven guys for that!) which I followed religiously. Maybe you could write another one for Maven-based podling releases but I'm not sure it's worth it. Most of the pain we (Shiro) experienced was with the website - these rules are really not clear and there's a million different competing technologies to put together a project website. Unless incubator starts dictating the technologies to use for a podling website (which I'd be strongly against), I don't see how one could write up a *simple* checklist. It's worth an effort to clarify the http://incubator.apache.org/guides/releasemanagement.html page though. Whatever the technology, I'd much rather improve something existing than whip up yet another semi-official Confluence page. Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Shiro version 1.0.0-incubating
Vote closed and passed, lazy consensus. Binding votes: +1 Ant Elder Non-binding votes: +1 Gerolf Seitz Thank you all. Release promoted, announcements to follow. Kalle On Tue, May 25, 2010 at 3:32 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: This is the first incubator release for Apache Shiro, version 1.0.0-incubating. The release is made following the standard Apache/Maven release process as documented at http://maven.apache.org/developers/release/apache-release.html. This is a lazy consensus vote as we already received 3 binding IPMC +1 votes for the PPMC release vote on shiro-dev. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201005.mbox/%3caanlktik_mke9dwlatmxnzq7kwcdbs3amsu5ulymkp...@mail.gmail.com%3e The issues solved for 1.0.0 (after the project entered Apache incubator): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310950styleName=Htmlversion=12314078 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/shiro/tags/shiro-root-1.0.0-incubating/ Staging repo for binaries: https://repository.apache.org/content/repositories/orgapacheshiro-005/ Staging site: http://incubator.apache.org/shiro/static/1.0.0-incubating/ Project website (just for informational purposes, not to be voted upon): http://incubator.apache.org/shiro/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Lazy consensus, vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Shiro version 1.0.0-incubating
On Wed, May 26, 2010 at 10:14 AM, sebb seb...@gmail.com wrote: It's a bit confusing to have two copies of the NL files in the root of the archive: LICENSE and LICENSE.txt have the same content. NOTICE and NOTICE.txt have significantly different content. LICENSE and NOTICE are not in SVN as far as I can tell, so where do they come from? The ones in our SVN are redundant. LICENSE and NOTICE come via the remote-resources-plugin configuration in Apache parent pom, see http://repo2.maven.org/maven2/org/apache/apache/7/apache-7.pom It would be helpful to include a pointer to the KEYS file (eventually found it at the root of SVN). KEYS file should always be at the root of the svn right? But I do apologize, should have included a link to it in the voting post. Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Shiro version 1.0.0-incubating
This is the first incubator release for Apache Shiro, version 1.0.0-incubating. The release is made following the standard Apache/Maven release process as documented at http://maven.apache.org/developers/release/apache-release.html. This is a lazy consensus vote as we already received 3 binding IPMC +1 votes for the PPMC release vote on shiro-dev. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201005.mbox/%3caanlktik_mke9dwlatmxnzq7kwcdbs3amsu5ulymkp...@mail.gmail.com%3e The issues solved for 1.0.0 (after the project entered Apache incubator): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310950styleName=Htmlversion=12314078 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/shiro/tags/shiro-root-1.0.0-incubating/ Staging repo for binaries: https://repository.apache.org/content/repositories/orgapacheshiro-005/ Staging site: http://incubator.apache.org/shiro/static/1.0.0-incubating/ Project website (just for informational purposes, not to be voted upon): http://incubator.apache.org/shiro/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Lazy consensus, vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Removed from incubator group
Hello, my username kaosko has been removed from incubator group for some reason. I'm a committer in Shiro project, currently in incubator. This happened some weeks ago (caused by the JIRA breach or some restructuring?) and I'm certain I was part of the group before. Les Hazlewood (lhazlewood, also a committer in the same project) is part of the incubator group. Can somebody add me back in? Thanks, Kalle Korhonen (kaosko) -- Forwarded message -- From: Kalle Korhonen kalle.o.korho...@gmail.com Date: Wed, May 12, 2010 at 11:30 PM Subject: Permission issue writing to /www/incubator.apache.org/shiro To: infrastruct...@apache.org Hello, I'm a committer (username kaosko) in Shiro project, currently in incubator. I'm not able to write to /www/incubator.apache.org/shiro anymore, see http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201004.mbox/%3ct2h7281ca711004040810x54fb444ai422bf355a13dc...@mail.gmail.com%3e. I'm sure I used to be able to do this before, and that my primary group was incubator. Now my groups are: [kao...@minotaur:~]$ groups kaosko committers Is this as expected? Should incubator committers be able to directly create/add files in the respective project directories under /www/incubator.apache.org? Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Removed from incubator group
Noel J. Bergman kindly added me back to the group (thanks!), all good now. Kalle On Tue, May 18, 2010 at 2:00 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: Hello, my username kaosko has been removed from incubator group for some reason. I'm a committer in Shiro project, currently in incubator. This happened some weeks ago (caused by the JIRA breach or some restructuring?) and I'm certain I was part of the group before. Les Hazlewood (lhazlewood, also a committer in the same project) is part of the incubator group. Can somebody add me back in? Thanks, Kalle Korhonen (kaosko) -- Forwarded message -- From: Kalle Korhonen kalle.o.korho...@gmail.com Date: Wed, May 12, 2010 at 11:30 PM Subject: Permission issue writing to /www/incubator.apache.org/shiro To: infrastruct...@apache.org Hello, I'm a committer (username kaosko) in Shiro project, currently in incubator. I'm not able to write to /www/incubator.apache.org/shiro anymore, see http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201004.mbox/%3ct2h7281ca711004040810x54fb444ai422bf355a13dc...@mail.gmail.com%3e. I'm sure I used to be able to do this before, and that my primary group was incubator. Now my groups are: [kao...@minotaur:~]$ groups kaosko committers Is this as expected? Should incubator committers be able to directly create/add files in the respective project directories under /www/incubator.apache.org? Kalle - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache JSecurity/Ki Project Rename - Final Vote
+1 Apache Shiro Kalle On Thu, Jun 4, 2009 at 6:45 AM, Les Hazlewood lhazlew...@apache.org wrote: Hi All, This is the final vote for the Apache JSecurity/Ki project's new name between the two proposed finalists. Please vote for only one of the following two (alphabetically-ordered) names: Apache Aseca - relevant letters in Application SECurity Api Apache Shiro - castle in Japanese Voting ends Wednesday June 10th, Midnight (GMT-8) to allow some time after the weekend for additional votes. Thank you for your vote! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
