Draft incubator report for January 2019

[Justin Mclean]

Hi,

The draft report is up at [1]. If you think I’m missed something or see 
something that needs to be changed speak up or just go ahead and make the 
change.

Mentor sign off are due by Tuesday Jan 8th.

Currently these projects don’t have any sign offs:
- Amaterasu
- Annotator
- BatchEE
- Livy
- Milagro
- Weex

Congrats to NetBeans as all four mentors have already signed off the report, 
Rya also has had all mentors sign-off the report.

The report will be submitted Wednesday January 09.

Iceburg failed to report and will be asked to report next month.

Thanks,
Justin

1. https://wiki.apache.org/incubator/January2019
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Hudi Incubation Proposal

[Gosling Von]

Hi,

I just looked through the proposal for the Hudi and very interested in this 
project, and also willing to be a Hudi mentor.



Best Regards,
Von Gosling

> 在 2019年1月4日，上午6:10，Justin Mclean  写道：
> 
> Hi,
> 
> There's one issue I think needs to be addressed, if the proposed mentors 
> could follow up on my email sent a few weeks back on private@ that would be 
> appreciated.
> 
> Thanks,
> Justin
> -
> 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: Establishing an ASF project for training

[Gris Cuevas]

On 2018/12/17 14:26:47, Julian Feinauer  wrote: 
> Hey Lars,
> hi Rich,
> 
> I really like the idea!
> We, from time to time, also do trainings and workshops with Apache projects 
> and it would really help to have a better basis.
> And I agree for you that you don’t get payed for *having* slides but for the 
> show as well as for the insights you get from a good instructor or a person 
> with background knowledge, so I also see no big concerns in sharing.
> 
> One thing that came to my mind was to use some kind of "code based" 
> generation for the slides, notebooks, brochures like Latex, Markdown, 
> Asciidoc or else...

I would strongly advise against using code base generators as the only way to 
consume these materials. The reason why is that this is a entry barrier for 
folks wanting to contribute to community and project management and who are not 
technical. This will also put a huge adoption barrier since we'd need to assume 
people using this materials are versed in this technology. That been said. We 
could use the code based generator for folks wanting to do more with what's 
produced but also publishing official brochures and content that people can 
just "grab and go". 

This is in alignment with having a more active attitude towards recognizing 
non-code contributions. 

> I would not like to force users to use proprietary tools (PPT) to use the 
> material.
> And furthermore, this would allow us to have some kind of style files which 
> could be personalized for corps and which they could keep for each release.
> Another aspect is that it makes the whole versioning way easier as it is code 
> and one can see all changes and stuff which is impossible for "binary" 
> formats.
> I also think we have enough people here that would be able to easily do an 
> automated resources documentation, so that we could always offer "compiled" 
> material in pdf in default style or the possibility to do a custom build with 
> custom styles.
> 
> And I think that the incubator would be a good place to start to see if here, 
> as in all ASF projects, a community can be established and continuous effort 
> is spend on the project. This would reduce the risk of a "zombie" project 
> which is probably only really powered by one organization and lives and dies 
> on their will.
> 
> Julian
> 
> Am 17.12.18, 14:37 schrieb "Rich Bowen" :
> 
> It's worth mentioning that there's a conversation going right now over on
> the members@ list about creating a "central services" kind of entity. That
> discussion is primarily focused on design/graphic kind of stuff, but
> training/documentation/presentations are similar in concept, if not in
> content, and I'm definitely in favor of such an entity existing.
> 
> Your anticipated question "Isn't the ASF all about code, now you want to 
> do
> PPT!" is very insightful. The ASF exists to provide services to projects,
> and this is an unfilled need that many/most of our projects have. There is
> precedent - we have an infrastructure organization, a conferences entity, 
> a
> marketing group, legal, brand, and so on, that provide non-code services 
> to
> projects. Recognizing contributors for non-code contributions is 
> *critical*
> for the survival of our projects, and of the Foundation as a whole, and we
> tend to be very poor at it.
> 
> So, suffice it to say, a huge +1 to this concept, although I'm not sure
> where it should live - whether under ComDev (as you suggest) or as a
> top-level entity. I think the latter makes a little more sense. While this
> is indeed a function of community development/growth/education, it's also
> sufficiently different that it may need to be independent.
> 
> What are next steps? I don't *think* this is something that should go
> through the Incubator. It's not a Thing Like That. Perhaps a proposal to
> the Board to create a top-level thing? I'll put a pointer to this thread
> into that other thread (referenced above), and apologies to those of you
> who are not ASF Members and cannot see that thread.
> 
> 
> On Mon, Dec 17, 2018 at 8:23 AM Lars Francke  
> wrote:
> 
> > Hi,
> >
> > I'd like to start a discussion around establishing a project (or Central
> > Service) at the ASF to host and develop training and related materials 
> for
> > ASF (and possibly others, where it makes sense) projects.
> >
> > I'm a committer and contributor to a few projects and make money doing
> > consulting work. Naturally people do contact us for training, and we 
> have
> > developed our own slideware etc. but we find it incredibly hard work to
> > keep those up-to-date.
> >
> > We also work with lots of other companies and they all face the same
> > challenges. At the same time, we do not believe that a slide-deck is 
> worth
> > that much on its own (others disagree, as we used 

Re: Establishing an ASF project for training

[Gris Cuevas]

Hi Everyone, 

This is a fantastic idea and we'd love to contribute! Personally, I think it 
makes more sense to have this to be a central offering of the ASF instead of a 
project. The reason is that having a central service would help permeate the 
values and belief of the ASF to the projects. If we have this as an independent 
project we might lose the connection to the foundation as a parent. That been 
said, I'd love to help shape a proposal to the board if this is still under 
consideration. 

I'm interested in developing a training about the Apache Way for two audiences: 
a) Teams wanting to implement the Apache Way to open source their technology 
(new projects) 
b) New contributors/committers to an Apache project 

