Re: Incubator policy wording
Hi, And here's my attempt to update, simplify and modernise the policy. [1] Thanks, Justin 1. https://github.com/apache/incubator/pull/21/files - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[GitHub] [incubator] justinmclean opened a new pull request #21: Update, simplify and modernise policy
justinmclean opened a new pull request #21: Update, simplify and modernise policy URL: https://github.com/apache/incubator/pull/21 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[GitHub] [incubator] justinmclean merged pull request #20: fix a couple of links
justinmclean merged pull request #20: fix a couple of links URL: https://github.com/apache/incubator/pull/20 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[GitHub] [incubator] justinmclean opened a new pull request #20: fix a couple of links
justinmclean opened a new pull request #20: fix a couple of links URL: https://github.com/apache/incubator/pull/20 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Heron Release 0.20.1-incubating Release Candidate 3
Thanks! 发自我的 iPhone > 在 2019年7月26日，下午7:32，Josh Fischer 写道： > > Thanks for the vote and the information Justin. I will look into the files > you mentioned. > > - Josh > > On Thu, Jul 25, 2019 at 9:14 PM Justin Mclean > wrote: > >> Hi, >> >> I mentioned this last release as was and I see Dave mentioned on the your >> dev list that - "Any required copyright attribution should be in the >> NOTICE.” >> >> This doesn’t mean that you need to list all copyright lines in the NOTICE >> file only those that are mentioned in a NOTICE file of ALv2 software you >> have bundled. >> >> A quick check shows that none of the ALv2 software you mention has NOTICE >> files (so nothing to do there), but you might want to check the ALv2 >> software that is not listed and I’m mentioned. >> >> Thanks, >> Justin >> >> 1. https://github.com/apache/incubator-heron/blob/master/NOTICE >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> -- > Sent from A Mobile Device - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[PROPOSAL] MetaObjects for Apache Incubator
I would like to propose MetaObjects as an Apache Incubator project. The text of the proposal is included below. --carl = Abstract MetaObjects is a data model and metadata description framework to drive Model-Driven Development (MDD) across multiple environments and language stacks providing capabilities such as generated documentation, code generation, model-driven behaviors, and model-driven interfaces. == Proposal In general, Model-Driven Development describes a process which uses an abstract definition of a “model” of “something” to generate concrete artifacts related to that “something” which are consumable by end-users (client code, developers, etc). Typical use-cases provide for automatic generation of related artifacts/capabilities such as: * Data * Documentation * QA/Verification * Interface definitions * Code implementations * DTO/DAO/CRUD operations Common examples of model-driven development include: * Spring Annotations * .NET Data Annotations * Ruby on Rails * Swagger/OpenAPI * Faker.js * Protobuf MetaObjects aims to provide a generalized schema for describing data and related artifacts, along with generative templates to produce language- or environment-specific artifacts based upon the "canonical" data description. MetaObjects hoists the definition of object schemas up one level, allowing us to treat these schemas as "data" and derive further business value from the metadata in the model. The model metadata (attributes) allow for driving behaviors around the models. These behaviors can be manifested through conversion to annotations in the target language via code generation. In addition, systems can implement behavioral code by using the model metadata attributes directly to modify default behaviors. == Background Having a shared understanding of the core data models and the concepts they describe is critical to delivering value across a variety of user-facing systems. MetaObjects was born to support faster development following the 80/20 rule of most data models having 80% of the same behaviors that could be solved using MDD, while still supporting 20% with custom-written code. Over the past 15 years, the primary use cases were building web applications and APIs where the persistence, business layer, and user interface were all built using MDD techniques. As MetaObjects usage grew, its use-cases evolved to meet the needs of the users. At Liquent, it was extended to support "overlays", allowing different deployments of the same codebase to have their behaviors and interfaces modified by only modifying the MetaObjects data model and metadata (attributes) to customize for difference clients, without the need for heavy custom code modifications. At Cengage, MetaObjects evolved to support interoperable representations of the same data within both XML and JSON data formats. Through these experiences, the project adopted the perspective that XML and JSON are not themselves data models. Instead, they are just representations (serializations) of a higher-level "object". In a very real sense, MetaObjects provides metadata which describes the high-level "object" in ways that are maximally useful to a wide range of consumers. Along the way, it was recognized that more and more functionality could be efficiently generated from a core "meta-model" of the objects. Artifacts and capabilities such as DAO/DTO code, model-driven UI, validations, database schemas, API models, etc were added to the project. It was also recognized that there is a strong tendency to "solve the problem in front of you" and thereby suffer from a focus that is too narrow. As the MetaObjects project matured, architecture and capabilities evolved to solve for this myopia. However, it was also recognized that an organization such as Apache would attract a wide variety of users and use-cases and serve as the catalyst to realize the full potential of MetaObjects. == Rationale There is a strong need for common models which exist independent of the technology implementing the model. Identifying opportunities for generalization and commoditization of these models has been key to the success of many projects. The success of projects like Swagger/OpenAPI, Spring, Protobuf clearly indicates the perceived value of MDD. They also clearly point to the criticality of ensuring that these capabilities are Open Standards. MetaObjects embraces these Open Standards by providing capability and interop across as many technology standards as possible. MetaObjects also acknowledges the potential to suffer from an inverse relationship -- as more technologies are integrated, the "lowest common denominator" shrinks. As part of its design, MetaObjects has facilities for incorporating specialized behaviors on top of core functionality. This enables MetaObjects to remain generally useful across technologies while remaining maximally useful for specific technologies. For example, when implementing within a micro-services
[RESULT] [VOTE] Release Rya (Incubating) version 4.0.0 RC1
Hello, The vote to release Rya (Incubating) version 4.0.0 RC1 has passed. +1 (binding): Josh Elser Justin Mclean Paul King +1 (non binding): Adina Crainiceanu Aaron Mihalik (dev list vote) Puja Valiyil (dev list vote) David Lotts (dev list vote) Jeff Dasch (dev list vote) I will promote the artifacts to the central repository. --Aaron
Re: [VOTE] Heron Release 0.20.1-incubating Release Candidate 3
Thanks for the vote and the information Justin. I will look into the files you mentioned. - Josh On Thu, Jul 25, 2019 at 9:14 PM Justin Mclean wrote: > Hi, > > I mentioned this last release as was and I see Dave mentioned on the your > dev list that - "Any required copyright attribution should be in the > NOTICE.” > > This doesn’t mean that you need to list all copyright lines in the NOTICE > file only those that are mentioned in a NOTICE file of ALv2 software you > have bundled. > > A quick check shows that none of the ALv2 software you mention has NOTICE > files (so nothing to do there), but you might want to check the ALv2 > software that is not listed and I’m mentioned. > > Thanks, > Justin > > 1. https://github.com/apache/incubator-heron/blob/master/NOTICE > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Sent from A Mobile Device
Re: [IP CLEARANCE] Dubbo go-hessian2 project contribution
Hi, With no -1 votes being cast, this IP clearance vote passes by lazy consensus. I'll update the IP clearance page form [1] to include the result. [1] https://incubator.apache.org/ip-clearance/dubbo-go-hessian2.html On Tue, Jul 23, 2019 at 4:09 PM Huxing Zhang wrote: > > Hi Incubator PMC, > > The Apache Dubbo has been donated code for hessian2[1] being > referred to as `dubbo-go-hessian2`. > > This is the formal request for IP clearance to be checked as per [2]. > The donated code can be found at [3] . > > Please check the ip-clearance filed here[4] for more information. > The PMC has voted and passed to accept this donation[5]. > The ICLA of contributors have been filed. > Secretary has confirmed that SGA is not needed[6]. > > Please vote to approve this contribution. > > This majority vote is open for at least 72 hours and as usual lazy > consensus applies. > > [1] https://github.com/dubbogo/hessian2 > [2] > https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling > [3] https://issues.apache.org/jira/browse/INCUBATOR-242 > [4] https://incubator.apache.org/ip-clearance/dubbo-go-hessian2.html > [5] > https://lists.apache.org/thread.html/8e3df8f44969f8a24d20573e5128a45e66492988065aded5e0afde2e@%3Cdev.dubbo.apache.org%3E > [6] > https://lists.apache.org/thread.html/0c1b6446cbef47e8fb803db90a9a22c732e65dec2a24766364f1ab15@%3Cprivate.dubbo.apache.org%3E > -- > Best Regards！ > Huxing -- Best Regards！ Huxing - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Rya (Incubating) version 4.0.0 RC1
+1 (binding) I checked: - incubating in name - signatures and hashes okay - DISCLAIMER exists - NOTICE year needs updating as previously noted (fix next release) - LICENSE is okay - No unexpected binary files - Al files have ASF headers - `mvn -DskipTests clean install` passes - `mvn clean install` fails (probably my machine) On Tue, Jul 23, 2019 at 8:24 AM Aaron D. Mihalik wrote: > The Apache Rya community has voted and approved the proposed release of > Apache Rya 4.0.0 (Incubating) RC1. > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that > supports SPARQL queries. Rya is a scalable RDF data management system built > on top of Apache Accumulo®. Rya uses novel storage methods, indexing > schemes, and query processing techniques that scale to billions of triples > across multiple nodes. Rya provides fast and easy access to the data > through SPARQL, a conventional query mechanism for RDF data. More > information can be found at http://rya.incubator.apache.org/ > > [VOTE] Thread: > > https://lists.apache.org/thread.html/e4ac6e5908dd61912d9f6423d6eab794fc07a77db5a3606b583bef60@%3Cdev.rya.apache.org%3E > > [VOTE][RESULT] Email: > > https://lists.apache.org/thread.html/a26193173404558eec762a39dd8ab87890c9fd536c37a8f6d1ae0f85@%3Cdev.rya.apache.org%3E > > The source zip, including signatures, digests, etc. can be found at: > > https://dist.apache.org/repos/dist/dev/incubator/rya/rya-incubating-4.0.0-rc1/ > > Ancillary artifacts such as poms, jars, wars, ect. can be found here: > > https://repository.apache.org/content/repositories/orgapacherya-1011/org/apache/rya/ > > The Git tag is rya-incubating-4.0.0-rc1 > The Git commit ID is 824090ac1b33c3b4ba52bfb8a67abfdc4f0ceea3 > > https://gitbox.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=824090ac1b33c3b4ba52bfb8a67abfdc4f0ceea3 > > Checksums of rya-project-4.0.0-source-release.zip: > SHA1: e5e91b19abddbdf3c9f0e18469433e730bef7957 > MD5: 1d46620a37df803c3ba0b1b383c1da10 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/mihalik.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/incubator/rya/KEYS > > Issues that were closed/resolved for this release are here: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319020=12341289 > > > The vote will be open for 72 hours and close at 6:30 PM Thursday, July 25, > 2019 (EDT). > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, and test. Then > please vote: > > [ ] +1 Release this package as rya-project-4.0.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because because... >
