Re: Incubator voting status page
On 28.01.2013 08:58, Daniel Shahaf wrote: Branko Čibej wrote on Mon, Jan 28, 2013 at 08:22:42 +0100: On 27.01.2013 16:17, Daniel Shahaf wrote: Branko Čibej wrote on Sat, Jan 26, 2013 at 15:30:04 +0100: On 26.01.2013 14:27, Benson Margulies wrote: Brane, are you currently using the pickled clutch metadata? If we just need to add a field to it we can. Nope, I'm currently walking the incubator archive tree. The clutch metadata is in general good enough, since if clutch can generate target/current.ent, I can certainly get the information I need from that. The only question is the conversion from l...@podling.incubator.apache.org (which clutch knows about) to archive/podling.apache.org/list (which is where the podling mail archives will be in future) is consistent. Yes, it is, for all *@p.i.a.o lists. Well, I've found an inconsistency while changing the scripts to parse the content/podlings.xml and content/projects/podling-name.xml. Onami's dev list is the old-style: onami-...@incubator.apache.org but its archive is new-style: onami.incubator.apache.org/dev I don't want to special-case the script for this; can we make the archive consistent with the mailing list address? They seem consistent with the other new-style podlings: minotaur,9:~apmail/public-arch% find . -maxdepth 2 -name \*onami\* ./onami.apache.org minotaur,9:~apmail/public-arch% grep -h List-Id onami.apache.org/*/* | uniq List-Id: commits.onami.incubator.apache.org List-Id: dev.onami.incubator.apache.org List-Id: user.onami.incubator.apache.org Ah, could it be then that content/projects/onami.xml is just wrong and needs to be updated? It says: td id=mail-devcodeonami-dev/codecode@/codecodeincubator.apache.org/code/td -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator voting status page
Hi Branko! On Mon, Jan 28, 2013 at 9:57 AM, Branko Čibej br...@apache.org wrote: Ah, could it be then that content/projects/onami.xml is just wrong and needs to be updated? yes, we published the status page before we got the MLs addresses and noticed they are in the new pattern :P could one of the mentor please update it? TIA! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator voting status page
On 28.01.2013 10:01, Simone Tripodi wrote: Hi Branko! On Mon, Jan 28, 2013 at 9:57 AM, Branko Čibej br...@apache.org wrote: Ah, could it be then that content/projects/onami.xml is just wrong and needs to be updated? yes, we published the status page before we got the MLs addresses and noticed they are in the new pattern :P could one of the mentor please update it? I can do that. And have done it. Please review: svn diff -c1439308 http://svn.apache.org/repos/asf/incubator -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator voting status page
On Mon, Jan 28, 2013 at 10:06 AM, Branko Čibej br...@apache.org wrote: On 28.01.2013 10:01, Simone Tripodi wrote: Hi Branko! On Mon, Jan 28, 2013 at 9:57 AM, Branko Čibej br...@apache.org wrote: Ah, could it be then that content/projects/onami.xml is just wrong and needs to be updated? yes, we published the status page before we got the MLs addresses and noticed they are in the new pattern :P could one of the mentor please update it? I can do that. And have done it. Please review: svn diff -c1439308 http://svn.apache.org/repos/asf/incubator Looks good, thanks for updating it. We (mentors) need to give this file some more love, but thats another story. Cheers Christian -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Potential proposal + request volunteers for champion mentor roles - MetaModel
Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator - Abstract MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Proposal MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. Background The MetaModel project was initially developed by eobject.dk to service the DataCleaner application. The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Rationale Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. Initial goals MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio (currently a Salesforce.com web service consumer datastore is being tested), but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora and CouchDB) and potentially renaming the 'MetaModel' project to something more rememberable. -- Current status Meritocracy We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been dragged into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. Community The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and closed source application, both at Human Inference (HIquality MDM), it's open source projects DataCleaner, SassyReader and AnalyzerBeans and by other parties (such as the Quipo data warehouse automation project), we believe that the critical mass to sustain a community is there. Core developers MetaModel was founded by Kasper Sørensen in 2009. Later it was incorporated as a core library by Human Inference, meaning that more than 20
[ANNOUNCE] Apache Bloodhound 0.4 incubating Released
The Apache Bloodhound (Incubating) team is pleased to announce the availability of the 0.4-incubating release. Apache Bloodhound is a tool to track progress and defects in software products. Standing on the shoulders of the mature Trac project, Bloodhound provides issue tracking, repository browsing and wiki functionality. On top of this Bloodhound aims to provide intuitive support for managing multiple software projects, a user-friendly interface and simple installation, incorporating the some of Trac's best plugins. This release includes the following highlights: * Replaces ticket edit form with a new 'in-place' edit and workflow control * Added white-labeling for error messages and basic branding * Improvements to the quick ticket creation form including ability to specify the select fields and their order * Various bug fixes The release can be downloaded from: http://www.apache.org/dyn/closer.cgi/incubator/bloodhound/apache-bloodhound-incubating-0.4.tar.gz For further information, please visit the project website at http://incubator.apache.org/bloodhound/ The Apache Bloodhound Team Disclaimer: Apache Bloodhound is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
[ANNOUNCE] Apache Bloodhound 0.4 incubating Released
The Apache Bloodhound (Incubating) team is pleased to announce the availability of the 0.4-incubating release. Apache Bloodhound is a tool to track progress and defects in software products. Standing on the shoulders of the mature Trac project, Bloodhound provides issue tracking, repository browsing and wiki functionality. On top of this Bloodhound aims to provide intuitive support for managing multiple software projects, a user-friendly interface and simple installation, incorporating the some of Trac's best plugins. This release includes the following highlights: * Replaces ticket edit form with a new 'in-place' edit and workflow control * Added white-labeling for error messages and basic branding * Improvements to the quick ticket creation form including ability to specify the select fields and their order * Various bug fixes The release can be downloaded from: http://www.apache.org/dyn/closer.cgi/incubator/bloodhound/apache-bloodhound-incubating-0.4.tar.gz For further information, please visit the project website at http://incubator.apache.org/bloodhound/ The Apache Bloodhound Team Disclaimer: Apache Bloodhound is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
Re: Potential proposal + request volunteers for champion mentor roles - MetaModel
Hi Kasper, the proposal looks quite interesting, but I have two questions: 1) How this is related with the emergent at ASF elated with RDF (mainly Jena and Marmotta)? I see some clear lines of cooperation there. 2) How this proposal is related with other well-established open source tools? Such as DataNucleus AccessPlatform http://www.datanucleus.org/products/accessplatform/. Greetings, On 28/01/13 11:07, Kasper Sørensen wrote: Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator - Abstract MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Proposal MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. Background The MetaModel project was initially developed by eobject.dk to service the DataCleaner application. The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Rationale Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. Initial goals MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio (currently a Salesforce.com web service consumer datastore is being tested), but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora and CouchDB) and potentially renaming the 'MetaModel' project to something more rememberable. -- Current status Meritocracy We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been dragged into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. Community The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and
RE: Potential proposal + request volunteers for champion mentor roles - MetaModel
Hi Sergio, I am not sure how to characterize the comparison with RDF / Jena / Marmotta, since I actually didn't know about these topics before now. Linked data might be a relevant topic for MetaModel also, but in the current form MetaModel is very much focused on a tabular view of data, resembling that of RDBMs, CSV/spreadsheet files etc. But also to adapt other datastores to a similar tabular view so that very widely used SQL techniques and wisdom can be applied to it. Not because we love SQL (MetaModel also supports several NoSQL databases), but because we needed a common metaphor of all data and data tables was found to be the easiest metaphor to comprehend for the users. We've looked to DataNucleus a few times also. They do a good job in implementing the various object mapping protocols (JDO/JPA etc.) but less so (to my understanding) of exposing data in a dynamic model. As such I see them as a ORM library, where we're still metadata-driven. The metadata that drives MetaModel comes from the datastore itself, not from the application code. So if you add a column to your database, or a sheet to your spreadsheet - then it automatically is also available in MetaModel. In a ORM you would define a new entity type etc. which is what we needed to get rid of, because the kind of application that typically runs on MetaModel is focused on the data itself, not any specific domain. Hope this makes some sort of sense :-) Best regards, Kasper -Original Message- From: Sergio Fernández [mailto:sergio.fernan...@salzburgresearch.at] Sent: 28. januar 2013 12:21 To: general@incubator.apache.org Cc: Kasper Sørensen Subject: Re: Potential proposal + request volunteers for champion mentor roles - MetaModel Hi Kasper, the proposal looks quite interesting, but I have two questions: 1) How this is related with the emergent at ASF elated with RDF (mainly Jena and Marmotta)? I see some clear lines of cooperation there. 2) How this proposal is related with other well-established open source tools? Such as DataNucleus AccessPlatform http://www.datanucleus.org/products/accessplatform/. Greetings, On 28/01/13 11:07, Kasper Sørensen wrote: Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator - Abstract MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Proposal MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. Background The MetaModel project was initially developed by eobject.dk to service the DataCleaner application. The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Rationale Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards
Re: Incubator voting status page
thanks a lot Branko, much more than appreciated!!! all the best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Mon, Jan 28, 2013 at 10:06 AM, Branko Čibej br...@apache.org wrote: On 28.01.2013 10:01, Simone Tripodi wrote: Hi Branko! On Mon, Jan 28, 2013 at 9:57 AM, Branko Čibej br...@apache.org wrote: Ah, could it be then that content/projects/onami.xml is just wrong and needs to be updated? yes, we published the status page before we got the MLs addresses and noticed they are in the new pattern :P could one of the mentor please update it? I can do that. And have done it. Please review: svn diff -c1439308 http://svn.apache.org/repos/asf/incubator -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache cTAKES 3.0.0-incubating RC5 release
On Sat, Jan 26, 2013 at 4:23 AM, Andrea Pescetti pesce...@apache.org wrote: On 25/01/2013 Benson Margulies wrote: On Fri, Jan 25, 2013 at 3:04 AM, Mattmann, Chris A (388J) What about Apache OpenOffice? I asked this question about Open Office, and I got, more or less, what I typed in above. I was puzzled, but there you have it. As I recall, Roy made a remark like 'our real users are people who will take the source of Open Office ...'. This is not exactly the way the OpenOffice project sees this. We are voting on a release right now, and of course we put great care in ensuring that the source code is clean and that it can be used by our downstream projects to build upon; but we also make extensive tests on the convenience binaries, since we know that our largest group of users is the 35 millions and counting who already downloaded the approved binaries. Who the real users are is an empirical question, and it does a disservice to introduce a false dichotomy between end users of the convenience binaries and developers who work on the core C++ code. We have in OpenOffice a large group of developers who use the SDK to develop extensions 3rd party extensions to OpenOffice. They've created around 700 such extensions. The most popular ones have thousands of downloads per week. That is a thriving part of the ecosystem. This might not fit a 1999 view of how open source is consumed by an ecosystem, but in 2013 any product that can only be enhanced by modifying 20 year old C++ code is stunting its own ecosystem The fact that 3rd party value is created more in extensions than core C++ code modifications is a very good thing from an engineering perspective. For example it allows end-users to mix and match extensions from different vendors. This did not happen by accident. This was a design goal. In any case, I think it is deserving of more recognition at Apache that ecosystems do not always require compiled code and core code modifications to exist, and there are indeed real users in this ecosystem who thrive on such extensions. Regards, -Rob Regards, Andrea. - 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
[jira] [Commented] (INCUBATOR-125) How-to guide for Assembling LICENSE and NOTICE
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13564925#comment-13564925 ] Marvin Humphrey commented on INCUBATOR-125: --- I think it will also be useful to mention about the DISCLAIMER file requirement [1] for the incubator podlings. The DISCLAIMER file is already documented here: http://incubator.apache.org/guides/branding.html#disclaimers In my view, it would not be appropriate to mention DISCLAIMER in the LICENSE/NOTICE how-to. LICENSE and NOTICE are tightly intertwined, but DISCLAIMER is only related to them insofar as they are all required to be present in incubating releases. What we need is a page under incubator.apache.org/ which enumerates the requirements for incubating releases, and which ought to link to *both* the licensing how-to and the DISCLAIMER documentation along with many other documents. In fact, such a page already exists -- it's our infamous [http://incubator.apache.org/guides/releasemanagement.html]. Unfortunately, that page is monumentally bloated because everything including the kitchen sink has been thrown into it, regardless of whether the additions duplicate information found elsewhere -- or even right there on the page itself. Rather than add material to the licensing how-to because releasemanagement.html fails to serve its purpose, we should work to improve releasemanagement.html itself. How-to guide for Assembling LICENSE and NOTICE Key: INCUBATOR-125 URL: https://issues.apache.org/jira/browse/INCUBATOR-125 Project: Incubator Issue Type: Improvement Components: site Reporter: Marvin Humphrey Attachments: licensing_howto.mdtext While the ASF provides reference documentation for LICENSE and NOTICE, confusion persists and existing versions vary widely in quality. To address these problems, we should augment the reference documentation with a how-to guide which provides formulaic instructions for assembling LICENSE and NOTICE under common conditions. One key feature of this how-to should be a mapping of approved licenses to what they require as far as NOTICE. This mapping will help PMCs determine when the licensing information of a dependency contains a required third party notice which must be added to NOTICE. There are at least four possible locations where this how-to might live: * www.apache.org/dev/licensing_howto.html -- probably the best location, considering the intended audience. * www.apache.org/legal/licensing_howto.html -- if legal wants it. * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, because the information applies to TLPs as well as podlings and we have a problem with duplication. * Somewhere on community.apache.org -- in theory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Potential proposal + request volunteers for champion mentor roles - MetaModel
Kasper Sørensen wrote: Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). You need to ask on this general@ list and tell your wiki username. See http://wiki.apache.org/incubator/FrontPage -David Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator - Abstract MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Proposal MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. Background The MetaModel project was initially developed by eobject.dk to service the DataCleaner application. The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Rationale Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. Initial goals MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio (currently a Salesforce.com web service consumer datastore is being tested), but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora and CouchDB) and potentially renaming the 'MetaModel' project to something more rememberable. -- Current status Meritocracy We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been dragged into the open by third parties. We believe that meritocracy will be further stimulated by granting the control of the project to an independent committee. Community The community around MetaModel already exists, but we believe it will grow substantially by becoming an Apache project. With MetaModel used in a wide range of both open and closed source application, both at Human Inference (HIquality MDM), it's open source projects DataCleaner, SassyReader and AnalyzerBeans and by other parties (such as the Quipo data
Re: [DISCUSS] Apache Open Climate Workbench
Dear Nick, On 1/27/13 10:34 PM, Nick Kew n...@apache.org wrote: On 26 Jan 2013, at 19:48, Mattmann, Chris A (388J) wrote: Hi Everyone! I bring to the Incubator a new proposal for the Apache Open Climate Workbench (incubating) project. I've added the proposal to the Incubator wiki here: http://wiki.apache.org/incubator/ClimateProposal Sounds quite exciting! I'd like to come on board, though whether as an active participant or passively will depend on time and circumstance. You are welcome to join and we'd be happy to have you as a mentor, a PPMC member, or a committer. Your wisdom will be great. Some years back I spent a lot of timeeffort on the somewhat-related task of developing systems, firstly to produce, archive and distribute some of the datasets (mostly the Global AVHRR 1Km series in the '90s) and secondly to develop tools to visualise different datasets alongside and superimposed on each other. Awesome, so you were dealing with remote sensing stuff there, cool. I see your proposal has a slightly different focus (and obviously benefits from a new generation of infrastructure in which a terabyte is no longer a mindblowing amount of data to manage), but I hope my background might still serve to kick-start an involvement! Yep that would be awesome welcome aboard! Cheers, Chris -- Nick Kew - 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 voting status page
Branko Čibej wrote: On 28.01.2013 08:58, Daniel Shahaf wrote: Branko Čibej wrote on Mon, Jan 28, 2013 at 08:22:42 +0100: On 27.01.2013 16:17, Daniel Shahaf wrote: Branko Čibej wrote on Sat, Jan 26, 2013 at 15:30:04 +0100: On 26.01.2013 14:27, Benson Margulies wrote: Brane, are you currently using the pickled clutch metadata? If we just need to add a field to it we can. Nope, I'm currently walking the incubator archive tree. The clutch metadata is in general good enough, since if clutch can generate target/current.ent, I can certainly get the information I need from that. ... Clutch does not generate that file. It is handled by the Incubator Ant build.xml ... The only question is the conversion from l...@podling.incubator.apache.org (which clutch knows about) to archive/podling.apache.org/list (which is where the podling mail archives will be in future) is consistent. Yes, it is, for all *@p.i.a.o lists. Well, I've found an inconsistency while changing the scripts to parse the content/podlings.xml and content/projects/podling-name.xml. Onami's dev list is the old-style: onami-...@incubator.apache.org but its archive is new-style: onami.incubator.apache.org/dev I don't want to special-case the script for this; can we make the archive consistent with the mailing list address? They seem consistent with the other new-style podlings: minotaur,9:~apmail/public-arch% find . -maxdepth 2 -name \*onami\* ./onami.apache.org minotaur,9:~apmail/public-arch% grep -h List-Id onami.apache.org/*/* | uniq List-Id: commits.onami.incubator.apache.org List-Id: dev.onami.incubator.apache.org List-Id: user.onami.incubator.apache.org Ah, could it be then that content/projects/onami.xml is just wrong and needs to be updated? It says: td id=mail-devcodeonami-dev/codecode@/codecodeincubator.apache.org/code/td You are striking the same type of problems that Clutch has needed to deal with over the years. In general, the state of podling metadata is not reliable. That is something that we need to get podling developers interested with. So Clutch makes educated guesses about the podling mail lists. When it sees that its mbox files are flowing (they could be not yet established or held up waiting for initial moderation) then it writes their dev list address into the report_due_[1-3].txt files for 'marvin' to utilise (see http://incubator.apache.org/clutch.html#data) and puts hasMailListDev into clutch.pkl for the mod_mbox URL. With the latter, if the name starts with incubator- then that is an old-style list. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Ambari (incubating) 1.2.0 Release Candidate RC0.
If I download the SVN tag and run 'mvn install' I get the following: [INFO] Reactor Summary: [INFO] [INFO] Ambari Main ... SUCCESS [9.258s] [INFO] Apache Ambari Project POM . SUCCESS [0.045s] [INFO] Ambari Web FAILURE [1.744s] [INFO] Ambari Server . SKIPPED [INFO] Ambari Agent .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 56.720s [INFO] Finished at: Mon Jan 28 15:06:56 CET 2013 [INFO] Final Memory: 8M/81M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (compile) on project ambari-web: An Ant BuildException has occured: Execute failed: java.io.IOException: Cannot run program npm (in directory /Users/user/Desktop/amb/ambari-web): error=2, No such file or directory [ERROR] around Ant part ...exec dir=/Users/user/Desktop/amb/ambari-web executable=npm failonerror=false... @ 4:90 in /Users/user/Desktop/amb/ambari-web/target/antrun/build-ambari-web-compile.xml [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :ambari-web am I missing anything? Apart from that it looks good. Tommaso 2013/1/28 Mahadev Konar maha...@apache.org Hi everyone, This is a call for a vote on Apache Ambari 1.2.0 incubating. A vote was held on developer mailing list and it passed with 8 +1's with 6 of them binding. mahadev (IPMC, PPMC) ddas (IPMC, PPMC) acmurthy (IPMC) jitendra (PPMC) hitesh (PPMC) yusaku (PPMC) http://mail-archives.apache.org/mod_mbox/incubator-ambari-dev/201301.mbox/%3CCALF7aMRrJxiMORuzMuYxnAuncias9Gnvd1awqaPO-Zuuo1cDqQ%40mail.gmail.com%3E The staging Staging site is: http://people.apache.org/~mahadev/ambari-1.2.0-incubating-rc0/ with user docs at: http://incubator.apache.org/ambari/1.2.0/installing-hadoop-using-ambari/content/index.html and dev docs at: https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development SVN source tag: https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.0-rc0 PGP release keys (signed using 8EE2F25C) http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x0DFF492D8EE2F25C One can look into the issues fixed in this release at https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%221.2.0%22%20AND%20project%20%3D%20AMBARI Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks mahadev - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Potential proposal + request volunteers for champion mentor roles - MetaModel
Thank you for helping David. My username is KasperSorensen. Can someone please provide me access to create a new proposal wiki page on http://wiki.apache.org/incubator/ProjectProposals ? Best regards, Kasper -Original Message- From: David Crossley [mailto:cross...@apache.org] Sent: 29. januar 2013 04:51 To: general@incubator.apache.org Subject: Re: Potential proposal + request volunteers for champion mentor roles - MetaModel Kasper Sørensen wrote: Dear all, After some time spent (yeah, sorry quite a lot more time than we had hoped), we finally now have the green light to officially post a proposal to the Incubator to take on MetaModel as a project. Since it's been a while, I wish to call out again for sponsors. We found a few some months ago, but we where out of contact for so long I feel it's most fair to ask again. Please find below the draft proposal which we would love to further work on together with sponsors before finally submitting it. (I tried posting it on the wiki but was not authorized, probably because my account is a new one). You need to ask on this general@ list and tell your wiki username. See http://wiki.apache.org/incubator/FrontPage -David Best regards, Kasper Sørensen - MetaModel - uniform data access across datastores Proposal for Apache Incubator - Abstract MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. Proposal MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. Background The MetaModel project was initially developed by eobject.dk to service the DataCleaner application. The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Rationale Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. Initial goals MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio (currently a Salesforce.com web service consumer datastore is being tested), but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora and CouchDB) and potentially renaming the 'MetaModel' project to something more rememberable. -- Current status Meritocracy We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and discussion forums. We believe that the approach going forward should be more encouraging by sharing all the design ideas and discussions in the open, not only just the topics that have been dragged into the open by third parties. We believe that meritocracy will be further stimulated by
