Re: [DISCUSS] Freemarker Incubation proposal
As we are community over code and I haven't read anything about the history we have with Freemarker, it is probably now the time to mention it. The first response on this proposal was Huh? They want to come to Apache ? The Freemarker community was a fan of trolling the Apache Velocity mailinglists (at least from before 2005 up to 2008 and according to Geir at least from 2000/2001). The 2 names constantly popping up in these threads are Jonathan Revusky and Daniel Dekany. Even though Daniel uses a lot friendlier words, had some useful discussions on the Velocity lists and disapproved of the strong wording Jonathan uses, he was agreeing with the general message expressed in those mails and *active* in these useless threads and even replying to mails Jonathan send. So : - Since Jonathan is the main author of the code, does he agree to the move to Apache ? (as we like to have voluntary code donations) - I would be -1 on him becoming a committer at Apache at this time, if he would turn up. It would need some kind of proof to show that behaviour has improved. His message were exactly the kind of communication that make people run away from projects and we need of code of conduct for. - Daniel - what has changed ? [1] Since you are listed as a committer, it would be nice to know you will not become a toxic member of the Apache community, but a constructive. Mvgr, Martin [1] http://markmail.org/message/mx7bpfd4sflm6yee (the whole thread is typical for the trolling) , more examples simply by searching Jonathan and Daniel's name on the velocity lists. 2015-05-21 15:23 GMT+02:00 Jacopo Cappellato jacopo.cappell...@gmail.com: Hi all, my name is Jacopo Cappellato, I am an ASF member and the PMC chair of Apache OFBiz. As the proposal's champion, I would like to open up a discussion thread on the proposal for Freemarker to join ASF as an incubating project. The proposal is available here: https://wiki.apache.org/incubator/FreemarkerProposal I would like to thank the co-authors Dániel Dékány, David Jones and Jean-Frederic Clere. Thanks in advance for your time! Jacopo Cappellato - 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: PMC chair vs. reorg proposals
+1 Mvgr, Martin 2012/2/5 Jukka Zitting jukka.zitt...@gmail.com: Hi, I find it unfortunate that the PMC chair nominations got turned into a debate about the future of the Incubator, especially when the original reason to consider a new chair were fairly minor issues in timely handling of PMC mechanics. As a fellow PMC chair I think it's troublesome that people seem to expect that a VP title is needed to push forward major changes; it's not. In my opinion the primary role of the PMC chair in discussions like these is to make sure that all opinions are heard and to help reach consensus where none exists. Often the best way to do that is to step back and let the discussion flow before taking a stand. Thus, since Noel is willing to continue as the chairman, I propose that he should do so, possibly with Benson and/or others as delegates to help deal with the volume of day-to-day issues. Meanwhile others who wish to drive the incubation process to new directions, be it inside the Incubator or not, can and should continue to do so. AFAICT none of these proposals require the added authority of a VP title. 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: [Vote] Accept JRS project for incubation
projects. Homogeneous developers -- Since the Java Resource Simulator has been developed to date by American Express, the initial contributors to the project are associated with that corporation, though not all are employees of American Express. They are experienced working in a geographically distributed and diverse team and they have a broad range of experiences with open source, industry standards, emerging technologies and product development. Furthermore, our strong intention is to attract a diverse set of additional committers, beyond the initial contributors and current Apache committers listed below. Reliance on salaried developers - It is expected that, at the beginning, JRS development will occur on both salaried time and on volunteer time, after hours. While there is reliance on developers associated with American Express, through the incubation process, we expect the independent Community to become actively involved in the project. No ties to other Apache products --- JRS currently uses or is planned to use a number of Apache and other open source projects. These have been outlined above. A fascination with the Apache brand --- JRS has been started as a response to real and critical needs of development projects over many years. The originating environment has been IT internal of a non-software company, as such there was/is no need to associate the Apache brand with JRS. We believe that JRS will solve in an elegant and lightweight manner development lifecycle problems and, as such, we are interested in the best way for the project to develop and flourish. We have no interest or intention of productizing JRS for commercial purposes or offering paid services associated with its use; though part of our motivation for pursuing open development of JRS under the ASL is that this will not prevent others from doing so. Scope of the project The scope of the JRS project at ASF would be to continue the product development and would include adding new features and improving performance, scalability, quality, and extensibility. Documentation - Documentation is available on request. See below. Initial source - Initial source code for the project will be granted (see next section) to the ASF on acceptance of this proposal and once granted it will be made publicly available and the normal Incubator IP Clearance process will be followed to approve inclusion of the initial sources in the project source repository. Source and Intellectual Property Submission Plan --- American Express is prepared to submit a code grant and a CCLA and to license all JRS code under the ASL. All rights to the current codebase are owned by American Express. The initial committers have or will all submit ICLAs. External Dependencies -- The current implementation depends on the following components: * XStream- BSD- [WWW] http://xstream.codehaus.org/license.html * JUnit- CPL - [WWW] http://www.opensource.org/licenses/cpl.php * Maven - ASF * Log4J - ASF * J2EE API - CDDL * XPP3 - [WWW] http://www.extreme.indiana.edu/viewcvs/~checkout~/XPP3/java/LICENSE.txt All dependencies have ASL or ASL-compatible licenses. Cryptography - JRS currently makes no direct use of cryptographic functions. Required resources --- Mailing lists * jrs-private (with moderated subscriptions) * jrs-dev * jrs-commits * jrs-user Subversion or CVS repositories - JRS would like to use a Subversion repository: [WWW] https://svn.apache.org/repos/asf/incubator/jrs Issue tracking Since JRS would have its own release cycle, it should have its own JIRA project * Project Name: JRS * Project Key: JRS Initial set of committers --- * Brendan McCarthy (brendan_dot_mccarthy_at_ gorillalogic_dot_com) * Tony Ambrozie (tony_dot_a_dot_ambrozie_at_aexp_dot_com) * Phil Steitz (psteitz_at_apache_dot_org) * Ian Gray (ian_dot_d_dot_gray_at_aexp_dot_com) * Rahul Akolkar (rahul_at_apache_dot_org) * Sebastian Bazley (sebb_at_apache_dot_org) * Martin van den Bemt (mvdb_at_apache_dot_org) * Henri Yandell (bayard_at_apache_dot_org) Affiliations - Tony Ambrozie, Phil Steitz and Ian Gray are employees of American Express. Brendan McCarthy is an employee of Gorilla Logic, working under contract to American Express. The rest are ASF committers working for distinct companies. As individuals, none of the ASF committers have any
Re: [Proposal] Java Resource Simulator (JRS)
gorillalogic_dot_com) * Tony Ambrozie (tony_dot_a_dot_ambrozie_at_aexp_dot_com) * Phil Steitz (psteitz_at_apache_dot_org) * Ian Gray (ian_dot_d_dot_gray_at_aexp_dot_com) * Rahul Akolkar (rahul_at_apache_dot_org) * Sebastian Bazley (sebb_at_apache_dot_org) * Martin van den Bemt (mvdb_at_apache_dot_org) * Henri Yandell (bayard_at_apache_dot_org) Affiliations - Tony Ambrozie, Phil Steitz and Ian Gray are employees of American Express. Brendan McCarthy is an employee of Gorilla Logic, working under contract to American Express. The rest are ASF committers working for distinct companies. As individuals, none of the ASF committers have any contract or employment relationship with American Express. Sponsors - Champion --- * Phil Steitz Nominated Mentors * Phil Steitz * Sebastian Bazley * Martin van den Bemt * Henri Yandell Sponsoring Entity - We are asking the Incubator PMC to sponsor this proposal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator reports due
Did a review just now.. Mvgr, Martin robert burrell donkin wrote: On 6/18/07, William A. Rowe, Jr. [EMAIL PROTECTED] wrote: This is due to board@ with PMC oversight/feedback 12 hours from now. noel is having hardware issues and he's asked me to pull this together so it's likely to be a little late Oversight implies at least three reviewers of each report. we could *really* do with one more reviewer - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [IP CLEARANCE] Petar Tahchiev donation Jakarta Cactus
Have checked it (before I voted) Mvgr, Martin robert burrell donkin wrote: On 6/15/07, Petar Tahchiev [EMAIL PROTECTED] wrote: On 6/11/07, Martin van den Bemt [EMAIL PROTECTED] wrote: snip Ok, I am closing the vote now. Results: Two +1's and no -1's or 0's. The vote passed. fine I want to ask who am I supposed to send this vote in order to proceed with setting up a repository in the incubator and importing my changes in it? :-\ there's nothing more that you need to do here: just the paperwork is managed by the incubator the cactus community will handle the import. drop them a post to the dev list containing a link to this thread and take it from there :-) (martin will probably check in the donated artifact somewhere so that a record exists) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IP CLEARANCE] Petar Tahchiev donation Jakarta Cactus
+1.. Sorry Petar for ignoring you, glad to see you want to get going ! Mvgr, Martin Petar Tahchiev wrote: Hello everybody, My name is Petar Tahchiev I donated a cactus maven2 build system. It is registered under Petar Tahchiev / Representing Self Cactus Maven2 Build System ... http://mamouth.svn.sourceforge.net/svnroot/mamouth/Cactus; - The code is attached to an issue tracker [1] for review as well as in a repository in the sourceforge [2]. - Jakarted voted to accept the codebase. [3] - The ASF secretary recorded the software grant in grants.txt (under above description) - The ip clearance form is attached to this mail. [4] Please check the clearance. The clearance passes by lazy concensus if no -1 votes are cast within the next 72 hours (adjusting timeframe to the discussion that just took place). P.S. This pass is a second attempt. The previous conversation can be found here [4]. [1] http://issues.apache.org/jira/browse/CACTUS-247 [2] http://mamouth.svn.sourceforge.net/svnroot/mamouth/Cactus [3] http://www.mail-archive.com/[EMAIL PROTECTED]/msg08612.html [4] http://marc.info/?l=incubator-generalm=117761896525126w=2 http://marc.info/?l=incubator-generalm=117761896525126w=2 -- Regards, Petar! Karlovo, Bulgaria. Bulgarian medics in Libya are innocent! http://www.nestesami.bg/main/index.php Public PGP Key at: http://keyserver.linux.it/pks/lookup?op=getsearch=0x1A15B53B761500F9 http://keyserver.linux.it/pks/lookup?op=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: To vote or not to vote
I think voting for a mentor is the good thing to do, at least on the dev / ppmc (assuming it is healthy) of the podling. At least that was my condition to be added as a Mentor for Trinidad at that time. I like the group that needs to work with you to make the final call (as a general rule, there can always be exceptions of course) Even though we use the concept of merit heavily, that doesn't mean that merit is always a match with that specific project. OTOH this is also a non issue, since there is rather a shortage of mentors, so there probably will vote down a mentor when they need one :) (not really a reply to your mail, just some thoughts about this) Mvgr, Martin Noel J. Bergman wrote: Cool :) So should we have a vote on ode-dev then? shrug Sometimes I think that we get a bit vote happy. Is this really something that is in need of a vote? E.g., is this a policy decision, karma grant or code release? Does being a Mentor grant any special powers/rights? Is it really just a term for a PMC Member who is actively engaged in the mutual act of mentoring the community? Now, let us say that you have a vote. The result is 6 to 4. Majority, even 60%. But I'd hardly consider that a consensus. On the other hand, if there is a clear consensus, do we always need to explicitly count it? Consider: do we need to vote for a release manager? The answer is no, by the way. We vote for a release, though. We require a community decision on the release, in large measure to protect individuals. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Appoint Niclas Hedhman as Mentor to ODE
+1.. Mvgr, Martin Paul Fremantle wrote: $subject says it all. Here is my +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Apache Wicket from the incubator
+1.. Mvgr, Martin Martijn Dashorst wrote: Dear Incubator, The Wicket podling respectfully requests the Incubator to consider its graduation to a Top Level Project. Please vote on recommending the attached draft board resolution. The vote will end in 72 hours, 1900 hours CET sunday 27-May-2007. [ ] +1 Recommend to the board to establish Apache Wicket [ ] -1 Do not recommend establishing Apache Wicket because... The community vote for proposing the graduation can be found at: http://www.nabble.com/forum/ViewPost.jtp?post=10697484framed=y The Wicket community was already diverse when it entered the incubator, and has grown even more diverse by adding 3 additional members to its core. In the months following the incubation the Wicket community has resolved several licensing issues, and overcame a very drastic change in the future of the project (scrapping a future direction of the framework). During the process of incubation, the PPMC learned how to govern itself, voting in new committers and PPMC members. Mentors offered invaluable advice and assistance in getting the project set up and settled in the Apache infrastructure. Their guidance has helped the project mature and follow Apache community principles even more than it already did. During the incubation the Wicket project has issued one release. The incubator checklist web page for Wicket can be found at: http://incubator.apache.org/projects/wicket.html The proposed resolution for establishing the Apache Wicket project: Establish the Apache Wicket 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, to be known as Apache Wicket Project, related to the creation and maintenance of open source software, grounded in object oriented programming principles, for creating highly dynamic, component oriented web applications for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC) is hereby established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Wicket PMC be and hereby is charged with the creation and maintenance of Apache Wicket; and be it further RESOLVED, that the office of Vice President, Apache Wicket 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 Wicket PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Wicket PMC; 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 Wicket PMC: * Upayavira [EMAIL PROTECTED] * Alex Karasulu [EMAIL PROTECTED] * Sylvain Wallez [EMAIL PROTECTED] * Martijn Dashorst[EMAIL PROTECTED] * Ate Douma [EMAIL PROTECTED] * Eelco Hillenius [EMAIL PROTECTED] * Gwyn Evans [EMAIL PROTECTED] * Jonathan Locke [EMAIL PROTECTED] * Johan Compagner [EMAIL PROTECTED] * Juergen Donnerstag [EMAIL PROTECTED] * Igor Vaynberg [EMAIL PROTECTED] * Matej Knopp [EMAIL PROTECTED] * Janne Hietamäki [EMAIL PROTECTED] * Frank Bille Jensen [EMAIL PROTECTED] * Al Maw [EMAIL PROTECTED] * Jean-Baptiste Quenot[EMAIL PROTECTED] NOW, THEREFORE, BE IT FURTHER RESOLVED, that Martijn Dashorst be appointed to the office of Vice President, Apache Wicket, 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 Apache Wicket Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Wicket podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Wicket podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
Re: Todo or not todo: cc'ing podling-private@ when sending message to private@
I tend to use the private list as the place to look for decisions and actions taken of things that are PMC concerns, so I tend to cc private in most cases. Mvgr, Martin Martijn Dashorst wrote: In the doc's for voting in a new PPMC member [1] it is stated that a message with the vote results should be sent to the [EMAIL PROTECTED] list. Should the PPMC private list be on the CC list? If so, shall I provide a patch to add this to the doc? In more general terms: is it considered good practise to CC both parties with 'official' communication between the private@ and the [EMAIL PROTECTED] Martijn [1] http://incubator.apache.org/guides/ppmc.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: making project decisions with a small number of PMC members
If I am not mistaken there is no relationship with the sponsoring PMC, which in my view needs to change (as you indirectly point out). There are a couple of things : 1) The incubated project doesn't even need to know about the sponsoring project 2) The sponsoring project doesn't even have to know about the project being sponsored (even as VP I was at one point unaware that Jakarta was sponsoring a project in the Incubator) 3) A big bang integration after a project ends up in the sponsoring project, isn't a good start and there probable needs to be a closer defined relationship between the two. Should people on the IPMC also be on the sponsoring PMC ? (assuming the PMC != committers) 4) To give an example : is Brett (in his role of being a mentor) representing the Maven PMC or on a personal basis and is there or should there be a difference between the 2 ? 5) What's the use of having a vote on sponsoring a project in the Incubator if no one is volunteering to represent the sponsoring project ? Sorry for hijacking your question :) Lot's of questions, no time for answers (yet) :) Mvgr, Martin Brett Porter wrote: Hi, Quick question (I hope). I was thinking about what will happen if the NMaven podling would like to add a committer, make a release, etc. Would votes by Maven PMC members (As the sponsoring project) be considered binding in this case, or should we have IPMC members? We currently only have 2 IPMC members on the project, so I was going to ask for an additional mentor anyway, but I feel like the appropriate people to be casting votes should be Maven PMC folk. Thoughts? Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IP CLEARANCE] Petar Tahchiev donation Jakarta Cactus
Please take this question back to the cactus list to discuss it there. The diff of what currently is in Cactus and the donation is not in scope of the ip clearance. Mvgr, Martin Dion Gillard wrote: My vote is not binding, but I think there is still isn't enough clarity on the donation for me to do anything other than vote -1. I can't tell so far what the full set of changes in the grant are. My last question on what the refactoring of the source tree entails have gone unanswered, and hence can't really do a full check. Reading between the lines on the viewvc svn log view there is more than a refactoring of source being donated (e.g. new mojos / m2 integration, new docs etc). Is there any way we can view the changes other than reading the entire svn log? I think we've fixed some licensing issues, which is good. On 4/23/07, Martin van den Bemt [EMAIL PROTECTED] wrote: Hi everyone, Petar Tahchiev donated a cactus related codebase to Jakarta Cactus. Registered under Petar Tahchiev / Representing Self Cactus Maven2 Build System ... http://mamouth.svn.sourceforge.net/svnroot/mamouth/Cactus; - The code is not attached to an issue tracker for review to make it possible for Petar to continue development, awaiting the ip clearance. [1] - Jakarted voted to accept the codebase. [2] - The ASF secretary recorded the software grant in grants.txt (under above description) - The ip clearance form was added to the Incubator site [3] Please check the clearance. The clearance passes by lazy concensus if no -1 votes are cast within the next 72 hours (adjusting timeframe to the discussion that just took place). Mvgr, Martin [1] http://mamouth.svn.sourceforge.net/svnroot/mamouth/Cactus [2] http://www.mail-archive.com/[EMAIL PROTECTED]/msg08612.html [3] http://incubator.apache.org/ip-clearance/jakarta-cactus-tahchiev.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IP CLEARANCE] Petar Tahchiev donation Jakarta Cactus
robert burrell donkin wrote: On 4/23/07, Martin van den Bemt [EMAIL PROTECTED] wrote: What happened here ? Not that this doesn't need fixing, but this code donation is hardly a new event (was announced on February 3rd on the PMC list and the grant was discussed numerous times on general. should be easy enough to fix: just take a tar ball of the latest revision in svn (taking a note) and checksum or GPG sign it. attach the signature to the grant and commit the tar into svn. development can continue. submit patches for revisions to JIRA. once you have a CCLA for petar, commit them. Petar is already a committer (and paperwork was handled over month ago). Probably best to let Jim decide if he needs new paperwork for this (I assume we are not supposed to change the grants.txt ourselves, at least it would make feel quite uneasy). Resending the grant seems a waste of paper and unnecessary in this case. Would have been nice to caught this earlier. +1 sorry - been a little overstretched recently :-/ It's not just your responsibility and health comes first :) See you on Sunday.. Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IP CLEARANCE] Petar Tahchiev donation Jakarta Cactus
Dion Gillard wrote: On 4/24/07, Martin van den Bemt [EMAIL PROTECTED] wrote: What happened here ? Not that this doesn't need fixing, but this code donation is hardly a new event (was announced on February 3rd on the PMC list and the grant was discussed numerous times on general. I don't know who discussed it previously, but this is the first time it caught my eye. Sorry i missed the initial discussion. It was never discussed, my mail about that didn't get a response (besides me saying I was going ahead with what I planned) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IP CLEARANCE] Petar Tahchiev donation Jakarta Cactus
What happened here ? Not that this doesn't need fixing, but this code donation is hardly a new event (was announced on February 3rd on the PMC list and the grant was discussed numerous times on general. Would have been nice to caught this earlier. Mvgr, Martin robert burrell donkin wrote: On 4/23/07, Dion Gillard [EMAIL PROTECTED] wrote: On 4/23/07, Petar Tahchiev [EMAIL PROTECTED] wrote: snip Dion hi, I was also wondering how to fill in the software grant, yeh - the documentation isn't great but please feel free to ask: we're here to help so I wrote the donation as the Cactus Maven2 Build system and the whole repository strucure on http://mamouth.svn.sourceforge.net/svnroot/mamouth/Cactus; But you are right, I didn't mention any revision number, and I guess that is my mistake :-(. It's not a mistake, and please don't get me wrong, I'd really like to get a M2 build system for cactus in place, +1 but we just need to dot the i's and cross the t's when dealing with legal stuff like code donations and licensing. +1 - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[IP CLEARANCE] Petar Tahchiev donation Jakarta Cactus
Hi everyone, Petar Tahchiev donated a cactus related codebase to Jakarta Cactus. Registered under Petar Tahchiev / Representing Self Cactus Maven2 Build System ... http://mamouth.svn.sourceforge.net/svnroot/mamouth/Cactus; - The code is not attached to an issue tracker for review to make it possible for Petar to continue development, awaiting the ip clearance. [1] - Jakarted voted to accept the codebase. [2] - The ASF secretary recorded the software grant in grants.txt (under above description) - The ip clearance form was added to the Incubator site [3] Please check the clearance. The clearance passes by lazy concensus if no -1 votes are cast within the next 72 hours (adjusting timeframe to the discussion that just took place). Mvgr, Martin [1] http://mamouth.svn.sourceforge.net/svnroot/mamouth/Cactus [2] http://www.mail-archive.com/[EMAIL PROTECTED]/msg08612.html [3] http://incubator.apache.org/ip-clearance/jakarta-cactus-tahchiev.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] Graduate Trinidad (to an Apache MyFaces subproject)
+1 (mentor) Mvgr, Martin Matthias Wessendorf wrote: Incubator PMC, The Trinidad community believes that Trinidad is ready for graduation, as evidenced by this vote (see [1]). We would like to initiate a vote to graduate to be a subproject of the Apache MyFaces project. There was a vote on the MyFaces dev list, on which the MyFaces PMC voted to accept Trinidad as its subproject, when it graduates from the Apache Incubator (12 binding votes from MyFaces PMC) (see [2]). For additional information, the status file is here: http://incubator.apache.org/projects/adffaces.html Please cast your votes -Matthias [1] http://tinyurl.com/29hz5p [2] http://tinyurl.com/yntwh6 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Formally retired the Wadi project
+1. Mvgr, Martin Noel J. Bergman wrote: Brian McCallister wrote: I think wadi withdrew from incubation. It seems alive here: http://wadi.codehaus.org/ Correct. +1 to formally retire it. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ApacheCon] who arrives when in Amsterdam
And people who want to stay in Amsterdam can also party all night.. See http://www.koninginnedagamsterdam.nl/?en for more info (yeah, Amsterdam has an English page :) Mvgr, Martin Eelco Hillenius wrote: It might be good to know that on 30th April, there is Queensday (Dutch guys know how to celebrate... :)) It might be a little bit too much flag waving for tourist, but in general if the weather is nice, it can be a fun day. Be warned though, Amsterdam will be *very* busy. Also good to know for the people ariving the day before (or earlier) is that traditionally there is a big party the night before in The Hague (Koninginnenach). I'm thinking about going there, so if you're thinking about it, send me a note or mark on that WIKI and maybe we can hook up. Their web site sucks (Dutch only) but can be found here: http://www.koninginnenach.nl/2007/index1.htm. There's trains running every hour between The Hague and Amsterdam during the night. Anyway, thanks for creating that page, Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] RCF proposal (was: [Proposal] RCF - a rich component library for JSF)
+1 (binding) Mvgr, Martin Omar Tazi wrote: Hi, Based on a positive initial feedback we are calling a vote on the RCF contribution (see proposal below). This proposal is for the donation of a rich component library for the JavaServer Faces technology to the Apache Software Foundation. The live version of the proposal is available at: http://wiki.apache.org/incubator/RCFProposal A vote was held on the Apache MyFaces dev list and we got 15 +1 votes (13 binding) therefore Apache MyFaces is proposed as the sponsoring entity/project. The Champion for the RCF proposal is Manfred Geiler (manolito at apache dot org) and the three mentors are Martin van den Bemt (mvdb at apache dot org), Carsten Ziegeler (cziegeler at apache dot org), and Henning Schmiedehausen (henning at apache dot org). Please cast your votes. Thanks, Omar Tazi - Omar Tazi Chief Open Source Evangelist SOA Evangelist Middleware and Tools Oracle Corporation Work: (650) 506-3216 Cell: (408) 656-5354 Email: [EMAIL PROTECTED] Blog: http://otazi.blogspot.com = RCF, a rich component library for JSF = Abstract -- RCF is a rich (Ajax-style) component set for the JavaServer Faces(tm) 1.2 technology. . Proposal RCF is an Ajax-based component library for the JavaServer Faces technology. RCF comes with very high quality components, and skinning (CSS-based) capabilities. RCF features include: file upload support, client-side conversion and validation, a complete Ajax-integration, data tables, hierarchical tables, color/date pickers, menu tabs/buttons, wizards, popups, toolbars, toolboxes, internationalization and accessibility. This project starts with more than 100 components which have already been documented and thoroughly tested. RCF stands for Rich Client Framework and it means that web applications, using this component set look very similar to a real, native desktop application. The name for this project can be a subject to change. RCF depends on some artifacts, provided by the Apache Trinidad project, such as framework features or Apache Maven plug-ins. Background -- The development of RCF started in 2005 at Oracle Corporation. With the advent of Ajax and requirements for highly interactive rich user experience, Oracle decided to implement a rich/Ajax-style JSF component set. The goal was to advance the already existing ADF Faces product, donated to the ASF in early 2006 (Apache Trinidad). When the development of RCF started, there wasn't any JSF component set that provided similar richness to the user. The RCF components run on any JSF 1.2 compliant implementation. RCF is based on some internal features of the Apache Trinidad project. The JavaServer Faces technology is a key technology for the RCF component set, since RCF requires JSF as its runtime environment. Oracle has a large commitment to both open source and open standards. This proposal illustrates Oracle's commitment to the success of the JSF standard and supporting the open source community by providing a rich component set under a liberal license, the Apache 2.0 license. Rationale - The project is interested in moving to Apache for the following reasons: To provide Apache-licensed implementation of a full-blown Ajax-based JSF component set, to become better integrated with the MyFaces and Shale initiatives, and to build a strong vendor-neutral community that will outlast any one person's or company's participation. Initial Goals - The initial goals of the proposed project are: * Viable community around the RCF code base * Active relationships and possible cooperation with related projects and communities, such as Apache MyFaces (and its subprojects) or Apache Trinidad. Current Status == Meritocracy --- All the initial committers are familiar with the meritocracy principles of Apache, and have already worked on the various source code bases. Some of the initial committers also have experience, undergoing the Apache incubation process. We will follow the normal meritocracy rules also with other potential contributors. Community - The Apache MyFaces project, the Apache Trinidad podling and the JavaServer Faces standard hold great promise. A fully Ajax-based set of user interface components will significantly accelerate their adoption. We strongly believe that RCF will gather significant momentum and enough developers to build a vibrant community of users and contributors. Core Developers --- Four of the initial committers are Oracle employees and all are committers on the Apache Trinidad podling. One of them is a committer at Apache MyFaces and Apache Shale. Four of the initial committers are committers on the Apache MyFaces
Re: Ratifying lots of artifacts was(Re: [VOTE] Ratify the release of Apache Wicket 1.3.0-incubating-alpha)
Maybe cool to give it some time at the hackathon ? Don't if Martijn is going to be there ? Mvgr, Martin robert burrell donkin wrote: On 4/1/07, Martijn Dashorst [EMAIL PROTECTED] wrote: We appreciate the effort! i'm very sad to say that i'm afraid that i might not get the cycle's i hoped this week :-/ The maven repo can of course be retrieved by logging on to p.a.o and creating a tar ball (or I can make one available if that is needed). Would some ant script be of any help? help of any kind would be appreciated! code, design or ideas all welcomed :-) what i had in mind was a spider that crawled down the links then downloaded everything. sounds like something that shouldn't be too hard in either groovy or python. i'd like to create something that could be reused easily by release manager to check the artifacts that had been uploaded. however, i see now that it would probably be easier just to tar up the directories and download. (seems a little less elegant but would save time.) what did you have in mind? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] [RETRY] approve the release of Trinidad's Core (1.0.0-incubating)
+1... Mvgr, Martin Matthias Wessendorf wrote: Dear Incubator PMC Several issues were found by Robert, with the previous release files and have been resolved: 1.) bad signatures for trinidad-api-1.0.0-incubating.jar and trinidad-impl-1.0.0-incubating.jar - Resolution: Update to newer GPG Maven Plugin. A verify looks good: gpg: Signature made Wed Mar 21 07:21:31 2007 WEST using DSA key ID C2062385 gpg: Good signature from Matthias Wessendorf [EMAIL PROTECTED] 2.) missing signature for trinidad-api-1.0.0-incubating-tests.jar and trinidad-impl-1.0.0-incubating-tests.jar - Resolution: Update to newer versions of GPG Maven Plugin. A verify looks good, too. 3.) missing LICENSE, NOTICE and DISCLAIMER in the following files: *trinidad-api-1.0.0-incubating-javadoc.jar *trinidad-api-1.0.0-incubating-tests.jar *trinidad-impl-1.0.0-incubating-javadoc.jar *trinidad-impl-1.0.0-incubating-tests.jar - Resolution: Update to newer version of Remote-Resource-Plugin. 4.) trinidad-1.0.0-incubating-example.zip is missing DISCLAIMER - Resolution: added missing file, to be included by the assembly 5.) Missing license header in: http://svn.apache.org/repos/asf/incubator/adffaces/trunk/trinidad/trinidad-impl/src/main/java/org/apache/myfaces/trinidadinternal/config/upload/UploadRequestWrapper.java - Resolution: added missing header 6.) In the trindad-impl-1.0.0-incubating-sources RAT reveals that there are lots of javascript files in META-INF/adf/jsLibs/ and some configuration files in META-INF without headers. are these generated? -Answer: Yes, some are generated and some are obfuscated, during build. The whole point of obfuscating is to eliminate unnecessary content in our downloads. (when sending the JavaScript files to the client/browser). -- New versions of the release files can be found at: http://people.apache.org/~matzew/stage_trin_core/(maven2 staging repo) http://people.apache.org/~matzew/dist_trin_core/ (the distribution) Please cast your votes: [ ] +1 Release is approved [ ] -1 Veto the release (provide specific comments) Thanks, Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Killing the incubator m2 repository
Let's then at least *mirror* the thing to other (maven) repo's.. Mvgr, Martin Noel J. Bergman wrote: We've discussed this many times before, and so far the consensus has been to not conflate the Incubator artifacts with regular ASF artifacts. I am still -1 to conflating ASF artifacts with incubator artifacts, but that's just my view. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] approve the release of Trinidad's Maven plugins (1.0.0-incubating)
Can someone please have a look, we are still one vote short.. Mvgr, Martin Matthias Wessendorf wrote: The Trinidad community voted to release the the maven plugins as a 1.0.0-incubating release. These plugins are required for the maven build of the core code of the Trinidad Podling. To fulfill the incubator guides, we like to ask you guys, the Incubator PMC, for a permission to release those maven plugins. There were seven +1 votes and the vote has been tracked at [1]. (5 binding) The plugins are documented at [2] and our release notes inculde the bugs that have been addressed ([3]). The plugins are available as source and bin inside the following m2 staging repo (see [4]). Thanks Matthias [1] http://tinyurl.com/3dpa5g [2] http://incubator.apache.org/adffaces/plugins/index.html [3] http://wiki.apache.org/myfaces/ADF_Faces/plugins_release_1_0_0-incubating [4] http://people.apache.org/~matzew/stage/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [discussion] Graduating a subproject
William A. Rowe, Jr. wrote: The reason to approach the existing PMC first, it seems to me, would be to make sure the graduating project meets the standards and criteria of the PMC already. Isn't this the job of the mentors/champions to make sure it is up to those standards ? If it does not, the podling could accept the list of issues that PMC identifies, or the podling could change its focus to become it's own TLP or a subproject of a different TLP. But the sanity check of the accepting PMC makes alot of sense before the incubator PMC is asked if everything's complete to their satisfaction. We can't graduate a subproject without it's TLP home accepting it. The vote is on the fact that the project is ready to graduate, according to documentation at least, if that doesn't reflect reality, we need to fix the documentation. Effectively the only party to allow graduation of a project is the incubator and what happens after that is up to the accepting project or the board (in case of TLP) and as fas as I understood the mentors and champions will be there to help out the project until the PMC / Board has voted to accept the project. Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[SITE] Legal section in Incubation policy.
Hi everyone, On the http://incubator.apache.org/incubation/Incubation_Policy.html#Exiting+the+Incubator page there is a Legal item with the content of : No non ASL or ASL compatbile dependencies in the code base Which kind of reads weird to me, it would probably read better as No non ASL or *non* ASL compatbile dependencies in the code base I know what was meant, but if you just read it it looks like you shouldn't have ASL compatible dependencies :) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Roller graduation
+1.. Mvgr, Martin Dave wrote: OK, let's try this again. The Roller community believes that Roller is ready for graduation, as evidenced by this vote: http://mail-archives.apache.org/mod_mbox/incubator-roller-dev/200702.mbox/browser We would like to initiate a vote to graduate to a top level project. We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting. For additional information, the Roller status file is here: http://incubator.apache.org/projects/roller.html Thanks for your consideration. Please commence voting... - Dave Here is the resolution: https://svn.apache.org/repos/asf/incubator/roller/trunk/tlp-resolution.txt Establish the Apache Roller 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 the Roller blog server, 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 Roller Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Roller Project be and hereby is responsible for the creation and maintenance of open-source software related to the Roller blog server; and be it further RESOLVED, that the office of Vice President, Roller 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 Roller Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Roller 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 Roller Project: * Anil Gangolli [EMAIL PROTECTED] * Allen Gilliland [EMAIL PROTECTED] * Dave Johnson[EMAIL PROTECTED] * Matt Raible [EMAIL PROTECTED] * Craig Russell [EMAIL PROTECTED] * Matthew Schmidt [EMAIL PROTECTED] * Elias Torres[EMAIL PROTECTED] * Henri Yandell [EMAIL PROTECTED] NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Johnson be appointed to the office of Vice President, Roller, 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 Roller Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Roller Project; and be it further RESOLVED, that the initial Apache Roller Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Roller podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Roller podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] Incubating Project Policy
I am +1 on this and the main reason for this is that people that become committers through the incubator don't necessarily have any experience with apache projects and how issues like this are normally handled. As a side effect it gives us the option to link to this policy in case something like this would happen in non incubating projects. The only thing that would be nice to add to the policy is a more clear description of why this policy is there. It's often better to say why things are in place, people can also apply this knowledge to other scenario's that they might encounter. Mvgr, Martin William A. Rowe, Jr. wrote: I believe many projects practice this policy, although it's unwritten, and perhaps there are others who don't (and probably deserve some scrutiny to determine if it's helpful or harmful). I'm proposing the following policy become explicit across the incubator; Where the project policy permits commit-then-review contributions to its Subversion repository, committers may commit code they personally authored, or with proper attribution, commit patches posted on the project's mailing list or posted to the project's bug tracking system (Jira/Bugzilla). No third-party code (beyond bugzilla and mailing list submissions) may be directly committed without first posing the submission to the mailing list. This goes for submissions by associates who are unaffiliated with the project, private correspondence to a committer, and third party open source code which is otherwise compatible with the Apache Software License. Where the project's policy is review-then-commit, there truly is no change to their current practice. All of the above cases are subject to review first on the mailing list. I believe the policy would directly address not only concerns w.r.t. the Heraldry project, but several prior issues and those that will still pop up over the horizon. Votes? +1 here. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Change to Board reporting process
Noel J. Bergman wrote: Justin Erenkrantz wrote: For example, rather than close the cat-herding the weekend before the report is due (and, factually, finishing herding tardy projects the day that the report is filed), we could set a cut-off of the second Monday of each month, or similarly appropriate date, and give the PMC a week to review and approve the report before it is submitted to the Board. I assume that vote would just be about the reports submitted by podlings, not your personal notes add to the report ? The latter shouldn't be subject to votes in my opinion.. Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Release request] Trinidad podling maven2 plugins
Looks better.. Although a couple of things : - No reference to any license in the pom (and therefor not on the generated site). It's (at least for me) a piece of vital data. I even heard talk about tooling around that specific metadata, to be able to detect eg unacceptable licenses. (probably adding the license section to the plugins parent pom will do) - javacc link is now https://javacc.dev.java.net - Probably the INCUBATOR_NOTICE.txt should be included too. - Also nice would be the tag (and with lack thereof) the revision number of what is going to be released) It would make things easier to start the thread with [VOTE] (which is convention) and stating the version to be released in the title.. Mvgr, Martin Matthias Wessendorf wrote: Hi Daniel, thanks for your vote, see inline On 1/15/07, Daniel Kulp [EMAIL PROTECTED] wrote: -1 (non-binding) Issues: 1) We shouldnt' be voting on SNAPSHOT's. We need to be voting on the final artifacts that will be put in the non-snapshot repository. is that new ? My understanding is that a vote is held on a snapshot and when it passes it will be deployed as non-snapshot to a non-snap repo 2) The -sources jars do not have the proper NOTICE, DISCLAIMER, and LICENSE files in them. old source jars, changed 3) Nothing is signed. .asc files now available 4) All the sources in the sources jar are using the old style Apache header with copyright date and no mention of the NOTICE file. See: http://www.apache.org/legal/src-headers.html#faq changed the headers 5) I think not having a version number in there may cause long term issues. (Maven expert want to jump in here?) I usually expect the version to be of the form: #.#[.#]-qualifier with the qualifier in your case being incubator-m1. I think that has already been discussed, that a incubator-m1 is ok I think that we should use a *real* qualifier like 1.0.0, after a project is out of incubation. I hope I satisfied your concerns. thanks for pointing that out! -M Dan On Monday 15 January 2007 16:24, Matthias Wessendorf wrote: Hi all, the Trinidad community voted on and approved to release the the maven2 plugins as a milestone1 release. These plugins are required for the maven2 build of the core code of the Trinidad Podling. To fulfill the incubator guides, we like to ask you guys, the Incubator PMC, for a permission to release those maven plugins. The vote has been tracked at [1], see it for the results. (three binding +1 and one non-binding +1) The plugins are documented at [2] and our release notes inculde the bugs that have been addressed ([3]). The plugins are available as source and bin inside the incubator m2 repo (see [4]). Thanks Matthias [1] http://mail-archives.apache.org/mod_mbox/incubator-adffaces-dev/200701.mbox /ajax/[EMAIL PROTECTED] [2] http://incubator.apache.org/adffaces/plugins/index.html [3] http://wiki.apache.org/myfaces/ADF_Faces/plugins_release_candidate_m1 [4] http://people.apache.org/repo/m2-incubating-repository/org/apache/myfaces/t rinidadbuild/ -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] graduate Solr to Lucene
+1.. Mvgr, Martin Yonik Seeley wrote: The Solr community has voted and believes Solr is ready for graduation from the Incubator and has met all incubation requirements, and the Lucene PMC has voted to accept Solr. The Solr podling is therefore requesting to graduate from the Incubator to become an Apache Lucene subproject. Please send in your +1/0/-1 to approve/abstain/disapprove. References: Lucene PMC Vote on it's private list: Message-ID: [EMAIL PROTECTED] Solr community vote: http://mail-archives.apache.org/mod_mbox/lucene-solr-dev/200701.mbox/[EMAIL PROTECTED] The project status for Solr is at: http://incubator.apache.org/projects/solr.html The Solr home page is at: http://incubator.apache.org/solr/ -Yonik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: clarification on SF license and sandboxes
If I am not mistaken, if it is a patch it is already handles by the apache license itself. If it isn't a patch, I think it's best to ask for the granting specifically.. Mvgr, Martin kelvin goodson wrote: Can anyone tell me if it's OK to put code into a sandbox that has been attached to a JIRA without granting ASF license? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release ? (was Re: [Release request] Trinidad podling maven2 plugins)
Became binding yesterday evening :) Mvgr, Martin Matthias Wessendorf wrote: Hi, I am just wondering if there is anything new from here. Is the vote of Martin now binding or not ? If not, I guess we are not allowed to make a release. If so, that would be a pity, because we all (the Trinidad podling) like to go the next step and if I read the Harmony releated emails right, creating a release is step that a podling should/must do. We need this plugins-release to work on the core-release, since it *heavily* depends on that plugins stuff. So what to do, that there is more attention, when we try to get a first m1 release of our plugins out ? Thanks, Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release ? (was Re: [Release request] Trinidad podling maven2 plugins)
Matthias Wessendorf wrote: Hi Congrats to you Martin to be a IPMC member. So we now can move forward w/ pushing that release out? Post a vote result and start pushing :) But I am still wondering about the attention on this. Is it just a matter of time and the point, that not really everybody is using JSF for web apps ? I don't use Trinidad myself (or JSF for that matter), but since you guys appeared on my radar last year I actively monitor all myfaces (related) lists. The lack of attention you are getting on the incubator list could also be viewed from a positive side : you are, as a project, handling yourselves pretty well, although the lack of member attention also holds you back quite a lot (lack of mentors in this case). On the website it just stated Craig, even though you said Manfred is also a Mentor/Champion. If it is useful for the project, you can add me as a mentor, but I guess you best have a vote about that on the PPMC list. Mvgr, Martin Thanks! Matthias On 10/27/06, Martin van den Bemt [EMAIL PROTECTED] wrote: Became binding yesterday evening :) Mvgr, Martin Matthias Wessendorf wrote: Hi, I am just wondering if there is anything new from here. Is the vote of Martin now binding or not ? If not, I guess we are not allowed to make a release. If so, that would be a pity, because we all (the Trinidad podling) like to go the next step and if I read the Harmony releated emails right, creating a release is step that a podling should/must do. We need this plugins-release to work on the core-release, since it *heavily* depends on that plugins stuff. So what to do, that there is more attention, when we try to get a first m1 release of our plugins out ? Thanks, Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release ? (was Re: [Release request] Trinidad podling maven2 plugins)
Not being noticed doesn't mean you are doing a bad job :) I tried to find some info about adding a mentor, but couldn't find anything specific, but I guess just a notification after to the vote to the general should do it (assuming I get voted as a mentor that is) Mvgr, Martin Matthias Wessendorf wrote: I don't use Trinidad myself (or JSF for that matter), but since you guys appeared on my radar last year I actively monitor all myfaces (related) lists. The lack of attention you are getting on the incubator list could also be viewed from a positive side : you are, as a project, handling yourselves pretty well, although the lack of member attention also holds you back quite a lot (lack of mentors in this case). On the website it just stated Craig, even though you said Manfred is also a Mentor/Champion. If it is useful for the project, you can add me as a mentor, but I guess you best have a vote about that on the PPMC list. Yes, the original proposal had Manfred as a Champion. Craig is Mentor. I am pretty fine with adding you as a mentor. So I now start a vote on private / PPMC list. Do we need an approval for that from IPMC too, I think so. Thanks, also for pointing out the positive view point :) -Matthias Mvgr, Martin Thanks! Matthias On 10/27/06, Martin van den Bemt [EMAIL PROTECTED] wrote: Became binding yesterday evening :) Mvgr, Martin Matthias Wessendorf wrote: Hi, I am just wondering if there is anything new from here. Is the vote of Martin now binding or not ? If not, I guess we are not allowed to make a release. If so, that would be a pity, because we all (the Trinidad podling) like to go the next step and if I read the Harmony releated emails right, creating a release is step that a podling should/must do. We need this plugins-release to work on the core-release, since it *heavily* depends on that plugins stuff. So what to do, that there is more attention, when we try to get a first m1 release of our plugins out ? Thanks, Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Release request] Trinidad podling maven2 plugins
You need to be part of the incubator PMC to have a binding vote. Every member can request to do so (which I did), but still waiting for the approval.. Mvgr, Martin Matthias Wessendorf wrote: To summarize there are three votes and that from Martin is not binding, as far as I understand it. Only Incubator PMC, right ? Or member is allowed to vote (binding) too? Thanks, Matthias On 10/14/06, Craig McClanahan [EMAIL PROTECTED] wrote: +1 (binding) on the revised plugins that include the license and notice files. Craig On 9/26/06, Matthias Wessendorf [EMAIL PROTECTED] wrote: The Trinidad community voted on and approved to release the the maven2 plugins as a milestone1 release. These plugins are required for the maven2 build of the core code of the Trinidad Podling. To fulfill the incubator guides, we like to ask you guys, the Incubator PMC, for a permission to release those maven plugins. The vote has been tracked at [1], see it for the results. (three binding +1 and one non-binding +1) The plugins are documented at [2] and our release notes inculde the bugs that have been addressed ([3]). The plugins are available as source and bin inside the incubator m2 repo (see [4]). Thanks Matthias [1] http://mail-archives.apache.org/mod_mbox/incubator-adffaces-dev/200608.mbox/ajax/[EMAIL PROTECTED] [2] http://incubator.apache.org/adffaces/plugins/index.html [3] http://wiki.apache.org/myfaces/ADF_Faces/plugins_release_candidate_m1 [4] http://people.apache.org/repo/m2-incubating-repository/org/apache/myfaces/trinidadbuild/ -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Glasgow - new name proposal
There is even a song about that :) Mvgr, Martin Thomas Dudziak wrote: On Aug 9, 2006, at 1:06 PM, Rafael Schloming wrote: How about Qpid? It could mean Queuing Protocol for Information Delivery or something like that. or Qupid Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] NOMINATION: Craig Russell
The vote was public on the roller-dev list.. Mvgr, Martin Matthias Wessendorf wrote: It's a good thing to notify [EMAIL PROTECTED]; I think the vote was not public, isn't it ? Maybe we should put it to the guide lines; that for non-public votes the result shouldn't posted only only the *involved* group's list; also to [EMAIL PROTECTED] @Craig: congrats! -Matthias On 8/3/06, Henri Yandell [EMAIL PROTECTED] wrote: Notifying [EMAIL PROTECTED] of the vote at Roller for Craig Russell to have karma. +1s from: Dave Johnson Allen Gilliland Anil Gangolli Matt Raible Elias Torres Henri Yandell (PMC) Ted Husted (PMC) Noel Bergman (PMC) Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Incubate Wicket
+1 :) And to second Leo, nice to see some more Dutch people :) Mvgr, Martin Upayavira wrote: The Wicket developers (http://wicket.sourceforge.net) have expressed a desire to incubate their project within the ASF. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Commit mails..
Hi everyone, Yesterdat I fixed a type in the link to the Agila website, but the commits never turned up in the commit maillist. Could it be that it is still in the mod queue ? Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Use of Incubating Project Names without mentioning Incubator?
Would probably also be a good idea to fix the tuscany page itself..It mentions that it is in the incubator, but the page title and header is Apache Tuscany.. Mvgr, Martin Mike Edwards wrote: Dion, You're right. It should mention Incubator. I apologise for this oversight and I'll get it fixed. Yours, Mike. PS I didn't write it! ;-) Dion Gillard wrote: Are documents like https://www14.software.ibm.com/iwm/web/cc/earlyprograms/websphere/soawas61/ supposed to mention that a project is in the incubator? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] CeltiXfire Project Proposal
+1.. Mvgr, Martin Jason van Zyl wrote: Hi, There has been plenty of discussion around the CeltiXfire proposal, we feel that all the issues forwarded have been addressed, and we would now like to officially propose CeltiXfire to the Incubator for consideration. The proposal can be found in the Incubator wiki here: http://wiki.apache.org/incubator/CeltiXfireProposal I am an enthusiastic +1 :-) Thanks, Jason van Zyl [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mentors - the more, the merrier? [WAS Re: [VOTE] Accept Heraldry into the Incubator]
+1.. Mvgr, Martin robert burrell donkin wrote: On 7/11/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote: snip (And I'll note now that I'm interested in participating, although can't commit the time to be a mentor right now.) this seems like a good opportunity to reintroduce an existing issue ( http://mail-archives.apache.org/mod_mbox/incubator-general/200607.mbox/[EMAIL PROTECTED]) under a better heading :-) the incubator seems to be moving to favouring more mentors. this works better in many ways: it gives an initial ppmc a builtin quruom and provides better oversight. the role of a solo mentor has traditionally been difficult and has consumed a lot of energy. multiple mentors would allow wider participation (without some of the current worries about mentors becoming overstretched by working on too many projects). but this approach may lead to problems if none of the mentors actually have enough consistent energy to devote to the podling. i've been wondering whether the answer may be to have a chair for each ppmc analogous to the role of the pmc chair. the initial pmc would be composed of the mentors for the podling and so a chair would need to be elected from within their number. at least one mentor would therefore need to commit to devote the energy required to perform this role. they would also form the first point of contact for the incubator pmc. opinions? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OFBiz - next steps
David N. Welton wrote: Hi, *) Cleaning up the code - they're in the process of cleaning up the code, getting rid of LGPL dependencies. This needs to happen prior to the code touching our subversion repositories, correct? Preferrably, though not a must. eg Roller has them.. Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] OFBiz Proposal
+1 (non binding) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] KabukiProposal
+1 (non binding) Mvgr, Martin Sam Ruby wrote: http://wiki.apache.org/incubator/KabukiProposal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] OFBiz Proposal
After some good thought about what to do with the system I am currently writing, I have come to the conclusion that there is a big overlap between ofbiz and it is worth it to invest the time to start using ofbiz for my solution and also this way prevent too much code duplication. In short : I would definitely like to get involved and help out with the incubation effort. Mvgr, Martin Martin van den Bemt wrote: +1 (non binding) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for OFBiz to Join the ASF
Leo Simons wrote: On Sun, Jan 22, 2006 at 10:39:51PM -0500, Noel J. Bergman wrote: Anyone on the PMC want to comment on this proposal? It seems as if there is significant interest from ASF Members, a willingness on the part of the donors to adopt The Apache Way, a number of ASF Members willing to act as Mentors, and no noticeably egregious problems. +1. Leo PS: My non-pmc-hat comment would be boring, but nevermind me :-) The field ofbiz covers is actually quite interesting (it's similar to what I did with a former employer, so that's probably part of the reason why it is interesting. Although not on the PMC, a +1 from me :) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] AJAX Toolkit Proposal - Updated (Again)
Sam Ruby wrote: Martin van den Bemt wrote: How do you fit in / are going to fit in with http://www.eclipse.org/proposals/atf/ ? Zimbra is mentioned there. If you look closely, that proposal closely matches the diffs between the first draft and second draft of the AJAX Toolkit Proposal that was presented here. It is indeed a diff :) In short, the ASF was originally the first choice for where that code would continue to be developed. Based on the feedback received here and elsewhere, an executive decision was made, and as far as I know, the proposal is receiving a warm welcome at Eclipse. Which (at least in my opinion) has a better natural home at Eclipse. Especially with looks like generic tooling for Ajax toolkits (not saying it wouldn't do well at Apache though) I would suggest that those who want there to be one or more AJAX projects at the ASF take a moment and consider how to make constructive suggestions on how to make that happen. My mail wasn't meant to be destructive at all (at least if that is the impression you got). It would be nice to have more Ajax projects onboard though, but it is still up to those projects to decide if they want to move here or not. A bit more constructive wouldn't hurt though, we could unintentionally give the wrong signal to the outside world and this way prevent interested project from taking the step to Apache. Although on the other side it is better to have a discussion than complete silence :) And, should you feel so inclined, feel free to update the Kabuki proposal: http://wiki.apache.org/incubator/KabukiProposal Adjusted and also added the Kabuki proposal to the main incubator wiki page. If you want to chose different words for what I have written, please go ahead :) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] AJAX Toolkit Proposal - Updated (Again)
How do you fit in / are going to fit in with http://www.eclipse.org/proposals/atf/ ? Zimbra is mentioned there. Mvgr, Martin Andrew Clark wrote: I have made a few modifications to the Ajax proposal Wiki page[1] in an attempt to resolve a few of the issues people have raised. The changes include: * Changed name to Kabuki * Added text to clarify the scope of the project Please let me know if there are any other issues that should be addressed by changes to the proposal text. Please note that the name change requires you to update any bookmarks you may already have for the old link. [1] http://wiki.apache.org/incubator/KabukiProposal - Original Message - From: Sam Ruby [EMAIL PROTECTED] To: general@incubator.apache.org Sent: Tuesday, January 17, 2006 1:03:59 PM Subject: Re: [VOTE] AJAX Toolkit Proposal - Updated Andrew Clark wrote: Sam Ruby wrote: And fwiw, I like 'Jambaloo' as a name but probably that's just me ;-) Andy, any preference? I don't have any particular preference in regards to the name. If people have a problem with AjaxTk being too broad, then any other name will do. I have a natural preference towards Japanese names, though, so I'll suggest Kabuki. :) That does seem like a very fitting name. Can I ask you to create the following page, and fold in your answer to Justin's concern? http://wiki.apache.org/incubator/KabukiProposal - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Filling out an Incubation Status
The way I read them is that when a date is set, the task is completed. Mvgr, Martin Henri Yandell wrote: Dumb question. Are the completion dates on http://incubator.apache.org/projects/roller.html when the event happened, or when it was marked as complete. ie) to start ticking these things off, do I need to go do mailing list audits etc to figure out when things happen, or can I just put today's date? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Roller release policy
I see roller already in SVN, is the development already going on in there ? Based on the README.txt in SVN, you can scratch radeox as being LGPL. They switched to BSD... (at least one legal issue got solved automatically :) Mvgr, Martin Henri Yandell wrote: As many know, Roller releases have been happening outside the ASF on the old site (rollerweblogger.org) with various incubating and 'not-ASF' statements added. These releases point to the non-ASF Roller website, wiki and Jira. The reason being that Roller still has non-ASF desirable dependencies included in its distribution. I presume that for much the same reason, the website, wiki and Jira can't migate (assuming possible) to the ASF as the releases would then point to the ASF sites? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Roller release policy
I subscribed to the roller user and dev list (found it at the bottom of the status html file..), so you can reply there if it's more appropiate.. Mvgr, Martin Martin van den Bemt wrote: I see roller already in SVN, is the development already going on in there ? Based on the README.txt in SVN, you can scratch radeox as being LGPL. They switched to BSD... (at least one legal issue got solved automatically :) Mvgr, Martin Henri Yandell wrote: As many know, Roller releases have been happening outside the ASF on the old site (rollerweblogger.org) with various incubating and 'not-ASF' statements added. These releases point to the non-ASF Roller website, wiki and Jira. The reason being that Roller still has non-ASF desirable dependencies included in its distribution. I presume that for much the same reason, the website, wiki and Jira can't migate (assuming possible) to the ASF as the releases would then point to the ASF sites? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator 2006Q1 Status Report to the ASF Board
About Axion : the db PMC is going to request removal of Axion (at least I pinged them about Axion and that was the reply).. Mvgr, Martin Noel J. Bergman wrote: Tobago came through with its report. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Being a mentor
Hi everyone, I was under the impression that being a mentor was just for ASF members, but couldn't find that written down anywhere. If it is not just a thing for ASF Members, I wouldn't mind freeing up some time to help out with mentoring. Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Changes to Incubator process(es)
[ ] - Any new proposal should have 3 ASF Members / Officers as mentors (without regard to affiliation) Where 3 are responsible, it could be no one is responsible. Better have one main mentor with possible backups (if the mentor is on holiday, etc..). Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: iBatis..
Larry Meadors wrote: 3) Probaly will not make that change (and break all those apps) until 3.x You are informing new adopters about this ? Since you are forcing them to change quite quickly after their adoption, even though everyone needs to switch to the new package naming eventually anyway. So give new adopters that extra work ? Just a thought to consider :) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Universal Login proyect proposal
On Wed, 2004-11-10 at 07:51, hammett wrote: Hiya, I think MS already implemented this idea. Its called Passport. Which has failed, so I read. Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] How to prevent abusing Apache priviliges
I will not vote on policy which makes no sense or is based on unproven facts from the past. I really do not see your point that this policy do not make sense! I started this abstract thread to prevent that things from happening *in the future*. Rules don't prevent anything from happening! Unless you are living in Utopia of course.. It's just a matter of oversight and common sense Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
