Fwd: Apache Big Data EU - Discussion Lounge available for after-session discussion & project meetings

[Greg Chase]

Passing this offer on to podlings that would be interested to host an
introductory discussion about their community at Apache Big Data

-- Forwarded message --
From: Gregory Chase <gch...@pivotal.io>
Date: Sun, Nov 13, 2016 at 5:10 AM
Subject: Apache Big Data EU - Discussion Lounge available for after-session
discussion & project meetings
To: d...@community.apache.org


Dear Apache Big Data Community,

ODPi.org is sponsoring a Community Lounge that anyone is welcome to use as
a place for short discussions.  This is a great way to have an extended Q
session after your talk, or to have a short meeting of your project
community.

Sign up now for a 30 minute slot.  The current schedule is posted here:
https://www.odpi.org/blog

We have lots of time available tomorrow, Monday, and Tuesday.

-Greg

--
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: [VOTE] Graduate Apache Geode (incubating)

[Greg Chase]

+1!

On Mon, Nov 7, 2016 at 10:13 AM, Nabarun Nag <n...@pivotal.io> wrote:

> +1
>
> On Mon, Nov 7, 2016 at 10:11 AM Mark Bretl <mbr...@apache.org> wrote:
>
> > +1
> >
> > --Mark
> >
> > On Sun, Nov 6, 2016 at 11:07 PM, Avinash Dongre <adon...@apache.org>
> > wrote:
> >
> > > +1
> > >
> > > On Mon, Nov 7, 2016 at 12:35 PM, Sergio Fernández <wik...@apache.org>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > good luck, guys!
> > > >
> > > > On Sun, Nov 6, 2016 at 11:42 PM, John D. Ament <
> johndam...@apache.org>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Nov 6, 2016 15:58, "Roman Shaposhnik" <ro...@shaposhnik.org>
> > wrote:
> > > > >
> > > > > > Hi!
> > > > > >
> > > > > > after a very positive discussion in the Geode community
> > > > > > and at the IPMC level:
> > > > > > http://markmail.org/message/z4prj62hr7rn6cu6
> > > > > > I'd like to bring the following resolution for a formal vote.
> > > > > >
> > > > > > Please vote on the resolution pasted below to graduate
> > > > > > Apache Geode from the incubator to top level project.
> > > > > >
> > > > > > [ ] +1 Graduate Apache Geode from the Incubator.
> > > > > > [ ] +0 Don't care.
> > > > > > [ ] -1 Don't graduate Apache Geode from the Incubator because...
> > > > > >
> > > > > > This vote will be open for at least 72 hours.
> > > > > >
> > > > > > Many thanks to our mentors and everyone else for the support,
> > > > > > Roman (on behalf of the Apache Geode PPMC).
> > > > > >
> > > > > > Resolution:
> > > > > >
> > > > > > Establish the Apache Geode 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 data management platform that provides
> > > > > > real-time, consistent access to data-intensive applications
> > > > > > throughout widely distributed cloud architectures.
> > > > > >
> > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > > > > > Committee (PMC), to be known as the "Apache Geode Project",
> > > > > > be and hereby is established pursuant to Bylaws of the
> > > > > > Foundation; and be it further
> > > > > >
> > > > > > RESOLVED, that the Apache Geode Project be and hereby is
> > > > > > responsible for the creation and maintenance of software
> > > > > > related to a data management platform that provides real-time,
> > > > > > consistent access to data-intensive applications throughout
> > > > > > widely distributed cloud architectures.
> > > > > >
> > > > > > RESOLVED, that the office of "Vice President, Apache Geode" 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 Geode Project, and to have primary responsibility
> > > > > > for management of the projects within the scope of
> > > > > > responsibility of the Apache Geode 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 Geode Project:
> > > > > >
> > > > > > * Anilkumar Gingade <aging...@apache.org>
> > > > > > * Anthony Baker <aba...@apache.org>
> > > > > > * Ashvin Agrawal <ash...@apache.org>
> > > > > > * Avinash Dongre <adon...@apache.org>
> > > > > > * Bar

