Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex
Hi, In my opinion mentioning such trademarks in documentation is perfectly ok as long as we acknowledge them, I don't see how that could cause harm to their owner. And normally that would be the case and everything would be fine. However Adobe legal have asked to add a non standard attribution which may (or may not) exclude us using their other trademarks like Photoshop, Illustrator, Dreamweaver, ColdFusion etc that are also contained within the donated content and that were missed when doing the IP clearance. Again possible solutions are: 1) Use standard attribution [1] for AIR, Flash and remove all other Adobe trademarks. Should be straight forward and neither Adobe or us should have an issue with that. 2) Leave all trade marks in, add the provided non standard attribution for all Adobe trademarks, and double check with Adobe legal if that’s what they actually intended. The simpler option would be IMO 1. It is extremely hard to second guess what Adobe legal requires or even intended here as a) the conversation around this happened off list b) no reason has been given for using the non standard attribution. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex
Hi, On Fri, Apr 24, 2015 at 10:13 AM, Justin Mclean jus...@classsoftware.com wrote: ...Adobe legal have asked to add a non standard attribution which may (or may not) exclude us using their other trademarks like Photoshop, Illustrator, Dreamweaver, ColdFusion etc that are also contained within the donated content and that were missed when doing the IP clearance Where can I see that non standard attribution? A jira ticket might be good to be able to follow and document what's happening here. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Help publishing Myriad status page update
Worked. Thanks Marvin! -me- On Fri, Apr 24, 2015 at 12:33 AM, Marvin Humphrey mar...@rectangular.com wrote: On Fri, Apr 24, 2015 at 12:12 AM, Adam Bordelon a...@mesosphere.io wrote: I managed to commit my first change to the status page set up by our mentors, and it looks like the build succeeded: http://ci.apache.org/builders/incubator-site-staging/builds/585 However, when I try to publish the page, I get the following error: svnmucc: E175013: Access to '/repos/infra/!svn/txr/948995-kdyv/websites/production/incubator/content' forbidden I tried on both https://cms.apache.org/incubator/publish and https://incubator.staging.apache.org/incubator/publish Is it possible that I have commit permissions, but not publish permissions? I am already an Apache Mesos committer, but this is my first incubator project. Yes, that's right -- you weren't in the incubator ldap group. To deal with this expeditiously, I just abused my privileges as Lucy Chair to run modify_unix_group.pl and added you. (Officially it should have been the IPMC Chair granting karma, but this is an unusual situation.) Please try publishing again. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Whimsy PMC
On Fri, Apr 24, 2015 at 8:47 AM, Shane Curcuru a...@shanecurcuru.org wrote: On 4/23/15 5:41 PM, Ross Gardler (MS OPEN TECH) wrote: Infra already supports Whimsy so having a TLP is irrelevant in that respect (although on reason Sam is doing this is because infra expressed a concern about maintaining a service that only had Sam working on it). To be clear: is the current whimsy.apache.org with a variety of board agenda, email lookup, etc. services a formally infra-supported service? Just curious. I would lobby that it should be formally supported at a normal level (i.e. it's not critical level like email/svn is). (Apologies if we already formally talked about this) Short version: Ross has requested that it be, but the reality isn't quite there yet. Longer version: to be clear, there is no 'fault' in what I am about to say. If the VM goes down, or becomes inaccessible, the infra team does quickly take responsibility. Tool by tool, however is a different matter. We are trying to work through the details. An example: https://issues.apache.org/jira/browse/INFRA-9095 As stated there I believe that there is a big difference between the secretary workbench and the STV vote explorer tool in terms of foundation priority. The service is separate from the TLP status. We run the service to help our own project operations, which we'll do in any case. The presumed pTLP would be to develop the code; I could easily imagine some of the code being useful as examples outside of the ASF. Being a pTLP would also make development easier for newcomers, since code/mailinglists/etc. would all be normalized with other projects. The relationship is tenuous, but there is a relationship. The infrastructure team should not be deploying or held responsible for tools that are developed and maintained by a single individual. It doesn't matter whether that person has been around for more than a decade, or is formally on the infra payroll. Or both, as was the case with Joe and the CMS. To take an example, the board agenda tool should be maintained by a community. The infra team should have some responsibility for deploying and monitoring that tool, but shouldn't be responsible for feature development. Of course individuals on the infrastructure team would be welcome to be a part of the community. I'm +1 and will join. Great! Please update the wiki page. - Shane - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Whimsy PMC
On 24 April 2015 at 14:47, Shane Curcuru a...@shanecurcuru.org wrote: On 4/23/15 5:41 PM, Ross Gardler (MS OPEN TECH) wrote: Infra already supports Whimsy so having a TLP is irrelevant in that respect (although on reason Sam is doing this is because infra expressed a concern about maintaining a service that only had Sam working on it). To be clear: is the current whimsy.apache.org with a variety of board agenda, email lookup, etc. services a formally infra-supported service? Just curious. I would lobby that it should be formally supported at a normal level (i.e. it's not critical level like email/svn is). (Apologies if we already formally talked about this) if you look at the infra ML, it is not full support like e.g. the mail server, but merely a restart it help. That was the reason for my question in order to have a fully supported service (upgrades, bug fixes in response to OS upgrades etc, maintaining the vm as such), infra might have wishes to the project. The service is separate from the TLP status. We run the service to help our own project operations, which we'll do in any case. The presumed pTLP would be to develop the code; I could easily imagine some of the code being useful as examples outside of the ASF. Being a pTLP would also make development easier for newcomers, since code/mailinglists/etc. would all be normalized with other projects. I thought the pTLP was also there to help in case of OS upgrades and other external things that might affect the running whimsy service. rgds jan i. I'm +1 and will join. - Shane Ross -Original Message- From: jan i [mailto:j...@apache.org] Sent: Thursday, April 23, 2015 2:32 PM To: general@incubator.apache.org Subject: Re: [DISCUSS] Whimsy PMC On Thursday, April 23, 2015, Sam Ruby ru...@intertwingly.net wrote: Initial sketch placed on the wiki: https://wiki.apache.org/incubator/WhimsyProposal Anyone who is so inclined is welcome to edit the proposal directly. No urgency or timeframe in mind (other than preferably starting sometime in 2015ish). My current thinking is to follow in Steve's footprints and go directly to TLP, but I'm starting a discussion here (in Incubator) to see if there are any other thoughts on the matter. I like the proposal, it is very clear, I do miss one bit though. If this becomes a TLP project is infra then prepared to support keeping whimsy running 24/7, or do they have additional requirements on the project? maybe the response to the above could be worked into the proposal. rgds jan i - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Sent from My iPad, sorry for any misspellings. - 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: [DISCUSS] Whimsy PMC
On 4/23/15 5:41 PM, Ross Gardler (MS OPEN TECH) wrote: Infra already supports Whimsy so having a TLP is irrelevant in that respect (although on reason Sam is doing this is because infra expressed a concern about maintaining a service that only had Sam working on it). To be clear: is the current whimsy.apache.org with a variety of board agenda, email lookup, etc. services a formally infra-supported service? Just curious. I would lobby that it should be formally supported at a normal level (i.e. it's not critical level like email/svn is). (Apologies if we already formally talked about this) The service is separate from the TLP status. We run the service to help our own project operations, which we'll do in any case. The presumed pTLP would be to develop the code; I could easily imagine some of the code being useful as examples outside of the ASF. Being a pTLP would also make development easier for newcomers, since code/mailinglists/etc. would all be normalized with other projects. I'm +1 and will join. - Shane Ross -Original Message- From: jan i [mailto:j...@apache.org] Sent: Thursday, April 23, 2015 2:32 PM To: general@incubator.apache.org Subject: Re: [DISCUSS] Whimsy PMC On Thursday, April 23, 2015, Sam Ruby ru...@intertwingly.net wrote: Initial sketch placed on the wiki: https://wiki.apache.org/incubator/WhimsyProposal Anyone who is so inclined is welcome to edit the proposal directly. No urgency or timeframe in mind (other than preferably starting sometime in 2015ish). My current thinking is to follow in Steve's footprints and go directly to TLP, but I'm starting a discussion here (in Incubator) to see if there are any other thoughts on the matter. I like the proposal, it is very clear, I do miss one bit though. If this becomes a TLP project is infra then prepared to support keeping whimsy running 24/7, or do they have additional requirements on the project? maybe the response to the above could be worked into the proposal. rgds jan i - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Sent from My iPad, sorry for any misspellings. - 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: [DISCUSS] Whimsy PMC
On Thu, Apr 23, 2015 at 8:36 PM, Sam Ruby ru...@intertwingly.net wrote: On Thu, Apr 23, 2015 at 8:58 PM, Greg Stein gst...@gmail.com wrote: I'd suggest striking the user@ mailing list. Keep the community (such as it is) on dev@ until traffic gets too heavy. I've seen early splitting of the user/dev keep a new project from reaching a good critical mass. FWIW, I copied from Steve. Struck. Yeah :-( ... before sending my email, I realized Steve actually has a user@ mailing list. Bleh. Missed that when we set up, and now I see there have been a few messages there. Mostly just pending. The community is over/only on dev@. Cheers, -g
Re: [DISCUSS] Whimsy PMC
Updated proposal with everyone from board@ that expressed interest in being involved -Jake On Fri, Apr 24, 2015 at 9:24 AM, Sam Ruby ru...@intertwingly.net wrote: On Fri, Apr 24, 2015 at 8:47 AM, Shane Curcuru a...@shanecurcuru.org wrote: On 4/23/15 5:41 PM, Ross Gardler (MS OPEN TECH) wrote: Infra already supports Whimsy so having a TLP is irrelevant in that respect (although on reason Sam is doing this is because infra expressed a concern about maintaining a service that only had Sam working on it). To be clear: is the current whimsy.apache.org with a variety of board agenda, email lookup, etc. services a formally infra-supported service? Just curious. I would lobby that it should be formally supported at a normal level (i.e. it's not critical level like email/svn is). (Apologies if we already formally talked about this) Short version: Ross has requested that it be, but the reality isn't quite there yet. Longer version: to be clear, there is no 'fault' in what I am about to say. If the VM goes down, or becomes inaccessible, the infra team does quickly take responsibility. Tool by tool, however is a different matter. We are trying to work through the details. An example: https://issues.apache.org/jira/browse/INFRA-9095 As stated there I believe that there is a big difference between the secretary workbench and the STV vote explorer tool in terms of foundation priority. The service is separate from the TLP status. We run the service to help our own project operations, which we'll do in any case. The presumed pTLP would be to develop the code; I could easily imagine some of the code being useful as examples outside of the ASF. Being a pTLP would also make development easier for newcomers, since code/mailinglists/etc. would all be normalized with other projects. The relationship is tenuous, but there is a relationship. The infrastructure team should not be deploying or held responsible for tools that are developed and maintained by a single individual. It doesn't matter whether that person has been around for more than a decade, or is formally on the infra payroll. Or both, as was the case with Joe and the CMS. To take an example, the board agenda tool should be maintained by a community. The infra team should have some responsibility for deploying and monitoring that tool, but shouldn't be responsible for feature development. Of course individuals on the infrastructure team would be welcome to be a part of the community. I'm +1 and will join. Great! Please update the wiki page. - Shane - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Whimsy PMC
On Fri, Apr 24, 2015 at 7:47 AM, Shane Curcuru a...@shanecurcuru.org wrote: ... our own project operations, which we'll do in any case. The presumed pTLP would be to develop the code; I could easily imagine some of the code being useful as examples outside of the ASF. Being a pTLP would also make development easier for newcomers, since code/mailinglists/etc. would all be normalized with other projects. The pTLP concept is on hiatus. We don't have any (lately, Orc and Zest hit TLP directly), and Whimsy is not suggested to operate under that idea. ... it would become a standard TLP. Cheers, -g
Re: [VOTE] Accept Geode into the Apache Incubator
+1 Niall (binding) On Monday, April 20, 2015, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Oxt I would like to call a VOTE for accepting Geode as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/GeodeProposal and is also included at the bottom of this email. Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST [ ] +1 accept Geode in the Incubator [ ] ±0 [ ] -1 because... Thanks, Roman. == Abstract == Geode is a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. Geode pools memory (along with CPU, network and optionally local disk) across multiple processes to manage application objects and behavior. It uses dynamic replication and data partitioning techniques for high availability, improved performance, scalability, and fault tolerance. Geode is both a distributed data container and an in-memory data management system providing reliable asynchronous event notifications and guaranteed message delivery. == Proposal == The goal of this proposal is to bring the core of Pivotal Software, Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software Foundation (ASF) in order to build a vibrant, diverse and self-governed open source community around the technology. Pivotal will continue to market and sell Pivotal GemFire based on Geode. Geode and Pivotal GemFire will be managed separately. This proposal covers the Geode source code (mainly written in Java), Geode documentation and other materials currently available on GitHub. While Geode is our primary choice for a name of the project, in order to facilitate PODLINGNAMESEARCH we have come up with two alternatives: * Haptic * FIG == Background == GemFire is an extremely mature and robust product that can trace its legacy all the way back to one of the first Object Databases for Smalltalk: GemStone. The GemFire code base has been maintained by the same group of engineers as a closed source project. Because of that, even though the engineers behind GemFire are the de-facto knowledge leaders for distributed in-memory management, they have had little exposure to the open source governance process.The original company developing GemStone and GemFire was acquired by VMWare in 2010 and later spun off as part of Pivotal Software in 2013. Today GemFire is used by over 600 enterprise customers. An example deployment includes China National Railways that uses Pivotal GemFire to run railway ticketing for the entire country of China with a 10 node cluster that manages 2 gigabytes hot data in memory, and 10 backup nodes for high availability and elastic scale. == Rationale == Modern-day data management architectures require a robust in-memory data grid solution to handle a variety of use cases, ranging from enterprise-wide caching to real-time transactional applications at scale. In addition, as memory size and network bandwidth growth continues to outpace those of disk, the importance of managing large pools of RAM at scale increases. It is essential to innovate at the same pace and Pivotal strongly believes that in the Big Data space, this can be optimally achieved through a vibrant, diverse, self-governed community collectively innovating around a single codebase while at the same time cross-pollinating with various other data management communities. ASF is the ideal place to meet these ambitious goals. == Initial Goals == Our initial goals are to bring Geode into the ASF, transition internal engineering processes into the open, and foster a collaborative development model according to the Apache Way. Pivotal plans to develop new functionality in an open, community-driven way. To get there, the existing internal build, test and release processes will be refactored to support open development. == Current Status == Currently, the project code base is licensed for evaluation purposes and is available for download from Pivotal.io (https://network.pivotal.io/products/project-geode). The documentation and wiki pages are available as public GitHub repositories under Project Geode organization on GitHub (https://github.com/project-geode). Although Pivotal GemFire was developed as a proprietary, closed-source product, the internal engineering practices adopted by the development team lend themselves well to an open, collaborative and meritocratic environment. The Pivotal GemFire team has always focused on building a robust end user community of paying and non-paying customers. The existing documentation along with StackOverflow and other similar forums are expected to facilitate conversions between our existing users so as to transform them into an active community of Geode members, stakeholders and developers. === Meritocracy === Our proposed
Re: [DISCUSS] Whimsy PMC
On Thu, Apr 23, 2015 at 8:46 PM, Sam Ruby ru...@intertwingly.net wrote: Initial sketch placed on the wiki: https://wiki.apache.org/incubator/WhimsyProposal Looks good to me! BTW as I've said before I think discussing new projects here even if they mean to go direct to TLP makes a lot of sense, so thanks for doing that. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Help publishing Myriad status page update
I managed to commit my first change to the status page set up by our mentors, and it looks like the build succeeded: http://ci.apache.org/builders/incubator-site-staging/builds/585 However, when I try to publish the page, I get the following error: svnmucc: E175013: Access to '/repos/infra/!svn/txr/948995-kdyv/websites/production/incubator/content' forbidden I tried on both https://cms.apache.org/incubator/publish and https://incubator.staging.apache.org/incubator/publish Is it possible that I have commit permissions, but not publish permissions? I am already an Apache Mesos committer, but this is my first incubator project.
Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex
Hi, On Thu, Apr 23, 2015 at 11:06 PM, Justin Mclean jus...@classsoftware.com wrote: ...can you clarify what you mean by use those trademarks”? By use I just mean have them appear in the existing text as they currently do. Obviously the missing attributions would also need to be added... So IIUC the donated docs that will eventually be published at http://flex.apache.org/ include mentions of trademarks that we do not own. In my opinion mentioning such trademarks in documentation is perfectly ok as long as we acknowledge them, I don't see how that could cause harm to their owner. So I suppose if those docs mention Flex and Foo, you just need to add a note that Apache Flex is our trademark, and Foo is a trademark of whoever owns it. Where there might be a problem is for other modules that were donated to Flex in the meantime, without providing an explicit trademark donation - their name might need to be changed in Flex, if we don't own the corresponding trademarks. But that's not directly related to this issue IIUC. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Help publishing Myriad status page update
On Fri, Apr 24, 2015 at 12:12 AM, Adam Bordelon a...@mesosphere.io wrote: I managed to commit my first change to the status page set up by our mentors, and it looks like the build succeeded: http://ci.apache.org/builders/incubator-site-staging/builds/585 However, when I try to publish the page, I get the following error: svnmucc: E175013: Access to '/repos/infra/!svn/txr/948995-kdyv/websites/production/incubator/content' forbidden I tried on both https://cms.apache.org/incubator/publish and https://incubator.staging.apache.org/incubator/publish Is it possible that I have commit permissions, but not publish permissions? I am already an Apache Mesos committer, but this is my first incubator project. Yes, that's right -- you weren't in the incubator ldap group. To deal with this expeditiously, I just abused my privileges as Lucy Chair to run modify_unix_group.pl and added you. (Officially it should have been the IPMC Chair granting karma, but this is an unusual situation.) Please try publishing again. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache TinkerPop 3.0.0.M8-incubating Release (Part Deux)
Hello everyone, We need one more +1 vote to release. A review would be much appreciated. Thank you, Marko. http://markorodriguez.com On Apr 23, 2015, at 6:31 PM, Matt Franklin m.ben.frank...@gmail.com wrote: +1 binding On Tue, Apr 21, 2015 at 10:03 PM Justin Mclean jus...@classsoftware.com wrote: Hi, (sending again as sent from wrong address first time) +1 binding For the source release I checked: - incubating in artifact name - signatures and hashes good - LICENSE and NOTICE ok - All source files have Apache headers - No unexpected binary files - Still can’t compile from source but it tells me I have wrong java version - most of the issues raised from the last release have been fixed Minor issues - please fix for next release. - No need to add normalise.css to NOTICE as it is MIT licensed (Permissive licenses only need to be added to LICENSE in most cases - the main exceptions being Apache licensed software with NOTICE files and files that have had their copyright removed). The copyright notice here should go into LICENSE. - I'm still not sure of the reason why some of the artefacts are named gremlin rather than tinkerpop Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
