Re: all podlings please update and maintain project metadata
Christian Grobmeier wrote: > Daniel Shahaf wrote: > > Shane Curcuru wrote: > >> > >> Separately, I'd love to hear any comments about how this kind of > >> requirement is expressed in the graduation guides. I.e. is it clear, > >> even to normal humans (i.e. 99.99% of the world who are not Incubator > >> experts) that these things are required of TLPs before (and after) > >> graduation? > > > > FWIW, https://www.apache.org/dev/infra-contact#requesting-graduation > > seems to be read and followed by most graduating projects. Ah, maybe we have identified the breakdown. Perhaps they skip the Incubator documentation. I reckon that we need to link in both directions. > Guess we need to give this a little love: > http://incubator.apache.org/guides/graduation.html#project-first-steps > and point to the new docs (which are fantastic btw) Yes. We already do point to the infra docs. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Proposal for better docs on trademark research (Incubator)
Daniel Shahaf wrote: > Christian Grobmeier wrote: > > Daniel Shahaf wrote: > > > > >> +GitHub > > >> +SourceForge.net > > >> +Google Code > > >> +Ohloh > > >> + > >> href="http://tsdr.uspto.gov";>USPTO > > >> +Google, Bing, Yahoo > > >> + > >> href="http://www.trademarkia.com";>Trademarkia > > > > > > Errr. Isn't this list of resources already available on another page? > > > If so please just point to it, rather than duplicate it. (There should > > > be exactly one canonical location for such info.) > > > > I didn't find one, > > /me surprised Yes there was already documentation. See http://incubator.apache.org/guides/names.html Some of the discussions that devised the process: http://s.apache.org/suitable-names-search-1 Subject: Trademark Kill Searches... Date: 2011-10-25 http://s.apache.org/suitable-names-search-2 Subject: Suitable Names Search [WAS Re: Trademark Kill Searches...] Date: 2011-11-09 http://s.apache.org/suitable-names-search-3 Subject: [Podling Suitable Name Search] Feedback Please Date: 2011-11-22 http://s.apache.org/suitable-names-search-4 Subject: [POLL] Suitable Name Search: Drop Or Retain? Date: 2011-11-29 http://s.apache.org/suitable-names-search-5 Subject: Help Wanted: Improved Podling Name Search Documentation Date: 2012-01-15 http://s.apache.org/suitable-names-search-6 Subject: [names] Public Review Date: 2012-01-29 http://s.apache.org/suitable-names-search-7 Subject: Proposal for better docs on trademark research (Incubator) Date: 2013-03-18 -David > > thats why I took the time and worked on this docs. > > I extracted the information from the old Jira issues. > > Thanks. > > > > And BTW infra experience tells me info about execuding the PNS > > > process (PODLINGNAMESEARCH) should live on www.a.o/foundation/marks/, > > > but that might be an issue for another patch. > > > > Its PODLING name search. Because of this name I was looking in the > > incubator docs first. > > As long as it is not named "NAMESEARCH" only I think it belongs to the > > incubator. > > If you have a semantic argument (eg: why shouldn't Apache Steve have > been expected to run a name search at some point) I'll be glad to hear it. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
Falcon is also the name of a database engine: http://en.wikipedia.org/wiki/Falcon_(storage_engine) the name of a programming language http://falconpl.org/project_docs/core/index.html and very close to the name of some kind of oracle add on vendor: http://www.falconstor.com/solutions/business-applications/oracle-database-solutions david jencks On Mar 20, 2013, at 10:02 PM, Srikanth Sundarrajan wrote: > Hi Justin, >I am assuming it won't be an issue as Falcon used within the > Adobe/Apache Flex isn't related to Hadoop. > > Regards > Srikanth Sundarrajan > > On Thu, Mar 21, 2013 at 10:23 AM, Justin Mclean wrote: > >> Hi, >> >> JFYI Falcon is already a name used by Adobe and Apache Flex. It's an AS >> compiler and an experimental AS to JS compiler (Falcon JS) - not sure if >> that is an issue or not. >> >> Justin >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> > > -- > _ > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others > authorized to receive it. It may contain confidential or legally privileged > information. If you are not the intended recipient you are hereby notified > that any disclosure, copying, distribution or taking any action in reliance > on the contents of this information is strictly prohibited and may be > unlawful. If you have received this communication in error, please notify > us immediately by responding to this email and then delete it from your > system. The firm is neither liable for the proper and complete transmission > of the information contained in this communication nor for any delay in its > receipt. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
Hi Justin, I am assuming it won't be an issue as Falcon used within the Adobe/Apache Flex isn't related to Hadoop. Regards Srikanth Sundarrajan On Thu, Mar 21, 2013 at 10:23 AM, Justin Mclean wrote: > Hi, > > JFYI Falcon is already a name used by Adobe and Apache Flex. It's an AS > compiler and an experimental AS to JS compiler (Falcon JS) - not sure if > that is an issue or not. > > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- _ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
[VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)
Hi, Thanks for participating in the proposal discussion on Falcon (formerly Ivory). I'd like to call a VOTE for acceptance of Apache Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST). [ ] +1 Accept Apache Falcon into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Falcon into the Incubator because... Full proposal is pasted at the bottom of this email, and the corresponding wiki is http://wiki.apache.org/incubator/FalconProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Srikanth Sundarrajan = Falcon Proposal = == Abstract == Falcon is a data processing and management solution for Hadoop designed for data motion, coordination of data pipelines, lifecycle management, and data discovery. Falcon enables end consumers to quickly onboard their data and its associated processing and management tasks on Hadoop clusters. == Proposal == Falcon will enable easy data management via declarative mechanism for Hadoop. Users of Falcon platform simply define infrastructure endpoints, data sets and processing rules declaratively. These declarative configurations are expressed in such a way that the dependencies between these configured entities are explicitly described. This information about inter-dependencies between various entities allows Falcon to orchestrate and manage various data management functions. The key use cases that Falcon addresses are: * Data Motion * Process orchestration and scheduling * Policy-based Lifecycle Management * Data Discovery * Operability/Usability With these features it is possible for users to onboard their data sets with a comprehensive and holistic understanding of how, when and where their data is managed across its lifecycle. Complex functions such as retrying failures, identifying possible SLA breaches or automated handling of input data changes are now simple directives. All the administrative functions and user level functions are available via RESTful APIs. CLI is simply a wrapper over the RESTful APIs. == Background == Hadoop and its ecosystem of products have made storing and processing massive amounts of data commonplace. This has enabled numerous organizations to gain valuable insights that they never could have achieved in the past. While it is easy to leverage Hadoop for crunching large volumes of data, organizing data, managing life cycle of data and processing data is fairly involved. This is solved adequately well in a classic data platform involving data warehouses and standard ETL (extract-transform-load) tools, but remains largely unsolved today. In addition to data processing complexities, Hadoop presents new sets of challenges and opportunities relating to management of data. Data Management on Hadoop encompasses data motion, process orchestration, lifecycle management, data discovery, etc. among other concerns that are beyond ETL. Falcon is a new data processing and management platform for Hadoop that solves this problem and creates additional opportunities by building on existing components within the Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without reinventing the wheel. Falcon has been in production at InMobi, going on its second year and has been managing hundreds of feeds and processes. Falcon is being developed by engineers employed with InMobi and Hortonworks. This platform addition will increase the adoption of Apache Hadoop by driving data management tractable for end users. We are therefore proposing to make Falcon an Apache open source project. == Rationale == The Falcon project aims to improve the usability of Apache Hadoop. As a result Apache Hadoop will grow its community of users by increasing the places Hadoop can be utilized and the use cases it will solve. By developing Falcon in Apache we hope to gather a diverse community of contributors, helping to ensure that Falcon is deployable for a broad range of scenarios. Members of the Hadoop development community will be able to influence Falcon’s roadmap, and contribute to it. We believe having Falcon as part of the Apache Hadoop ecosystem will be a great benefit to all of Hadoop's users. == Current Status == Falcon is widely deployed in production within InMobi and moving on to its second year. A version with a valuable set of features is developed by the list of initial committers and is hosted on github. === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around Falcon following the Apache meritocracy model. We have wanted to make the project open source and encourage contributors from multiple organizations from the start. We plan to provide plenty of support to new developers and to quickly recruit those who make solid contributions to committer status. === Community === We are happy to report that the initial team already represents multiple organizations. We hope to extend the user and develope
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
Hi, JFYI Falcon is already a name used by Adobe and Apache Flex. It's an AS compiler and an experimental AS to JS compiler (Falcon JS) - not sure if that is an issue or not. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
As there were a few concerns relating to the name of the project, we are renaming this project to Falcon. The proposal has been updated accordingly. (PS: http://wiki.apache.org/incubator/FalconProposal) = Falcon Proposal = == Abstract == Falcon is a data processing and management solution for Hadoop designed for data motion, coordination of data pipelines, lifecycle management, and data discovery. Falcon enables end consumers to quickly onboard their data and its associated processing and management tasks on Hadoop clusters. == Proposal == Falcon will enable easy data management via declarative mechanism for Hadoop. Users of Falcon platform simply define infrastructure endpoints, data sets and processing rules declaratively. These declarative configurations are expressed in such a way that the dependencies between these configured entities are explicitly described. This information about inter-dependencies between various entities allows Falcon to orchestrate and manage various data management functions. The key use cases that Falcon addresses are: * Data Motion * Process orchestration and scheduling * Policy-based Lifecycle Management * Data Discovery * Operability/Usability With these features it is possible for users to onboard their data sets with a comprehensive and holistic understanding of how, when and where their data is managed across its lifecycle. Complex functions such as retrying failures, identifying possible SLA breaches or automated handling of input data changes are now simple directives. All the administrative functions and user level functions are available via RESTful APIs. CLI is simply a wrapper over the RESTful APIs. == Background == Hadoop and its ecosystem of products have made storing and processing massive amounts of data commonplace. This has enabled numerous organizations to gain valuable insights that they never could have achieved in the past. While it is easy to leverage Hadoop for crunching large volumes of data, organizing data, managing life cycle of data and processing data is fairly involved. This is solved adequately well in a classic data platform involving data warehouses and standard ETL (extract-transform-load) tools, but remains largely unsolved today. In addition to data processing complexities, Hadoop presents new sets of challenges and opportunities relating to management of data. Data Management on Hadoop encompasses data motion, process orchestration, lifecycle management, data discovery, etc. among other concerns that are beyond ETL. Falcon is a new data processing and management platform for Hadoop that solves this problem and creates additional opportunities by building on existing components within the Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without reinventing the wheel. Falcon has been in production at InMobi, going on its second year and has been managing hundreds of feeds and processes. Falcon is being developed by engineers employed with InMobi and Hortonworks. This platform addition will increase the adoption of Apache Hadoop by driving data management tractable for end users. We are therefore proposing to make Falcon an Apache open source project. == Rationale == The Falcon project aims to improve the usability of Apache Hadoop. As a result Apache Hadoop will grow its community of users by increasing the places Hadoop can be utilized and the use cases it will solve. By developing Falcon in Apache we hope to gather a diverse community of contributors, helping to ensure that Falcon is deployable for a broad range of scenarios. Members of the Hadoop development community will be able to influence Falcon’s roadmap, and contribute to it. We believe having Falcon as part of the Apache Hadoop ecosystem will be a great benefit to all of Hadoop's users. == Current Status == Falcon is widely deployed in production within InMobi and moving on to its second year. A version with a valuable set of features is developed by the list of initial committers and is hosted on github. === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around Falcon following the Apache meritocracy model. We have wanted to make the project open source and encourage contributors from multiple organizations from the start. We plan to provide plenty of support to new developers and to quickly recruit those who make solid contributions to committer status. === Community === We are happy to report that the initial team already represents multiple organizations. We hope to extend the user and developer base further in the future and build a solid open source community around Falcon. === Core Developers === Falcon is currently being developed by three engineers from InMobi – Srikanth Sunderrajan, Shwetha G S, and Shaik Idris, two Hortonworks employees – Sanjay Radia and Venkatesh Seetharam. In addition, Rohini Palaniswamy and Thiruvel Thirumoolan, were also involved in the initial design discus
Re: all podlings please update and maintain project metadata
On Wed, Mar 20, 2013 at 3:32 PM, Daniel Shahaf wrote: > Shane Curcuru wrote on Wed, Mar 20, 2013 at 08:57:55 -0400: >> Separately, I'd love to hear any comments about how this kind of >> requirement is expressed in the graduation guides. I.e. is it clear, >> even to normal humans (i.e. 99.99% of the world who are not Incubator >> experts) that these things are required of TLPs before (and after) >> graduation? > > FWIW, https://www.apache.org/dev/infra-contact#requesting-graduation > seems to be read and followed by most graduating projects. Guess we need to give this a little love: http://incubator.apache.org/guides/graduation.html#project-first-steps and point to the new docs (which are fantastic btw) > - > 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
Re: all podlings please update and maintain project metadata
Shane Curcuru wrote on Wed, Mar 20, 2013 at 08:57:55 -0400: > Separately, I'd love to hear any comments about how this kind of > requirement is expressed in the graduation guides. I.e. is it clear, > even to normal humans (i.e. 99.99% of the world who are not Incubator > experts) that these things are required of TLPs before (and after) > graduation? FWIW, https://www.apache.org/dev/infra-contact#requesting-graduation seems to be read and followed by most graduating projects. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: all podlings please update and maintain project metadata
Similarly, it is a *requirement* that TLPs keep their DOAP files and other aspects of their project websites updated. So it's a really good thing for podlings to get in this habit before graduation. http://www.apache.org/foundation/marks/pmcs Separately, I'd love to hear any comments about how this kind of requirement is expressed in the graduation guides. I.e. is it clear, even to normal humans (i.e. 99.99% of the world who are not Incubator experts) that these things are required of TLPs before (and after) graduation? - Shane On 3/18/2013 10:23 PM, David Crossley wrote: Please maintain your incubation metadata. This then enables other volunteers to have information at their fingertips to assist them to assist others. There are also some automated processes that utilise this metadata, as also happens when you become a Top-Level Project (TLP). Please see previous email below. -David David Crossley wrote: Would all podlings please update and maintain your project metadata. It is up to your project members. This metadata is used by various processes to assist with managing the many projects in the Incubator. Please do not expect other people to do it for you. This will not scale, either now or when you are TLPs. Recently Clutch is detecting that there are many such issues [1]. The notes in that table try to assist by linking to some relevant documentation. Incoming projects need to add their details to content/podlings.xml Incubating projects need to keep that content up-to-date. Outgoing projects need to adjust that content as they go through the graduation phases. This then assists all volunteers to assist all volunteers. [1] http://incubator.apache.org/clutch.html#other -David - 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
