Re: [VOTE] Graduate Apache MADlib podling

[Gregory Chase]

+1 (loiterer)

On Tue, May 30, 2017 at 6:09 PM, Konstantin Boudnik  wrote:

> +1 [binding]
>
> On Sat, May 27, 2017 at 04:56PM, FENG, Xixuan (Aaron) wrote:
> > Greetings IPMC!
> >
> > The discussion seems to have died down, so I'm calling the
> > vote:  I propose that we graduate Apache MADlib from the Incubator.
> > The full text of the proposal is below.  The discuss thread can be found
> > here:
> > https://lists.apache.org/thread.html/535f9871636f6e10c13e47f1ec6e41
> > 5eca7f666e1580d8b762d8a42d@%3Cgeneral.incubator.apache.org%3E
> >
> > Please vote on the resolution:
> >
> > [ ] +1 Graduate Apache MADlib from the Incubator.
> > [ ] +0 No opinion
> > [ ] -1 Don't graduate Apache MADlib from the Incubator (please provide
> > the reason)
> >
> > This VOTE will be opened for the next 72 hours.
> >
> > Thanks to all Mentors and Apache MADlib Project members for their
> > support and contributions.
> >
> > Thanks,
> > Aaron.
> >
> > Resolution:
> >
> > Establish the Apache MADlib Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best
> > interests of the Foundation and consistent with the
> > Foundation's purpose to establish a Project Management
> > Committee charged with the creation and maintenance of
> > open-source software, for distribution at no charge to the
> > public, related to a scalable, Big Data, SQL-driven machine
> > learning framework for Data Scientists.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache MADlib Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache MADlib Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to a scalable, Big Data, SQL-driven machine
> > learning framework for Data Scientists.
> >
> > RESOLVED, that the office of "Vice President, Apache MADlib" be
> > and hereby is created, the person holding such office to
> > serve at the direction of the Board of Directors as the chair
> > of the Apache MADlib Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache MADlib Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and
> > hereby are appointed to serve as the initial members of the
> > Apache MADlib Project:
> >
> > Sarah Aerni 
> > Greg Chase 
> > Aaron Feng 
> > Rahul Iyer 
> > Jim Jagielski 
> > Nandish Jayaram 
> > Anirudh Kondaveeti 
> > Orhan Kışlal 
> > Frank McQuillan 
> > Srivatsan R 
> > Rashmi Raghu 
> > Roman Shaposhnik 
> > Atri Sharma 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Aaron Feng
> > be appointed to the office of Vice President, Apache MADlib, to
> > serve in accordance with and subject to the direction of the
> > Board of Directors and the Bylaws of the Foundation until
> > death, resignation, retirement, removal or disqualification,
> > or until a successor is appointed; and be it further
> >
> > RESOLVED, that the initial Apache MADlib PMC be and hereby is
> > tasked with the creation of a set of bylaws intended to
> > encourage open development and increased participation in the
> > Apache MADlib Project; and be it further
> >
> > RESOLVED, that the Apache MADlib Project be and hereby
> > is tasked with the migration and rationalization of the Apache
> > Incubator MADlib podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache
> > Incubator MADlib podling encumbered upon the Apache Incubator
> > Project are hereafter discharged.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Product team
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: Slack support?

[Gregory Chase]

Slack is becoming a standard in many non ASF communities.

RabbitMQ recently switched from IRC to Slack as its "real time"
conversation.

On Wed, Mar 22, 2017 at 5:43 PM, James Bognar 
wrote:

> There's interest from me personally.  Slack appears to be becoming
> popular.  HipChat appears to be slowing down in interest.
>
> On Wed, Mar 22, 2017 at 5:40 PM, John D. Ament 
> wrote:
>
> > Hey guys
> >
> > Just wondering, would there be interest within the Incubator allow Slack
> > support?  Presently ASF has support for HipChat and Gitter, but I see
> more
> > podlings coming in asking for Slack support.
> >
> > John
> >
>
>
>
> --
> James Bognar
>



-- 
Greg Chase

Product team
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: [ANNOUNCE] Apache Geode 1.0.0-incubating released

[Gregory Chase]

Congrats!

On Tue, Oct 25, 2016 at 3:33 PM, Swapnil Bawaskar 
wrote:

> The Apache Geode team is proud to announce Apache Geode release
> 1.0.0-incubating.
>
> Apache Geode (incubating) is a data management platform that provides a
> database-like consistency model, reliable transaction processing and a
> shared-nothing architecture to maintain very low latency performance with
> high concurrency processing.
>
> Download the new release here:
> http://geode.incubator.apache.org/releases/
>
> Changes since the last release include renaming packages from
> com.gemstone.gemfire to org.apache.geode, bundling docs with the source
> distribution, securing the REST API, and 225 other bug fixes and minor
> improvements.
> See the release notes for more details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12318420=12332343
>
> To get started with Apache Geode check out the Geode in 5 minutes tutorial:
> https://cwiki.apache.org/confluence/display/GEODE/Index#Index-
> Geodein5minutesGeodein5minutes
>
> To learn more and get involved, please visit our website in join our
> mailing
> lists:
> http://geode.incubator.apache.org/
>
> Regards,
> The Apache Geode (incubating) team
>
> =
> *Disclaimer*
>
> Apache Geode is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the name of Apache Incubator PMC. 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.
>



-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: Radical proposal: no initial list of committers

[Gregory Chase]

Having been through this with Apache Geode, I like the idea of paying
homage to emeritus committers in the proposal and history of the
technology.  If you start with a rule of providing committer privileges to
those who have directly committed to the project in the last two or three
years, and a liberal policy of granting new committer privileges as needed,
I think you should be ok.  Does an emeritus committer need commit
privileges today? Only if they start committing again.

And for those that want prestige - the prestige rests in being an active
evangelist of the project. One does not ever need to be a committer to
achieve prestige.

On Tue, Sep 27, 2016 at 7:03 AM, Emmanuel Lécharny 
wrote:

> Le 27/09/16 à 13:25, Greg Stein a écrit :
> > The NetBeans proposal (among many others in the past) has demonstrated a
> > significant "problem" with trying to establish an appropriate list of
> > initial committers. There are many people that want to be on, for various
> > reasons. Because they are committers, recent or historic. Or they want
> the
> > "prestige" to be there. Some people believe they "deserve" to be on the
> > list. etc etc
> >
> > Establishing the list is particularly difficult for large and old
> > communities.
> >
> > But. What if we just said "no such list" ?
> >
> > This will shift the initial voting of committers upon the
> Champion/Mentors
> > who will construct the entirety of the PPMC. But hey: aren't they
> supposed
> > to be involved? Aren't they supposed to demonstrate how to earn merit,
> and
> > the committership that results?
> >
> > This would also solve the problem of initial committers that have not
> > established any merit whatsoever. We've had many situations where people
> > simply add themselves to the list. Why? Cuz they chose to do so. It is
> sort
> > of silently allowed for IPMC members to add themselves. "I wanna join!"
> > BAM. It happens.
> >
> > So yeah. Radical thought: NO initial list. The PPMC is just the Champion
> +
> > Mentors. They will build the committers and PPMC according to merit.
> (note:
> > this could be *very* fast for a particular few highly-engaged with
> bringing
> > the project to the ASF)
> >
> > ???
> >
> > Cheers,
> > -g
> >
> Well, that's tempting...
>
>
> OTOH there is no problem with having an initial list, even with people
> who want to see their name on the web site for teh sake of their own ego
> : it's easy to demote committer in the long run (moving them to an
> emeritus status).
>
>
> We have so many dormant committers in so many projects anyway !
>
>
> My take is the initial list is just a curtesy made to the involved
> people, and a few more. Nothing less, nothing more. The PPMC list, OTOH,
> is critical.
>
>
> My 2 cts.
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: Notes on branding

