Qpid mailing lists
The Qpid project (formerly known as Blaze and Glasgow) mailing lists are now set up. Please subscribe to the dev list if you are interested in following or participating in the project. A commits list is also set up for those wanting to track changes to the repository. Here's the info: qpid-dev at incubator.a.o qpid-commits at incubator.a.o As with any Apache mailing list, to subscribe, simply send a blank email to *-subscribe, e.g. qpid-dev-subscribe at incubator.a.o. Cliff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: [VOTE] Publish Lokahi M01
On 8/28/06, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote: robert burrell donkin wrote: > On 8/11/06, Steve Toback <[EMAIL PROTECTED]> wrote: >> The Lokahi community voted on and has approved a proposal to release >> Lokahi M01. Pursuant to the Releases section of the Incubation Policy >> we would now like to request the permission of the Incubator PMC to >> publish the tarball on the Lokahi Download page. > > there are some files which IMO could and should have license headers but > do not: > > * most of the files in conf > * most of the files in database > * docs/setup.html Robert, was this an objection to the M01 tarball, or something to address before M02? i'm not -1 on M01 but IMHO the license header issue should be addressed before the release there are some issues around license headers and sometimes a project needs to take a view about how they want to apply policy. for example, see http://mail-archives.apache.org/mod_mbox/incubator-general/200607.mbox/[EMAIL PROTECTED] (at the bottom) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xml -> doap + xml - take #1
robert burrell donkin wrote: > On 8/26/06, david reid <[EMAIL PROTECTED]> wrote: >> Leo Simons wrote: >> > I suggest something like >> > >> > >> http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/doap-converter >> >> >> Is this really the right place? How do the files get from this set of >> directories to site-publish? > > i'm not sure that i understand why the stylesheets need to move anywhere > > for the generated sitemap over in www.apache.org, the stylesheets are > in xdocs/stylesheets/texen. the document is generated in the work > directory and then processed. the results are generated into the docs > directory. > >> Before I add any files I want to be sure >> that I won't add a directory that will end up creating a problem. > > i don't think that there will be a problem (but maybe i'm missing the > point...) I don't have karma to commit anyways, so it's a mute point. *shrug* I have the files done and the svn commit ready to roll. I'll post them online somewhere when I get home. david - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [policy] incubating projects and maven repositories v1.0
On Sun, Aug 27, 2006 at 12:44:58PM -0400, Jason van Zyl wrote: > There was discussion that incubator repository would not be sync'd to > the central repository but I don't really see much point in this. A > few folks with incubating projects have voiced concerns that they > don't want to see their projects be taken out of circulation in the > central repository because they are incubating. If each and every > incubating project has a version for each artifact like that above > then it will be fairly clear that it's from the incubator. Moreso > then if you just had a repository definition pointing at the > incubator repository. > > Also someone may make an repository request to place an incubator > artifact in the central repository and at this point a policy > mandated here would conflict with someone's right to redistribute > artifacts created in the incubator. I don't really want to get into > the business of policing repository requests. I think it is in the > best interests of the incubating projects to have the incubator > repository sync'd to Maven's central repository. The source of > artifacts for incubating projects is clear from the version so I > don't think there will be any confusion by consumers of these > artifacts and as such I don't really see any downside to allowing the > sync to Maven's central repository. > > Thoughts? "central repository" is ibiblio.org right? Eg not an ASF machine? I think its not up to the incubator to dictate policies on what external parties should and should not do with our software. It all comes back to being clear to users and providing a consistent message, and I think the steps we agreed on here (seperate repo, clear versioning, incubation notices on website and in readme) are sufficient, and I doubt we should go any further than that. If other ASF projects depend on projects that depend on projects that depend on incubating projects that are published on the ibiblio site and that is not sufficiently clear for users of that project, then that's not the responsibility of the incubator pmc to fix. IOW, I don't really want to to get into the business of policing anything but the bits we're actually responsible for policing :) So I'll withold actual thoughts (which would've been along the lines of "centralized storage is so 1990s") ;) LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [policy] incubating projects and maven repositories v1.0
On 28 Aug 06, at 11:44 AM 28 Aug 06, Leo Simons wrote: On Sun, Aug 27, 2006 at 12:44:58PM -0400, Jason van Zyl wrote: There was discussion that incubator repository would not be sync'd to the central repository but I don't really see much point in this. A few folks with incubating projects have voiced concerns that they don't want to see their projects be taken out of circulation in the central repository because they are incubating. If each and every incubating project has a version for each artifact like that above then it will be fairly clear that it's from the incubator. Moreso then if you just had a repository definition pointing at the incubator repository. Also someone may make an repository request to place an incubator artifact in the central repository and at this point a policy mandated here would conflict with someone's right to redistribute artifacts created in the incubator. I don't really want to get into the business of policing repository requests. I think it is in the best interests of the incubating projects to have the incubator repository sync'd to Maven's central repository. The source of artifacts for incubating projects is clear from the version so I don't think there will be any confusion by consumers of these artifacts and as such I don't really see any downside to allowing the sync to Maven's central repository. Thoughts? "central repository" is ibiblio.org right? Correct. Eg not an ASF machine? Correct. I think its not up to the incubator to dictate policies on what external parties should and should not do with our software. It all comes back to being clear to users and providing a consistent message, and I think the steps we agreed on here (seperate repo, clear versioning, incubation notices on website and in readme) are sufficient, and I doubt we should go any further than that. If other ASF projects depend on projects that depend on projects that depend on incubating projects that are published on the ibiblio site and that is not sufficiently clear for users of that project, then that's not the responsibility of the incubator pmc to fix. IOW, I don't really want to to get into the business of policing anything but the bits we're actually responsible for policing :) So I'll withold actual thoughts (which would've been along the lines of "centralized storage is so 1990s") ;) LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Jason van Zyl [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[doc] are board resolutions ok for http://incubator.apache.org/official/...?
i have one or two board resolutions that it would be a good idea to bring to the attention of new podlings. since it's board policy, i think it'd be better to link to html documents containing the actual content rather a second hand account. can anyone think of any reason why board resolutions should be private...? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [doc] are board resolutions ok for http://incubator.apache.org/official/...?
On 8/28/06, robert burrell donkin <[EMAIL PROTECTED]> wrote: i have one or two board resolutions that it would be a good idea to bring to the attention of new podlings. since it's board policy, i think it'd be better to link to html documents containing the actual content rather a second hand account. can anyone think of any reason why board resolutions should be private...? http://www.apache.org/foundation/board/calendar.html (They should generally be treated as private until the minutes are approved and posted there.) HTH. -- justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-41) [policy neutral] cut unnecessary preamble
[policy neutral] cut unnecessary preamble - Key: INCUBATOR-41 URL: http://issues.apache.org/jira/browse/INCUBATOR-41 Project: Incubator Issue Type: Improvement Components: policy Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin The policy document can only be changed by a VOTE. The prose should therefore be concise. The preamble to the Incubator Activities adds nothing substantial. This patch cuts that unnecessary paragraph. This change is intended to be policy neutral. Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 437587) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -268,9 +268,6 @@ Incubation Activities - The following sections detail the minimum activities that must be -undertaken by the various parties during an Incuabation process. - Setting Up a New Podling Once the Podling and Mentor have been accepted by the Incubator PMC, Index: site-publish/incubation/Incubation_Policy.html === --- site-publish/incubation/Incubation_Policy.html (revision 437587) +++ site-publish/incubation/Incubation_Policy.html (working copy) @@ -357,9 +357,6 @@ -The following sections detail the minimum activities that must be -undertaken by the various parties during an Incuabation process. - Setting Up a New Podling -- 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]
[jira] Created: (INCUBATOR-42) [policy neutral] consistent use of term
[policy neutral] consistent use of term --- Key: INCUBATOR-42 URL: http://issues.apache.org/jira/browse/INCUBATOR-42 Project: Incubator Issue Type: Improvement Components: policy Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin The patch tightens the prose and uses language more consistently with the rest of the revisions. Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 437587) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -273,13 +273,15 @@ Setting Up a New Podling -Once the Podling and Mentor have been accepted by the Incubator PMC, -the following activities SHOULD take place : + +Once a proposal has been accepted +and the podling created +a Mentor SHOULD initiate the creation of: - creation of "project status" page (see below); - creation of mailing lists; - creation of SVN-space; + the project status page; + the mailing lists; + the repository space; Incubator PMC mandating a helper Mentor Index: site-publish/incubation/Incubation_Policy.html === --- site-publish/incubation/Incubation_Policy.html (revision 437587) +++ site-publish/incubation/Incubation_Policy.html (working copy) @@ -364,13 +364,15 @@ Setting Up a New Podling -Once the Podling and Mentor have been accepted by the Incubator PMC, -the following activities SHOULD take place : + +Once a proposal has been accepted +and the podling created +a Mentor SHOULD initiate the creation of: - creation of "project status" page (see below); - creation of mailing lists; - creation of SVN-space; + the project status page; + the mailing lists; + the repository space; Incubator PMC mandating a helper Mentor -- 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]
[jira] Created: (INCUBATOR-43) [policy neutral] cut line which doesn't make much sense
[policy neutral] cut line which doesn't make much sense --- Key: INCUBATOR-43 URL: http://issues.apache.org/jira/browse/INCUBATOR-43 Project: Incubator Issue Type: Improvement Components: policy Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin Cuts a line which seems to make very little sense within the context. This should be policy neutral since the line makes very little sense in it's context. Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 437587) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -281,9 +281,6 @@ creation of mailing lists; creation of SVN-space; - - Incubator PMC mandating a helper Mentor - Your project's mentors are able to undertake many of the setup tasks. See notes about how to Index: site-publish/incubation/Incubation_Policy.html === --- site-publish/incubation/Incubation_Policy.html (revision 437587) +++ site-publish/incubation/Incubation_Policy.html (working copy) @@ -372,9 +372,6 @@ creation of mailing lists; creation of SVN-space; - - Incubator PMC mandating a helper Mentor - Your project's mentors are able to undertake many of the setup tasks. See notes about how to -- 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]
[jira] Created: (INCUBATOR-44) [policy neutral] cut discursive material better handled in the guides
[policy neutral] cut discursive material better handled in the guides - Key: INCUBATOR-44 URL: http://issues.apache.org/jira/browse/INCUBATOR-44 Project: Incubator Issue Type: Improvement Components: policy Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin Cuts non-policy discursive material that is better located in the guides. This change is intended to be policy neutral. Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 437587) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -285,21 +285,9 @@ Incubator PMC mandating a helper Mentor - Your project's mentors are able to undertake many of the setup - tasks. See notes about how to - http://www.apache.org/dev/reporting-issues.html";>request project resources - such as new committer accounts and new mailing lists. - (Note that a committer account will not be created - http://www.apache.org/dev/pmc.html#newcommitter";>until the - Contributor License Agreement (CLA) has been recorded.) - - - Your project committers/PPMC members need to become familiar with - the http://www.apache.org/dev/";>ASF Infrastructure information - and in particular the - http://www.apache.org/dev/#pmc";>PMC notes. - Also see the Incubator PMC Guide. - + See http://www.apache.org/dev/reporting-issues.html";>how to + request project resources. + Ongoing Activities Index: site-publish/incubation/Incubation_Policy.html === --- site-publish/incubation/Incubation_Policy.html (revision 437587) +++ site-publish/incubation/Incubation_Policy.html (working copy) @@ -376,21 +376,9 @@ Incubator PMC mandating a helper Mentor - Your project's mentors are able to undertake many of the setup - tasks. See notes about how to - http://www.apache.org/dev/reporting-issues.html";>request project resources - such as new committer accounts and new mailing lists. - (Note that a committer account will not be created - http://www.apache.org/dev/pmc.html#newcommitter";>until the - Contributor License Agreement (CLA) has been recorded.) - - - Your project committers/PPMC members need to become familiar with - the http://www.apache.org/dev/";>ASF Infrastructure information - and in particular the - http://www.apache.org/dev/#pmc";>PMC notes. - Also see the Incubator PMC Guide. - + See http://www.apache.org/dev/reporting-issues.html";>how to + request project resources. + Ongoing Activities -- 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]
[jira] Created: (INCUBATOR-45) [policy neutral] improvement to wording in ongoing activities and add link to referenced section
[policy neutral] improvement to wording in ongoing activities and add link to referenced section Key: INCUBATOR-45 URL: http://issues.apache.org/jira/browse/INCUBATOR-45 Project: Incubator Issue Type: Improvement Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin improvement to wording in ongoing activities and add link to referenced section. It is hoped that these changes are policy neutral. Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 437587) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -303,10 +303,12 @@ Ongoing Activities -The progress of a Podling SHALL be tracked in a "project status" file -which SHALL be stored in the incubator/site-author/projects/ -repository and so become available at - +The progress of a Podling SHALL be tracked in a "project status" document. +This SHALL be stored in + +http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/ + +and so become available at http://incubator.apache.org/projects/";>http://incubator.apache.org/projects/ @@ -316,21 +318,16 @@ status of setup tasks; - all exit criteria (see section - -Exiting the Incubator -below); - + all exit criteria (see +Exiting the Incubator); status of Podling against exit criteria. -The Mentor MUST ensure that the "project status" document is up to -date at all times. See - +The Mentors MUST ensure that the "project status" document is up to +date at all times. See these instructions . - Index: site-publish/incubation/Incubation_Policy.html === --- site-publish/incubation/Incubation_Policy.html (revision 437587) +++ site-publish/incubation/Incubation_Policy.html (working copy) @@ -396,10 +396,12 @@ Ongoing Activities -The progress of a Podling SHALL be tracked in a "project status" file -which SHALL be stored in the incubator/site-author/projects/ -repository and so become available at - +The progress of a Podling SHALL be tracked in a "project status" document. +This SHALL be stored in +http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/";> +http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/ + +and so become available at http://incubator.apache.org/projects/";>http://incubator.apache.org/projects/ @@ -409,21 +411,16 @@ status of setup tasks; - all exit criteria (see section - -Exiting the Incubator -below); - + all exit criteria (see +Exiting the Incubator); status of Podling against exit criteria. -The Mentor MUST ensure that the "project status" document is up to -date at all times. See - +The Mentors MUST ensure that the "project status" document is up to +date at all times. See these instructions . - -- 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]
Re: [VOTE] Accept Wicket into the Incubator
Oops. I guess I should vote :-) [X] +1 Accept Wicket as an Incubator podling Upayavira Upayavira wrote: > Folks, > > Without further ado (and before my PC dies again), I'd like to call a > vote on accepting Wicket into the incubator. > > As previously mentioned, the Wicket community held a unanimous vote to > approach the incubator. The vote thread is here: > > http://www.mail-archive.com/wicket-develop@lists.sourceforge.net/index.html#08808 > > Below is the complete proposal for this project. > > So, please cast your votes: > > [ ] +1 Accept Wicket as an Incubator podling > [ ] 0 Don't care > [ ] -1 Reject this proposal for the following reason: > > Regards, Upayavira > > - o - > > = Wicket Proposal = > > This proposal outlines the creation of a new top-level Wicket project > within the Apache Software Foundation. > > == Rationale == > > Wicket is a unique web application framework that focusses on bringing > plain object oriented Java programming to the web tier. It is unique in > it's focus amongst the (many) web frameworks that exist today. Due to > it's unmanaged nature and reliance on plain Java, it is a very good > match for frameworks like OSGi and Eclipse RSP. Wicket has been gaining > a very steady increase in popularity, and with two books coming out and > vastly improved new releases we are working on, we expect this trend to > continue. We consider moving to Apache being an additional boost, and we > hope it will open the way for possible future cooperation with other > Apache projects. > > The maintainers of Wicket are interested in joining the Apache Software > Foundation for several reasons: > > * Apache has a widely recognized name, which will help Wicket get an > increased visibility and acceptance. > > * We'd like to enjoy the benefits of utilizing Apache's infrastructure > and legal protection. > > * Most team members have been enthusiastic users of Apache software for > many years and would like to be part of the family with it's get > togethers etc. > > * It might open the door for cooperation with other projects, such as > Felix or Jetspeed. > > * Apache seems to attract great communities around its projects, we > hope joining Apache will help as make our growing community even bigger. > > * We hope to contribute to Apache's ongoing success by delivering an > innovative, dynamic project with an enthusiastic user base. > > == Criteria == > > === Community === > > Wicket has striven to foster a diverse community that is open to > everyone. It is released > under a non-reciprocal license (Apache License 2.0) to encourage the > maximum possible adoption by all > potential users and developers. The Wicket community encourages > suggestions and > contributions from any potential user, and more developers have joined > as contributors > since the project's inception in 2004. > > === Meritocracy === > > Wicket was originally created by Jonathan Locke in April 2004. Then it > was taken over in September 2004 by Eelco Hillenius, Johan Compagner and > Martijn Dashorst. Chris Turner and Juergen Donnerstag were invited to > join that same week based on their contributions and discussions. The > project now has committers and users from around the world, and Jonathan > Locke is back with the project again. The newer committers of the > project joined in subsequent years by initially submitting patches, then > having commit privileges for some of the applications (wicket-stuff), > and then privileges over a larger range of applications. The project > members understand the importance of letting motivated individuals > contribute to the project after they have proven themselves. > > == Scope of Sub projects == > > Wicket is distributed as one large subversion tree, but contains several > distinct parts: the core framework, a couple of extensions project that > are endorsed by the core developers, an examples project (which includes > a component reference), a quick start project and a developer sandbox. > One of the extensions projects, called wicket-extensions, has a dual > purpose. The first is to ensure the core project does not get too large, > while still having a place to put interesting components and utility > classes. The second purpose of that project is to provide a place where > components can prove themselves before potentially graduating to the > core project. > > Whilst Wicket has these various subprojects, access to the subversion > tree is maintained with a single ACL. Once voted in as a committer, an > individual will have access to the entire tree, and trust is used to > ensure that they only touch the parts of the tree that they are > knowledgeable enough to change. > > == Features == > > Wicket is a Java web application framework that takes simplicity, > separation of concerns and ease of development to a whole new level. > Wicket pages can be mocked up, previewed and later revised using > standard WYSIWYG HT
[RESULT] [VOTE] Accept Wicket into the Incubator
The vote has now, IMO, had enough time to run. To summarise, we had 8 binding +1s, from Leo Simons, Alex Karasulu, Jason van Zyl, Justin Erenkrantz, Don Brown, Yoav Shapira, Robert Burrell Donkin, Upayavira, and one binding -0 from Greg Stein. We also had eight non-binding +1s. This means that this proposal has passed, and Wicket is now free to join the Apache Incubator. Welcome Wicket! Some ICLAs have already started rolling in. I shall now get on with requesting the necessary infrastructure. Regards, Upayavira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] Accept Wicket into the Incubator
Welcome Wicket! Thanks a lot everyone! Looking forward to start incubation. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] approve the m1 release of Trinidad's Maven plugins
The Trinidad community voted on and approved to release the the maven plugins as a milestone1 release. These plugins are required for the maven build of the "core" code of the Trinidad Podling. To fulfill the incubator guides, we like to ask you guys, the Incubator PMC, for a permission to release those maven plugins. The vote has been tracked at [1], see it for the results. (three binding +1 and one non-binding +1) The plugins are documented at [2] and our release notes inculde the bugs that have been addressed ([3]). The plugins are available as source and bin inside the incubator m2 repo (see [4]). Thanks Matthias [1] http://mail-archives.apache.org/mod_mbox/incubator-adffaces-dev/200608.mbox/ajax/[EMAIL PROTECTED] [2] http://incubator.apache.org/adffaces/plugins/index.html [3] http://wiki.apache.org/myfaces/ADF_Faces/plugins_release_candidate_m1 [4] http://people.apache.org/repo/m2-incubating-repository/org/apache/myfaces/trinidadbuild/ -- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] Accept Wicket into the Incubator
+1 :) -Igor On 8/28/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > Welcome Wicket! Thanks a lot everyone! Looking forward to start incubation. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] Accept Wicket into the Incubator
Congratulations and good luck to the wicket team ;) Yoav On 8/28/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote: +1 :) -Igor On 8/28/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > Welcome Wicket! > > Thanks a lot everyone! Looking forward to start incubation. > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] Accept Wicket into the Incubator
Yoav Shapira wrote: Congratulations and good luck to the wicket team ;) +1 (binding) :) Alex Yoav On 8/28/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote: +1 :) -Igor On 8/28/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > Welcome Wicket! > > Thanks a lot everyone! Looking forward to start incubation. > > Eelco > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: what wicket is (was: Re: [VOTE] Accept Wicket into the Incubator)
> The model sounds cool, but I don't happen to like it. Fair enough. :-) There are several projects in the Incubator for which I could personally say the same thing. But other ASF Members like them, and that's all good. :-) With respect to Wicket, well I happen to like JavaServer Pages, so you can imagine my thoughts on the topic. ;-) But then see above. :-) --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for a new incubation project: Unstructured Information Management Architecture - UIMA
Hi Brian - Yes, this is the framework that we discussed when you visited the Hawthorne Research lab a couple of years ago. It has grown since then, both in the number of users and in the components that "plug-in". And, you're right, it did originally grow out of a real need to bring together the researchers working in this field, and allow them to benefit by being able to easily build on each other's work. -Marshall Brian McCallister wrote: On Aug 25, 2006, at 4:07 AM, Leo Simons wrote: What does it *do*? I believe it is basically a big, pluggable, harness for analyzing and annotating streams of arbitrary data, if this is the same thing I talked with a bunch of folks about (including Martin, I believe) a couple years ago at Hawthorne. I think it actually grew out of a real need in the research community - lots of cool tools were being built to do unstructured information analysis and none of them could be used together. -Brian ps: I may also be totally wrong. My guesstimate is based on a couple hours of conversations a few years ago. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