Re: Radical proposal: no initial list of committers

[Greg Chase]

In Apache Geode, we are trying to be liberal about bringing in new
committers. Anyone who shows an interest, and a series of well formatted
pull requests that follow are code guidelines are pretty quickly nominated
to become committers.

This would make it very easy for emeritus contributors to become active
again, as well as new diverse community members.

On Tue, Sep 27, 2016 at 8:35 AM, Alex Harui <aha...@adobe.com> wrote:

> It is an interesting idea.  I thought that the initial committers list
> provided the set of people who could define the merit to approve other new
> committers.  The mentors may not be familiar enough with the technology
> and people to make the decision with the "Flavor" the community wants.
>
> The only sticking point I ran into in incubation was that folks felt the
> need to be "fair" and require anybody not on the initial list to provide a
> series of patches to show their commitment before voting them in.  I'd
> rather have a "quick-add" for folks who have been past contributors.  Then
> you could say the initial committers list should be 3 to 8 people, and
> they could just add someone who shows up with something they want to
> commit if that person is already in the commit history of the imported
> code without having to make them submit a patch and wait 72 hours or more
> for the vote.
>
> My 2 cents,
> -Alex
>
> On 9/27/16, 7:44 AM, "Gregory Chase" <gch...@pivotal.io> wrote:
>
> >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 <elecha...@gmail.com>
> >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 ow

Re: Notes on branding

[Greg Chase]

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 <johndam...@apache.org> wrote:
> 
>> On Fri, Jul 1, 2016 at 4:35 PM Tim Williams <william...@gmail.com> 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 <g...@gregchase.com> 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.




>> 
>> --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

Re: Notes on branding

[Greg Chase]

On Fri, Jul 1, 2016 at 12:05 PM, Marvin Humphrey <mar...@rectangular.com>
wrote:

> On Fri, Jul 1, 2016 at 9:35 AM, Greg Chase <g...@gregchase.com> wrote:
>
> > The branding guidelines do not address feedback such as "logo in footer"
> or
> > "disclaimer is buried deep or below the fold".
>
> What would be best is if podlings just understood that intent, and as and
> took
> it upon themselves to ensure that their incubating status was communicated
> effectively -- in websites, in release announcements, etc.
>

Except podlings are now being told they are "not being effective enough"
according to an unspecified standard.


>
> It should be apparent to anyone who groks that intent that websites where
> the
> disclaimers and logos are buried subvert the branding guidelines.
>

You are dealing with new community members. It should not be assumed that
something is grokable, especially when it seems there isn't a communicated
consensus.


> It seems that we will have to spell things out more aggressively.  The new
> language should make it plain that podlings are expected to uphold the
> *spirit* of the guidelines, and not treat them as some bs technicality to
> work
> around.
>

Spirits can be hard to grasp.  As I suggested before.  If being
prescriptive is too difficult, then force new podlings into a standardized
web template that meets requirements, and spirt.  This would actually
really simplify the getting started process for new podlings.  Then they
can either do something new with their website once they become a TLP, or
perhaps at some mid-level of maturity.


>
> If podlings don't like the disclaimers, they can hurry up and do the work
> to
> graduate.


There are no objections to the disclaimer from Geode.  The only issue is
the lack of guidelines and being held to an ungrokable standard.  We
discussed the issue in our community and the response is "So what do we
need to do?"

Re: Notes on branding

[Greg Chase]

Thanks for doing the audit.

The Geode PPMC has noted the finding in the wiki with our site.

However, we'd like to see a good example of a compliant website.

The branding guidelines do not address feedback such as "logo in footer" or
"disclaimer is buried deep or below the fold".

Considering the Geode web design was forked from another TLP, is it
possible that some of the feedback is a bit arbitrary?