[Gregory Chase]

On Fri, Jul 1, 2016 at 2:16 PM, John D. Ament  wrote:

> On Fri, Jul 1, 2016 at 4:52 PM Greg Chase  wrote:
>
> >
> >
> > This email encrypted by tiny buttons & fat thumbs, beta voice
> recognition,
> > and autocorrect on my iPhone.
> >
> > > On Jul 1, 2016, at 1:41 PM, John D. Ament 
> wrote:
> > >
> > >> On Fri, Jul 1, 2016 at 4:35 PM Tim Williams 
> > wrote:
> > >>
> > >> On Fri, Jul 1, 2016 at 3:05 PM, Marvin Humphrey <
> mar...@rectangular.com
> > >
> > >> wrote:
> > >>> On Fri, Jul 1, 2016 at 9:35 AM, Greg Chase 
> wrote:
> > >>>
> >  The branding guidelines do not address feedback such as "logo in
> > >> footer" or
> >  "disclaimer is buried deep or below the fold".
> > >>>
> > >>> Incubation disclaimers are intended to be substantive.  They are not
> > CYA
> > >> legal
> > >>> boilerplate that can be are buried in fine print. The intent is to
> > >> communicate
> > >>> (effectively!) to consumers that a project is incubating.
> > >>
> > >> I haven't heard anyone suggesting "CYA" or "buried in fine print"?
> > >> Most sites put notices at the bottom of a page similar to how we put
> > >> our equally important copyright/trademark notices at the bottom of our
> > >> home page.  That, along with having the page saying "(Incubating)" all
> > >> over the place is surely enough of a notice... this "must be above the
> > >> fold" stuff is overreaching and encroaching on the PPMC.  They have
> > >> the disclaimer, let's not overcome our boredom by being helicopter
> > >> parents...
> > >
> > > Please don't interpret the current research being done as saying that
> the
> > > logo/disclaimer has to be above the fold.  There are certain ways I've
> > seen
> > > the disclaimer where its not clear how its used, or what it's related
> to.
> > > I've seen podlings use differing fonts to make it seem unimportant, and
> > > actually think it makes more sense in the footer.
> > >
> > > John
> > >
> > >
> > The observations are listed as "issues" and this is described as a
> > "branding audit", not a "survey."
> >
> > The meaning is clear. It's fine if you choose to redefine as a result of
> > feedback.
> >
>
> Good point.  In my mind I was treating them as findings/observations.
> Reworded the title.
>
> John
>
>
> >
> >
> >
> >
> > >>
> > >> --tim
> > >>
> > >> -
> > >> 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
> >
> >
>


Now that is good fodder for a discussion.

Re: MADLib "contributors"

[Gregory Chase]

I would agree that MADlib can use more contributors to help make these
changes.  Would you like to join?

-Greg

On Thu, Jun 2, 2016 at 1:00 PM, Jim Jagielski <j...@jagunet.com> wrote:

> Part of the incubation process is to fully embrace the tenets of the
> Apache Way; considering that MADlib started in Sept 2015 and it is
> now June 2016, I would have expected that the page would have been
> changed awhile ago. It does beg the question on whether or not
> MADlib itself fully groks how important this issue is, allowing the
> page to continue as-is for so long...
>
>
> > On Jun 2, 2016, at 3:52 PM, Gregory Chase <gch...@pivotal.io> wrote:
> >
> > In MADlib's history, contribution was enabled by institutions prior to
> > coming to Apache.  However, I agree that this needs to be "historical"
> not
> > "current.
> >
> > -Greg
> >
> > On Thu, Jun 2, 2016 at 12:43 PM, Jim Jagielski <j...@jagunet.com> wrote:
> >
> >> Looking at:
> >>
> >>http://madlib.incubator.apache.org/community.html
> >>
> >> I am not sure I like the statement that:
> >>
> >>"including both individuals and institutions. Amongst our current
> >> contributors:"
> >>
> >> and then a list of entities.
> >>
> >> There are only individuals who contribute. Not institutions. In other
> >> words, Pivotal is not a "contributor"... nor is ANY institution.
> >>
> >> Please fix this. Thx!
> >>
> >> PS: I am not on the private@madlib list
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
> >
> > --
> > Greg Chase
> >
> > Global Head, Big Data Communities
> > http://www.pivotal.io/big-data
> >
> > Pivotal Software
> > http://www.pivotal.io/
> >
> > 650-215-0477
> > @GregChase
> > Blog: http://geekmarketing.biz/
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: MADLib "contributors"

[Gregory Chase]

In MADlib's history, contribution was enabled by institutions prior to
coming to Apache.  However, I agree that this needs to be "historical" not
"current.

-Greg

On Thu, Jun 2, 2016 at 12:43 PM, Jim Jagielski  wrote:

> Looking at:
>
> http://madlib.incubator.apache.org/community.html
>
> I am not sure I like the statement that:
>
> "including both individuals and institutions. Amongst our current
> contributors:"
>
> and then a list of entities.
>
> There are only individuals who contribute. Not institutions. In other
> words, Pivotal is not a "contributor"... nor is ANY institution.
>
> Please fix this. Thx!
>
> PS: I am not on the private@madlib list
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: Fwd: [jira] [Created] (HAWQ-694) 1844-313-4857 Quickbooks payroll support usa/canada

[Gregory Chase]

Cool and thanks!

On Thu, Apr 21, 2016 at 1:44 PM, Mark Thomas <ma...@apache.org> wrote:

> On 21/04/2016 21:40, Gregory Chase wrote:
> > Seems we have a JIRA user who's spamming Apache HAWQ? Is this a
> compromised
> > account, or someone who has access that shouldn't?
>
> It is a public Jira instance on which anyone can create an account.
> Sometimes spam happens. It is the cost of an open development process.
>
> The infra team is already on the case to clean up the spam and is
> looking into what further filtering can be applied to reduce future
> instances.
>
> Mark
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Fwd: [jira] [Created] (HAWQ-694) 1844-313-4857 Quickbooks payroll support usa/canada

[Gregory Chase]

Seems we have a JIRA user who's spamming Apache HAWQ? Is this a compromised
account, or someone who has access that shouldn't?

-Greg
-- Forwarded message --
From: Kalramin (JIRA) 
Date: Thu, Apr 21, 2016 at 1:34 PM
Subject: [jira] [Created] (HAWQ-694) 1844-313-4857 Quickbooks payroll
support usa/canada
To: iss...@hawq.incubator.apache.org


Kalramin created HAWQ-694:
-

 Summary: 1844-313-4857 Quickbooks  payroll support usa/canada
 Key: HAWQ-694
 URL: https://issues.apache.org/jira/browse/HAWQ-694
 Project: Apache HAWQ
  Issue Type: Bug
