Empire-DB Incubation Status
Hi, Current status: - ICLAS for Rainer, Matthew and Manuel have been received - Code grant has been received Open items: - CCLA for esteam has not yet been received (strictly speaking that is optional but as Empire-DB has been developed largely inside esteam, it would make me feel better to get a CCLA). - ICLA for Jörg has not yet been received - Thomas has not yet been added to the Incubator PMC - Apache account names for Rainer, Matthew, Manuel and Jörg needed (see http://www.apache.org/dev/new-committers-guide.html#cla for reference on already taken names) - Open Tickets: INFRA-1673, INFRA-1674, INFRA-1675, INFRA-1676, INFRA-1677, INFRA-1678 Ciao Henning - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Empire-DB Incubation Status
Hi Henning, Jörg has sent his CLA to the secretary last Wednesday - you and I were on CC. We have sent the CCLA together with the Software Grant (i.e. same mail - different attachment) also last Wednesday. You were also on CC. But I will now send the CCLA again. Apache account names: For me doebele (or rdoebele). Matthew is not in today. But I am sure bond (or mbond) is fine. I am convinced that Jörg and Manuel would go for the same scheme. Thanks and best regards, Rainer -Ursprüngliche Nachricht- Von: Henning Schmiedehausen [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 15. Juli 2008 10:57 An: general@incubator.apache.org Cc: Rainer Döbele; Matthew Bond; Jörg Reiher; Manuel Gamerdinger; Thomas Fischer; Martijn Dashorst Betreff: Empire-DB Incubation Status Hi, Current status: - ICLAS for Rainer, Matthew and Manuel have been received - Code grant has been received Open items: - CCLA for esteam has not yet been received (strictly speaking that is optional but as Empire-DB has been developed largely inside esteam, it would make me feel better to get a CCLA). - ICLA for Jörg has not yet been received - Thomas has not yet been added to the Incubator PMC - Apache account names for Rainer, Matthew, Manuel and Jörg needed (see http://www.apache.org/dev/new-committers-guide.html#cla for reference on already taken names) - Open Tickets: INFRA-1673, INFRA-1674, INFRA-1675, INFRA-1676, INFRA-1677, INFRA-1678 Ciao Henning - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Empire-DB Incubation Status
They have not yet been recorded; they are probably still in the secretary queue. No reason to worry. If they don't show up in a week or so, I will ping secretary. Me getting them is fine, but as long as they are not recorded by the secretary, it does not count. :-) Ciao Henning On Tue, 2008-07-15 at 11:16 +0200, Rainer Döbele wrote: Hi Henning, Jörg has sent his CLA to the secretary last Wednesday - you and I were on CC. We have sent the CCLA together with the Software Grant (i.e. same mail - different attachment) also last Wednesday. You were also on CC. But I will now send the CCLA again. Apache account names: For me doebele (or rdoebele). Matthew is not in today. But I am sure bond (or mbond) is fine. I am convinced that Jörg and Manuel would go for the same scheme. Thanks and best regards, Rainer -Ursprüngliche Nachricht- Von: Henning Schmiedehausen [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 15. Juli 2008 10:57 An: general@incubator.apache.org Cc: Rainer Döbele; Matthew Bond; Jörg Reiher; Manuel Gamerdinger; Thomas Fischer; Martijn Dashorst Betreff: Empire-DB Incubation Status Hi, Current status: - ICLAS for Rainer, Matthew and Manuel have been received - Code grant has been received Open items: - CCLA for esteam has not yet been received (strictly speaking that is optional but as Empire-DB has been developed largely inside esteam, it would make me feel better to get a CCLA). - ICLA for Jörg has not yet been received - Thomas has not yet been added to the Incubator PMC - Apache account names for Rainer, Matthew, Manuel and Jörg needed (see http://www.apache.org/dev/new-committers-guide.html#cla for reference on already taken names) - Open Tickets: INFRA-1673, INFRA-1674, INFRA-1675, INFRA-1676, INFRA-1677, INFRA-1678 Ciao Henning - 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: [DISCUSS] Do we really need an incubator?
On Mon, 2008-07-07 at 17:06 -0700, Roy T. Fielding wrote: Yes, it would be nice if Maven was more secure, properly checked signatures, and properly delegated namespaces so that third-parties would be unable to add artifacts within other org's trees. None of those issues are specific to incubator. In the light of these reports: http://www.cs.arizona.edu/people/justin/packagemanagersecurity/attacks-on-package-managers.html http://www.heise.de/newsticker/Bericht-Paket-Management-Systeme-unter-Linux-nur-bedingt-vertrauenswuerdig--/meldung/110908/ the question on attacks on the maven repository is probably no longer how but only when. These are attacks on Linux repositories, which might be larger and more distributed than the maven repos, but the jackpot of cracking *the* central Java artifact distribution center would probably be bigger than getting a few thousand Linux systems to run a repo delivered backdoor. This is definitely an issue that needs resolving sooner than later. Ciao Henning - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Incubator Wiki policy (was: Re: A zone!)
On Tue, 2008-07-15 at 11:19 +0200, Chris Chabot wrote: If only life was that easy. The party line message we received was This wiki is for committers only, and you have to request access first, this due to capacity problems. Well, there is no reason why you can't vote in people as documentation committers. The party line might be a bit unclear here. If you use the Confluence Wiki as the web site generator like e.g. Geronimo does (create your web site on the wiki, then use the export plugin to export a static version of the site), then everyone allowed to write on that wiki must have signed a CLA. They don't need to be committers, but they must have signed a CLA. However what i think we -want- from a wiki is what makes wiki's great in general ... the fact that anyone can edit and add documentation to it :) (with a proper amount of reviewing moderation happening where required ofc. AFAIK, those limitations are not for the regular Wikis under wiki.apache.org (which are MoinMoin wikis). There could be a few special incubator rules, too. :-) Ciao Henning -- Chris On Jul 15, 2008, at 11:16 AM, Henning Schmiedehausen wrote: Getting a Wiki is as simple as requesting either a MoinMoin or a Confluence Wiki from infra. According to http://cwiki.apache.org/confluence/display/SHINDIGxSITE/Index there seems to be a Wiki set up already. :-) Ciao Henning [Cutting down the Cc list a bit] On Tue, 2008-07-15 at 10:46 +0200, Chris Chabot wrote: What I'm still very hopeful to see is a Wiki system (any flavor will do) for Shindig. The lack of documentation and possibilities for people to contribute too- has really held our adoptation back a bit, and caused many duplicate threads on the same subjects to happen. On the other hand i remember infrastructure@ saying that a zone should not be used for anything important? Thoughts? -- Chris On Jul 15, 2008, at 10:33 AM, Kevin Brown wrote: [+shindig-dev, This doesn't belong on shindig-private] A sample running on ASF infrastructure probably isn't going to happen. Continuous integration will, but it's not really reasonable to expect apache infrastructure to maintain the kind of secure setup that an opensocial container needs, and it'd be far too easy for someone to screw it up to subject said infrastructure to those kinds of security risks. There's really no strong reason for running a shindig build on apache infrastructure, and that wasn't the reason for requesting the zone in the first place. On Mon, Jul 14, 2008 at 10:25 PM, Dan Peterson [EMAIL PROTECTED] wrote: (bcc: infra-private) Shindig-private, can someone summarize and get this ball moving on shindig-dev? It'd be nice to have the sample running on Apache's infrastructure with periodic builds. Thanks, -Dan On Thu, Jul 10, 2008 at 5:14 PM, Joe Schaefer [EMAIL PROTECTED] wrote: Can we please move this conversation about the domain name off infra-private now, and put it on shindig-dev instead? Thanks. --- On Thu, 7/10/08, Brian Eaton [EMAIL PROTECTED] wrote: From: Brian Eaton [EMAIL PROTECTED] Subject: Re: A zone! To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], Ben Laurie [EMAIL PROTECTED] Date: Thursday, July 10, 2008, 6:12 PM Why have shindig in the name? This is only used for rendering iframes, it never shows up in the URL bar at all. On Thu, Jul 10, 2008 at 3:03 PM, Henning Schmiedehausen [EMAIL PROTECTED] wrote: How about shindiggadgets.org ? On Thu, 2008-07-10 at 14:59 -0700, Brian Eaton wrote: On Thu, Jul 10, 2008 at 2:51 PM, Henning Schmiedehausen [EMAIL PROTECTED] wrote: Let's go with shindigcontainer.org or apache-shindig.org. Everyone will know what is meant. Will they? To me apache-shindig.org means This is code provided by the Apache Shindig project. That's not true at all for gadgets. I'm still leaning towards amodules.org. Nothing Apache or Shindig branded, this is third-party code. -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | JEE, Linux, Unix 91054 Buckenhof, Germany -- +49 9131 506540 | Apache Java Software Open Source Consulting, Development, Design| INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 Gesellschaftssitz: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen char name_buf[257]; /* max unix filename is 256, right? */ -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | JEE, Linux, Unix 91054 Buckenhof, Germany -- +49 9131 506540 | Apache Java Software Open Source Consulting, Development, Design| INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 Gesellschaftssitz: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen
Re: [VOTE] Approve hotfix 1 for Apache UIMA v2.2.2-incubating
+1 -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Tashi
Matthieu, * The sponsoring entity is the Incubator so I'm guessing you're shooting for graduating as a TLP. What kind of interactions do you foresee with Hadoop for example? We talked with Doug Cutting about whether to shoot for a TLP or a subproject under Hadoop. We decided ultimately to go the TLP route because Tashi and Hadoop are at different levels in the stack. However, we see Hadoop as one of the important applications running on Tashi virtual clusters, so the two projects are quite complementary. * IIC Tashi is only about management, not about the underlying storage/computing technology. Is that correct? And if so which ones do you plan to integrate with? Yes, that's correct. We plan to integrate with the major VMMs, such as Xen, Linux KVM and VMWare. For storage, we're looking at integrating with HDFS, pVFS and later pNFS when it becomes more mature.An important goal is to provide the hooks and interfaces that allow any DFS and VMM vendor to integrate with the system. * I can't help asking for more technical details. What's the implementation language for your POC code? What are the non-proprietary interfaces you're thinking of? The POC code is a couple of thousand lines of original Python code. Major components are cluster manager (cm), which runs on one of the cluster nodes, a node manager (nm), which runs on each of the other physical cluster nodes, a simple db on the cluster manager for configuration data, and some client utilities. We're really thinking hard about interfaces now, but don't have clear definitions yet. The kinds of things wer are thinking about are interfaces between the client and cm and cm and nm for manipulating starting, starting, and migrating vms, interfaces for some kind of event/messaging system for monitoring and reporting system state to the cm and client, interfaces between the cm/nm and storage system to allow the cm to do storage-aware scheduling of vms, interfaces to power management and system management hardware features, and possibly interfaces for federating different Tashi clusters. Thanks, Dave -- -- David O'Hallaron -- Director, Intel Research Pittsburgh -- Assoc Prof of CS and ECE, Carnegie Mellon University -- http://www.cs.cmu.edu/~droh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][RESULT] Approve hotfix 1 for Apache UIMA v2.2.2-incubating
The vote runs for more than 72 hours and we have enough +1 votes to pass. Vote result: +1 Ant Elder +1 Bertrand Delacretaz +1 Ken Coar No 0 or -1 votes received. The vote passes. Thanks all for voting! -- Michael Michael Baessler wrote: The Apache UIMA committers ask the Apache Incubator PMC for permission to publish a hotfix for the UIMA core release v2.2.2-incubating. The hotfix release fp1 contains fixes for two UIMA memory issues of release version 2.2.2-incubating. The release just ships the jar that has been modified and a readme that contains the hotfix information. LICENSE, NOTICE, and DISCLAIMER files are inside the Jar. The fixes made for this hotfix are based on a UIMA v2.2.2 branch with a separate tag in SVN. Release tag: http://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-2.2.2/uimaj-2.2.2-fp1-02 Hotfix source: http://svn.apache.org/repos/asf/incubator/uima/uimaj/branches/uimaj-2.2.2-01 We had a vote on uima-dev that resulted in 6 binding +1s (all the committers) and no 0s or -1s. The vote thread is here: http://www.mail-archive.com/[EMAIL PROTECTED]/msg07527.html Please review the release candidate at: people.a.o/~mbaessler/uima-2.2.2-fp1/02 The package is just provided as zip since all the content (one jar) is platform independent. The KEYS file can be found in the SVN at: http://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk/uimaj-distr/src/main/readme/KEYS Please vote: [ ] +1 Accept to release Apache UIMA 2.2.2-fp1-incubating [ ] -1 No, because Thanks! -- Michael - 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] Release Apache UIMA CasEditor-2.2.2-incubating
+1 -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache UIMA-AS 2.2.2-incubating
+1 -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Click for Incubation
+1 On Jul 14, 2008, at 7:14 AM, Henning Schmiedehausen wrote: This vote will run until Monday, July 21st, 2008. [ ] +1 Accept Click for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason: = Click Proposal = This proposal specifies the migration of Click web application framework to the Apache Software Foundation as a Top Level Project. http://click.sourceforge.net/ == Rationale == Click is a modern J2EE web application framework released under the Apache License 2.0. It takes a component and page orientated approach to web applications with its main goals being ease of use and low barrier to entry. A major difference between Click and other component oriented frameworks, is that Click is stateless by design, although stateful pages are supported. It is an optimal framework, always trading off bloating features to its main goals of simplicity. Another important focus of the project has been to provide high quality documentation and examples to get people started as quickly as possible. We see Click becoming an Apache project as a logical step in its evolution. Becoming part of the Apache community will increase visibility and expose the framework to a larger community of developers. === Current Status === == Meritocracy == Click was developed by Malcolm Edgar in 2003 publicly released in March 2005. Since then there have been contributions from a number of developers across the world. New contributors are encouraged to provide patches, and later commit privileges are assigned to them. In 2008 Bob Schellink joined Malcolm Edgar as a joint lead on the project after contributing to the project for a number of years. == Community == Click is a small but growing community of users and developers. Its two mailing lists receive around 200 messages per month. == Core Developers == * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe == Alignment == Click has already built up relationships with existing Apache projects especially Velocity and Cayenne. Using Velocity as its default rendering engine, Click has formed a close relationship with the Velocity community. Click also supports good integration with the Apache Cayenne ORM framework. == Known Risks == * Orphaned Software: Click has a healthy community of users and developers and has a very low risk of becoming orphaned. Experience With Open Source: Click was started as an open source project in 2005 and has remained so for 3 years. * Homogeneous Developers: The community is very diverse with users and developers from all over the world. * Reliance on salaried developers: None of the Click developers are compensated for their contributions. It is a complete voluntary project. * Relationships with Other Apache Products: As mentioned in the Alignment section, Click has formed close relationships with Velocity and Cayenne. Other Apache products used include commons-* and log4j. * An Excessive Fascination with the Apache Brand: Although it is true that the Apache Brand will increase visibility of the framework, we are more interested in building stronger relationships and influence Apache projects such as Velocity. == Scope of the project == Currently Click consists of the following parts: the core framework, an extras package for non core controls, an examples project and a quick start project. There is also an Eclipse plugin called ClickIDE. == Initial Source == Click sources is available from http://sourceforge.net/projects/click == External Dependencies == There are some concerns over incompatible licensed libraries Click depends on. * calendar.js is released under a LGPL licensed library from http://www.dynarch.com/projects/calendar/ * Hibernate is released under a LGPL licensed library from http://www.hibernate.org/ * HSQLDB is released under the license specified here: http://hsqldb.org/web/hsqlLicense.html == Required Resources == == Mailing lists == Create new mailing lists * click-dev * click-private == Subversion Directory == Migrate the current subversion code from sourceforge to Apache * https://svn.apache.org/repos/asf/incubator/click == Issue Tracking == * Need to create a new JIRA project called CLICK for the Click framework * Migrate the current JIRA issue tracker from http://www.avoka.com/jira/ == Other Resources == Need to create a new Confluence Wiki * CLICK == Initial Committers == The initial committers for the project should include: * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe * Henning Schmiedehausen * Will Glass-Husain * Ted Husted * Andrus Adamchik == Sponsors == === Champion === * Henning Schmiedehausen === Nominated Mentors === * Will Glass-Husain * Ted Husted * Andrus Adamchik === Sponsoring Entity === * Velocity
Re: [VOTE] Accept Click for Incubation
+1 On Tue, Jul 15, 2008 at 12:00 PM, Jim Jagielski [EMAIL PROTECTED] wrote: +1 On Jul 14, 2008, at 7:14 AM, Henning Schmiedehausen wrote: This vote will run until Monday, July 21st, 2008. [ ] +1 Accept Click for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason: = Click Proposal = This proposal specifies the migration of Click web application framework to the Apache Software Foundation as a Top Level Project. http://click.sourceforge.net/ == Rationale == Click is a modern J2EE web application framework released under the Apache License 2.0. It takes a component and page orientated approach to web applications with its main goals being ease of use and low barrier to entry. A major difference between Click and other component oriented frameworks, is that Click is stateless by design, although stateful pages are supported. It is an optimal framework, always trading off bloating features to its main goals of simplicity. Another important focus of the project has been to provide high quality documentation and examples to get people started as quickly as possible. We see Click becoming an Apache project as a logical step in its evolution. Becoming part of the Apache community will increase visibility and expose the framework to a larger community of developers. === Current Status === == Meritocracy == Click was developed by Malcolm Edgar in 2003 publicly released in March 2005. Since then there have been contributions from a number of developers across the world. New contributors are encouraged to provide patches, and later commit privileges are assigned to them. In 2008 Bob Schellink joined Malcolm Edgar as a joint lead on the project after contributing to the project for a number of years. == Community == Click is a small but growing community of users and developers. Its two mailing lists receive around 200 messages per month. == Core Developers == * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe == Alignment == Click has already built up relationships with existing Apache projects especially Velocity and Cayenne. Using Velocity as its default rendering engine, Click has formed a close relationship with the Velocity community. Click also supports good integration with the Apache Cayenne ORM framework. == Known Risks == * Orphaned Software: Click has a healthy community of users and developers and has a very low risk of becoming orphaned. Experience With Open Source: Click was started as an open source project in 2005 and has remained so for 3 years. * Homogeneous Developers: The community is very diverse with users and developers from all over the world. * Reliance on salaried developers: None of the Click developers are compensated for their contributions. It is a complete voluntary project. * Relationships with Other Apache Products: As mentioned in the Alignment section, Click has formed close relationships with Velocity and Cayenne. Other Apache products used include commons-* and log4j. * An Excessive Fascination with the Apache Brand: Although it is true that the Apache Brand will increase visibility of the framework, we are more interested in building stronger relationships and influence Apache projects such as Velocity. == Scope of the project == Currently Click consists of the following parts: the core framework, an extras package for non core controls, an examples project and a quick start project. There is also an Eclipse plugin called ClickIDE. == Initial Source == Click sources is available from http://sourceforge.net/projects/click == External Dependencies == There are some concerns over incompatible licensed libraries Click depends on. * calendar.js is released under a LGPL licensed library from http://www.dynarch.com/projects/calendar/ * Hibernate is released under a LGPL licensed library from http://www.hibernate.org/ * HSQLDB is released under the license specified here: http://hsqldb.org/web/hsqlLicense.html == Required Resources == == Mailing lists == Create new mailing lists * click-dev * click-private == Subversion Directory == Migrate the current subversion code from sourceforge to Apache * https://svn.apache.org/repos/asf/incubator/click == Issue Tracking == * Need to create a new JIRA project called CLICK for the Click framework * Migrate the current JIRA issue tracker from http://www.avoka.com/jira/ == Other Resources == Need to create a new Confluence Wiki * CLICK == Initial Committers == The initial committers for the project should include: * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe * Henning Schmiedehausen * Will Glass-Husain * Ted Husted * Andrus Adamchik == Sponsors == === Champion === * Henning Schmiedehausen === Nominated Mentors === * Will Glass-Husain * Ted Husted * Andrus Adamchik ===
Re: [VOTE] Release Apache UIMA-AS 2.2.2-incubating
+1 ...ant On Mon, Jun 30, 2008 at 8:57 PM, Marshall Schor [EMAIL PROTECTED] wrote: Hi Everyone, Please review and vote on approving the 1st release of Apache UIMA-AS, an add-on to base UIMA. The release artifacts and the annotated RAT reports can be found here: http://people.apache.org/~schor/uima-release-candidates/uima-as/08http://people.apache.org/%7Eschor/uima-release-candidates/uima-as/08 UIMA-AS originally came to Apache under a software grant, and has an IP Clearance form recorded: http://incubator.apache.org/ip-clearance/uima-as.html and linked from http://incubator.apache.org/ip-clearance/index.html The UIMA project dev-list vote to release was 6 +1's, and no other votes; see the vote here: http://markmail.org/message/t6l2ineufbr3qo4g UIMA-AS adds a scaleout capability to base UIMA based on asynchronous messaging; it makes use of the recently released UIMA base 2.2.2-incubating level, as well as Apache ActiveMQ and the Spring middleware framework (also licensed under the Apache v.2 license), internally. Because this release includes a distribution of parts of ActiveMQ, which in turn is classified as a 5D002 export, we submitted classification for UIMA-AS also as a 5D002 category. The http://apache.org/licenses/exports/page has been updated to reflect this. Thanks. -Marshall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache UIMA CasEditor-2.2.2-incubating
+1 ...ant On Thu, Jul 3, 2008 at 10:52 AM, Jörn Kottmann [EMAIL PROTECTED] wrote: Hello, the Cas Editor is a text annotation tool which supports manual and automatic annotation of CAS files. It is now ready for its first release. Please review and vote for releasing the Apache Uima Cas Editor-2.2.2-02. The release artifacts and the rat reports can be found at: http://people.apache.org/~joern/CasEditor-2.2.2-02/http://people.apache.org/%7Ejoern/CasEditor-2.2.2-02/ On the uima-dev list there were 5 +1 votes and no 0 or -1 votes to release it. The Cas Editor originally came to Apache under a software grant. Thanks, Jörn
Re: [PROPOSAL] Tashi
On Tue, Jul 15, 2008 at 6:55 AM, David O'Hallaron [EMAIL PROTECTED] wrote: Matthieu, * The sponsoring entity is the Incubator so I'm guessing you're shooting for graduating as a TLP. What kind of interactions do you foresee with Hadoop for example? We talked with Doug Cutting about whether to shoot for a TLP or a subproject under Hadoop. We decided ultimately to go the TLP route because Tashi and Hadoop are at different levels in the stack. However, we see Hadoop as one of the important applications running on Tashi virtual clusters, so the two projects are quite complementary. * IIC Tashi is only about management, not about the underlying storage/computing technology. Is that correct? And if so which ones do you plan to integrate with? Yes, that's correct. We plan to integrate with the major VMMs, such as Xen, Linux KVM and VMWare. For storage, we're looking at integrating with HDFS, pVFS and later pNFS when it becomes more mature.An important goal is to provide the hooks and interfaces that allow any DFS and VMM vendor to integrate with the system. * I can't help asking for more technical details. What's the implementation language for your POC code? What are the non-proprietary interfaces you're thinking of? The POC code is a couple of thousand lines of original Python code. Major components are cluster manager (cm), which runs on one of the cluster nodes, a node manager (nm), which runs on each of the other physical cluster nodes, a simple db on the cluster manager for configuration data, and some client utilities. We're really thinking hard about interfaces now, but don't have clear definitions yet. The kinds of things wer are thinking about are interfaces between the client and cm and cm and nm for manipulating starting, starting, and migrating vms, interfaces for some kind of event/messaging system for monitoring and reporting system state to the cm and client, interfaces between the cm/nm and storage system to allow the cm to do storage-aware scheduling of vms, interfaces to power management and system management hardware features, and possibly interfaces for federating different Tashi clusters. Okay, sounds good to me, thanks for the clarifications. Also if you need another mentor, you can count me in. Cheers, Matthieu Thanks, Dave -- -- David O'Hallaron -- Director, Intel Research Pittsburgh -- Assoc Prof of CS and ECE, Carnegie Mellon University -- http://www.cs.cmu.edu/~droh http://www.cs.cmu.edu/%7Edroh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-78) Unreliable report schedule and list of podlings
[
https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613703#action_12613703
]
Noel J. Bergman commented on INCUBATOR-78:
--
As a suggestion, each incubating project could have a status file at [...]
where PROJECT is the project name.
They already do. See all of the ${PROJECT}.xml files under
http://svn.apache.org/viewvc/incubator/public/trunk/site-author/projects
Unreliable report schedule and list of podlings
---
Key: INCUBATOR-78
URL: https://issues.apache.org/jira/browse/INCUBATOR-78
Project: Incubator
Issue Type: Bug
Reporter: Bertrand Delacretaz
As discussed in http://markmail.org/message/le55q754m4eypu7r it would be
useful to generate the podlings report schedule and the list of projects on
the http://incubator.apache.org/ automatically from a master file.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache UIMA CasEditor-2.2.2-incubating
Luciano Resende wrote: The binary distributions, both windows and linux, have the com.ibm.icu_3.6.1.v20070906.jar in the plugins directory and the about_files/license.html from the ICU jar mention the following : ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1995-2007 International Business Machines Corporation and others All rights reserved. . But I haven't found any attribution on License/Notice files. Argh, you're right, we missed ICU. Everything else ok, or did you stop looking when you found this issue? --Thilo On Tue, Jul 15, 2008 at 10:46 AM, ant elder [EMAIL PROTECTED] wrote: +1 ...ant On Thu, Jul 3, 2008 at 10:52 AM, Jörn Kottmann [EMAIL PROTECTED] wrote: Hello, the Cas Editor is a text annotation tool which supports manual and automatic annotation of CAS files. It is now ready for its first release. Please review and vote for releasing the Apache Uima Cas Editor-2.2.2-02. The release artifacts and the rat reports can be found at: http://people.apache.org/~joern/CasEditor-2.2.2-02/http://people.apache.org/%7Ejoern/CasEditor-2.2.2-02/ On the uima-dev list there were 5 +1 votes and no 0 or -1 votes to release it. The Cas Editor originally came to Apache under a software grant. Thanks, Jörn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache UIMA CasEditor-2.2.2-incubating
Luciano Resende wrote: The binary distributions, both windows and linux, have the com.ibm.icu_3.6.1.v20070906.jar in the plugins directory and the about_files/license.html from the ICU jar mention the following : ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1995-2007 International Business Machines Corporation and others All rights reserved. . But I haven't found any attribution on License/Notice files. Some background on the license/notice file for this is in this thread from legal - discuss: http://markmail.org/message/nnfarn3c4snxyrxw The bottom line here I think is to append the ICU license to the LICENSE file, and a short ref about it in the NOTICE file, following Luciano's recommendation in the 1st reply to the above referenced thread. -Marshall On Tue, Jul 15, 2008 at 10:46 AM, ant elder [EMAIL PROTECTED] wrote: +1 ...ant On Thu, Jul 3, 2008 at 10:52 AM, Jörn Kottmann [EMAIL PROTECTED] wrote: Hello, the Cas Editor is a text annotation tool which supports manual and automatic annotation of CAS files. It is now ready for its first release. Please review and vote for releasing the Apache Uima Cas Editor-2.2.2-02. The release artifacts and the rat reports can be found at: http://people.apache.org/~joern/CasEditor-2.2.2-02/http://people.apache.org/%7Ejoern/CasEditor-2.2.2-02/ On the uima-dev list there were 5 +1 votes and no 0 or -1 votes to release it. The Cas Editor originally came to Apache under a software grant. Thanks, Jörn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Click for Incubation
On Mon, Jul 14, 2008 at 1:14 PM, Henning Schmiedehausen [EMAIL PROTECTED] wrote: [X] +1 Accept Click for incubation Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache UIMA CasEditor-2.2.2-incubating
On Tue, Jul 15, 2008 at 12:27 PM, Thilo Goetz [EMAIL PROTECTED] wrote: Luciano Resende wrote: The binary distributions, both windows and linux, have the com.ibm.icu_3.6.1.v20070906.jar in the plugins directory and the about_files/license.html from the ICU jar mention the following : ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1995-2007 International Business Machines Corporation and others All rights reserved. . But I haven't found any attribution on License/Notice files. Argh, you're right, we missed ICU. Everything else ok, or did you stop looking when you found this issue? --Thilo That's the only think I could find. On Tue, Jul 15, 2008 at 10:46 AM, ant elder [EMAIL PROTECTED] wrote: +1 ...ant On Thu, Jul 3, 2008 at 10:52 AM, Jörn Kottmann [EMAIL PROTECTED] wrote: Hello, the Cas Editor is a text annotation tool which supports manual and automatic annotation of CAS files. It is now ready for its first release. Please review and vote for releasing the Apache Uima Cas Editor-2.2.2-02. The release artifacts and the rat reports can be found at: http://people.apache.org/~joern/CasEditor-2.2.2-02/http://people.apache.org/%7Ejoern/CasEditor-2.2.2-02/ On the uima-dev list there were 5 +1 votes and no 0 or -1 votes to release it. The Cas Editor originally came to Apache under a software grant. Thanks, Jörn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][CANCEL] Release Apache UIMA CasEditor-2.2.2-incubating
This vote is canceled because ICU is not referenced in the License/ Notice file and in the about dialog. Thanks to Luciano for finding this. Jörn On Jul 15, 2008, at 10:00 PM, Luciano Resende wrote: On Tue, Jul 15, 2008 at 12:27 PM, Thilo Goetz [EMAIL PROTECTED] wrote: Luciano Resende wrote: The binary distributions, both windows and linux, have the com.ibm.icu_3.6.1.v20070906.jar in the plugins directory and the about_files/license.html from the ICU jar mention the following : ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1995-2007 International Business Machines Corporation and others All rights reserved. . But I haven't found any attribution on License/Notice files. Argh, you're right, we missed ICU. Everything else ok, or did you stop looking when you found this issue? --Thilo That's the only think I could find. On Tue, Jul 15, 2008 at 10:46 AM, ant elder [EMAIL PROTECTED] wrote: +1 ...ant On Thu, Jul 3, 2008 at 10:52 AM, Jörn Kottmann [EMAIL PROTECTED] wrote: Hello, the Cas Editor is a text annotation tool which supports manual and automatic annotation of CAS files. It is now ready for its first release. Please review and vote for releasing the Apache Uima Cas Editor-2.2.2-02. The release artifacts and the rat reports can be found at: http://people.apache.org/~joern/CasEditor-2.2.2-02/http://people.apache.org/%7Ejoern/CasEditor-2.2.2-02/ On the uima-dev list there were 5 +1 votes and no 0 or -1 votes to release it. The Cas Editor originally came to Apache under a software grant. Thanks, Jörn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