My employer (Google) is betting heavily in helping our technical teams 
contributing to Apache projects to become good open source citizens, and as 
part of this effort we're organizing an internal Summit with the following 
sessions: 

a. The economics of Open Source (why we bet in open source technology)
b. Introduction to the Apache Way 
- Focusing on best practices & citizenship
c. Understanding individual participation and representing a company
d. Community Management 
e. Project Management in Open Source Projects 

Personally, I'm a true believer that creating resources for new community 
members is key to grow and sustain any online community, so I'd love to help 
make this a resource we share with all projects, this is an opportunity to 
build a solid common ground that unifies the way companies and individuals get 
to become part of the ASF. 

How could I help?


On 2018/12/18 09:06:44, Bertrand Delacretaz  wrote: 
> On Mon, Dec 17, 2018 at 8:24 PM Lars Francke  wrote:
> >...I believe we can probably hash out most details on
> > the list as well?..
> 
> Yes, that's how we work ;-)
> 
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

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

Re: [DISCUSS] Hudi Incubation Proposal

[Justin Mclean]

Hi,

There's one issue I think needs to be addressed, if the proposed mentors could 
follow up on my email sent a few weeks back on private@ that would be 
appreciated.

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

Re: Write Access to incubator Wiki

[Julian Feinauer]

Thank you Justin!

Am 03.01.19, 10:54 schrieb "Justin Mclean" :

Hi,

> could I get write access to the incubator Wiki to update the Podling 
reports for the next time?

Done and enjoy!

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




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

Re: [DISCUSS] Hudi Incubation Proposal

[Pierre Smits]

You’re welcome.

Looking forward to see the vote thread started and cast my ballot.

Happy new year to you and the team, and

Best regards,

Pierre

On Thu, 3 Jan 2019 at 15:41 Vinoth Chandar  wrote:

> Thanks Pierre!
> I think we are ready to move forward with the VOTE, given there are no
> additional concerns/comments for the past week or so.
>
> On Thu, Dec 27, 2018 at 11:38 PM Pierre Smits 
> wrote:
>
> > Hi Vinoth,
> >
> > There is no typical timeline. Each proposal to incubate is unique and
> each
> > timeline depends on the interactions of interested parties.
> >
> > You can use your own judgement to determine whether everything has been
> > said and to take the next step.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > *Apache Trafodion , Vice President & PMC
> > Chair*
> > *Apache Directory , PMC Member*
> > Apache Incubator , committer
> > *Apache OFBiz , contributor (without
> privileges)
> > since 2008*
> > Apache Steve , committer
> >
> >
> > On Fri, Dec 28, 2018 at 2:13 AM Vinoth Chandar 
> > wrote:
> >
> > > Hi all,
> > >
> > > Thanks for the feedback and comments.
> > >
> > > Its been over a week. Whats the typical timeline/due process for
> starting
> > > the vote?
> > >
> > > Thanks
> > > Vinoth
> > >
> > >
> > >
> > > On Tue, Dec 25, 2018 at 8:04 PM Mohammad Asif Siddiqui <
> > > mohammad.asif.siddiq...@huawei.com> wrote:
> > >
> > > > Looks like an interesting project.
> > > >
> > > > Regards
> > > > Asif
> > > >
> > > > -Original Message-
> > > > From: Luciano Resende [mailto:luckbr1...@gmail.com]
> > > > Sent: 22 December 2018 PM 05:06
> > > > To: general@incubator.apache.org
> > > > Subject: Re: [DISCUSS] Hudi Incubation Proposal
> > > >
> > > > Very nice, looks like you guys might need one more mentor, feel free
> to
> > > > include myself.
> > > >
> > > > On Fri, Dec 21, 2018 at 20:29 Vinoth Chandar  >
> > > > wrote:
> > > >
> > > > > Hi Justin,
> > > > >
> > > > > Thanks for the questions. I will try to answer them below .
> > > > >
> > > > > >>- Use of slack for communication. [1] Has the project thought
> about
> > > > > >>how
> > > > > moving conversations and decision making to a mailing list will
> > affect
> > > > > the community?
> > > > > Good point. We use Slack for interactive debugging, critical
> > decisions
> > > > > (approaches, designs, PR) still happens over github issues (which
> > will
> > > > > remain the same anyway).
> > > > > I can try running a poll if you are really interested. But moving
> to
> > > > > mailing list should be fine.
> > > > >
> > > > > >>- Relatively high bar for committership [1]
> > > > > So far we used a tweaked version of the chromium project's
> > guidelines.
> > > > > Open to advice on this going forward inside ASF
> > > > >
> > > > > >>No mention of non-code contributions at [1],
> > > > > Yes, [1] did not recognize that. But we as a project value it
> > > > > definitely, In fact, the last two committers are the list are
> > included
> > > > > with incubation precisely for non-code contributions. They helped
> get
> > > > > Hudi running on cloud systems.
> > > > >
> > > > > >>- Why the low number (6) of initial committers?
> > > > > No specific reason. We have included folks who have contributed
> > > > > significantly so far to the project, based on the guidelines we set
> > > out.
> > > > > Once we have neutral/standardized governance in place from ASF,
> might
> > > > > be easier to absorb more committers.
> > > > >
> > > > > >>- Of the initial committers mentioned it’s not obvious that all
> > have
> > > > > >>made
> > > > > contributions to the project. You mind listing their GitHub names
> or
> > > > > listing their previous contribution to the project.
> > > > > The first four committers would jump out, if you look at the
> > > > > contributions here <
> https://github.com/uber/hudi/graphs/contributors
> > >.
> > > > > (vinothchandar, n3nash, bvaradar, prazanna). prazanna actually has
> a
> > > > > lot more code ownership, but github is not showing his commits for
> > > > > some reason. You can find it in the raw git log. Already covered
> the
> > > > > last two committers in the previous answer.
> > > > >
> > > > > >>- Under relationships with other Apache Products “there are no
> > > > > >>direct
> > > > > competing projects with Hudi” is not a concern. The ASF allows
> > > > > directly competing projects.
> > > > > Sure. we were just describing positioning of the project in the
> > > > > ecosystem
> > > > >
> > > > > Thanks
> > > > > Vinoth
> > > > >
> > > > > On Fri, Dec 21, 2018 at 2:42 PM Justin Mclean
> > > > > 
> > > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Nice proposal and sounds like an interesting project.
> > > > > >
> > > > > > A couple of things I noticed that may need some further thought
> or
> > > > > > discussion:
> > > > > > - Use of 

Re: [DISCUSS] Hudi Incubation Proposal

[Vinoth Chandar]

Thanks Pierre!
I think we are ready to move forward with the VOTE, given there are no
additional concerns/comments for the past week or so.

On Thu, Dec 27, 2018 at 11:38 PM Pierre Smits 
wrote:

> Hi Vinoth,
>
> There is no typical timeline. Each proposal to incubate is unique and each
> timeline depends on the interactions of interested parties.
>
> You can use your own judgement to determine whether everything has been
> said and to take the next step.
>
> Best regards,
>
> Pierre Smits
>
> *Apache Trafodion , Vice President & PMC
> Chair*
> *Apache Directory , PMC Member*
> Apache Incubator , committer
> *Apache OFBiz , contributor (without privileges)
> since 2008*
> Apache Steve , committer
>
>
> On Fri, Dec 28, 2018 at 2:13 AM Vinoth Chandar 
> wrote:
>
> > Hi all,
> >
> > Thanks for the feedback and comments.
> >
> > Its been over a week. Whats the typical timeline/due process for starting
> > the vote?
> >
> > Thanks
> > Vinoth
> >
> >
> >
> > On Tue, Dec 25, 2018 at 8:04 PM Mohammad Asif Siddiqui <
> > mohammad.asif.siddiq...@huawei.com> wrote:
> >
> > > Looks like an interesting project.
> > >
> > > Regards
> > > Asif
> > >
> > > -Original Message-
> > > From: Luciano Resende [mailto:luckbr1...@gmail.com]
> > > Sent: 22 December 2018 PM 05:06
> > > To: general@incubator.apache.org
> > > Subject: Re: [DISCUSS] Hudi Incubation Proposal
> > >
> > > Very nice, looks like you guys might need one more mentor, feel free to
> > > include myself.
> > >
> > > On Fri, Dec 21, 2018 at 20:29 Vinoth Chandar 
> > > wrote:
> > >
> > > > Hi Justin,
> > > >
> > > > Thanks for the questions. I will try to answer them below .
> > > >
> > > > >>- Use of slack for communication. [1] Has the project thought about
> > > > >>how
> > > > moving conversations and decision making to a mailing list will
> affect
> > > > the community?
> > > > Good point. We use Slack for interactive debugging, critical
> decisions
> > > > (approaches, designs, PR) still happens over github issues (which
> will
> > > > remain the same anyway).
> > > > I can try running a poll if you are really interested. But moving to
> > > > mailing list should be fine.
> > > >
> > > > >>- Relatively high bar for committership [1]
> > > > So far we used a tweaked version of the chromium project's
> guidelines.
> > > > Open to advice on this going forward inside ASF
> > > >
> > > > >>No mention of non-code contributions at [1],
> > > > Yes, [1] did not recognize that. But we as a project value it
> > > > definitely, In fact, the last two committers are the list are
> included
> > > > with incubation precisely for non-code contributions. They helped get
> > > > Hudi running on cloud systems.
> > > >
> > > > >>- Why the low number (6) of initial committers?
> > > > No specific reason. We have included folks who have contributed
> > > > significantly so far to the project, based on the guidelines we set
> > out.
> > > > Once we have neutral/standardized governance in place from ASF, might
> > > > be easier to absorb more committers.
> > > >
> > > > >>- Of the initial committers mentioned it’s not obvious that all
> have
> > > > >>made
> > > > contributions to the project. You mind listing their GitHub names or
> > > > listing their previous contribution to the project.
> > > > The first four committers would jump out, if you look at the
> > > > contributions here  >.
> > > > (vinothchandar, n3nash, bvaradar, prazanna). prazanna actually has a
> > > > lot more code ownership, but github is not showing his commits for
> > > > some reason. You can find it in the raw git log. Already covered the
> > > > last two committers in the previous answer.
> > > >
> > > > >>- Under relationships with other Apache Products “there are no
> > > > >>direct
> > > > competing projects with Hudi” is not a concern. The ASF allows
> > > > directly competing projects.
> > > > Sure. we were just describing positioning of the project in the
> > > > ecosystem
> > > >
> > > > Thanks
> > > > Vinoth
> > > >
> > > > On Fri, Dec 21, 2018 at 2:42 PM Justin Mclean
> > > > 
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > Nice proposal and sounds like an interesting project.
> > > > >
> > > > > A couple of things I noticed that may need some further thought or
> > > > > discussion:
> > > > > - Use of slack for communication. [1] Has the project thought about
> > > > > how moving conversations and decision making to a mailing list will
> > > > > affect
> > > > the
> > > > > community?
> > > > > - Relatively high bar for committership [1]. While it's up to every
> > > > (P)PMC
> > > > > to set the bar, having a high bar hinders project growth and limits
> > > > people
> > > > > who are unable to work full time of the project.
> > > > > - No mention of non-code contributions at [1], as teh 

Re: Incubator Wiki write access

[Justin Mclean]

Hi,

> I will also need to update the Podling reports next time. Could you
> please add me to the group?
> My username is WoonsanKo

Your user name has already been added and you should have edit rights.

Thanks,
Justin

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

Re: Incubator Wiki write access

[Bertrand Delacretaz]

On Thu, Jan 3, 2019 at 11:11 AM Woonsan Ko  wrote:
> ...My username is WoonsanKo

done.
-Bertrand

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

Incubator Wiki write access

[Woonsan Ko]

Hi,

I will also need to update the Podling reports next time. Could you
please add me to the group?
My username is WoonsanKo

Thanks in advance,

Woonsan

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

Re: Write Access to incubator Wiki

[Justin Mclean]

Hi,

> could I get write access to the incubator Wiki to update the Podling reports 
> for the next time?

Done and enjoy!

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

Write Access to incubator Wiki

[Julian Feinauer]

Hi,

could I get write access to the incubator Wiki to update the Podling reports 
for the next time?
Username is jfeinauer

Thanks!
Julian