Otherwise maybe all incubating projects should have the same website
template, and then be free to evolve their design once they graduate to TLP.

-Greg

On Fri, Jul 1, 2016 at 7:37 AM, Shane Curcuru  wrote:

> John D. Ament wrote on 6/29/16 7:36 AM:
> > Hey guys
> >
> > I'm starting to go through the podlings to identify branding issues.
> > Touched the first 12 projects, for those that had websites, 4 were not
> > within branding requirements.
> >
> > I'm not sure if other scan give a hand here on contacting podlings, but I
> > went through Airflow -> Fineract, and contacted Airflow, Atlas, Beam and
> > Blur.  Otherwise I'll continue to churn through contacting projects.
> >
> > John
> >
>
> Thanks for the good work!  Please do report back - here or to
> trademarks@ - about your progress and how PPMCs respond.
>
> In particular, any feedback on our published policies/guidelines is very
> important.  As we scale, we need to ensure that most podlings can figure
> out the right thing to do from the docs, and not as much from direct
> pushes by our volunteer mentors and IPMC folks.
>
> Separately, a long-term project of mine is to ensure the branding bits
> on the incubator site are clear and point to the right parts of the
> formal trademark policies here:
>
>   http://www.apache.org/foundation/marks/resources
>
> - Shane
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Subject: [RESULT][VOTE] MADlib v1.9alpha-rc2

[Greg Chase]

Congrats!

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Mar 11, 2016, at 5:23 PM, Frank McQuillan  wrote:
> 
> The vote has PASSED with 3 +1 binding votes from the Incubator PMC members,
> and no 0 or -1 votes:
> 
> +1 Justin Mclean
> +1 Roman Shaposhnik
> +1 Konstantin Boudnik
> 
> Thread:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201603.mbox/%3CCAKBQfzQh%3DJ3DrFSgFEY8teRDpEf5Yz3r7eBffTZVVN_9evpBJg%40mail.gmail.com%3E
> 
> On behalf of the MADlib community, thank you to all who reviewed and voted
> on this release candidate.
> 
> We will proceed with promoting this release candidate.
> 
> Regards,
> Frank McQuillan

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

Re: [RESULT] [VOTE] Release Apache Geode (incubating) 1.0.0-incubating.M1

[Greg Chase]

Congratulations on the first official release!

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Feb 6, 2016, at 8:31 AM, Nitin Lamba  wrote:
> 
> Hello,
> 
> 
> Here are the results of the vote for releasing Apache Geode (incubating) 
> release 1.0.0-incubating.M1 (RC2):
> 
> 
> +1 votes: 3 (3 binding)
> 
> +0 votes: 1 (0 binding)
> 
> -1 votes: 0 (0 binding)
> 
> 
> The vote has succeeded - the release will now be completed.
> 
> 
> Nitin (on behalf of the Geode team)

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

Re: [DISCUSS] Geode Incubation proposal

[Greg Chase]

jan i jani at apache.org writes:

 
 On Sunday, April 12, 2015, dsh daniel.haischt at gmail.com wrote:
 
  Just as a quick remark. Geode might be a trademark owned by AMD:
  http://en.wikipedia.org/wiki/Geode_%28processor%29
 
 Good catch, we need to hear the opinion of trademark at  because it depend 
 on
 it is in an overlapping field (as I understood it). F.x. Corinthia is
 registered as a print font and hotel chain, but that was not a problem.
 
 I think it is a good proposal and the project seems to have good chances of
 growing under the wings of apache.
 
 rgds
 jan i
 


The name Geode was thought up by the Geode contributors at Pivotal.  

Pivotal legal did a pretty extensive trademark search to ensure there would 
be no infringement.  It was their opinion that there  is low risk of trademark 
infringement with the AMD product.

However, its fully understandable that Apache legal needs to vet the name 
of the project should it be accepted for incubation.


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