RE: [ANNOUNCE] Etch 1.1.0-incubating
-Original Message- From: Holger Grandy [mailto:holger.gra...@bmw-carit.de] Sent: Friday, 22 October 2010 1:19 AM To: general@incubator.apache.org Subject: [ANNOUNCE] Etch 1.1.0-incubating Hi everybody, the Etch community released a new version! Etch is a cross-platform, language- and transport-independent framework for building and consuming bidirectional network services. The Etch toolset includes a network service description language, a compiler, and binding libraries for Java, C# and C. The goal of Etch is to make it simple to define small, focused services that can be easily accessed, combined, and deployed in a similar manner. We are grateful to all our mentors, contributors, PMCers and everyone else, that helped us with this release! Version 1.1.0-incubating is available for download from http://incubator.apache.org/etch/downloads.html Please report bugs you may find using https://issues.apache.org/jira/browse/ETCH We welcome questions, discussions, ... at: etch-...@incubator.apache.org etch-u...@incubator.apache.org Release Notes are available at https://svn.apache.org/repos/asf/incubator/etch/releases/release-1.1.0- incubating/RELEASE_NOTES.txt Hope you like the new version! Regards, the Etch project team Well Done Etch Team, I know how hard it was for this to come around and how close things were to it not happening at all so is especially a great achievement. Gav... - 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] Release Apache Libcloud 0.4.0
-Original Message- From: Paul Querna [mailto:p...@querna.org] Sent: Thursday, 7 October 2010 6:37 AM To: general@incubator.apache.org; libcl...@incubator.apache.org Subject: [VOTE] Release Apache Libcloud 0.4.0 Test tarballs for Apache Libcloud 0.4.0 are available at: http://people.apache.org/~pquerna/dev/libcloud-0.4.0/ Please test and place your votes please; +/- 1 [+1] Release Apache Libcloud 0.4.0 Looks good. Thanks Gav... Vote closes on Monday October 11, 2010 at 10am PST. This is our first release of the 0.4 and trunk for a couple months, it includes many bug fixes, a few new features, and removal of the dependency on Zope.Interface. It is based upon this tag: https://svn.apache.org/repos/asf/incubator/libcloud/tags/0.4.0 Thanks, Paul - 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] Thrift 0.5.0 RC1
Nice work Thrifters. +1 Gav... -Original Message- From: Bryan Duxbury [mailto:br...@rapleaf.com] Sent: Wednesday, 6 October 2010 8:42 AM To: general@incubator.apache.org Subject: Re: [VOTE] Thrift 0.5.0 RC1 Hey all, Just a gentle reminder that I need your votes to get this release out... 24 hours remaining and zero votes. -Bryan On Mon, Oct 4, 2010 at 9:47 AM, Bryan Duxbury br...@rapleaf.com wrote: I propose that we accept http://people.apache.org/~bryanduxbury/thrift-0.5.0- rc1.tar.gzhttp://people.apache.org/%7Ebryanduxbury/thrift-0.5.0- rc1.tar.gzas the official Thrift 0.5.0 release. I produced this tarball by checking out a clean copy of the 0.5.x branch and running ./bootstrap.sh ./configure make dist. The GPG signature can be found at http://people.apache.org/~bryanduxbury/thrift-0.5.0- rc1.tar.gz.aschttp://people.apache.org/%7Ebryanduxbury/thrift-0.5.0- rc1.tar.gz.asc. It has an MD5 sum of 14c97adefb4efc209285f63b4c7f51f2. Please download, verify sig/summ, and install/test the libraries of your choice. We held the podling vote on thrift-dev and had 5 +1 votes, include 3 PPMC votes, and no -1 votes. (Message-ID: AANLkTimgHmKRsXG-iw7JuJr9PW=+SO6uVQ77yr- gj...@mail.gmail.com ) This vote will be open for 72 hours. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [jira] Commented: (ISIS-3) Import Naked Objects code into the Apache repo
Hi All, For now I have imported in the test repo for review. Please see the INFRA-3039 issue for more comments. Gav... -Original Message- From: Mark Struberg [mailto:strub...@yahoo.de] Sent: Wednesday, 6 October 2010 12:02 AM To: general@incubator.apache.org; d...@haywood-associates.co.uk Subject: Re: [jira] Commented: (ISIS-3) Import Naked Objects code into the Apache repo +1 LieGrue, strub --- On Tue, 10/5/10, Dan Haywood dkhayw...@gmail.com wrote: From: Dan Haywood dkhayw...@gmail.com Subject: Re: [jira] Commented: (ISIS-3) Import Naked Objects code into the Apache repo To: general@incubator.apache.org Cc: Robert Matthews rmatth...@nakedobjects.org Date: Tuesday, October 5, 2010, 1:51 PM On 05/10/2010 08:27, Mark Struberg wrote: The thing is that I first like to browse through the sources, just to be sure. Since the project already uses ASL since a long time, I doubt that there are any problems. We can also move this into isis/contribution/ and add a README explaining that these are the original projects which got moved to the ASF repos and do not necessarily express the opinion of the ASF. Since - as Upayavira has pointed out - no code should nor can be made private, can I suggest instead that we import into isis/contrib/initial-import (rather than isis/private/initial-import, which is what the ticket [1] currently states?) Thx Dan [1] https://issues.apache.org/jira/browse/INFRA-3039 - 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: [jira] Commented: (ISIS-3) Import Naked Objects code into the Apache repo
-Original Message- From: Mark Struberg [mailto:strub...@yahoo.de] Sent: Tuesday, 5 October 2010 5:56 AM To: general@incubator.apache.org Subject: Fw: [jira] Commented: (ISIS-3) Import Naked Objects code into the Apache repo Hi folks! Whom to ask for importing the historic NakedObjects SVN drops? This needs svn admin rights which I most probably do not have. Infra needs to do this. Please create an INFRA jira ticket, refer to your isis ticket. also, I see you have content and directories in there already, this will get blown away unless you specify you want to import to end up in there somewhere. HTH Gav... txs and LieGrue, strub --- On Mon, 10/4/10, Robert Matthews (JIRA) j...@apache.org wrote: From: Robert Matthews (JIRA) j...@apache.org Subject: [jira] Commented: (ISIS-3) Import Naked Objects code into the Apache repo To: isis-...@incubator.apache.org Date: Monday, October 4, 2010, 5:29 PM [ https://issues.apache.org/jira/browse/ISIS- 3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanelfocusedCommentId=12917664#action_12917664 ] Robert Matthews commented on ISIS-3: As I could not attach it I have uploaded to it this location: http://nakedobjects.org/isis-repo.gz Please can can it now be imported. Import Naked Objects code into the Apache repo -- Key: ISIS-3 URL: https://issues.apache.org/jira/browse/ISIS-3 Project: Isis Issue Type: Task Reporter: Robert Matthews Attached is the export data from our repository (using svnadmin dump). This needs to be imported into /incubator/isis/private/initial-import/nakedobjects. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - 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: Podling to use native git
-Original Message- From: Guillaume Nodet [mailto:gno...@gmail.com] Sent: Friday, 1 October 2010 5:11 PM To: general@incubator.apache.org Subject: Re: Podling to use native git I do agree with you. I don't really get this argument either. But in the meantime, you need to use an svn backend, and ask for a git mirror. You can then fork / merge at github the way you want, merge back into trunk and git svn dcommit from there. I think it's really worse, as branches aren't maintained anymore in the apache svn area, What's wrong with 'git tag' ?? but that's what we need to live with until git can be properly supported at Apache. It will be a while. Gav... On Fri, Oct 1, 2010 at 08:49, Mark Struberg strub...@yahoo.de wrote: Hmm, to be honest, I don't see this argument. Because you can also use a centralised model with GIT. Also, the main benefit of GIT is not only that you can do offline commits, but mostly that it's sooo much easier to merge! I had a merge hell with my colleague in the company this week. He kept a SVN feature branch for only one week and merging his feature branch into the trunk (team with 10 developers) did cost us a whole day... The reason is that SVN applies an end to end diff while git aims to merge by walking the commit tree of the branch and applying each commit separately. GIT even supports signing off commits. So each committer who pushes to the central repo 'signs' that the contribution is ASL licensed. LieGrue, stru --- On Thu, 9/30/10, Noel J. Bergman n...@devtech.com wrote: From: Noel J. Bergman n...@devtech.com Subject: RE: Podling to use native git To: general@incubator.apache.org Date: Thursday, September 30, 2010, 11:13 PM Does any other podling use git-only workflow. No ASF project is permitted to use git-only. And the typical git workflow is part of the problem. We strongly believe in a single, central, repository as part of the process of community building. The git model is better suited to disparate groups partially sharing a codebase. Fundamentally, we WANT people working in a central, shared, repository. If/when the ASF allows git as a technology, you can expect that the workflow will be an ASF workflow. And once Greg gets offline commmit working with SVN, I suspect that it will be harder to push for git. --- Noel --- -- 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 -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Podling to use native git
-Original Message- From: Florent Guillaume [mailto:f...@nuxeo.com] Sent: Friday, 1 October 2010 7:52 PM To: general@incubator.apache.org Subject: Re: Podling to use native git On Fri, Oct 1, 2010 at 11:40 AM, Toni Menzel t...@okidokiteam.com wrote: Its now the question to balance innovation (hence coolness) and solid, well well known processes. Its also that Subversion is still the king in corporates (well, together with CVS). So you would attract a whole different kind of developers when adopting git. FWIW people who use git/mercurial don't use it to be cool or innovative, they use it because it has become invaluable to their lives and they will never ever go back willingly to svn or even worse cvs. For them, git/mercurial *is* a well-known process. and to others there are another 15 at least to choose from, where does it stop, do you want infra to support all of them? or just the one *you* prefer. Let's be blunt, Subversion is and will remain the number one canonical repository at the ASF. We are looking at the possibilities of what we can do in terms of git and some of us will be having a meeting about it at ApacheCon. If we end up with a 2nd canonical git repo alongside svn sometime in the future then that is good, but it is also in the future, not now. Those that want it now, go elsewhere. Maybe I should go hack on some Git code and tell them I want them to have a svn repo that I can commit to because that is basically what everyone is doing here regarding Git when the ASF has Apache Subversion in house. We ARE working towards it but those getting there knickers in a twist about wanting it now and we are not with the times, tough. Gav... Florent -- Florent Guillaume, Director of RD, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 - 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
Deltacloud Mentors, an Infra issue requires your attention.
https://issues.apache.org/jira/browse/INFRA-2867 Thanks :-) Gav... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: No dev-, user- lists for small podlings (was: Re: [PROPOSAL] Kitty to Enter the Incubator)
The private, dev and commits list is all that has been asked for. See https://issues.apache.org/jira/browse/INFRA-2971 so your fine. gav... -Original Message- From: mwessend...@gmail.com [mailto:mwessend...@gmail.com] On Behalf Of Matthias Wessendorf Sent: Wednesday, 8 September 2010 7:29 PM To: general@incubator.apache.org Cc: d...@haywood-associates.co.uk Subject: Re: No dev-, user- lists for small podlings (was: Re: [PROPOSAL] Kitty to Enter the Incubator) +1 especially since incubation is about establishing a developers community -M On Wed, Sep 8, 2010 at 11:27 AM, Mark Struberg strub...@yahoo.de wrote: +1 I barely see the users list used in OWB and even in MyFaces ;) I'd say an isis-...@incubator.a.o + isis-comm...@i.a.o list would do fine for now. LieGrue, strub --- On Wed, 9/8/10, Dan Haywood dkhayw...@gmail.com wrote: From: Dan Haywood dkhayw...@gmail.com Subject: Re: No dev-, user- lists for small podlings (was: Re: [PROPOSAL] Kitty to Enter the Incubator) To: general@incubator.apache.org Date: Wednesday, September 8, 2010, 7:16 AM Isis mentors: Given we're in the same situation and are still being bootstrapped, should we follow this advice, ie start off with a combined mailing list for -dev and -user? Dan On 08/09/2010 08:10, Martijn Dashorst wrote: On Wed, Sep 8, 2010 at 7:22 AM, Greg Steingst...@gmail.com wrote: On Tue, Sep 7, 2010 at 20:29, Matthew Sacksmatt...@matthewsacks.comwrote: ... *Mailing Lists* kitty-dev kitty-commits kitty-user Is there a large user community already? If not, then splitting the community across dev/user does not make sense. You want to keep the users and developers on the same mailing list until one starts to overwhelm the other. By partitioning the lists too early, you risk never reaching critical mass on *either* mailing list. This is actually great advice, and I wish we'd done this with a couple of podlings that are currently too small to graduate. In retrospect empire-db and etch really could have done without the user- list IMO. Martijn - 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 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - 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] Change name of Lucene Connectors Framework to Apache Connectors Framework
-Original Message- From: Grant Ingersoll [mailto:gsing...@apache.org] Sent: Wednesday, 8 September 2010 10:18 PM To: general@incubator.apache.org Subject: [VOTE] Change name of Lucene Connectors Framework to Apache Connectors Framework 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. I have mentioned before, the wording of your request to change suggests that your are removing the word 'Lucene' and replacing it with the word 'Apache' . This is misleading and wrong. 'Apache' is a given, in both scenarios. You are changing from: 'Lucene Connectors Framework' to 'Connectors Framework' That could also be written as: 'Apache Lucene Connectors Framework' to 'Apache Connectors Framework' One or the other, don't mix the two, its misleading. That said, heres my vote: [] +1 Change the Lucene Connector Framework to the Apache Connector Framework [] 0 Don't care [] -1 Don't change it +1 I don't care for the name but my view is I'll leave it to the project to decide. Gav... 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: ISIS vote result
-Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Tuesday, 7 September 2010 9:49 PM To: general@incubator.apache.org Subject: ISIS vote result I just created the first JIRA for ISIS infrastructure, but I have this sinking feeling that I've gotten ahead of myself. Should I have waited for Noel to formally announce the vote results, or does Dan's email do the job? You should be fine, Noel will no doubt mention it in his report, but the vote is final, carry on. Gav... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: ISIS housewarming
-Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Wednesday, 8 September 2010 8:14 AM To: general@incubator.apache.org Subject: Re: ISIS housewarming Also, the mentor page specifically tells us to get assistance inside of the incubator for JIRA, not from INFRA. So, that page needs an edit if a ticket is really the correct thing to do. Interesting, the guide says: ...Issue Tracking If any Mentor has project-creation karma (in the issue tracking system to be used) then they should execute. If no Mentor has the required karma then post an email request to the IPMC list. An IPMC member with karma will then execute So Benson, you are correct. It has been my experience however that mostly this does not happen. I think what it should say is: ...Issue Tracking If any Mentor has project-creation karma (in the issue tracking system to be used) then they should execute. If no Mentor has the required karma then file an INFRA issue using the 'new jira project' type (not bug or request) So, Benson, feel free to file an issue, remember to choose the 'New Jira Project' bug type and provide all the requested details. Thanks, Gav... On Tue, Sep 7, 2010 at 5:55 PM, Luciano Resende luckbr1...@gmail.comwrote: On Tue, Sep 7, 2010 at 2:49 PM, Benson Margulies bimargul...@gmail.com wrote: If any kind souls in the intersection of infra and incubator would care to create some mailing lists (INFRA-2971) or set up a JIRA project (an internal incubator matter according to the web page), I would be most grateful. I'm hoping to start using the lists really soon to help the mentors organize ourselves for the other setup tasks, so this seems like the right bootstrap step. I'd create all the required sub-tasks for the podling setup, usually they would do most of them at once. See [1] as an example. [1] https://issues.apache.org/jira/browse/INFRA-2831 -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - 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: ISIS housewarming
-Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Wednesday, 8 September 2010 8:07 AM To: general@incubator.apache.org Subject: Re: ISIS housewarming Well, hmm. My fellow mentors would like to be more involved in the process, and until we have a mailing list, that's somewhat clumsy to organize. Also, all the iclas aren't in place yet for accounts. So my thought was to ask for mailing lists *first*, and then put all the others into place. If this is not making people happy I'll retreat and retrench. Nope, what you are doing is fine, most podling processes do involve all steps being done together but that doesn’t have to be. Whatever is easiest for the podling is fine by me. Less red tape to podlings life easier, is fine by me. I'll set up your lists today. Gav... On Tue, Sep 7, 2010 at 5:55 PM, Luciano Resende luckbr1...@gmail.comwrote: On Tue, Sep 7, 2010 at 2:49 PM, Benson Margulies bimargul...@gmail.com wrote: If any kind souls in the intersection of infra and incubator would care to create some mailing lists (INFRA-2971) or set up a JIRA project (an internal incubator matter according to the web page), I would be most grateful. I'm hoping to start using the lists really soon to help the mentors organize ourselves for the other setup tasks, so this seems like the right bootstrap step. I'd create all the required sub-tasks for the podling setup, usually they would do most of them at once. See [1] as an example. [1] https://issues.apache.org/jira/browse/INFRA-2831 -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - 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: ISIS housewarming
-Original Message- From: Gav... [mailto:ga...@16degrees.com.au] Sent: Wednesday, 8 September 2010 8:49 AM To: general@incubator.apache.org Subject: RE: ISIS housewarming -Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Wednesday, 8 September 2010 8:14 AM To: general@incubator.apache.org Subject: Re: ISIS housewarming Also, the mentor page specifically tells us to get assistance inside of the incubator for JIRA, not from INFRA. So, that page needs an edit if a ticket is really the correct thing to do. Interesting, the guide says: ...Issue Tracking If any Mentor has project-creation karma (in the issue tracking system to be used) then they should execute. If no Mentor has the required karma then post an email request to the IPMC list. An IPMC member with karma will then execute So Benson, you are correct. It has been my experience however that mostly this does not happen. I think what it should say is: ...Issue Tracking If any Mentor has project-creation karma (in the issue tracking system to be used) then they should execute. If no Mentor has the required karma then file an INFRA issue using the 'new jira project' type (not bug or request) I have made this change in r993556. Gav... So, Benson, feel free to file an issue, remember to choose the 'New Jira Project' bug type and provide all the requested details. Thanks, Gav... On Tue, Sep 7, 2010 at 5:55 PM, Luciano Resende luckbr1...@gmail.comwrote: On Tue, Sep 7, 2010 at 2:49 PM, Benson Margulies bimargul...@gmail.com wrote: If any kind souls in the intersection of infra and incubator would care to create some mailing lists (INFRA-2971) or set up a JIRA project (an internal incubator matter according to the web page), I would be most grateful. I'm hoping to start using the lists really soon to help the mentors organize ourselves for the other setup tasks, so this seems like the right bootstrap step. I'd create all the required sub-tasks for the podling setup, usually they would do most of them at once. See [1] as an example. [1] https://issues.apache.org/jira/browse/INFRA-2831 -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ --- -- 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: Name change from Lucene Connectors Framework to Apache Connectors Framework
I think the title of the name change is a little misleading. We are not Replacing 'Lucene' with 'Apache' . Apache is a given. IOW - The proposal is either: Change Apache Lucene Connectors Framework to Apache Connectors Framework or: Change Lucene Connectors Framework to Connectors Framework It should therefore be clear that the only change being proposed here is the 'dropping' of the word 'Lucene' due to the fact that Lucene is no longer its governing TLP. Gav... -Original Message- From: Paul Borgermans [mailto:paul.borgerm...@gmail.com] Sent: Wednesday, 25 August 2010 6:33 AM To: general@incubator.apache.org Subject: Re: Name change from Lucene Connectors Framework to Apache Connectors Framework On Tue, Aug 24, 2010 at 9:20 PM, Glen Daniels g...@thoughtcraft.com wrote: Gotta agree with David here. I'd prefer a less ambiguous name. Something in the line of Apache Content Connectors Framework maybe? Just my 0.02€ Regards Paul - 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: an experiment
-Original Message- From: Noel J. Bergman [mailto:n...@devtech.com] Sent: Tuesday, 17 August 2010 4:07 AM To: general@incubator.apache.org Subject: RE: an experiment Noel J. Bergman wrote: Your reading of the corporate structure of this org is needlessly formal. And sometimes the job description of a PMC Chair is Sorry, got distracted by the phone, and didn't finish the thought. Part of the job description of a PMC Chair is to look after the Foundation's interests. I hope that no one would say that I take an obstructionist approach to our projects, but if the PMC Chair doesn't look at these issues, who will? How about a PMC Chair that does more than turn up once a month at , ooh, day before board reports are due and then disappears for a whole month until , ooh, day before report time. And you still expect to run the whole show your way and jump in with 20+ messages in one day about subjects people have been discussing for days if not weeks before. if (P)PMC chairs of other projects acted in this manner others including yourself maybe, would have something to say about it. I'm surprised no-one has mentioned about the Incubator PMC Chair up until now (actually I'm not, and I bet that no one steps up to agree with me here, I expect to be alone in my opinion.) And I can't wait for your excuse to be that the sole role of PMC chair is to file reports. It's a shame because when you do turn up, you do a half decent job. Now to catch up with the other 30+ messages that have steamed in these last few hours. Gav... --- Noel - 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: an experiment
-Original Message- From: Noel J. Bergman [mailto:n...@devtech.com] Sent: Tuesday, 17 August 2010 9:13 AM To: general@incubator.apache.org Subject: RE: an experiment Gavin McDonald wrote: How about a PMC Chair that does more than turn up once a month at , ooh, day before board reports are due and then disappears for a whole month until , ooh, day before report time. Actually, I read Incubator e-mail pretty much every day. Then why do you store up all your replies until report time? It makes no sense. And you still expect to run the whole show your way and jump in with 20+ messages in one day about subjects people have been discussing for days if not weeks before. I'm voicing an opinion, backing it up, and taking the issue to the Board for their input. If I really expected to run the whole show [my] way, I wouldn't make sure that as much as possible is delegated and distributed to the PMC, and I would be much more vocal. Personally, I believe that the Incubator runs smoothly precisely because of that delegation. In the specific case of Joe's experiment, I would have voice my opinion earlier, but was away. Please note that, as an Incubator PMC Member, you were notified of my schedule. Yes, and if it were just this month then fine, but it's not. Why on earth I notice these things I don't know, maybe it's not important in the grand scheme of things, but I can't help feeling irritated that you turn up once a month with your slew of emails and then think all is great again until the following months reporting period. Oh right, I need to back that up. Let's just only go as far back as January this year. January board meeting was: 20th: you posted on 18th,19th. February board meeting was: 17th: you posted on 15th,16th,24th. March board meeting was: 17th: you posted on 16th. April board meeting was: 21st: you posted on 20th,21st. May board meeting was: 19th: you posted on 18th. June board meeting was: 16th: you posted on 15th,18th. July board meeting was: 21st: you posted on 19th,22nd. Note that these dates are as I received them my TZ (GMT+9) but you get the idea. I see a pattern. And I can't wait for your excuse to be that the sole role of PMC chair is to file reports. No, it isn't. The role of the PMC Chair is to make sure that the project runs smoothly. I was very vocal during the formative days of the Incubator, and speak up when I've something to say. Otherwise, I am quite happy to see others stepping up and staking a role in the Incubator. Ok, if you see all is well then fine, but can you not just at least look like you are a bit more interested other than just at reporting time? another example, you just posted a whole months worth at members requesting to join the Incubator PMC and Greg just acked the lot -- is this something that only you as Incubator PMC chair can do or can any member send off this ack request to the board? If it makes things easier I'd be glad to help. Gav... --- Noel - 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: svn commit: r984937 - /incubator/public/trunk/site-publish/deltacloud/
-Original Message- From: cctriel...@apache.org [mailto:cctriel...@apache.org] Sent: Friday, 13 August 2010 6:05 AM To: public-comm...@incubator.apache.org Subject: svn commit: r984937 - /incubator/public/trunk/site- publish/deltacloud/ Author: cctrieloff Date: Thu Aug 12 20:05:21 2010 New Revision: 984937 URL: http://svn.apache.org/viewvc?rev=984937view=rev Log: Add dir for deltacloud website in incubator Added: incubator/public/trunk/site-publish/deltacloud/ Why? Gav... - To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org For additional commands, e-mail: cvs-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] NPanday to enter the incubator
-Original Message- From: Brett Porter [mailto:br...@porterclan.net] On Behalf Of Brett Porter Sent: Thursday, 12 August 2010 10:31 AM To: general@incubator.apache.org Subject: Re: [VOTE] NPanday to enter the incubator On 07/08/2010, at 1:21 AM, Brett Porter wrote: Hi, We have finalised the proposal with the additional committer and it has now been posted for a couple of weeks, so I'd like to put it to a vote. With the weekend included, I'll tally the votes after 5 days (120 hours). Obviously +1 from me. Would anybody else like to weigh in? ooh ooh is that my que, am I on ? Seriously, +1 Gav... Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - 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: [PROPOSAL] NPanday Project
-Original Message- From: Josimpson Ocaba [mailto:joc...@g2ix.net] Sent: Thursday, 29 July 2010 8:10 PM To: general@incubator.apache.org Subject: Re: [PROPOSAL] NPanday Project Hi, We would like to inquire if there are any more comments before we could start a vote. No news is good news :) As a prospective listed Mentor for the project obviously I am +1 on the idea and the proposal itself looks fine. note: We also have a current vote for a new committer at codeplex, so we will wait for the results on that and adjust the proposal before the vote if needed. Good plan, this allows extra time this end for any other comments. Gav... - Original Message - From: Josimpson Ocaba joc...@g2ix.net To: general@incubator.apache.org Sent: Friday, July 23, 2010 1:23:18 PM Subject: [PROPOSAL] NPanday Project Good Day, In behalf of the NPanday community I would like to share with you our proposal for the NPanday project to be included amongst one of the incubation projects. Here is the link for the proposal in the incubation: http://wiki.apache.org/incubator/NPandayProposal and here is the link for the current location of the project: http://npanday.codeplex.com/ Please let us know any feedbacks or questions about the proposal. We would very much welcome any volunteers to help us guide NPanday through this incubation process. -- NPanday Proposal -- Abstract NPanday allows projects using the .NET framework to be built with Apache Maven. NPanday allows .NET projects to be converted into Maven projects thus allowing them to fully utilize the other technologies driven by Maven. Proposal NPanday primarily provides two capabilities: a set of Maven plugins, for constructing builds in Maven that use the .NET command-line tools; and a Visual Studio Addin that keeps a Visual Studio project in sync with the Maven POM and adds reference resolution from Maven artifact repositories. Together this allows you to use a single tool across .NET, Java or any other Maven-based projects, including the same benefits of dependency management, automated release and source control management. Background When building .NET projects traditionally you would use the built in components in Visual Studio or compile the source code by hand in the command line using .NET frameworks. NPanday gives an alternative building management option. NPanday also allows developers to continue to build and develop .NET projects even without the aid of Visual Studio. Rationale NPanday allows developers to still use the .NET Frameworks and technologies that they need and at the same time allow their projects to be distributed and released with greater ease using Maven's conventions. NPanday also helps those developers maintain and integrate their project in a continuus integration that could host both Java and .NET projects. Initial Goals The initial goals for NPanday are: * Donate the existing codebase and import it. * Setup the incubation infrastructure (svn repository, build system, website) so we can run continuous builds with automated testing and publish all available documentation and releases, and migrate from Codeplex * Get people involved in advancing the code base in different directions, integrating it with other projects at Apache. * Work closely with current contributors and seek to add new committers * Prepare for a point release that meets incubator and Apache criteria * Start active development on NPanday 2.0 Current Status The current codebase is developed and tested in both .NET and Java. It was developed at Codeplex for the last two years after originally being forked from the failed NMaven incubator podling. We have a number of releases all of which have followed a clear transparent process. Documentation for the project is currently available in http://www.npanday.org/docs/1.2/, which can be donated and converted to the Apache NPanday website. The development team is currently using Codeplex discussion forums as the primary colaborative process. Meritocracy Some of the core developers are already committers and PMC members at Apache, so they understand what it means to have a process based on meritocracy. NPanday has been operating under an Apache-like model since its inception. Community We've seen a number of new contributors joining the community recently.. Most of the community members have found NPanday through searching for Maven in .NET and have donated their own tweaks as they continue to consume NPanday. The community members have actively created issues that are improving the behaviors and bugs in the current version. Core Developers The core development team started mostly with members from MaestroDev and has been recently added
[Travel Assistance] - One week until Applications for financial assistance ends for ApacheCon NA 2010
Podling PPMCs - please re-post this message to your mailing lists. Hi All, There is only ONE WEEK to go before we stop accepting applications for financial assistance. The Travel Assistance Committee is now taking in applications for those wanting to attend ApacheCon North America (NA) 2010, which is taking place between the 1st and 5th November in Atlanta. The Travel Assistance Committee is looking for people who would like to be able to attend ApacheCon, but who need some financial support in order to be able to get there. There are limited places available, and all applications will be scored on their individual merit. Financial assistance is available to cover travel, accommodation and entrance to the event, either in part or in full, depending on circumstances. However, the support available for those attending only the barcamp is smaller than that for people attending the whole event. The Travel Assistance Committee aims to support all ApacheCons, and cross-project events, and so it may be prudent for those in Asia and the EU to wait for an event closer to them. More information can be found on the main Apache website at http://www.apache.org/travel/index.html - where you will also find a link to the online application and details for submitting. Applications for applying for travel assistance are now being accepted, and will close on the 7th July 2010. Good luck to all those that will apply. You are welcome to tweet, blog as appropriate. Regards, The Travel Assistance Committee. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: svn commit: r947941 - in /incubator/public/trunk: ./ site-author/ site-publish/
-Original Message- From: cross...@apache.org [mailto:cross...@apache.org] Sent: Tuesday, 25 May 2010 4:56 PM To: public-comm...@incubator.apache.org Subject: svn commit: r947941 - in /incubator/public/trunk: ./ site- author/ site-publish/ Author: crossley Date: Tue May 25 06:55:52 2010 New Revision: 947941 URL: http://svn.apache.org/viewvc?rev=947941view=rev Log: cassandra partially tidied up after graduation. Thanks, let me know what else needs doing here. subversion partially tidied up after graduation. and here. Cheers Gav... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Graduated projects please tidy up
-Original Message- From: David Crossley [mailto:cross...@apache.org] Sent: Tuesday, 25 May 2010 10:59 AM To: general@incubator.apache.org Subject: Re: Graduated projects please tidy up On Fri, Apr 30, 2010 David Crossley wrote: I have noticed a trend lately, that Graduated projects are not tidying up after themselves. They should be self-sufficient by this stage. For example, if they don't remove themselves from the Wiki page ReportingSchedule then they will be still listed to report this month. Poor Clutch only gets the data that it is fed, so it will add your dev mail list to the set of projects due to report. Marvin will try to contact you. Clutch also tries to list some other clean-up issues, such as removing your stuff from the Incubator distribution mirrors. http://incubator.apache.org/clutch.html#other abdera buildr log4php openwebbeans pig sanselan shindig subversion uima Thanks to pig and shindig for tidying up. The following are listed this month: abdera buildr log4php openwebbeans subversion trafficserver uima Subversion done, trafficserver done. Also Cassandra is still listed on ReportingSchedule and in the Projects-in-Incubation table. https://issues.apache.org/jira/browse/INCUBATOR-108 I'll do Cassandra next. Gav... Here are some tips for graduation: http://incubator.apache.org/clutch.html#h-Graduate - 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: svn commit: r947923 - /incubator/public/trunk/site-author/stylesheets/project.xml
-Original Message- From: grobme...@apache.org [mailto:grobme...@apache.org] Sent: Tuesday, 25 May 2010 3:32 PM To: public-comm...@incubator.apache.org Subject: svn commit: r947923 - /incubator/public/trunk/site- author/stylesheets/project.xml Author: grobmeier Date: Tue May 25 05:32:13 2010 New Revision: 947923 URL: http://svn.apache.org/viewvc?rev=947923view=rev Log: added zeta components to the menu coo, whilst generating for my own updates, I generated the html output for your change. Thanks for the commit war :) Gav... Modified: incubator/public/trunk/site-author/stylesheets/project.xml Modified: incubator/public/trunk/site-author/stylesheets/project.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/site- author/stylesheets/project.xml?rev=947923r1=947922r2=947923view=diff === === --- incubator/public/trunk/site-author/stylesheets/project.xml [utf-8] (original) +++ incubator/public/trunk/site-author/stylesheets/project.xml [utf-8] Tue May 25 05:32:13 2010 @@ -116,6 +116,7 @@ limitations under the License. lia href=/projects/whirr.htmlWhirr/a/li lia href=/projects/wink.htmlWink/a/li lia href=/projects/wookie.htmlWookie/a/li + lia href=/projects/zetacomponents.htmlZeta Components/a/li /menu /body - To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org For additional commands, e-mail: cvs-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: svn commit: r947928 - in /incubator/public/trunk/site-publish: projects/deltacloud.html projects/zetacomponents.html sitemap.html
-Original Message- From: grobme...@apache.org [mailto:grobme...@apache.org] Sent: Tuesday, 25 May 2010 3:44 PM To: public-comm...@incubator.apache.org Subject: svn commit: r947928 - in /incubator/public/trunk/site-publish: projects/deltacloud.html projects/zetacomponents.html sitemap.html Author: grobmeier Date: Tue May 25 05:44:19 2010 New Revision: 947928 URL: http://svn.apache.org/viewvc?rev=947928view=rev Log: regenerated website for zeta addition snip Modified: incubator/public/trunk/site-publish/sitemap.html URL: http://svn.apache.org/viewvc/incubator/public/trunk/site- publish/sitemap.html?rev=947928r1=947927r2=947928view=diff === === --- incubator/public/trunk/site-publish/sitemap.html [utf-8] (original) +++ incubator/public/trunk/site-publish/sitemap.html [utf-8] Tue May 25 05:44:19 2010 @@ -1865,6 +1865,7 @@ href=/projects/index.htmlProjects/a lia href=/projects/sis.htmlSIS/a/li lia href=/projects/socialsite.htmlSocialSite/a/li lia href=/projects/stonehenge.htmlStonehenge/a/li + lia href=/projects/subversion.htmlSubversion/a/li lia href=/projects/tashi.htmlTashi/a/li lia href=/projects/thrift.htmlThrift/a/li lia href=/projects/vcl.htmlVCL/a/li Interesting, looks like your commit after mine put subversion back after I removed it. I'll check it again in a few minutes. Gav... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[Travel Assistance] - applications Open for ApacheCon NA 2010
Hi Incubator folks, Incubator Projects - Please distribute this notice to your user and dev lists: The Travel Assistance Committee is now taking in applications for those wanting to attend ApacheCon North America (NA) 2010, which is taking place between the 1st and 5th November in Atlanta. The Travel Assistance Committee is looking for people who would like to be able to attend ApacheCon, but who need some financial support in order to be able to get there. There are limited places available, and all applications will be scored on their individual merit. Financial assistance is available to cover travel to the event, either in part or in full, depending on circumstances. However, the support available for those attending only the barcamp is smaller than that for people attending the whole event. The Travel Assistance Committee aims to support all ApacheCons, and cross-project events, and so it may be prudent for those in Asia and the EU to wait for an event closer to them. More information can be found on the main Apache website at http://www.apache.org/travel/index.html - where you will also find a link to the online application and details for submitting. Applications for applying for travel assistance are now being accepted, and will close on the 7th July 2010. Good luck to all those that will apply. You are welcome to tweet, blog as appropriate. Regards, The Travel Assistance Committee. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Release Apache Libcloud 0.3.1
No problems my end. +1 Gav... -Original Message- From: Paul Querna [mailto:p...@querna.org] Sent: Friday, 7 May 2010 9:09 AM To: libcl...@incubator.apache.org; general@incubator.apache.org Subject: [VOTE] Release Apache Libcloud 0.3.1 Test tarballs for Apache Libcloud 0.3.1 are available at: http://people.apache.org/~pquerna/libcloud-0.3.1/ Please test and place your votes please; +/- 1 [ ] Release Apache Libcloud 0.3.1 Vote closes on Monday May 10, 2010 at 1pm PST. This release fixes several issues related to the license blocks, NOTICE file, and test cases that were noticed in the scrubbed 0.3.0 release. It is based upon this tag: https://svn.apache.org/repos/asf/incubator/libcloud/tags/0.3.1 Thanks, Paul - 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: Zeta proposal - Next steps
-Original Message- From: Julien Vermillard [mailto:jvermill...@gmail.com] Sent: Saturday, 8 May 2010 8:53 PM To: general@incubator.apache.org Subject: Re: Zeta proposal - Next steps On Fri, May 7, 2010 at 6:57 PM, Christian Grobmeier grobme...@gmail.com wrote: Sorry according to http://incubator.apache.org/incubation/Incubation_Policy.html#Mentor he should be in the Incubator PMC. ah, sorry, I misread this paragraph. I thought only 1 mentor must be a member of the IPMC. Christian is not an ASF member, but applied also for becoming an IPMC member. I have no feedback so far from the IPMC. If this doesn't change I cannot help on mentoring - but I will enjoy helping on the mailing list and such. Looks like there is a lot of latency from the IPMC. Julien Just a little while longer I'm sure. I've shown my support for Christian, we just need to wait for the Incubator PMC chair to approve or not, and he is on his holidays currently I believe. Gav... - 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: [PROPOSAL] Zeta Components - Further comments?
-Original Message- From: Tobias Schlitt [mailto:tob...@schlitt.info] Sent: Thursday, 22 April 2010 9:55 PM To: general@incubator.apache.org Cc: Christian Grobmeier Subject: Re: [PROPOSAL] Zeta Components - Further comments? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 snip The CI stuff is secondary to get started, since we will also have external CI. We can take care of that as soon as we are incubated, I think. Incubation periods vary, it could be 3 months, 6, a year, two, no one knows for sure. Certainly not a blocker for starting incubation though. Once incubation has started, you can detail all your CI needs to the builds@ list and we'll see what can be done, or you can detail them now and I can give you an idea. Gav... Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvQOScACgkQ5bO3TcRivBSelwCeOkq4q/OKtJlyK6mo5UEkkjS3 T2IAn0Avp5m9KE4lcHW6zReT3BG0ucwu =BUUN -END PGP SIGNATURE- - 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: [PROPOSAL] Zeta Components
An excellent well thought out, complete proposal, with none of the usual copying of previous proposals with a bit of tweaking. All looks good to me. Gav... -Original Message- From: Tobias Schlitt [mailto:tob...@schlitt.info] Sent: Monday, 19 April 2010 11:53 PM To: general@incubator.apache.org Cc: Derick Rethans; Kore Nordmann; Sebastian Bergmann; Ole Marius Smestad; Roland Benedetti Subject: [PROPOSAL] Zeta Components -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, please find below our proposal for Zeta Components. The proposal is also available in the wiki: http://wiki.apache.org/incubator/ZetaComponentsProposal Regards, Toby = Proposal: Zeta Components = Zeta Components is a high-quality library of loosely coupled PHP components. - Proposal - The Zeta project was originally named *eZ Components* [1]_ and was developed as an open source project under New BSD license by eZ Systems AS [2]_. Involving a name change, eZ Systems is willing relicense the source code basis and documentation and to donate it to the Apache Software Foundation. The goal of the project is to provide high-quality, loosely coupled components for the development of applications based on PHP version 5.1 and above. On the one hand, Zeta contains standard components for e.g. database abstraction, templating, email, image manipulation and more, on the other hand there are modules which are unique in the PHP world, like a document format conversion component, a WebDAV server module and a workflow based programming framework. The project is developed with a strong focus on code and documentation quality, as well as on backwards compatibility. It follows a well- defined development process with extensive architecture and design discussions and prescribes a test driven development approach. - -- Background - -- PHP is the most common language for developing web applications, but is also in use in other areas. While the language itself already ships with many libraries to solve different tasks, there is still a need for user land libraries to provide more complex repetitive functionality. Zeta provides components dedicated to such functionality. An example for a tasks that can be solved using Zeta are processing and sending of email. This is already possible from within pure PHP. But working with multi-part MIME emails is not easily possible and a real pain when doing that on your own. For that reason, a module [5]_ exists in Zeta which allows the developer to easily create and send such emails and to receive and process them. The Zeta project currently consists of the following components: - - Archive - - Authentication - - AuthenticationDatabaseTiein - - Base - - Cache - - Configuration - - ConsoleTools - - Database - - DatabaseSchema - - Debug - - Document - - EventLog - - EventLogDatabaseTiein - - Execution - - Feed - - File - - Framework - - Graph - - GraphDatabaseTiein - - ImageAnalysis - - ImageConversion - - Mail - - MvcAuthenticationTiein - - MvcFeedTiein - - MvcMailTiein - - MvcTemplateTiein - - MvcTools - - PersistentObject - - PersistentObjectDatabaseSchemaTiein - - PhpGenerator - - Search - - SignalSlot - - SystemInformation - - Template - - TemplateTranslationTiein - - Translation - - TranslationCacheTiein - - Tree - - TreeDatabaseTiein - - TreePersistentObjectTiein - - Url - - UserInput - - Webdav - - Workflow - - WorkflowDatabaseTiein - - WorkflowEventLogTiein - - WorkflowSignalSlotTiein As can be seen, there are typical web-application modules included, such as the Feed component - which allows users to generate and consume different types of aggregation feeds -, the already mentioned Mail component, a template component for website templates and a WebDAV server component. Beside that, the library also contains many modules which are not only suitable for web applications, like a component for managing various archive file formats, multiple layers of database abstraction, tools for image manipulation, basic interfaces and implementations of a model-view-controller [17]_ structure and more. In contrast to other frameworks, the components in Zeta are loosely coupled and there are almost no hard inter-dependencies between them. Instead, if a component can be integrated with another one, a so-called *Tiein* component is provided, supplying the classes necessary to couple the components. This allows users to cherry pick the components they need, without the need of using the whole stack. That is especially useful for using the provided modules in legacy code or when there is a standard framework to build new applications on. - - Rationale - - Zeta is a library of high-quality, loosely coupled components for application development on basis of PHP
[RESULT] - [VOTE] - Graduate Log4PHP as a subproject of Logging project
The votes received were: +1 - Martijn Dashorst , Brett Porter, Joe Schaefer, Stefan Bodewig, Bertrand Delacretaz, Jim Jagielski, Alan D Cabrera, Ant Elder, Ralph Goers, Luciano Resende, Robert Burrell Donkin, Yoav Shapira, Kevan Millar So with 13 +1 , and no +/-0 and no -1 , this vote passes and Log4PHP graduates as a sub-project of Logging. Thanks everyone for the nice voter turnout. I believe the next step here is for the IPMC Chair to do a handover to the Logging PMC Chair, after which resources can start to be moved over - thanks Noel in advance :) Gav... -Original Message- From: Gav... [mailto:ga...@16degrees.com.au] Sent: Thursday, 4 March 2010 7:19 PM To: general@incubator.apache.org Subject: [VOTE] - Graduate Log4PHP as a subproject of Logging project Hi All, The Log4PHP community has voted [1] with 5 +1 votes and no other votes as follows, to graduate to become a sub-project of the Logging Project. * Gavin McDonald * Christian Hammers * Jim Jagielski * Jesus Christian (non binding) * Christian Grobmeier The Logging PMC has voted [2] with 7 +1 votes and no other votes as follows, to accept Log4PHP as a sub-project. * Ceki Gülcü * Niclas Hedhman * Curt Arnold * Scott Deboy * Paul Smith * Ron Grabowski * Christian Grobmeier The Log4PHP community feels it has fulfilled all graduation requirements to become a sub-project. This vote is to ask that the IPMC approve the graduation of Log4PHP as a sub-project of Apache Logging. The vote starts now and will run for a minimum of 72 hours. [ ] - +1 - Graduate Log4PHP as a sub-project of Apache Logging. [ ] - +/-0 - Don't care, whatever the majority decides. [ ] - -1 - Strongly object to this graduation (because ... Thanks All, Gav... [1] - Message-ID: ded132f11003032357v5f4edbb2k7579ffbb3be22...@mail.gmail.com [2] - Message-ID: ded132f11003032352h5d11607ene1811d34b9670...@mail.gmail.com - 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] - Graduate Log4PHP as a subproject of Logging project
Hi All, The Log4PHP community has voted [1] with 5 +1 votes and no other votes as follows, to graduate to become a sub-project of the Logging Project. * Gavin McDonald * Christian Hammers * Jim Jagielski * Jesus Christian (non binding) * Christian Grobmeier The Logging PMC has voted [2] with 7 +1 votes and no other votes as follows, to accept Log4PHP as a sub-project. * Ceki Gülcü * Niclas Hedhman * Curt Arnold * Scott Deboy * Paul Smith * Ron Grabowski * Christian Grobmeier The Log4PHP community feels it has fulfilled all graduation requirements to become a sub-project. This vote is to ask that the IPMC approve the graduation of Log4PHP as a sub-project of Apache Logging. The vote starts now and will run for a minimum of 72 hours. [ ] - +1 - Graduate Log4PHP as a sub-project of Apache Logging. [ ] - +/-0 - Don't care, whatever the majority decides. [ ] - -1 - Strongly object to this graduation (because ... Thanks All, Gav... [1] - Message-ID: ded132f11003032357v5f4edbb2k7579ffbb3be22...@mail.gmail.com [2] - Message-ID: ded132f11003032352h5d11607ene1811d34b9670...@mail.gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Release Apache libcloud 0.2.0
-Original Message- From: Paul Querna [mailto:p...@querna.org] Sent: Thursday, 11 February 2010 11:30 AM To: general@incubator.apache.org Subject: [VOTE] Release Apache libcloud 0.2.0 The Apache Libcloud project is currently voting on our first release, 0.2.0. As required by Incubator policy, we need IPMC approval for this release. There is a concurrent release vote ongoing on libcl...@incubator.apache.org. The current (passing) RAT output can be seen at: http://ci.apache.org/projects/libcloud/rat-output.txt Test tarballs for Apache Libcloud 0.2.0 are available at: http://people.apache.org/~pquerna/lc-0.2.0/ Please test and place your votes please; +/- 1 [+1] Release Apache Libcloud 0.2.0 Note I also voted +1 in the libcloud vote as Mentor. Gav... Vote closes on Monday February 15, 2010 at 1pm PST. Thanks, Paul - 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: incubator group membership for tfischer
-Original Message- From: Thomas Fischer [mailto:fisc...@seitenbau.net] Sent: Friday, 5 February 2010 10:08 PM To: general@incubator.apache.org Subject: Re: incubator group membership for tfischer Can someone please add me (tfischer) to the incubator group so I can update the incubator's webste from svn ? I am member of the incubator PMC. You are already in the incubator group, I'm not sure what goes wrong. Hm, not on minotaur: [tfisc...@minotaur:~]$ groups tfischer tfischer apcvs member apsite db Added. Gav... Thomas - 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: Switching incubator.apache.org to svnpubsub?
-Original Message- From: Martijn Dashorst [mailto:martijn.dasho...@gmail.com] Sent: Wednesday, 3 February 2010 5:28 PM To: general@incubator.apache.org Subject: Re: Switching incubator.apache.org to svnpubsub? +0.9 I agree that the site update process is cumbersome, but it also gives podling folks an incentive to log on to p.a.o and learn to use that system to their advantage. Moving to svnpubsub would take that away. Only whilst they are podlings. This system is not applied to most TLPs, though they can request it. And I'm betting that every single project that graduates will make that request rather than learn the old cumbersome way. Gav... That said, I think that most committers never have to go to p.a.o in any case so perhaps the point is moot. Martijn On Wed, Feb 3, 2010 at 7:57 AM, Justin Erenkrantz jus...@erenkrantz.com wrote: Hi general@, I'd like to suggest switching incubator.apache.org over to svnpubsub. (We can do so by filing a JIRA like INFRA-2349: http://issues.apache.org/jira/browse/INFRA-2349) This would mean that any commits made to the site-publish tree would automatically be deployed to the site. No more delays, no more SSH and SVN up fun. Yay. This does mean you trade off the fact that you can't delay anything - but, in general, I think that's fine for the incubator site and would substantially lower the barrier of entry to folks working on the Incubator site. Often times, people's first experience with the ASF is through the podlings, so I think it would be nice if we could make it a bit easier to publish the incubator.a.o site. What do folks think? -- justin P.S. On IRC, Paul mentions there may be some complications with respect to podling sites as sub-directories, but he promises that it is feasible to address. *grin* - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4 - 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
test
ignore - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Release UIMA 2.3.0-rc9
-Original Message- From: Eddie Epstein [mailto:eaepst...@gmail.com] Sent: Sunday, 24 January 2010 11:52 PM To: general@incubator.apache.org Subject: Re: [VOTE] Release UIMA 2.3.0-rc9 Hi, sure. The unapproved licenses for each package are: Linux source - 17 unknown: 7 - regression and sample test data 6 - auto generated files (gnumake and JNI header) 1 - NOTICE file for binary package (with suffix) 1 - README file for binary package (with suffix) 1 - doxygen html template 1 - gdb init file for testing Windows source - 46 unknown: 35 - Microsoft devenv build control files (vcproj and sln) 7 - regression and sample test data 1 - NOTICE file for binary package (with suffix) 1 - README file for binary package (with suffix) 1 - doxygen html template 1 - JNI auto gen header Linux 32-bit and 64-bit binary - 377 unknown for each 259 - doxygen output files 108 - ICU redistributable headers 7 - xercesc redistributable headers 1 - APR redistributable header 1 - sample test data 1 - gdb init file Windows binary - 462 unknown 333 - doxygen output files 104 - ICU redistributable headers 13 - Microsoft devenv build files (vcporj and sln) 10 - xercesc redistributable headers 1 - APR redistributable header 1 - sample test data Although it doesnt do any harm, performing RAT reports on generated files (currently) is not strictly necessary. Look at: http://incubator.apache.org/guides/releasemanagement.html#notes-license-head ers which states: All source capable of copyright should contain license header. Easiest way to comply is to ensure that every human readable file has the header. Note that source includes not just the source code compiled into the final product but also all other resources such as style sheets, test code and resources, build files and documentation source. When in doubt, add a header. and... The issue of licenses on generated documentation is a little controversial. Copyright may not subsist in a document which is generated by an transformation from an original. In which case, the license header may be unnecessary. License headers should always be present in the original. Where it is reasonable to do so, the templates should also add the license header to the generated documents. So, what you have done is akin to the second paragraph. What you have not done is produce a RAT report on your original untouched source files in svn. This is akin to paragraph one above and is what you should really be providing. Not only that, the results of the RAT reports should end up being 'zero' unknown/unapproved files. This can always be achieved, by either adding the headers as necessary, or by excluding the relevant files from the report. RAT is capable of excluding files by using an exclusion file kept in svn which RAT can then use. An example of 'zero' being achieved is at http://ci.apache.org/projects/log4php/rat-output.html. I took the liberty of using Buildbot to produce RAT reports for your trunk, uimacpp-2.3.0-09 tag and uima-2.3.0 release branch, results were: Trunk - 51 Unknown Licenses - http://ci.apache.org/projects/uima/rat-output.html uimacpp-2.3.0-09 Tag - 51 Unknown Licenses - http://ci.apache.org/projects/uima/tags/uimacpp-2.3.0-09/rat-output.html uimacpp-2.3.0 Branch - 51 Unknown Licenses - http://ci.apache.org/projects/uima/branches/uimacpp-2.3.0/rat-output.html All the same results which shows consistency which is good. Going through those source files we have: .buildbot-sourcedata - created by buildbot and can be excluded. NOTICE.* - can be excluded README.* - can be excluded createRelease.txt - can be excluded docs/doxyheader.html - optional **/*.vcproj - Don't see why these can't have headers **.*.asc - can be excluded So, just by applying either headers or exclusion list for the above will reduce the list to just a couple. Take a look at http://svn.apache.org/repos/asf/forrest/trunk/etc/rat-avoid.txt for a good example of an exclusion file that RAT can use. If you create one, let me know and I'll reconfigure the buildbot to use it, or let you know how you can use it in your own manual runs. Note that your current four RAT reports can be brought down to 'zero' just by creating an exclusion list as you are indicating that all of the those files are to be excluded. After saying all of the above, I am not voting on the release, just providing RAT report advice and havent the time currently to check the rest of the release. Having licenses in place for all source files (not generated) and/or exclusions I should think would be a requirement for release approval, I'd prefer others to clarify that though. Good luck. Gav... Thanks for digging into the UIMA release! Eddie On Sat, Jan 23, 2010 at 6:57 PM, Jean T. Anderson j...@bristowhill.com wrote: Eddie Epstein wrote: Hi Jean, Just noting that uimacpp does include rat reports, just poorly named
RE: Missing reports due NOW
-Original Message- From: Martijn Dashorst [mailto:martijn.dasho...@gmail.com] Sent: Tuesday, 19 January 2010 7:24 PM To: general@incubator.apache.org Subject: Re: Missing reports due NOW The notification was sent but got stuck in moderation with no moderator for the dev@ list. Or no 'active' moderators, these are listed as mods for the dev list. francisdb doebele reiher Gav... Martijn On Tue, Jan 19, 2010 at 7:53 AM, Francis De Brabandere franci...@gmail.com wrote: As far as I know we (empire-db) also did not receive a notification. Cheers, Francis On Tue, Jan 19, 2010 at 3:00 AM, Hyrum K. Wright hyrum_wri...@mail.utexas.edu wrote: On Jan 18, 2010, at 2:20 PM, Justin Erenkrantz wrote: On Mon, Jan 18, 2010 at 5:28 AM, Noel J. Bergman n...@devtech.com wrote: Missing: Subversion Hmm. Something went wrong with the automated notifier as this ball got dropped, I guess. Subversion should have something submitted by this evening. -- justin The automated notifier (Marvin?) sent it's notification on Jan. 1, and it was promptly missed in all the post-holiday revelry. -Hyrum - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.somatik.be Microsoft gives you windows, Linux gives you the whole house. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4 - 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 Shindig for Incubation
quote who=Brian McCallister This vote will run until Monday, Dec. 3, 2007. [X] +1 Accept Shindig for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason : (nb) Gav... = Abstract = Shindig will develop a container and backend server components for hosting OpenSocial applications. = Proposal = Shindig will develop a JavaScript container and implementations of the backend APIs and proxy required for hosting OpenSocial applications. = Background = OpenSocial provides a common set of APIs for social applications across multiple websites. With standard JavaScript and HTML, developers can create social applications that use a social network's friends and update feeds. A social application, in this context, is an application run by a third party provider and embedded in a web page, or web application, which consumes services provided by the container and by the application host. This is very similar to Portal/Portlet technology, but is based on client-side compositing, rather than server. More information can be found about OpenSocial at http://code.google.com/apis/opensocial/ == Rationale == Shindig will provide implementations of an emerging set of APIs for client-side composited web applications. The Apache Software Foundation has proven to have developed a strong system and set of mores for building community-centric, open standards based systems with a wide variety of participants. A robust, community-developed implementation of these APIs will encourage compatibility between service providers, ensure an excellent implementation is available to everyone, and enable faster and easier application development for users. The Apache Software Foundation has proven it is the best place for this type of open development. The Shindig OpenSocial implementation will be able to serve as a reference implementation of the standard. = Current Status = This is a new project. = Meritocracy = The initial developers are very familiar with meritocratic open source development, both at Apache and elsewhere. Apache was chosen specifically because the initial developers want to encourage this style of development for the project. === Community === Shindig seeks to develop developer and user communities during incubation. = Core Developers = The initial set of committers includes folks from several commercial OpenSocial container providers, including Ning, Google, Hi5, and MySpace. We have varying degrees of experience with Apache-style open source development, ranging from none to ASF Members. = Alignment = The developers of Shindig want to work with the Apache Software Foundation specifically because Apache has proven to provide a strong foundation and set of practices for developing standards-based infrastructure and server components. = Known Risks = == Orphaned products == Shindig is new development of an emerging set of APIs. == Inexperience with Open Source == The initial developers include long-time open source developers, including Apache Members. == Homogenous Developers == The initial set of developers is diverse, but are all employed by OpenSocial container providers. Building a more diverse developer community is a high priority for this project. == Reliance on Salaried Developers == The initial group of developers are all employed by potential consumers of the project. Remedying this is a large part of why we want to bring the project to Apache. == Relationships with Other Apache Products == None in particular. == A Excessive Fascination with the Apache Brand == We believe in the processes, systems, and framework Apache has put in place. The brand is nice, but is not why we wish to come to Apache. = Documentation = Google's OpenSocial Documentation: http://code.google.com/apis/opensocial/ Ning's OpenSocial Documentation: http://tinyurl.com/3y5ckx = Initial Source = The initial source will consist of the Javascript container and a Java based backend providing services to the container. The source is being contributed by Google, and will be by a code grant. = External Dependencies = The initial code relies on PHP and the jQuery library. = Required Resources = Developer and user mailing lists A subversion repository A JIRA issue tracker = Initial Committers = Andy Smith (Google) Brian McCallister (Ning) Brian Stoler(Google) Cassie Doll (Google) Dan Bentley (Google) Dan Farino (MySpace) David Glazer(Google) David Harkness (Google) David Sklar (Ning) Doug Coker (Google) Evan Gilbert(Google) Graham Spencer (Google) Jeffrey Regan (Google) John Hjelmstad (Google) John Panzer (Google) Jun Yang(Google) Jussi Myllymaki (Google
RE: [RESULT][PROPOSAL] Log4PHP restart proposal
-Original Message- From: Curt Arnold [mailto:[EMAIL PROTECTED] Sent: Wednesday, 4 July 2007 6:46 AM To: general@incubator.apache.org Subject: [RESULT][PROPOSAL] Log4PHP restart proposal On Jun 29, 2007, at 7:33 AM, Curt Arnold wrote: = Abstract = Revival of the terminated log4php incubation with a new development community and a goal to migrate log4php to PHP 5. Voting has now been open for over 5 days with 3 +1's from Curt Arnold, Jim Jagielski and Bertrand Delacretaz with no other votes. The Logging PMC vote on [EMAIL PROTECTED] supporting the proposal has also concluded with 3 +1's from Curt Arnold, Scott Deboy and Paul Smith and no other votes. As far as I can tell from the process docs, that is sufficient to restart the project. I plan to take the following actions unless there are objections: Modify asf-authorization to add carnold, jim and sdeboy as log4php committers. Request accounts for Knut Urdalen and Alvaro Carrasco (CLA's on file) Investigate the status of Michael Schmitz's CLA. Update log4php project page (and do it right this time, sorry for messing it up when it was terminated). Looks like the page is still there, although not linked to from the side-bar yet. http://incubator.apache.org/projects/log4php.html unless you were talking of the one on logging.apache.org/log4php/ Gav... Request a JIRA project for log4php. Announce votes and actions to [EMAIL PROTECTED] and get things started. Hand off mentoring to either Jim or Scott. - 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] Revised Heraldry commit ACL
-Original Message- From: Ted Leung [mailto:[EMAIL PROTECTED] Sent: Tuesday, 27 March 2007 1:22 AM To: general@incubator.apache.org Subject: Re: [VOTE] Revised Heraldry commit ACL On Mar 26, 2007, at 7:42 AM, Noel J. Bergman wrote: Ted, The list of David Recordon (recordond) Johannes Ernst (jernst) Matt Pelletier (mattpelletier) is a start. I'll also suggest that they be the core of the revised PPMC for Heraldry. However ... Other committers to Ruby PIP are: Dan Quellhorst Hans Granqvist Gary Krall Trotter Cashion Mike Graves They aren't on the proposed ACL because of the lack of a response? I see Yes, those folks are not on the ACL because of the lack of a response. If people didn't care enough to send a single e-mail message indicating their interest, then I doubt seriously whether they will invest the effort needed to get Heraldry running on the right track. Dan Quellhorst eventually replied, and I also see: I would be fine with adding Dan to the ACL Eugene Eric Kim Michael Mell Gav... None of these people were on the original ACL, which were the original committers to the project. These three folks haven't actually contributed anything to the code that we've got. If they are serious about participating, they can do so via the regular committer process. Would you add those four, pending CLAs as necessary? So a starting Community of 7, again pending CLAs. More like a community of 4. A 'community' includes those on the dev list, not just committers/pmc. There are 67 subscribed to heraldry-dev, another 20 to commits@ and 19 to the user@, this IMO is a community. However, you need a working community to get back up and running. I have offered several times to help where I can, but not with the code base at the moment , I don't know enough, but I can help with the website and putting up of docs etc, this is usually regarded as a need in most projects eyes. I have an ICLA already in as I am PMC member for Apache Forrest. However I am not asking for commit status at this stage, if you want my help then I'll submit doc and site patches via Jira and someone else can then take the extra step of applying the patches, it would make more sense that I do it directly but I agree I have not earned any Karma on the project so far. The few people you have so far I would have thought would be better concentrating on getting some more code in that site/docs. Anyway, I'll keep a look out and jump in where I can. Gav... I'm bringing this back to the Incubator PMC for discussion and ultimately, a vote. I would also point out that I am currently the only mentor for Heraldry, and I'm not willing to continue without some other people jumping in to help. Looks like Bill Rowe is willing to help. That still leaves us one mentor short. Id like to hear some opinions from the rest of the Incubator PMC. Ted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date: 3/22/2007 7:44 AM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: IRC Channel?
-Original Message- From: Jukka Zitting [mailto:[EMAIL PROTECTED] Sent: Thursday, 17 August 2006 3:29 PM To: general@incubator.apache.org Subject: Re: IRC Channel? Hi, On 8/17/06, Eelco Hillenius [EMAIL PROTECTED] wrote: If ASF is about people rather than procedures as is regularly stated, a discussion about IRC in open development should be more about 'how' and in the context of individual projects than simply denouncing the technology altogether. +1 Yes, I also echo Eelco's sentiments, forrest like Wicket has been successful in using IRC for nearly a year now to thrash through some Jira Issues, code enhancements and to discuss best ways of doing things etc, ideas get thrown around. No big decisions on new techniques or direction are decided on IRC but are put on dev@ for more discussion and resolution there. I personally have found IRC invaluable in live Q A to get an answer, try it out and respond straight away with yep that worked or no it didn't etc. The lists of course do this in a slower but sure manner also. Forrest also confirm that the Mail lists are the primary source of communication. That said, there is an issue on the future of Forrest IRC sessions, as the usual crew could usually attend, and others not, so we are to discuss a new approach to using IRC. I hope it does not disappear. I think a key question in the how category is how to make IRC (or IM in general) discussions easily accessible to people who weren't there or who want to go back and check what was discussed. If this question is solved, I see no reason not to embrace IM more, but as of now I don't see any good solutions around. Plain IRC logs are clearly not the answer as pointed out by Geir and others. Agree, I can not see any automated method to filter out the 'chatter' from the relevant material to keep. Someone has to fill the role each time to manually go through the logs and do the filtering. The prettying up processing and publish to a web page or wiki can be done in many automated ways when the good stuff remains. Perhaps then, the looking through of IRC material will be easier to do. FWIW I prefer IRC logs to Wiki any day. Gav... BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED] Software craftsmanship, JCR consulting, and Java development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.0/420 - Release Date: 8/16/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [jira] Created: (INCUBATOR-21) Jira required for incubating project Abdera
Should this have gone on @infra Jira request instead? If so let me know. Gav... -Original Message- From: Gavin (JIRA) [mailto:[EMAIL PROTECTED] Sent: Sunday, 18 June 2006 10:15 AM To: general@incubator.apache.org Subject: [jira] Created: (INCUBATOR-21) Jira required for incubating project Abdera Jira required for incubating project Abdera --- Key: INCUBATOR-21 URL: http://issues.apache.org/jira/browse/INCUBATOR-21 Project: Incubator Type: New Feature Reporter: Gavin Priority: Critical Hope this is the right place and that it has not been requested elewhere. Abdera (http://incubator.apache.org/abdera/) would like to have Jira for their project ASAP please. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.0/368 - Release Date: 6/16/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ARI, Atom Reference Implementation [Proposal]
quote who=Dave Johnson What a great idea! The code looks very nice and I'd love to help. - Dave Yes , I agree and hope to join in and dev at some point. James M Snell wrote: Hello, The following is a new project incubation proposal. We welcome your feedback and would like to extend a invitation for participation including mentors. The proposal is also located at http://wiki.apache.org/incubator/AriProposal I see this is now changed, http://wiki.apache.org/incubator/AbderaProposal A couple of other things on thwe Wiki I guess will need changing - 3. Identify the ASF resources to be created 3.1 mailing list(s) atom-ppmc (moderated subscriptions) atom-dev atom-commits atom-user 3.2 Subversion repository https://svn.apache.org/repos/asf/incubator/atom 3.3 Bugzilla Atom With all the talk of being too 'Atom' specific in naming, using it in mailing lists and SVN will be a bit confusing. The initial source for the project is available at: http://www.snellspace.com/public/ari.tar.gz Thank you, - James M Snell [EMAIL PROTECTED] [EMAIL PROTECTED] --- snip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gav... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Getting the Incubator PMC to be more responsive
-Original Message- From: Leo Simons [mailto:[EMAIL PROTECTED] Sent: Monday, 10 April 2006 9:54 PM To: general@incubator.apache.org Subject: Re: Getting the Incubator PMC to be more responsive Still thinking about this... ...just wanted to note that the incubator PMC is responsive for some stuff but not for other stuff. For example * when you raise a generic issue like this you get an answer or some kind of feedback within a few hours or at most a few days. * simpler questions of a FAQ level or the like are usually also answered and usually also answered quickly * for some votes, responses are swift, in abundance, and quite positive (consider the recent vote to graduate jackrabbit) But apparently this is the second time that a please-approve-release-for-activemq vote is left dangling. I don't know exactly what is going on, but its different from general unresponsiveness. I know *I* decided a few weeks ago not to spend any more time at any intersection between the wider geronimo community and the incubation stuff because its become obvious that my opinion on a variety of stuff doesn't mesh well with the apparent consensus within that community. I haven't gone so far as to set up an actual ignore filter on (activemq|wadi|servicemix|...) but I might as well have. I read your message sort-of by accident. Your opinion may not mesh well at the moment, but it needs to be continued to be heard I would have thought. And your vote is valued as is everyone elses. If someone raises a vote should it not be compulsory to vote on it in some kind of way? Maybe other incubator pmc members have a similar mail-reading behaviour. This surely is unacceptable behaviour. Why else is the Incubator PMC here but to sort out EVERY Incubator related Issue. Blocking some issues whilst being active in only what you find interesting is not good is it. Gav... LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 8/04/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jira Usage (was Re: (in)appropriate wiki use)
- Original Message - From: David Crossley [EMAIL PROTECTED] To: general@incubator.apache.org Sent: Thursday, January 19, 2006 11:58 AM Subject: Re: Jira Usage (was Re: (in)appropriate wiki use) | Gav wrote: | | Apologies if I have it wrong here, as I am new to this particular list, but | does anyone | take any notice of the Jira Issues for Incubator site? | My patches and comments needed for me to provide more patches are only a few | days | old, I am used to quick turnaround of patches on other lists so I may be a | bit | premature in thinking I am being ignored. | | You are doing it correctly. | | The only thing is that you will need to wait for some | time for patches to be applied. Committers that are | here are very overworked. Thats cool, now I know. | | Ditto with your questions. I really hope that someone | will answer you. I for one, am busy with other stuff. | | -David Yes you are, so I should assume others have responsibilities in others areas too. I always assume people have main salaried jobs and family too, on the other side of it I assumed it was the job of one or two here to prioritize on getting Jira Issues done etc.. The patches and the answers can wait, no problem. Gav... | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | | -- | No virus found in this incoming message. | Checked by AVG Free Edition. | Version: 7.1.375 / Virus Database: 267.14.20/234 - Release Date: 18/01/2006 | | -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.14.20/234 - Release Date: 18/01/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Jira Usage (was Re: (in)appropriate wiki use)
- Original Message - From: Leo Simons [EMAIL PROTECTED] | There's well over a hundred people with write access to the parts of incubator | SVN where such stuff would live. If there's not enough of those people willing to | handle the apply patch workload for this kind of stuff then we should really be | putting that the incubator is currently closed sign up. Do these 100+ people have access to the Incubator Jira Issues list also ? Apologies if I have it wrong here, as I am new to this particular list, but does anyone take any notice of the Jira Issues for Incubator site? My patches and comments needed for me to provide more patches are only a few days old, I am used to quick turnaround of patches on other lists so I may be a bit premature in thinking I am being ignored. I have commented on what needs to be done to every Issue on Jira for Incubator, and have no doubt that the current list of issues can be cleared up very quickly, there are only a few. (Not all by me though) However, there are some that have been there, sitting patiently with patches at the ready for between 6 months and a year. If my patches sit around for that long, I guess I wont be here to see what happens to them, which is a shame as I came here after hearing a rumour that you might want a bit of help doing this sort of stuff. If I am on the wrong track as to how things work around here, apologies, but without an archive to search through I am playing blind. Is Jira a new thing here or do people not like it and do it another way or ? My time is such that I have the time to browse through Jira and do what I can from it, supplying the relevant patches or info there, asking on-list (referring to Jira) if more info is required. (I am glad to do this whenever I can) I do not really have any more time to go searching for the Issues myself, so Jira would be my first stop after the list. Anyway, maybe I'll hear back ... Gav... -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.14.20/233 - Release Date: 18/01/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (INCUBATOR-12) Process_Description.html navigation improvement
- Original Message - From: David N. Welton (JIRA) general@incubator.apache.org To: general@incubator.apache.org Sent: Monday, January 16, 2006 5:12 PM Subject: [jira] Commented: (INCUBATOR-12) Process_Description.html navigation improvement |[ http://issues.apache.org/jira/browse/INCUBATOR-12?page=comments#action_12362832 ] | | David N. Welton commented on INCUBATOR-12: | -- | | I wouldn't get carried away reworking the whole thing. Just provide a link to where the mailing lists are... | | Cheers, | Dave The link to the mailing lists has been provided by DC, pointing to the /howtoparticipate.html document, unless they have a document of their own, I can't see a sensible way of adding a 'mailing lists' link on the navigation, which is how I interpreted your question. The other changes I proposed are mainly spelling corrections (while the document is being updated elsewhere, may as well fix those too). Point 1 needs confirming whether this should be done, a minor point, but we shouldnt make a link look like a mailto: if it is not. Point 2 needs checking by someone, where are the 'ASF Proposal Pages' now? Regarding changing the order of the Menu Items on the left Nav (re issue subject title), this will also change the order for the rest of the site to match. Despite my verbosity, it seems most pages on this particular site need 'approval' before any changes are made. If someone can just answer the queries I raised, it will not take long for me to make the changes and provide a patch. (if that is what people want) Gav... | | Process_Description.html navigation improvement | --- | | Key: INCUBATOR-12 | URL: http://issues.apache.org/jira/browse/INCUBATOR-12 | Project: Incubator | Type: Improvement | Reporter: David N. Welton | Priority: Minor | Attachments: Process_Description.html.diff | | http://incubator.apache.org/incubation/Process_Description.html | mentions a mailing lists section of this site, yet provides no link, and it is not at all obvious from the left-hand navigation where that might reside. A link should be provided. | Thanks, | Dave | | -- | This message is automatically generated by JIRA. | - | If you think it was sent incorrectly contact one of the administrators: | http://issues.apache.org/jira/secure/Administrators.jspa | - | For more information on JIRA, see: | http://www.atlassian.com/software/jira | | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | | -- | No virus found in this incoming message. | Checked by AVG Free Edition. | Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 14/01/2006 | | -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 14/01/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Outstanding Issues - (was Re: [jira] Updated: (INCUBATOR-12) Process_Description.html navigation improvement)
- Original Message - From: David Crossley [EMAIL PROTECTED] To: general@incubator.apache.org Sent: Saturday, January 14, 2006 7:25 AM Subject: Re: [jira] Updated: (INCUBATOR-12) Process_Description.html navigation improvement | Gav wrote: | The website mentions updating the 'source html' files in site-author ( | http://incubator.apache.org/guides/website.html) which | I have done for this Issue and also INCUBATOR-11, is this the preferred way | here or maybe us the source .xml files | where one exists ? | | That is absolutely correct. As that doc says html | are the sources. That makes it easier for people to edit | and preview, without needing to actually build. | | There are a couple of source files that use xml. | | Thanks for doing stuff like this. No probs. |The whole site needs | a content cleanup. Not something I can do off the cuff unless I spot obvious mistakes. If there are Issues I can patch, then I will. So if anyone sees anything that needs doing, create an Issue. A couple of Issues remain that I have volunteered to Patch if approved. With regards to all outstanding issues, I can summarise here as there aren't many. (But I wont make a habit out of it) INCUBATOR 1 - 'Document Copyright Changes' Copyright Issues and Notice file queries, this issue was raised in Sep 2004 and so is now very old, but no one has yet commented on it. This should be looked at again to see if it is still relevent. If not, close it, if yes then the answers need posting so I or someone else can provide relevent patches. INCUBATOR 2 - 'fixed a few URLs in apollo/hermes/muse STATUS pages' Created 12 Nov 2004, this issue was addressed immediatly with a Patch by Ian Springer. Over a year later and no-one has applied the Patch. A committer needs to address this. INCUBATOR 3 - Move clas.txt to a location accessible by non-members Created 14 May 2005, by mistake, and so this Issue should be Closed as 'Wont Fix' INCUBATOR 4 - better docs for new committer procedure Created 28 May 2005 and addressed immediatly with a Patch. Nearly 8 months later and this patch has not yet been applied. A committer needs to address this. INCUBATOR 5 - status file requirement unclear This Issue addressed by D Crossley 24 Nov 05 and advised to Close 1st Dec 05 by Martin Sebor. This Issue should be Closed as 'Fixed' In addition Martin Sebors' permissions need looking at. INCUBATOR 6 - unable to commit to incubator site dir in SVN Ian Springer reports he has commit access problems. This was on the 24th October 2005. This needs checking to see of this is still current information and if so needs addressing, otherwise Close the Issue. INCUBATOR 7 - STATUS file out of date, confusing David Crossley has addressed this and Martin Sebor said it was OK to close. ?? INCUBATOR 8 - Incubate Tuscany SOA project Placeholder for materials related to Tuscany SOA incubator proposal. Contains ongoing code samples, Issue is therefore current and ongoing. INCUBATOR 9 - Patch to create docs using coat skin Created by R Gardler, and Patch provided. Not sure if this Issue is now complete and needs closing or if more Patches are to come? INCUBATOR 10 - Incubation_Policy.html should specify to use the Incubator PMC I have commented on this today and await approval so I can provide a patch. INCUBATOR 12 - Process_Description.html navigation improvement I have commented on this today and await approval so I can provide a patch. | | -David | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | | -- | No virus found in this incoming message. | Checked by AVG Free Edition. | Version: 7.1.371 / Virus Database: 267.14.17/229 - Release Date: 13/01/2006 | | -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 14/01/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (INCUBATOR-10) Incubation_Policy.html should specify to use the Incubator PMC
If somebody approves any word changes as below I can create a patch if required. Gav... - Original Message - From: David N. Welton (JIRA) general@incubator.apache.org To: general@incubator.apache.org Sent: Sunday, January 08, 2006 1:16 AM Subject: [jira] Created: (INCUBATOR-10) Incubation_Policy.html should specify to use the Incubator PMC | Incubation_Policy.html should specify to use the Incubator PMC | -- | | Key: INCUBATOR-10 | URL: http://issues.apache.org/jira/browse/INCUBATOR-10 | Project: Incubator |Type: Improvement |Reporter: David N. Welton |Priority: Minor | | | This page http://incubator.apache.org/incubation/Incubation_Policy.html | | says: | | Approval by a Sponsor will generally occur only after a vote within the Entity, and will require that the Entity be convinced that the Candidate is appropriate for Incubation. A Sponsor may be one of: | |* the Board of the Apache Software Foundation; |* a Top Level Project (TLP) within the Apache Software Foundation (where the TLP considers the Candidate to be a suitable sub-project); or |* the Incubator PMC. | | Although in practice it appears that the Incubator PMC is the preferred sponsor for projects that would end up a TLP. The site could say something like this: | | Where a top level project is not an appropriate sponsor, the Incubator PMC is the preferred sponsor. Requests should be sent to the general (AT) incubator.apache.org mailing list. | | | -- | This message is automatically generated by JIRA. | - | If you think it was sent incorrectly contact one of the administrators: | http://issues.apache.org/jira/secure/Administrators.jspa | - | For more information on JIRA, see: | http://www.atlassian.com/software/jira | | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | | -- | No virus found in this incoming message. | Checked by AVG Free Edition. | Version: 7.1.371 / Virus Database: 267.14.15/223 - Release Date: 6/01/2006 | | -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.17/228 - Release Date: 12/01/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AJAX Toolkit Proposal - Updated
Good Advice either way :) Gav... | Sam Ruby wrote: | | Try NOT to ever get defensive. | | Even when you accidentally copy a public mailing list when you meant to | send a private reply. ;-) | | - Sam Ruby | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | | -- | No virus found in this incoming message. | Checked by AVG Free Edition. | Version: 7.1.371 / Virus Database: 267.14.17/226 - Release Date: 10/01/2006 | | -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.17/226 - Release Date: 10/01/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