Reporter: Kalramin
Assignee: Lei Chang


1844-313-4857 Quickbooks  payroll support usa/canada1844-313-4857
Quickbooks  payroll support usa/canada cloud hostinggeneralQuickbooks
cloudcloud computing can be thought 1844-313-4857 as any instance where
you're using a computer that resides outside 1844-313-4857 your physical
locationQuickbooks cloud Most users encounter cloud computing  cloud
hostingthe form 1844-313-4857 s1844-313-4857tware as a serviceQuickbooks
cloud You might pay a fee for the serviceQuickbooks cloudsuch as QuickBooks
OnlineQuickbooks cloudSalesforceQuickbooks cloudcomQuickbooks cloudor
Micros1844-313-4857t's 1844-313-4857fice 365Quickbooks cloudor you may pay
cloud hostinga nonmonetary fashion through an advertising-supported and/or
information-gathering modelsQuickbooks cloudsuch as GmailQuickbooks
cloudMintQuickbooks cloudor FacebookQuickbooks cloud

Cloud computing gives you access to an environment that you can customize
or build out to suit your needsQuickbooks cloud With SaaSQuickbooks
cloudyou're limited to the features and capabilities written into the
s1844-313-4857twareQuickbooks cloudbut cloud computing 1844-313-4857fers
the ability to increase server capacity or storage space on
demandQuickbooks cloud
Cloud computing 1844-313-4857fers elasticityQuickbooks cloudmeaning your
resources and costs can increase or decrease with your demandsQuickbooks
cloud SaaS typically involves a set fee per userQuickbooks cloudper
monthQuickbooks cloudso costs and the functionality 1844-313-4857fered tend
to be fixedQuickbooks cloud
 cloud hostingshortQuickbooks cloudcloud computing is highly
customizableQuickbooks cloudwhereas SaaS 1844-313-4857fers more
1844-313-4857 Quickbooks cloudapproachQuickbooks cloud

For SaaSQuickbooks cloudend users are removed from maintaining both the
application and the server equipmentQuickbooks cloud Benefits 1844-313-4857
SaaS versus desktop programs include:
ApplicationsQuickbooks cloudsuch as QuickBooks OnlineQuickbooks cloudallow
you to access accounting records from anywhere  cloud hostingthe
worldQuickbooks cloudinstead 1844-313-4857 from specific computers with
cloud hostingyour 1844-313-4857ficeQuickbooks cloud
New features appear  cloud hostingthe s1844-313-4857tware
automaticallyQuickbooks cloudso there's no need to purchase a
s1844-313-4857tware upgrade to be physically installed on each
1844-313-4857 your computersQuickbooks cloud
Your data is backed up automaticallyQuickbooks cloudso a local hard drive
crash won't affect your dataQuickbooks cloud

Consider the recent situation with megauploadQuickbooks cloudcomQuickbooks
cloudwhere certa cloud hostingpurported illegal actions 1844-313-4857 a
subset 1844-313-4857 users caused everyone using the service to lose access
to dataQuickbooks cloud Think about a toddler having a certa cloud
hostingbodily function  cloud hostinga public swimming pool Quickbooks
cloud everyone has to suddenly get out 1844-313-4857 the waterQuickbooks
cloud SimilarlyQuickbooks cloudactions 1844-313-4857 one or more rogue
users can cause unexpected and dramatic disruptions for everyone else
sharing a cloud-based resourceQuickbooks cloud
Both cloud computing and SaaS involve trustQuickbooks cloud cloud
hostingthat you're trusting an organization to hold up its end
1844-313-4857 the bargainQuickbooks cloud IntuitQuickbooks cloudmaker
1844-313-4857 QuickBooksQuickbooks cloudlast year experienced a spate
1844-313-4857 outages that caused business interruptions for users
1844-313-4857 their myriad online servicesQuickbooks cloud
A service you trust and rely on could suddenly change handsQuickbooks
cloudsuch as Facebook's recent acquisition 1844-313-4857
InstagramQuickbooks cloud You may then be forced to find a new service
provider if you have philosophical differences with the new owner
1844-313-4857 a tool that you've relied on or if customer service levels
start to slip to unacceptable levelsQuickbooks cloud
If you stop paying for the serviceQuickbooks cloudaccess to your data can
be immediately terminatedQuickbooks cloud HoweverQuickbooks cloudmany
providers 1844-313-4857fer a grace periodQuickbooks cloud For
instanceQuickbooks cloudif you cancel your QuickBooks Online
accountQuickbooks cloudyour data is maintained for a yearQuickbooks
cloudshould you 

Re: [VOTE] Graduate Zeppelin from the Incubator

[Gregory Chase]

+1 (non binding), but I'm a fan :)

On Sat, Apr 16, 2016 at 1:55 PM, Roman Shaposhnik 
wrote:

> On Sat, Apr 16, 2016 at 2:01 AM, moon soo Lee  wrote:
> > Hi,
> >
> > Apache Zeppelin started incubating about a year and 4 months ago
> > (2014-12-23) and the members of the community think that it is ready to
> > graduate from the incubator to be a TLP.
> >
> > Since it's inception, Zeppelin community has made 3 releases, recruited 4
> > PPMC and resolved 500+ issues [1] with 90+ contributors [2]. Now,
> community
> > is very open, active and continuously growing.
> >
> > The Apache Zeppelin community has discussed and voted on graduation to
> > top level
> > project.
> > The vote passed with 22 +1 votes (9 binding) and no 0 or -1 votes.
> >
> > Incubation Status:
> > http://incubator.apache.org/projects/zeppelin.html
> > Maturity Assessment:
> >
> https://cwiki.apache.org/confluence/display/ZEPPELIN/Apache+Zeppelin+Project+Maturity+Model
> > Discussion:
> > https://s.apache.org/gLi0
> > https://s.apache.org/GhqY (continue)
> > Vote:
> > https://s.apache.org/7hCK
> > Result:
> > https://s.apache.org/1rJD
> >
> > Please vote on the resolution pasted below to graduate Apache Zeppelin
> > from the incubator to top level project.
> >
> > [ ] +1 Graduate Apache Zeppelin from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache Zeppelin from the Incubator because
>
> +1
>
> Zeppelin turned into an awesome ASF community. Best of luck to you guys --
> it
> was a privilege to help you as a mentor!
>
> Thanks,
> Roman.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: [MARKETING] Re: [MARKETING] Re: License question

[Gregory Chase]

Hi Dor,
I did a talk a few months ago about Apache Geode's journey to open source,
you might find some of the information in selecting licenses useful:
https://lnkd.in/bqfB-p3  

When one selects an Apache V2 license and grants the code and related
patents to Apache, they do so specifically to build a broad,
developer-owned, multi vendor community around the technology.  Compare
this with the Spring Framework which is a single vendor community run by
Pivotal, or Cloud Foundry or Docker, which are other foundations with their
own specific membership and governance policies.

Now in terms of how to contribute back to a community, checking in code is
one way, but I like this blog that explains them any other ways people can
contribute to a technology community:
http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/

-Greg

On Sun, Feb 21, 2016 at 10:06 AM, Dor Ben Dov 
wrote:

> Ted,
>
> Thanks for the answer, this is the exactly what I know. Now I am calm.
> Regard the last part, of course, going to apache incubator is a commitment
> And building the community, being the community helping the community
> Being activate, answer questions solve if possible bugs is the goal. One
> of the benefits
> In the long run of course, is the self-growth by others.
>
> Dor
>
> -Original Message-
> From: Ted Dunning [mailto:ted.dunn...@gmail.com]
> Sent: יום א 21 פברואר 2016 19:55
> To: general@incubator.apache.org
> Subject: [MARKETING] Re: [MARKETING] Re: License question
>
> Dor,
>
> The short answer is yes.  By open sourcing your code, you are giving it to
> the world. If somebody wants to do something with that code, they can.
>
> That may be what you want.  Or not.  You have to decide that.
>
> Keep in mind as well that if you go the Apache route, you will be expected
> to help build a community to carry this code forward over time regardless
> of what any single contributor might do. That means you might drop out, but
> others could continue the project.
>
>
>
>
>
> On Sun, Feb 21, 2016 at 2:32 PM, John D. Ament 
> wrote:
>
> > Hi Dor,
> >
> > Here's the relevant part of section 4 of the ALv2.
> >
> > You may add Your own copyright statement to Your modifications and may
> > provide additional or different license terms and conditions for use,
> > reproduction, or distribution of Your modifications, or for any such
> > Derivative Works as a whole, provided Your use, reproduction, and
> > distribution of the Work otherwise complies with the conditions stated
> > in this License.
> >
> > This explicitly allows you to make modifications to Apache licensed
> > code while applying your own license to those modifications.
> >
> > An apache project probably should not encourage supported versions of
> > the apache project, so your tlp.apache.org / podling.i.a.o site
> > shouldn't refer to it.
> >
> > This may be a better discussion for legal-discuss, but I think anyone
> > on there may be subscribed here to provide additional insight on this
> > discussion.
> >
> > John
> >
> > On Sun, Feb 21, 2016 at 9:19 AM Dor Ben Dov 
> > wrote:
> >
> > > Thanks John,
> > >
> > > But does it means that other company for example, can take my
> > > product and suggest support for it ?
> > > Can that company take those sources and create their own product and
> > > sell it ?
> > >
> > > Dor
> > >
> > > -Original Message-
> > > From: John D. Ament [mailto:johndam...@apache.org]
> > > Sent: יום א 21 פברואר 2016 16:17
> > > To: general@incubator.apache.org
> > > Subject: [MARKETING] Re: License question
> > >
> > > The source code would have to be Apache V2 licensed.
> > >
> > > There are a lot of instances of companies providing commercial
> > > versions, supported versions of ASF projects.  Look at a few like
> > > DataStax,
> > Pivotal.
> > >
> > > John
> > >
> > > On Sun, Feb 21, 2016 at 8:25 AM Dor Ben Dov 
> > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > Let's say I (company) go the ASF way.
> > > >
> > > > To incubator and later on into TLP.
> > > >
> > > > Does it mean that the license would be in the end only Apache
> > > > License
> > 2 ?
> > > > or can it still remain for example, lgpl ?
> > > >
> > > > By means, when It is Apache License 2, can one company take this
> > > > open source and offer support for it for money ? or adopt it and
> sell it ?
> > > >
> > > > Regards,
> > > > Dor Ben Dov
> > > >
> > > > This message and the information contained herein is proprietary
> > > > and confidential and subject to the Amdocs policy statement, you
> > > > may review at http://www.amdocs.com/email_disclaimer.asp
> > > >
> > >
> > > This message and the information contained herein is proprietary and
> > > confidential and subject to the Amdocs policy statement, you may
> > > review at http://www.amdocs.com/email_disclaimer.asp

Re: New ASF visual identity

[Gregory Chase]

Saw it in action at FOSDEM - looks great.  However, the old style is now a
collector's item :)

-Greg

On Wed, Feb 3, 2016 at 11:27 PM, Sergio Fernández  wrote:

> +1
>
> On Wed, Feb 3, 2016 at 8:40 PM, Sravya Tirukkovalur 
> wrote:
>
> > +1
> >
> > On Wed, Feb 3, 2016 at 10:51 AM,  wrote:
> >
> > >
> > >
> > > +1
> > >
> > >
> > > Best,
> > >
> > >
> > > Markus
> > >
> > >
> > > .:: YAGNI likes a DRY KISS ::.
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Wed, Feb 3, 2016 at 10:07 AM -0800, "Marvin Humphrey" <
> > > mar...@rectangular.com> wrote:
> > >
> > >
> > >
> > >
> > >
> > > Greets,
> > >
> > > The ASF has a new look:
> > >
> > >
> > >
> >
> https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces86
> > > https://www.apache.org/foundation/press/kit/
> > >
> > > The main Incubator website needs to be updated with the new visual
> > > identity, as do podling websites.
> > >
> > > I volunteer to create a drop-in replacement for the egg logo:
> > >
> > > http://incubator.apache.org/images/egg-logo.png
> > >
> > > I expect to take the same approach as the last time the graphic was
> > > updated a few years back[1]: keep the black border and keep the same
> > > pixel dimensions, so that existing podling web pages can simply switch
> > > in the new file without needing to adapt their designs.
> > >
> > > Please note: the intent of this undertaking is to keep the Incubator up
> > > to date and in sync with the efforts of our marketing team. It is not
> > > to rework the Incubator's visual identity, so I hope that we can avoid
> a
> > > lengthy bikeshed painting debate.
> > >
> > > Marvin Humphrey
> > >
> > > [1] https://issues.apache.org/jira/browse/INCUBATOR-112
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> >
> > --
> > Sravya Tirukkovalur
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>



-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: [VOTE] Accept Beam into the Apache Incubator

[Gregory Chase]

+ 1 (non-binding), and cool name!

On Thu, Jan 28, 2016 at 2:47 PM, Byung-Gon Chun  wrote:

> +1 (non-binding)
>
>
>
> On Fri, Jan 29, 2016 at 5:31 AM, Adunuthula, Seshu 
> wrote:
>
> > +1 (non-binding)
> >
> > On 1/28/16, 12:05 PM, "Julian Hyde"  wrote:
> >
> > >+1 (binding)
> > >
> > >> On Jan 28, 2016, at 10:42 AM, Mayank Bansal 
> wrote:
> > >>
> > >> +1 (non-binding)
> > >>
> > >> Thanks,
> > >> Mayank
> > >>
> > >> On Thu, Jan 28, 2016 at 10:23 AM, Seetharam Venkatesh <
> > >> venkat...@innerzeal.com> wrote:
> > >>
> > >>> +1 (binding).
> > >>>
> > >>> Thanks!
> > >>>
> > >>> On Thu, Jan 28, 2016 at 10:19 AM Ted Dunning 
> > >>> wrote:
> > >>>
> >  +1
> > 
> > 
> > 
> >  On Thu, Jan 28, 2016 at 10:02 AM, John D. Ament
> > 
> >  wrote:
> > 
> > > +1
> > >
> > > On Thu, Jan 28, 2016 at 9:28 AM Jean-Baptiste Onofré
> > >
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> the Beam proposal (initially Dataflow) was proposed last week.
> > >>
> > >> The complete discussion thread is available here:
> > >>
> > >>
> > >>
> > >
> > 
> > >>>
> > >>>
> > http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%
> >
> >>>3CCA%2B%3DKJmvj4wyosNTXVpnsH8PhS7jEyzkZngc682rGgZ3p28L42Q%40mail.gmail.c
> > >>>om%3E
> > >>
> > >> As reminder the BeamProposal is here:
> > >>
> > >> https://wiki.apache.org/incubator/BeamProposal
> > >>
> > >> Regarding all the great feedbacks we received on the mailing list,
> > >>we
> > >> think it's time to call a vote to accept Beam into the Incubator.
> > >>
> > >> Please cast your vote to:
> > >> [] +1 - accept Apache Beam as a new incubating project
> > >> []  0 - not sure
> > >> [] -1 - do not accept the Apache Beam project (because: ...)
> > >>
> > >> Thanks,
> > >> Regards
> > >> JB
> > >> 
> > >> ## page was renamed from DataflowProposal
> > >> = Apache Beam =
> > >>
> > >> == Abstract ==
> > >>
> > >> Apache Beam is an open source, unified model and set of
> > >> language-specific SDKs for defining and executing data processing
> > >> workflows, and also data ingestion and integration flows,
> supporting
> > >> Enterprise Integration Patterns (EIPs) and Domain Specific
> Languages
> > >> (DSLs). Dataflow pipelines simplify the mechanics of large-scale
> > >>> batch
> > >> and streaming data processing and can run on a number of runtimes
> > >>> like
> > >> Apache Flink, Apache Spark, and Google Cloud Dataflow (a cloud
> >  service).
> > >> Beam also brings DSL in different languages, allowing users to
> > >>easily
> > >> implement their data integration processes.
> > >>
> > >> == Proposal ==
> > >>
> > >> Beam is a simple, flexible, and powerful system for distributed
> data
> > >> processing at any scale. Beam provides a unified programming
> model,
> > >>a
> > >> software development kit to define and construct data processing
> > >> pipelines, and runners to execute Beam pipelines in several
> runtime
> > >> engines, like Apache Spark, Apache Flink, or Google Cloud
> Dataflow.
> >  Beam
> > >> can be used for a variety of streaming or batch data processing
> > >>goals
> > >> including ETL, stream analysis, and aggregate computation. The
> > >> underlying programming model for Beam provides MapReduce-like
> > >> parallelism, combined with support for powerful data windowing,
> and
> > >> fine-grained correctness control.
> > >>
> > >> == Background ==
> > >>
> > >> Beam started as a set of Google projects (Google Cloud Dataflow)
> >  focused
> > >> on making data processing easier, faster, and less costly. The
> Beam
> > >> model is a successor to MapReduce, FlumeJava, and Millwheel inside
> > >> Google and is focused on providing a unified solution for batch
> and
> > >> stream processing. These projects on which Beam is based have been
> > >> published in several papers made available to the public:
> > >>
> > >>  * MapReduce - http://research.google.com/archive/mapreduce.html
> > >>  * Dataflow model  -
> > >>> http://www.vldb.org/pvldb/vol8/p1792-Akidau.pdf
> > >>  * FlumeJava - http://research.google.com/pubs/pub35650.html
> > >>  * MillWheel - http://research.google.com/pubs/pub41378.html
> > >>
> > >> Beam was designed from the start to provide a portable programming
> > >> layer. When you define a data processing pipeline with the Beam
> > >>> model,
> > >> you are creating a job which is capable of being processed by any
> >  number
> > >> of Beam processing engines. Several engines have been developed to
> > >>> run
> > >> Beam pipelines 

Re: [DISCUSS] Apache Dataflow Incubator Proposal

[Gregory Chase]

This is also a similarly named Spring project:
http://cloud.spring.io/spring-cloud-dataflow/

On Wed, Jan 20, 2016 at 9:40 AM, Marvin Humphrey 
wrote:

> On Wed, Jan 20, 2016 at 9:17 AM, Jean-Baptiste Onofré 
> wrote:
>
> > We're proposing Apache Dataflow naming because Google Cloud Dataflow is
> an
> > already known name and "brand".
>
> I don't see anything in the proposal about Google ceasing the use of the
> brand
> "Google Cloud Dataflow".  Yet the co-existence of "Google Cloud Dataflow"
> and
> "Apache Dataflow" would conflict with Apache requirements for vendor
> neutrality and project independence.
>
> The issue seems similar to the recent proposal to incubate "Apache
> OpenMiracl"
> while allowing the "Miracl" company to continue distribution of the
> "Miracl"
> project.  That situation was was resolved by renaming the Apache project to
> "Milagro", allowing the Miracl company to continue benefitting from the
> brand
> they had invested in so heavily.
>
> http://markmail.org/message/tpiphl55rcyezcvd
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform

[Gregory Chase]

So then I might suggest refining the positioning.

When I see "an enterprise IoT platform" I'm thinking of backend systems and
analysis, not end point embedded systems or devices beyond the node.

A Nest thermostat is a device, but the backend analysis and smart cloud app
that centralizes the service and enhances the intelligence of the end point
device is the "enterprise" portion of the solution IMHO.

-G

On Fri, Jan 15, 2016 at 6:01 PM, Greg Stein <gst...@gmail.com> wrote:

> Well aware of all that. Just kind of amazed that the data center is the
> focal point of this thread. That's a solved problem, rather than the IoT
> endpoints/sensors/etc. It seems the hard problem is lifting data from your
> embedded microcontroller, into a data packet sent via TCP/IP to $somewhere.
> In my house, I've got dozens of PIC16F688 microcontrollers; needless to
> say, they can't talk TCP/IP. Getting data from them is hard, then pushing
> that to an IP listener. Writing that listener, dropping data packets into a
> datastore, is about 10 lines of Python.
>
> So yeah. I find the focus strange.
>
> But hey... that's just commentary/curiosity. Has nothing to do with your
> proposal or acceptance into the Incubator.
>
> Cheers,
> -g
>
> On Fri, Jan 15, 2016 at 11:23 AM, Tony Faustini <t...@litbit.com> wrote:
>
> > Greg, think of this as a continuum some IoT use cases are simple ( a few
> > sensors) others might be at an industrial scale (data centers with
> 100,000s
> > of sensors). In between there are many other use cases. The data store
> > needed at different points of the continuum will be different. iota is
> > meant to provide a framework for this continuum enabling simple data
> stores
> > and complex ones depending on the particular use case. The data store is
> > not an integral part of iota, it simply enables the data store needs at
> > different points of the continuum. The same would apply to things like
> > Hadoop, Storm, or Flink. If you are at the data center end of the
> continuum
> > then iota should make it easy for you to use big data infrastructure.
> iota
> > can facilitate this but it’s not needed if you have a simple use case.
> For
> > example if you want to download iota and use it in a home project then
> that
> > should be a simple download and install process. If you are an global
> > company like ABB or Schneider then you might want to build your own
> > industrial scale IoT solution and iota could be at it’s core.
> >
> > -Tony
> >
> > > On Jan 15, 2016, at 12:18 AM, Greg Stein <gst...@gmail.com> wrote:
> > >
> > > Seriously? IoT can simply mean a temperature sensor in your house. No
> > need
> > > for a database, let alone something like Hadoop. ... that's just
> > > over-engineering.
> > >
> > > On Thu, Jan 14, 2016 at 7:51 PM, Gregory Chase <gch...@pivotal.io>
> > wrote:
> > >
> > >> I'd recommend a PostgreSQL adaptor, which opens a huge new world.
> > >>
> > >> Of course, if you are Apache and you are IOT, then Hadoop and Spark,
> and
> > >> all the streaming analytics technologies are key too.
> > >>
> > >> On Thu, Jan 14, 2016 at 3:39 PM, Tony Faustini <t...@litbit.com>
> wrote:
> > >>
> > >>> Thanks Gregory we look forward to seeing you around. We currently use
> > >>> MySQL and MongoDB but the data pipeline is written in in a way that
> any
> > >>> datastore could be used.
> > >>> Thanks
> > >>> -Tony
> > >>>
> > >>>> On Jan 14, 2016, at 3:24 PM, Gregory Chase <gch...@pivotal.io>
> wrote:
> > >>>>
> > >>>> I don't qualify as a "mentor", but plan on seeing me around your
> > >>> community
> > >>>> as it develops.  This is a very interesting topic for me.
> > >>>>
> > >>>> Maybe you need a database or two.  I know a few ;-)
> > >>>>
> > >>>> On Thu, Jan 14, 2016 at 2:19 PM, Tony Faustini <t...@litbit.com>
> > >> wrote:
> > >>>>
> > >>>>> Hi Hadrian, I have made the changes to the Tempo proposal relative
> to
> > >>> it’s
> > >>>>> renaming as iota. The changes are in the proposal itself I don’’t
> > >> think
> > >>> I
> > >>>>> can rename the top-level project name from Tempo to iota (let me
> know
> > >>> if I
> > >>>>> can or sh

Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform

[Gregory Chase]

Oh wait, we didn't say Apache Kafka.  That should get this thread another
1000 hits ;-)

