Architecture meeting

[Lucas Bonatto Miguel <lu...@apache.org>]

Folks, our meeting was interrupted due to Google Meets issues:
[image: image.png]

It was a good discussions. Let's share our notes here.

Best,
Lucas

Re: Architecture meeting

[harshit rohatgi <ha...@gmail.com>]

Thanks a lot Lucas.
Excited about the new direction Marvin is heading. That was my first
impression too.

Would be great if core maintainers could write their viewpoint as a rough
1-pager and link to Jira. That way others can start thinking in this
direction.

I believe there is a follow-up meeting scheduled. Would be helpful for
*cough cough* me to read some thought dump before the meeting.

On Fri, 25 Sep, 2020, 11:16 AM Wei Chen, <we...@apache.org> wrote:

> Hello Lucas and All,
>
> Thanks for the note!
> Sorry that I couldn't make it to the meeting.
> Should we consolidate these items as action points in our Jira?
>
> Best Regards,
> Wei
>
> On Fri, Sep 25, 2020 at 10:03 AM Lucas Cardoso Silva <
> cardosolucas61.lcs@gmail.com> wrote:
>
> > Hello guys, the meeting was interrupted but I believe we were almost
> > finishing anyway. It was a good discussion!
> >
> > My notes:
> >
> > 1. We need to work continuously on the documentation, as it is currently
> a
> > weak spot. We discussed and more or less agreed on the following:
> > - Let's use ReadTheDocs for the user guides (we will need to configure
> that
> > in the Github repository and configure redirect and DNS in Apache
> > infrastructure).
> > - Let's include "deeper" use cases, in the form of guides. We can divide
> > this work and invite more contributors to write. We need to decide on
> what
> > topics could appear in the documentation, so that we can start writing.
> > - For development, we can use RFC format. Maybe we can start by writing a
> > RFC with the proposal for Marvin's new direction (see item 3 below)
> >
> > 2. "We should focus on what we are good at, and reuse what others are
> good
> > at" (Taka's words). It is very difficult to be always updated with the
> > industry and new technologies.
> >
> > 3. A "new" direction for Marvin started to appear, with two main "new
> > features":
> > - We could provide alternatives to Marvin's serving. Like TFX, as it
> seems
> > close enough to DASFE (it might even have been inspired by it!). The idea
> > is to make Marvin extensible, more like a SDK, and focus on making the
> > learning curve for these tools smoother (as DASFE is a really easy to
> learn
> > design pattern).
> > - We could use Apache Beam to improve data acquisition in Marvin.
> > - I could try to write a simple RFC for this, so that we can work out the
> > details!
> >
> > Did I forget something?
> >
> > Best regards!
> >
> > Em qui., 24 de set. de 2020 às 22:05, Lucas Bonatto Miguel <
> > lucasbm88@apache.org> escreveu:
> >
> > > Folks, our meeting was interrupted due to Google Meets issues:
> > > [image: image.png]
> > >
> > > It was a good discussions. Let's share our notes here.
> > >
> > > Best,
> > > Lucas
> > >
> >
>

Re: Architecture meeting

[Wei Chen <we...@apache.org>]

Hello Lucas and All,

Thanks for the note!
Sorry that I couldn't make it to the meeting.
Should we consolidate these items as action points in our Jira?

Best Regards,
Wei

On Fri, Sep 25, 2020 at 10:03 AM Lucas Cardoso Silva <
cardosolucas61.lcs@gmail.com> wrote:

> Hello guys, the meeting was interrupted but I believe we were almost
> finishing anyway. It was a good discussion!
>
> My notes:
>
> 1. We need to work continuously on the documentation, as it is currently a
> weak spot. We discussed and more or less agreed on the following:
> - Let's use ReadTheDocs for the user guides (we will need to configure that
> in the Github repository and configure redirect and DNS in Apache
> infrastructure).
> - Let's include "deeper" use cases, in the form of guides. We can divide
> this work and invite more contributors to write. We need to decide on what
> topics could appear in the documentation, so that we can start writing.
> - For development, we can use RFC format. Maybe we can start by writing a
> RFC with the proposal for Marvin's new direction (see item 3 below)
>
> 2. "We should focus on what we are good at, and reuse what others are good
> at" (Taka's words). It is very difficult to be always updated with the
> industry and new technologies.
>
> 3. A "new" direction for Marvin started to appear, with two main "new
> features":
> - We could provide alternatives to Marvin's serving. Like TFX, as it seems
> close enough to DASFE (it might even have been inspired by it!). The idea
> is to make Marvin extensible, more like a SDK, and focus on making the
> learning curve for these tools smoother (as DASFE is a really easy to learn
> design pattern).
> - We could use Apache Beam to improve data acquisition in Marvin.
> - I could try to write a simple RFC for this, so that we can work out the
> details!
>
> Did I forget something?
>
> Best regards!
>
> Em qui., 24 de set. de 2020 às 22:05, Lucas Bonatto Miguel <
> lucasbm88@apache.org> escreveu:
>
> > Folks, our meeting was interrupted due to Google Meets issues:
> > [image: image.png]
> >
> > It was a good discussions. Let's share our notes here.
> >
> > Best,
> > Lucas
> >
>

Re: Architecture meeting

[Lucas Cardoso Silva <ca...@gmail.com>]

Hello guys, the meeting was interrupted but I believe we were almost
finishing anyway. It was a good discussion!

My notes:

1. We need to work continuously on the documentation, as it is currently a
weak spot. We discussed and more or less agreed on the following:
- Let's use ReadTheDocs for the user guides (we will need to configure that
in the Github repository and configure redirect and DNS in Apache
infrastructure).
- Let's include "deeper" use cases, in the form of guides. We can divide
this work and invite more contributors to write. We need to decide on what
topics could appear in the documentation, so that we can start writing.
- For development, we can use RFC format. Maybe we can start by writing a
RFC with the proposal for Marvin's new direction (see item 3 below)

2. "We should focus on what we are good at, and reuse what others are good
at" (Taka's words). It is very difficult to be always updated with the
industry and new technologies.

3. A "new" direction for Marvin started to appear, with two main "new
features":
- We could provide alternatives to Marvin's serving. Like TFX, as it seems
close enough to DASFE (it might even have been inspired by it!). The idea
is to make Marvin extensible, more like a SDK, and focus on making the
learning curve for these tools smoother (as DASFE is a really easy to learn
design pattern).
- We could use Apache Beam to improve data acquisition in Marvin.
- I could try to write a simple RFC for this, so that we can work out the
details!

Did I forget something?

Best regards!

Em qui., 24 de set. de 2020 às 22:05, Lucas Bonatto Miguel <
lucasbm88@apache.org> escreveu:

> Folks, our meeting was interrupted due to Google Meets issues:
> [image: image.png]
>
> It was a good discussions. Let's share our notes here.
>
> Best,
> Lucas
>