On Thu, Jan 14, 2016 at 6:05 PM, P. Taylor Goetz  wrote:

> Thanks Hadrian!
>
> -Taylor
>
> > On Jan 14, 2016, at 8:48 PM, Hadrian Zbarcea  wrote:
> >
> > hadrian@minotaur:~$ ls -al Tempo.zip
> > -rw-r--r--  1 hadrian  hadrian  739185 Dec 19 16:45 Tempo.zip
> >
> > Available to anybody who can access the host above.
> >
> > Cheers,
> > Hadrian
> >
> >
> >> On 01/14/2016 07:21 PM, P. Taylor Goetz wrote:
> >> May I have access to the source code as well?
> >>
> >> -Taylor
> >>
> >>> On Jan 11, 2016, at 8:35 PM, Hadrian Zbarcea 
> wrote:
> >>>
> >>> With a bit of delay due to the Holidays season, I think it's time to
> continue this thread.
> >>>
> >>> The code has been available for a while to mentors and those who
> requested. I assume the mentors did take a look at it, I certainly did. The
> code looks clean and the idea sound. Plus the IoT field is one that matures
> fast and I consider a good fit for ASF technologies.
> >>>
> >>> There is the outstanding issue of changing the name as it seems
> unlikely to graduate as Tempo. There is a proposal to incubate it under the
> "iota" name (whatever the capitalization). Tony, if you could update the
> proposal to reflect that (or whatever name you choose) it'd be great. After
> that, assuming no other objections or concerns, I would suggest starting a
> vote.
> >>>
> >>> Cheers,
> >>> Hadrian
> >>>
> >>>
>  On 12/25/2015 09:49 PM, Roman Shaposhnik wrote:
>  Hi Tony!
> 
>  Has there been any activity around this proposal? I find it really
> interesting,
>  and just like Hadrian I really would love to see the code on GitHub
> (although
>  it is NOT a pre-requisite to being consider for ASF Incubator).
> 
>  Thanks,
>  Roman.
> 
>  P.S. Greetings from your past life managing JavaStudio ;-)
> 
> 
> > On Wed, Dec 2, 2015 at 3:50 PM, Hadrian Zbarcea 
> wrote:
> > Hi Tony,
> >
> > It is a very interesting proposal and I would like to help out as
> well. I do
> > have a bit of experience of the IoT field, both part of my ASF
> contributions
> > and other work I did. I volunteer to be a mentor or champion. Looks
> like one
> > of your understated goals is to grow a community and I agree the ASF
> is the
> > right place for that.
> >
> > You mentioned the code being available on github, but I couldn't
> find it
> > where I thought it could be [1]. Would it be possible to make the
> code
> > available to potential mentors? I think it would speed up the
> process and
> > you would get more support faster.
> >
> > There were also a number of positive answers to your email on the
> incubator
> > list, but you were not cc'ed, so if you're not subscribed to the
> list you
> > might have missed them.
> >
> > It's a great idea, thanks for considering the ASF incubator and it
> could
> > have great success given the growth of IoT.
> >
> > Best Regards,
> > Hadrian
> >
> > [1] https://github.com/litbit
> >
> >
> >
> >> On 12/02/2015 03:34 PM, Tony Faustini wrote:
> >>
> >> To: general@incubator.apache.org
> >>
> >> Hi All, Litbit is an enterprise IoT company comprised of individuals
> >> that have worked for Yahoo, Apple, Microsoft, Sun Microsystems,
> Intel,
> >> Cisco Systems and 365 Main. We are working with some of the world's
> >> leading companies providing them with an enterprise IoT platform. We
> >> value the open source community and the way it is changing
> enterprise
> >> software. We are eager to build an open source community around
> Tempo
> >> which powers RhythmOS our commercial offering.
> >>
> >> Thanks
> >> -Tony Faustini (Litbit Co)
> >>
> >>
> >> Tempo - A Proposal for Apache Incubator
> >>
> >> Abstract
> >>
> >> The Apache Foundation has been very successful in bringing together
> >> key software components that have enabled people to interact with
> each
> >> other via a variety of content platforms and it will no doubt
> continue
> >> to do so.  At the same time modern society is becoming increasingly
> >> dependent on devices that interact with each other and with people.
> >> The amount of data that will be produced by devices will be orders
> of
> >> magnitude greater than what has been produced by humans in the past.
> >> In addition, the orchestration of devices and people will be an
> >> important area of growth for the foreseeable future. This new
> dynamic
> >> will eventually become manifest in a growing number of Apache
> projects
> >> that enable this to occur. Our wish is to contribute to this
> movement
> >> by contributing the Tempo system to the Open Source Community via
> the
> >> 

Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform

[Gregory Chase]

I'd recommend a PostgreSQL adaptor, which opens a huge new world.

Of course, if you are Apache and you are IOT, then Hadoop and Spark, and
all the streaming analytics technologies are key too.

On Thu, Jan 14, 2016 at 3:39 PM, Tony Faustini <t...@litbit.com> wrote:

> Thanks Gregory we look forward to seeing you around. We currently use
> MySQL and MongoDB but the data pipeline is written in in a way that any
> datastore could be used.
> Thanks
> -Tony
>
> > On Jan 14, 2016, at 3:24 PM, Gregory Chase <gch...@pivotal.io> wrote:
> >
> > I don't qualify as a "mentor", but plan on seeing me around your
> community
> > as it develops.  This is a very interesting topic for me.
> >
> > Maybe you need a database or two.  I know a few ;-)
> >
> > On Thu, Jan 14, 2016 at 2:19 PM, Tony Faustini <t...@litbit.com> wrote:
> >
> >> Hi Hadrian, I have made the changes to the Tempo proposal relative to
> it’s
> >> renaming as iota. The changes are in the proposal itself I don’’t think
> I
> >> can rename the top-level project name from Tempo to iota (let me know
> if I
> >> can or should). If anything else needs to be done please let me know.
> >> Thanks
> >> -Tony
> >>
> >>> On Jan 11, 2016, at 5:35 PM, Hadrian Zbarcea <hzbar...@gmail.com>
> wrote:
> >>>
> >>> With a bit of delay due to the Holidays season, I think it's time to
> >> continue this thread.
> >>>
> >>> The code has been available for a while to mentors and those who
> >> requested. I assume the mentors did take a look at it, I certainly did.
> The
> >> code looks clean and the idea sound. Plus the IoT field is one that
> matures
> >> fast and I consider a good fit for ASF technologies.
> >>>
> >>> There is the outstanding issue of changing the name as it seems
> unlikely
> >> to graduate as Tempo. There is a proposal to incubate it under the
> "iota"
> >> name (whatever the capitalization). Tony, if you could update the
> proposal
> >> to reflect that (or whatever name you choose) it'd be great. After that,
> >> assuming no other objections or concerns, I would suggest starting a
> vote.
> >>>
> >>> Cheers,
> >>> Hadrian
> >>>
> >>>
> >>> On 12/25/2015 09:49 PM, Roman Shaposhnik wrote:
> >>>> Hi Tony!
> >>>>
> >>>> Has there been any activity around this proposal? I find it really
> >> interesting,
> >>>> and just like Hadrian I really would love to see the code on GitHub
> >> (although
> >>>> it is NOT a pre-requisite to being consider for ASF Incubator).
> >>>>
> >>>> Thanks,
> >>>> Roman.
> >>>>
> >>>> P.S. Greetings from your past life managing JavaStudio ;-)
> >>>>
> >>>>
> >>>> On Wed, Dec 2, 2015 at 3:50 PM, Hadrian Zbarcea <hadr...@apache.org>
> >> wrote:
> >>>>> Hi Tony,
> >>>>>
> >>>>> It is a very interesting proposal and I would like to help out as
> >> well. I do
> >>>>> have a bit of experience of the IoT field, both part of my ASF
> >> contributions
> >>>>> and other work I did. I volunteer to be a mentor or champion. Looks
> >> like one
> >>>>> of your understated goals is to grow a community and I agree the ASF
> >> is the
> >>>>> right place for that.
> >>>>>
> >>>>> You mentioned the code being available on github, but I couldn't find
> >> it
> >>>>> where I thought it could be [1]. Would it be possible to make the
> code
> >>>>> available to potential mentors? I think it would speed up the process
> >> and
> >>>>> you would get more support faster.
> >>>>>
> >>>>> There were also a number of positive answers to your email on the
> >> incubator
> >>>>> list, but you were not cc'ed, so if you're not subscribed to the list
> >> you
> >>>>> might have missed them.
> >>>>>
> >>>>> It's a great idea, thanks for considering the ASF incubator and it
> >> could
> >>>>> have great success given the growth of IoT.
> >>>>>
> >>>>> Best Regards,
> >>>>> Hadrian
> >>>>>
> >>>>&g

Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform

[Gregory Chase]

I don't qualify as a "mentor", but plan on seeing me around your community
as it develops.  This is a very interesting topic for me.

Maybe you need a database or two.  I know a few ;-)

On Thu, Jan 14, 2016 at 2:19 PM, Tony Faustini  wrote:

> Hi Hadrian, I have made the changes to the Tempo proposal relative to it’s
> renaming as iota. The changes are in the proposal itself I don’’t think I
> can rename the top-level project name from Tempo to iota (let me know if I
> can or should). If anything else needs to be done please let me know.
> Thanks
> -Tony
>
> > On Jan 11, 2016, at 5:35 PM, Hadrian Zbarcea  wrote:
> >
> > With a bit of delay due to the Holidays season, I think it's time to
> continue this thread.
> >
> > The code has been available for a while to mentors and those who
> requested. I assume the mentors did take a look at it, I certainly did. The
> code looks clean and the idea sound. Plus the IoT field is one that matures
> fast and I consider a good fit for ASF technologies.
> >
> > There is the outstanding issue of changing the name as it seems unlikely
> to graduate as Tempo. There is a proposal to incubate it under the "iota"
> name (whatever the capitalization). Tony, if you could update the proposal
> to reflect that (or whatever name you choose) it'd be great. After that,
> assuming no other objections or concerns, I would suggest starting a vote.
> >
> > Cheers,
> > Hadrian
> >
> >
> > On 12/25/2015 09:49 PM, Roman Shaposhnik wrote:
> >> Hi Tony!
> >>
> >> Has there been any activity around this proposal? I find it really
> interesting,
> >> and just like Hadrian I really would love to see the code on GitHub
> (although
> >> it is NOT a pre-requisite to being consider for ASF Incubator).
> >>
> >> Thanks,
> >> Roman.
> >>
> >> P.S. Greetings from your past life managing JavaStudio ;-)
> >>
> >>
> >> On Wed, Dec 2, 2015 at 3:50 PM, Hadrian Zbarcea 
> wrote:
> >>> Hi Tony,
> >>>
> >>> It is a very interesting proposal and I would like to help out as
> well. I do
> >>> have a bit of experience of the IoT field, both part of my ASF
> contributions
> >>> and other work I did. I volunteer to be a mentor or champion. Looks
> like one
> >>> of your understated goals is to grow a community and I agree the ASF
> is the
> >>> right place for that.
> >>>
> >>> You mentioned the code being available on github, but I couldn't find
> it
> >>> where I thought it could be [1]. Would it be possible to make the code
> >>> available to potential mentors? I think it would speed up the process
> and
> >>> you would get more support faster.
> >>>
> >>> There were also a number of positive answers to your email on the
> incubator
> >>> list, but you were not cc'ed, so if you're not subscribed to the list
> you
> >>> might have missed them.
> >>>
> >>> It's a great idea, thanks for considering the ASF incubator and it
> could
> >>> have great success given the growth of IoT.
> >>>
> >>> Best Regards,
> >>> Hadrian
> >>>
> >>> [1] https://github.com/litbit
> >>>
> >>>
> >>>
> >>> On 12/02/2015 03:34 PM, Tony Faustini wrote:
> 
>  To: general@incubator.apache.org
> 
>  Hi All, Litbit is an enterprise IoT company comprised of individuals
>  that have worked for Yahoo, Apple, Microsoft, Sun Microsystems, Intel,
>  Cisco Systems and 365 Main. We are working with some of the world's
>  leading companies providing them with an enterprise IoT platform. We
>  value the open source community and the way it is changing enterprise
>  software. We are eager to build an open source community around Tempo
>  which powers RhythmOS our commercial offering.
> 
>  Thanks
>  -Tony Faustini (Litbit Co)
> 
> 
>  Tempo - A Proposal for Apache Incubator
> 
>  Abstract
> 
>  The Apache Foundation has been very successful in bringing together
>  key software components that have enabled people to interact with each
>  other via a variety of content platforms and it will no doubt continue
>  to do so.  At the same time modern society is becoming increasingly
>  dependent on devices that interact with each other and with people.
>  The amount of data that will be produced by devices will be orders of
>  magnitude greater than what has been produced by humans in the past.
>  In addition, the orchestration of devices and people will be an
>  important area of growth for the foreseeable future. This new dynamic
>  will eventually become manifest in a growing number of Apache projects
>  that enable this to occur. Our wish is to contribute to this movement
>  by contributing the Tempo system to the Open Source Community via the
>  Apache Foundation. Tempo is an open platform to interconnect any and
>  all devices, sensors, people, and applications, henceforth referred to
>  as points, through a scalable, secure, and modular architecture,
>  

Re: [DISCUSS] OpenMiracl for Incubation

[Gregory Chase]

Having been through this twice now with "Pivotal GemFire" begatting "Apache
Geode" and "Pivotal HAWQ" becoming "Apache HAWQ"

If the current owner intends to allow infringement on the MIRACL brand as a
policy by any user of Apache Miracl, then that should be ok.  In effect
they will be putting "MIRACL" into the public domain.

If the owner intends to license "MIRACL" for Apache's use only - how does
this extend to Apache's users?

For my company, we decided it was better to ensure the commercial
distribution and the Apache projects did not infringe on each others
brands.  And we have done both approaches:  suggest a new brand for Apache,
and give an existing brand to Apache and rebrand the commercial
distribution.

-Greg

On Wed, Nov 18, 2015 at 6:34 PM, Nick Kew  wrote:

> On Wed, 2015-11-18 at 08:48 +0900, Brian Spector wrote:
> > Hi Alex, thank you for the suggestion, but from our point of view, as I
> > outlined below, we would disadvantage the project as a whole by not
> having
> > the MIRACL name in it.
> >
> > At the same time, I completely understand the concern that a company who
> > creates a product based on OpenMiracl might feel themselves disadvantaged
> > by having to state an attribution 'based on Apache OpenMiracl' while
> > MIRACL, the company, sells a product called Datacenter Cryptosystem will
> > also say 'based on Apache OpenMiracl'. We get that.
>
> If folks are uneasy about OpenMiracl, how far does that extend?
> Would (for example) a name taking the "Mira" stem be sufficiently
> distinct for those expressing concerns here?  For example,
> Mirabile (Latin pronunciation) kind-of offers an element of
> historic continuity through the linguistic association with
> the miracle.
>
> --
> Nick Kew
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: Incubator mail archives lagging badly

[Gregory Chase]

http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201511.mbox/browser

As one example.

On Wed, Nov 18, 2015 at 11:00 AM, Bertrand Delacretaz <
bdelacre...@apache.org> wrote:

> Hi,
>
> On Wed, Nov 18, 2015 at 1:49 PM, Gregory Chase <gch...@pivotal.io> wrote:
> > ...I notice that a number of
> > the incubating projects mail archives have not updated since Nov 2
>
> There are several archives, which archive URLs are you referring to?
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Incubator mail archives lagging badly

[Gregory Chase]

Greetings,
Maybe this belongs in the Infra mail list, but I notice that a number of
the incubating projects mail archives have not updated since Nov 2.

I presume this is a known problem?

-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: Incubator mail archives lagging badly

[Gregory Chase]

Sorry all.  It's user error.  I was expecting most recent first :)

On Wed, Nov 18, 2015 at 11:54 AM, Bertrand Delacretaz <
bdelacre...@apache.org> wrote:

> On Wed, Nov 18, 2015 at 2:02 PM, Gregory Chase <gch...@pivotal.io> wrote:
> >
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201511.mbox/browser
> ...
>
> That looks up to date for me.
> That page uses javascript to load the content, maybe it's failing on
> your browser?
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: Resigning as HAWQ mentor

[Gregory Chase]

Owen, Thanks for guiding us out of the dock :)

-Greg

On Wed, Oct 28, 2015 at 7:35 PM, Owen O'Malley  wrote:

> All,
>I'd like to resign as a HAWQ mentor. HAWQ will still have 5 mentors, so
> it should still be in good shape.
>
> Thanks,
>Owen
>



-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: [VOTE] Accept MADlib into the Apache Incubator

[Gregory Chase]

+1 nonbinding

On Fri, Sep 11, 2015 at 8:12 AM, Chris Rawles  wrote:

> --
> Chris
>



-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: What is the legal basis for enforcing release policies at ASF?

[Gregory Chase]

Does ...based on Apache Hadoop require a clear dependency notation as to
which versions of Apache component releases are part of the commercial
distribution?

On Fri, Aug 7, 2015 at 5:39 AM, Sam Ruby ru...@intertwingly.net wrote:

 On Fri, Aug 7, 2015 at 7:53 AM, Niclas Hedhman nic...@hedhman.org wrote:
  Bill,
  So I can release Niclas Hadoop platform, based on Apache Hadoop ?? I
  thought the discussion a few years ago was that this was misleading...

 Things in law are rarely binary except at the edges or after an actual
 court ruling.

 Releasing a Niclas George platform powered by Apache Hadoop conforms
 with our branding requirements, so would likely be OK.  The further
 you go away from that, the less clear that what you are doing would be
 OK.

 Hadoop would be a especially problematic case for you, as Apache
 Hadoop, Hadoop, Apache, the Apache feather logo, and the Apache Hadoop
 project logo are either registered trademarks or trademarks of the
 Apache Software Foundation in the United States and other countries. 
 -- https://hadoop.apache.org/

 http is a more generic term, so including variants of it in your name
 (including httpd) would be less problematic than incorporating a name
 like Hadoop.

 - Sam Ruby

  On Fri, Aug 7, 2015 at 12:30 PM, William A Rowe Jr wr...@rowe-clan.net
  wrote:
 
  On Thu, Aug 6, 2015 at 7:50 PM, Roman Shaposhnik ro...@shaposhnik.org
  wrote:
 
   Hi!
  
   while answering a question on release policies and ALv2
   I've suddenly realized that I really don't know what is the
   legal basis for enforcing release policies we've got
   documented over here:
  http://www.apache.org/dev/release.html
  
   For example, what would be the legal basis for stopping
   a 3d party from releasing a snapshot of ASF's project
   source tree and claim it to be a release X.Y.Z of said
   project?
  
 
  Nothing other than the Trademarks.
 
  If someone wants to call httpd trunk 3.0.1-GA, they cannot do this as
  Apache httpd 3.0.1-GA or Apache HTTP Server 3.0.1-GA.
 
  They can certainly release trunk under the AL license and call it
 Kindred
  Http Server 3.0.1-GA, based on Apache HTTP Server. That is a statement
 of
  fact and not an abuse of the mark, IMHO. (If it was not actually based
 on
  Apache HTTP Server, then that would similarly be a Trademark
 infringement
  as it is a false use of the mark.)
 
  There are no less than two marks, one is the name of the foundation
 itself
  in conjunction with Open Source Software, and the other is the specific
  project name.
 
 
 
 
  --
  Niclas Hedhman, Software Developer
  http://zest.apache.org - New Energy for Java

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org




-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/