You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by David Cavazos <dc...@google.com> on 2018/08/01 22:12:15 UTC
Community Examples Repository
Hi everyone!
We wanted to migrate the examples from the core repository to a new Beam
community examples repository. As the number of examples grow, it makes
sense to modularize and decouple the core functionality from the examples.
We will also create some guidelines with the best practices for new
examples to be submitted.
For more details, feel free to take a look and comment on the proposal
<https://docs.google.com/document/d/1vhcKJlP0qH1C7NZPDjohT2PUbOD-k71avv1CjEYapdw/edit?usp=sharing>
.
Cheers,
David
Re: Community Examples Repository
Posted by Andrew Pilloud <ap...@google.com>.
Looks good to me. This also sounds like a great way to ensure we aren't
making breaking changes to the API surface of Beam across releases. I've
been told this is a painful thing we frequently do. Hopefully we can run
tests on these external examples against various versions of Beam.
Andrew
On Wed, Aug 1, 2018, 3:37 PM Jesse Anderson <je...@bigdatainstitute.io>
wrote:
> The examples have to be separate from the main beam repository. This way,
> they serve as an example of how to use them in your code instead of how to
> do it as part of Beam. It would also you to show the dependencies in sbt or
> Maven.
>
> On Wed, Aug 1, 2018, 3:16 PM Charles Chen <cc...@google.com> wrote:
>
>> The examples we have right now serve both as examples to users and along
>> with their unit tests, as tests of functionality. If we move the examples
>> out, what is a good way to make sure that we continue to have visibility
>> and test coverage? Can we address this in a section of the doc?
>>
>> On Wed, Aug 1, 2018 at 3:12 PM David Cavazos <dc...@google.com> wrote:
>>
>>> Hi everyone!
>>>
>>> We wanted to migrate the examples from the core repository to a new Beam
>>> community examples repository. As the number of examples grow, it makes
>>> sense to modularize and decouple the core functionality from the examples.
>>>
>>> We will also create some guidelines with the best practices for new
>>> examples to be submitted.
>>>
>>> For more details, feel free to take a look and comment on the proposal
>>> <https://docs.google.com/document/d/1vhcKJlP0qH1C7NZPDjohT2PUbOD-k71avv1CjEYapdw/edit?usp=sharing>
>>> .
>>>
>>> Cheers,
>>> David
>>>
>>
Re: Community Examples Repository
Posted by Davor Bonaci <da...@apache.org>.
>
> it makes sense to modularize
It certainly does, but somebody just had another proposal to move the
website into the main repository ;-). That proposal was also good for
~everyone. Fun times...
(I have my opinions, of course, but I'm fine with any approach.)
On Wed, Aug 1, 2018 at 4:37 PM, Ahmet Altay <al...@google.com> wrote:
> Thank you for this initiative.
>
> How about keeping a set of core examples in the main repository as a way
> of 1) convenient testing at a PR level 2) Testing with end to end tests
> against Beam head rather than a released Beam version 3) I think there is
> some educational value in having wordcount as a simple example living along
> with the code.
>
> For anything else examples repository would be a great idea.
>
> For testing, I would also like to understand how could we test examples
> against both released versions of Beam and the code currently being
> developed in master.
>
> Ahmet
>
> On Wed, Aug 1, 2018 at 3:36 PM, Jesse Anderson <je...@bigdatainstitute.io>
> wrote:
>
>> The examples have to be separate from the main beam repository. This way,
>> they serve as an example of how to use them in your code instead of how to
>> do it as part of Beam. It would also you to show the dependencies in sbt or
>> Maven.
>>
>>
>> On Wed, Aug 1, 2018, 3:16 PM Charles Chen <cc...@google.com> wrote:
>>
>>> The examples we have right now serve both as examples to users and along
>>> with their unit tests, as tests of functionality. If we move the examples
>>> out, what is a good way to make sure that we continue to have visibility
>>> and test coverage? Can we address this in a section of the doc?
>>>
>>> On Wed, Aug 1, 2018 at 3:12 PM David Cavazos <dc...@google.com>
>>> wrote:
>>>
>>>> Hi everyone!
>>>>
>>>> We wanted to migrate the examples from the core repository to a new
>>>> Beam community examples repository. As the number of examples grow, it
>>>> makes sense to modularize and decouple the core functionality from the
>>>> examples.
>>>>
>>>> We will also create some guidelines with the best practices for new
>>>> examples to be submitted.
>>>>
>>>> For more details, feel free to take a look and comment on the proposal
>>>> <https://docs.google.com/document/d/1vhcKJlP0qH1C7NZPDjohT2PUbOD-k71avv1CjEYapdw/edit?usp=sharing>
>>>> .
>>>>
>>>> Cheers,
>>>> David
>>>>
>>>
>
Re: Community Examples Repository
Posted by Ahmet Altay <al...@google.com>.
Thank you for this initiative.
How about keeping a set of core examples in the main repository as a way of
1) convenient testing at a PR level 2) Testing with end to end tests
against Beam head rather than a released Beam version 3) I think there is
some educational value in having wordcount as a simple example living along
with the code.
For anything else examples repository would be a great idea.
For testing, I would also like to understand how could we test examples
against both released versions of Beam and the code currently being
developed in master.
Ahmet
On Wed, Aug 1, 2018 at 3:36 PM, Jesse Anderson <je...@bigdatainstitute.io>
wrote:
> The examples have to be separate from the main beam repository. This way,
> they serve as an example of how to use them in your code instead of how to
> do it as part of Beam. It would also you to show the dependencies in sbt or
> Maven.
>
>
> On Wed, Aug 1, 2018, 3:16 PM Charles Chen <cc...@google.com> wrote:
>
>> The examples we have right now serve both as examples to users and along
>> with their unit tests, as tests of functionality. If we move the examples
>> out, what is a good way to make sure that we continue to have visibility
>> and test coverage? Can we address this in a section of the doc?
>>
>> On Wed, Aug 1, 2018 at 3:12 PM David Cavazos <dc...@google.com> wrote:
>>
>>> Hi everyone!
>>>
>>> We wanted to migrate the examples from the core repository to a new Beam
>>> community examples repository. As the number of examples grow, it makes
>>> sense to modularize and decouple the core functionality from the examples.
>>>
>>> We will also create some guidelines with the best practices for new
>>> examples to be submitted.
>>>
>>> For more details, feel free to take a look and comment on the proposal
>>> <https://docs.google.com/document/d/1vhcKJlP0qH1C7NZPDjohT2PUbOD-k71avv1CjEYapdw/edit?usp=sharing>
>>> .
>>>
>>> Cheers,
>>> David
>>>
>>
Re: Community Examples Repository
Posted by Jesse Anderson <je...@bigdatainstitute.io>.
The examples have to be separate from the main beam repository. This way,
they serve as an example of how to use them in your code instead of how to
do it as part of Beam. It would also you to show the dependencies in sbt or
Maven.
On Wed, Aug 1, 2018, 3:16 PM Charles Chen <cc...@google.com> wrote:
> The examples we have right now serve both as examples to users and along
> with their unit tests, as tests of functionality. If we move the examples
> out, what is a good way to make sure that we continue to have visibility
> and test coverage? Can we address this in a section of the doc?
>
> On Wed, Aug 1, 2018 at 3:12 PM David Cavazos <dc...@google.com> wrote:
>
>> Hi everyone!
>>
>> We wanted to migrate the examples from the core repository to a new Beam
>> community examples repository. As the number of examples grow, it makes
>> sense to modularize and decouple the core functionality from the examples.
>>
>> We will also create some guidelines with the best practices for new
>> examples to be submitted.
>>
>> For more details, feel free to take a look and comment on the proposal
>> <https://docs.google.com/document/d/1vhcKJlP0qH1C7NZPDjohT2PUbOD-k71avv1CjEYapdw/edit?usp=sharing>
>> .
>>
>> Cheers,
>> David
>>
>
Re: Community Examples Repository
Posted by David Cavazos <dc...@google.com>.
For visibility, we can have a link on both the beam.apache.org website and
in the core repository's README file.
Regarding testing *could* be a little trickier. Any unit test should
continue to live in the core repository, and the examples from the examples
repository could serve as end-to-end tests. This means the examples
repository also needs a testing infrastructure, which should be triggerable
from the root directory. Having it this way would allow us to have a test
in the core repository that clones the examples repository in a temporary
directory and runs the tests from there.
This way, users don't *need* to have the examples as a strict dependency,
but developers modifying the core repository will have both (just like it
is today).
On Wed, Aug 1, 2018 at 3:16 PM Charles Chen <cc...@google.com> wrote:
> The examples we have right now serve both as examples to users and along
> with their unit tests, as tests of functionality. If we move the examples
> out, what is a good way to make sure that we continue to have visibility
> and test coverage? Can we address this in a section of the doc?
>
> On Wed, Aug 1, 2018 at 3:12 PM David Cavazos <dc...@google.com> wrote:
>
>> Hi everyone!
>>
>> We wanted to migrate the examples from the core repository to a new Beam
>> community examples repository. As the number of examples grow, it makes
>> sense to modularize and decouple the core functionality from the examples.
>>
>> We will also create some guidelines with the best practices for new
>> examples to be submitted.
>>
>> For more details, feel free to take a look and comment on the proposal
>> <https://docs.google.com/document/d/1vhcKJlP0qH1C7NZPDjohT2PUbOD-k71avv1CjEYapdw/edit?usp=sharing>
>> .
>>
>> Cheers,
>> David
>>
>
Re: Community Examples Repository
Posted by Charles Chen <cc...@google.com>.
The examples we have right now serve both as examples to users and along
with their unit tests, as tests of functionality. If we move the examples
out, what is a good way to make sure that we continue to have visibility
and test coverage? Can we address this in a section of the doc?
On Wed, Aug 1, 2018 at 3:12 PM David Cavazos <dc...@google.com> wrote:
> Hi everyone!
>
> We wanted to migrate the examples from the core repository to a new Beam
> community examples repository. As the number of examples grow, it makes
> sense to modularize and decouple the core functionality from the examples.
>
> We will also create some guidelines with the best practices for new
> examples to be submitted.
>
> For more details, feel free to take a look and comment on the proposal
> <https://docs.google.com/document/d/1vhcKJlP0qH1C7NZPDjohT2PUbOD-k71avv1CjEYapdw/edit?usp=sharing>
> .
>
> Cheers,
> David
>
Re: Community Examples Repository
Posted by David Cavazos <dc...@google.com>.
The way I see it, the examples repo needs not be versioned. Each example
should specify it's dependencies the same way any external application
would. In Python this would be the *requirements.txt* where we can specify
*apache-beam>=2.5.0* for example. For Java, it can be specified in the
*pom.xml* file. This would show users how to use Beam for their own
applications as Jesse mentioned.
A high friction point I've experienced in Java is creating a new pom file,
so having a repository of examples that can be copy-pasted with a minimal
and working pom file would be great.
In terms of packaging, I think we can get away with it just being a
collection of *independent* examples with a testing infrastructure. Testing
should be trigger-able at the root, but each sample should be tested in its
own isolated environment. Since there are no dependencies, all examples can
be tested in parallel. For every example, create its virtual environment,
run all the tests and destroy it.
If we want the examples to also live in PyPI, then we would require
versioning (*major.minor.patch*). Since it doesn't really matter, we can
just have the *major.minor* part mirror the current *apache-beam* version
for consistency, and as new examples get added / modified we can bump the
*patch* version indefinitely.
On Fri, Aug 3, 2018 at 3:33 PM Charles Chen <cc...@google.com> wrote:
> We should separate out the decision for (1) whether examples should be
> packaged separately upon release and (2) where the example will live
> code-wise, i.e. whether we want another repo. With respect to the first
> item, I think the proposal needs more detail before we can decide here--for
> example, if we separate out the packaging for the examples, we need to
> change our build process and potentially release additional PyPI packages
> and this should be thought about before we can make a decision.
>
> On Fri, Aug 3, 2018 at 3:23 PM Pablo Estrada <pa...@google.com> wrote:
>
>> Hello all,
>> I see a number of mixed responses. I think it would be helpful to push
>> for a decision by calling for a vote.
>>
>> Also, the proposal has a number of parts, so perhaps we could ask David
>> and other contributors of the proposal to outline a couple alternatives the
>> we can all vote on. (e.g. #1 no examples repo, #2 all examples to new repo,
>> #3 examples repo, but some examples remain in main repo).
>>
>> The outcome may be no change at all, or some change, but at least we'll
>> have a definite decision from the community.
>>
>> Does that sound reasonable?
>> -P.
>>
>> On Thu, Aug 2, 2018 at 11:09 AM Ankur Goenka <go...@google.com> wrote:
>>
>>> I like he initiative but I feel that fragmenting the codebase will make
>>> it harder to discover examples. Having examples in a separate repo makes it
>>> easier to forget that examples should get the same love as the rest of the
>>> codebase.
>>> The other challenge is the tooling and integration which is harder with
>>> multiple repo.
>>> It makes sense to isolate the examples and make them more obvious.
>>> A sub project of examples as mentioned in the discussion might be
>>> sufficient without having much overhead.
>>>
>>> Thanks,
>>> Ankur
>>>
>>>
>>> On Thu, Aug 2, 2018 at 10:52 AM Kai Jiang <ji...@gmail.com> wrote:
>>>
>>>> Agreed with Rui. We could also add more SQL examples (like, different
>>>> IOs ) for everyone to get started with.
>>>>
>>>> Best,
>>>> Kai
>>>>
>>>> On 2018/08/02 17:40:32, Rui Wang <ru...@google.com> wrote:
>>>> > I might miss it: are examples to be moved including those which are
>>>> not
>>>> > under example/? For example there are some BeamSQL examples in
>>>> > org/apache/beam/sdk/extensions/sql/example
>>>> > <
>>>> https://github.com/apache/beam/tree/master/sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/example
>>>> >
>>>> > .
>>>> >
>>>> >
>>>> > It's better to keep BeamSQL examples in where it is because related
>>>> API
>>>> > might still change.
>>>> >
>>>> > -Rui
>>>> >
>>>> > On Thu, Aug 2, 2018 at 8:58 AM Ahmet Altay <al...@google.com> wrote:
>>>> >
>>>> > > Robert, I agree with you in general. However there is also a second
>>>> > > motivation. There is an increase in new PRs that are coming to add
>>>> new
>>>> > > examples. This is great however the core code (including
>>>> distributions) is
>>>> > > not a great place to host such examples. An examples repo would
>>>> help in
>>>> > > this case. It could also serve as an entry point for new
>>>> contributors.
>>>> > >
>>>> > >
>>>> > >
>>>> > > On Thu, Aug 2, 2018 at 12:40 AM, Robert Bradshaw <
>>>> robertwb@google.com>
>>>> > > wrote:
>>>> > >
>>>> > >> I have to admit I'm generally -1 on moving examples to a separate
>>>> > >> repository. In particular, I think it would actually inhibit the
>>>> > >> stated goals of increasing visibility and better keeping them up to
>>>> > >> date, and for all the reasons we just migrated the beam-site
>>>> directory
>>>> > >> in. It seems the primary motivation is that it's difficult in Java
>>>> to
>>>> > >> have a portion of the repo that depends on another as if it were
>>>> > >> "external" (i.e. the way others would use Beam) rather than being a
>>>> > >> sub-project of Beam. Is this not doable?
>>>> > >> On Wed, Aug 1, 2018 at 10:59 PM Charles Chen <cc...@google.com>
>>>> wrote:
>>>> > >> >
>>>> > >> > I would also prefer that examples be linked to releases so that
>>>> we can
>>>> > >> build and test them during development; i.e. if your commit breaks
>>>> > >> wordcount, we want to know right away so we can revert. Perhaps
>>>> we can
>>>> > >> keep these in the repo but more clearly modularize the artifacts
>>>> we release?
>>>> > >> >
>>>> > >> > For the Python SDK, if we separate this out in any way, there is
>>>> the
>>>> > >> separate issue of dealing with namespace packages (which are kind
>>>> of broken
>>>> > >> and poorly supported:
>>>> > >> https://github.com/pypa/python-packaging-user-guide/issues/265),
>>>> if we
>>>> > >> want to keep the examples under the apache_beam.examples module
>>>> path. See
>>>> > >> also
>>>> https://packaging.python.org/guides/packaging-namespace-packages/.
>>>> > >> >
>>>> > >> > On Wed, Aug 1, 2018 at 9:29 PM jb@nanthrax.net <jb...@nanthrax.net>
>>>> wrote:
>>>> > >> >>
>>>> > >> >> Hi,
>>>> > >> >>
>>>> > >> >> I don't have problem to move the examples in a dedicated
>>>> repository.
>>>> > >> However, IMHO, we have to:
>>>> > >> >>
>>>> > >> >> 1. Keep a build of examples linked to latest core
>>>> release/SNAPSHOT
>>>> > >> >> 2. Include the examples in the distribution (convenient for the
>>>> users)
>>>> > >> >>
>>>> > >> >> On another topic, I think it would be better to avoid usage of
>>>> Google
>>>> > >> Doc for such kind of discussion and directly share on the mailing
>>>> list (at
>>>> > >> least a summary/light details).
>>>> > >> >>
>>>> > >> >> Regards
>>>> > >> >> JB
>>>> > >> >>
>>>> > >> >> On Thursday, August 02, 2018 00:12 CEST, David Cavazos <
>>>> > >> dcavazos@google.com> wrote:
>>>> > >> >>
>>>> > >> >>
>>>> > >> >> Hi everyone!
>>>> > >> >>
>>>> > >> >> We wanted to migrate the examples from the core repository to a
>>>> new
>>>> > >> Beam community examples repository. As the number of examples
>>>> grow, it
>>>> > >> makes sense to modularize and decouple the core functionality from
>>>> the
>>>> > >> examples.
>>>> > >> >>
>>>> > >> >> We will also create some guidelines with the best practices for
>>>> new
>>>> > >> examples to be submitted.
>>>> > >> >>
>>>> > >> >> For more details, feel free to take a look and comment on the
>>>> proposal.
>>>> > >> >>
>>>> > >> >> Cheers,
>>>> > >> >> David
>>>> > >> >>
>>>> > >> >>
>>>> > >> >>
>>>> > >> >>
>>>> > >> >>
>>>> > >>
>>>> > >
>>>> > >
>>>> >
>>>>
>>> --
>> Got feedback? go/pabloem-feedback
>> <https://goto.google.com/pabloem-feedback>
>>
>
Re: Community Examples Repository
Posted by Charles Chen <cc...@google.com>.
We should separate out the decision for (1) whether examples should be
packaged separately upon release and (2) where the example will live
code-wise, i.e. whether we want another repo. With respect to the first
item, I think the proposal needs more detail before we can decide here--for
example, if we separate out the packaging for the examples, we need to
change our build process and potentially release additional PyPI packages
and this should be thought about before we can make a decision.
On Fri, Aug 3, 2018 at 3:23 PM Pablo Estrada <pa...@google.com> wrote:
> Hello all,
> I see a number of mixed responses. I think it would be helpful to push for
> a decision by calling for a vote.
>
> Also, the proposal has a number of parts, so perhaps we could ask David
> and other contributors of the proposal to outline a couple alternatives the
> we can all vote on. (e.g. #1 no examples repo, #2 all examples to new repo,
> #3 examples repo, but some examples remain in main repo).
>
> The outcome may be no change at all, or some change, but at least we'll
> have a definite decision from the community.
>
> Does that sound reasonable?
> -P.
>
> On Thu, Aug 2, 2018 at 11:09 AM Ankur Goenka <go...@google.com> wrote:
>
>> I like he initiative but I feel that fragmenting the codebase will make
>> it harder to discover examples. Having examples in a separate repo makes it
>> easier to forget that examples should get the same love as the rest of the
>> codebase.
>> The other challenge is the tooling and integration which is harder with
>> multiple repo.
>> It makes sense to isolate the examples and make them more obvious.
>> A sub project of examples as mentioned in the discussion might be
>> sufficient without having much overhead.
>>
>> Thanks,
>> Ankur
>>
>>
>> On Thu, Aug 2, 2018 at 10:52 AM Kai Jiang <ji...@gmail.com> wrote:
>>
>>> Agreed with Rui. We could also add more SQL examples (like, different
>>> IOs ) for everyone to get started with.
>>>
>>> Best,
>>> Kai
>>>
>>> On 2018/08/02 17:40:32, Rui Wang <ru...@google.com> wrote:
>>> > I might miss it: are examples to be moved including those which are not
>>> > under example/? For example there are some BeamSQL examples in
>>> > org/apache/beam/sdk/extensions/sql/example
>>> > <
>>> https://github.com/apache/beam/tree/master/sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/example
>>> >
>>> > .
>>> >
>>> >
>>> > It's better to keep BeamSQL examples in where it is because related API
>>> > might still change.
>>> >
>>> > -Rui
>>> >
>>> > On Thu, Aug 2, 2018 at 8:58 AM Ahmet Altay <al...@google.com> wrote:
>>> >
>>> > > Robert, I agree with you in general. However there is also a second
>>> > > motivation. There is an increase in new PRs that are coming to add
>>> new
>>> > > examples. This is great however the core code (including
>>> distributions) is
>>> > > not a great place to host such examples. An examples repo would help
>>> in
>>> > > this case. It could also serve as an entry point for new
>>> contributors.
>>> > >
>>> > >
>>> > >
>>> > > On Thu, Aug 2, 2018 at 12:40 AM, Robert Bradshaw <
>>> robertwb@google.com>
>>> > > wrote:
>>> > >
>>> > >> I have to admit I'm generally -1 on moving examples to a separate
>>> > >> repository. In particular, I think it would actually inhibit the
>>> > >> stated goals of increasing visibility and better keeping them up to
>>> > >> date, and for all the reasons we just migrated the beam-site
>>> directory
>>> > >> in. It seems the primary motivation is that it's difficult in Java
>>> to
>>> > >> have a portion of the repo that depends on another as if it were
>>> > >> "external" (i.e. the way others would use Beam) rather than being a
>>> > >> sub-project of Beam. Is this not doable?
>>> > >> On Wed, Aug 1, 2018 at 10:59 PM Charles Chen <cc...@google.com>
>>> wrote:
>>> > >> >
>>> > >> > I would also prefer that examples be linked to releases so that
>>> we can
>>> > >> build and test them during development; i.e. if your commit breaks
>>> > >> wordcount, we want to know right away so we can revert. Perhaps we
>>> can
>>> > >> keep these in the repo but more clearly modularize the artifacts we
>>> release?
>>> > >> >
>>> > >> > For the Python SDK, if we separate this out in any way, there is
>>> the
>>> > >> separate issue of dealing with namespace packages (which are kind
>>> of broken
>>> > >> and poorly supported:
>>> > >> https://github.com/pypa/python-packaging-user-guide/issues/265),
>>> if we
>>> > >> want to keep the examples under the apache_beam.examples module
>>> path. See
>>> > >> also
>>> https://packaging.python.org/guides/packaging-namespace-packages/.
>>> > >> >
>>> > >> > On Wed, Aug 1, 2018 at 9:29 PM jb@nanthrax.net <jb...@nanthrax.net>
>>> wrote:
>>> > >> >>
>>> > >> >> Hi,
>>> > >> >>
>>> > >> >> I don't have problem to move the examples in a dedicated
>>> repository.
>>> > >> However, IMHO, we have to:
>>> > >> >>
>>> > >> >> 1. Keep a build of examples linked to latest core
>>> release/SNAPSHOT
>>> > >> >> 2. Include the examples in the distribution (convenient for the
>>> users)
>>> > >> >>
>>> > >> >> On another topic, I think it would be better to avoid usage of
>>> Google
>>> > >> Doc for such kind of discussion and directly share on the mailing
>>> list (at
>>> > >> least a summary/light details).
>>> > >> >>
>>> > >> >> Regards
>>> > >> >> JB
>>> > >> >>
>>> > >> >> On Thursday, August 02, 2018 00:12 CEST, David Cavazos <
>>> > >> dcavazos@google.com> wrote:
>>> > >> >>
>>> > >> >>
>>> > >> >> Hi everyone!
>>> > >> >>
>>> > >> >> We wanted to migrate the examples from the core repository to a
>>> new
>>> > >> Beam community examples repository. As the number of examples grow,
>>> it
>>> > >> makes sense to modularize and decouple the core functionality from
>>> the
>>> > >> examples.
>>> > >> >>
>>> > >> >> We will also create some guidelines with the best practices for
>>> new
>>> > >> examples to be submitted.
>>> > >> >>
>>> > >> >> For more details, feel free to take a look and comment on the
>>> proposal.
>>> > >> >>
>>> > >> >> Cheers,
>>> > >> >> David
>>> > >> >>
>>> > >> >>
>>> > >> >>
>>> > >> >>
>>> > >> >>
>>> > >>
>>> > >
>>> > >
>>> >
>>>
>> --
> Got feedback? go/pabloem-feedback
> <https://goto.google.com/pabloem-feedback>
>
Re: Community Examples Repository
Posted by Pablo Estrada <pa...@google.com>.
Hello all,
I see a number of mixed responses. I think it would be helpful to push for
a decision by calling for a vote.
Also, the proposal has a number of parts, so perhaps we could ask David and
other contributors of the proposal to outline a couple alternatives the we
can all vote on. (e.g. #1 no examples repo, #2 all examples to new repo, #3
examples repo, but some examples remain in main repo).
The outcome may be no change at all, or some change, but at least we'll
have a definite decision from the community.
Does that sound reasonable?
-P.
On Thu, Aug 2, 2018 at 11:09 AM Ankur Goenka <go...@google.com> wrote:
> I like he initiative but I feel that fragmenting the codebase will make it
> harder to discover examples. Having examples in a separate repo makes it
> easier to forget that examples should get the same love as the rest of the
> codebase.
> The other challenge is the tooling and integration which is harder with
> multiple repo.
> It makes sense to isolate the examples and make them more obvious.
> A sub project of examples as mentioned in the discussion might be
> sufficient without having much overhead.
>
> Thanks,
> Ankur
>
>
> On Thu, Aug 2, 2018 at 10:52 AM Kai Jiang <ji...@gmail.com> wrote:
>
>> Agreed with Rui. We could also add more SQL examples (like, different IOs
>> ) for everyone to get started with.
>>
>> Best,
>> Kai
>>
>> On 2018/08/02 17:40:32, Rui Wang <ru...@google.com> wrote:
>> > I might miss it: are examples to be moved including those which are not
>> > under example/? For example there are some BeamSQL examples in
>> > org/apache/beam/sdk/extensions/sql/example
>> > <
>> https://github.com/apache/beam/tree/master/sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/example
>> >
>> > .
>> >
>> >
>> > It's better to keep BeamSQL examples in where it is because related API
>> > might still change.
>> >
>> > -Rui
>> >
>> > On Thu, Aug 2, 2018 at 8:58 AM Ahmet Altay <al...@google.com> wrote:
>> >
>> > > Robert, I agree with you in general. However there is also a second
>> > > motivation. There is an increase in new PRs that are coming to add new
>> > > examples. This is great however the core code (including
>> distributions) is
>> > > not a great place to host such examples. An examples repo would help
>> in
>> > > this case. It could also serve as an entry point for new contributors.
>> > >
>> > >
>> > >
>> > > On Thu, Aug 2, 2018 at 12:40 AM, Robert Bradshaw <robertwb@google.com
>> >
>> > > wrote:
>> > >
>> > >> I have to admit I'm generally -1 on moving examples to a separate
>> > >> repository. In particular, I think it would actually inhibit the
>> > >> stated goals of increasing visibility and better keeping them up to
>> > >> date, and for all the reasons we just migrated the beam-site
>> directory
>> > >> in. It seems the primary motivation is that it's difficult in Java to
>> > >> have a portion of the repo that depends on another as if it were
>> > >> "external" (i.e. the way others would use Beam) rather than being a
>> > >> sub-project of Beam. Is this not doable?
>> > >> On Wed, Aug 1, 2018 at 10:59 PM Charles Chen <cc...@google.com> wrote:
>> > >> >
>> > >> > I would also prefer that examples be linked to releases so that we
>> can
>> > >> build and test them during development; i.e. if your commit breaks
>> > >> wordcount, we want to know right away so we can revert. Perhaps we
>> can
>> > >> keep these in the repo but more clearly modularize the artifacts we
>> release?
>> > >> >
>> > >> > For the Python SDK, if we separate this out in any way, there is
>> the
>> > >> separate issue of dealing with namespace packages (which are kind of
>> broken
>> > >> and poorly supported:
>> > >> https://github.com/pypa/python-packaging-user-guide/issues/265), if
>> we
>> > >> want to keep the examples under the apache_beam.examples module
>> path. See
>> > >> also
>> https://packaging.python.org/guides/packaging-namespace-packages/.
>> > >> >
>> > >> > On Wed, Aug 1, 2018 at 9:29 PM jb@nanthrax.net <jb...@nanthrax.net>
>> wrote:
>> > >> >>
>> > >> >> Hi,
>> > >> >>
>> > >> >> I don't have problem to move the examples in a dedicated
>> repository.
>> > >> However, IMHO, we have to:
>> > >> >>
>> > >> >> 1. Keep a build of examples linked to latest core release/SNAPSHOT
>> > >> >> 2. Include the examples in the distribution (convenient for the
>> users)
>> > >> >>
>> > >> >> On another topic, I think it would be better to avoid usage of
>> Google
>> > >> Doc for such kind of discussion and directly share on the mailing
>> list (at
>> > >> least a summary/light details).
>> > >> >>
>> > >> >> Regards
>> > >> >> JB
>> > >> >>
>> > >> >> On Thursday, August 02, 2018 00:12 CEST, David Cavazos <
>> > >> dcavazos@google.com> wrote:
>> > >> >>
>> > >> >>
>> > >> >> Hi everyone!
>> > >> >>
>> > >> >> We wanted to migrate the examples from the core repository to a
>> new
>> > >> Beam community examples repository. As the number of examples grow,
>> it
>> > >> makes sense to modularize and decouple the core functionality from
>> the
>> > >> examples.
>> > >> >>
>> > >> >> We will also create some guidelines with the best practices for
>> new
>> > >> examples to be submitted.
>> > >> >>
>> > >> >> For more details, feel free to take a look and comment on the
>> proposal.
>> > >> >>
>> > >> >> Cheers,
>> > >> >> David
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >>
>> > >>
>> > >
>> > >
>> >
>>
> --
Got feedback? go/pabloem-feedback
Re: Community Examples Repository
Posted by Ankur Goenka <go...@google.com>.
I like he initiative but I feel that fragmenting the codebase will make it
harder to discover examples. Having examples in a separate repo makes it
easier to forget that examples should get the same love as the rest of the
codebase.
The other challenge is the tooling and integration which is harder with
multiple repo.
It makes sense to isolate the examples and make them more obvious.
A sub project of examples as mentioned in the discussion might be
sufficient without having much overhead.
Thanks,
Ankur
On Thu, Aug 2, 2018 at 10:52 AM Kai Jiang <ji...@gmail.com> wrote:
> Agreed with Rui. We could also add more SQL examples (like, different IOs
> ) for everyone to get started with.
>
> Best,
> Kai
>
> On 2018/08/02 17:40:32, Rui Wang <ru...@google.com> wrote:
> > I might miss it: are examples to be moved including those which are not
> > under example/? For example there are some BeamSQL examples in
> > org/apache/beam/sdk/extensions/sql/example
> > <
> https://github.com/apache/beam/tree/master/sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/example
> >
> > .
> >
> >
> > It's better to keep BeamSQL examples in where it is because related API
> > might still change.
> >
> > -Rui
> >
> > On Thu, Aug 2, 2018 at 8:58 AM Ahmet Altay <al...@google.com> wrote:
> >
> > > Robert, I agree with you in general. However there is also a second
> > > motivation. There is an increase in new PRs that are coming to add new
> > > examples. This is great however the core code (including
> distributions) is
> > > not a great place to host such examples. An examples repo would help in
> > > this case. It could also serve as an entry point for new contributors.
> > >
> > >
> > >
> > > On Thu, Aug 2, 2018 at 12:40 AM, Robert Bradshaw <ro...@google.com>
> > > wrote:
> > >
> > >> I have to admit I'm generally -1 on moving examples to a separate
> > >> repository. In particular, I think it would actually inhibit the
> > >> stated goals of increasing visibility and better keeping them up to
> > >> date, and for all the reasons we just migrated the beam-site directory
> > >> in. It seems the primary motivation is that it's difficult in Java to
> > >> have a portion of the repo that depends on another as if it were
> > >> "external" (i.e. the way others would use Beam) rather than being a
> > >> sub-project of Beam. Is this not doable?
> > >> On Wed, Aug 1, 2018 at 10:59 PM Charles Chen <cc...@google.com> wrote:
> > >> >
> > >> > I would also prefer that examples be linked to releases so that we
> can
> > >> build and test them during development; i.e. if your commit breaks
> > >> wordcount, we want to know right away so we can revert. Perhaps we
> can
> > >> keep these in the repo but more clearly modularize the artifacts we
> release?
> > >> >
> > >> > For the Python SDK, if we separate this out in any way, there is the
> > >> separate issue of dealing with namespace packages (which are kind of
> broken
> > >> and poorly supported:
> > >> https://github.com/pypa/python-packaging-user-guide/issues/265), if
> we
> > >> want to keep the examples under the apache_beam.examples module
> path. See
> > >> also
> https://packaging.python.org/guides/packaging-namespace-packages/.
> > >> >
> > >> > On Wed, Aug 1, 2018 at 9:29 PM jb@nanthrax.net <jb...@nanthrax.net>
> wrote:
> > >> >>
> > >> >> Hi,
> > >> >>
> > >> >> I don't have problem to move the examples in a dedicated
> repository.
> > >> However, IMHO, we have to:
> > >> >>
> > >> >> 1. Keep a build of examples linked to latest core release/SNAPSHOT
> > >> >> 2. Include the examples in the distribution (convenient for the
> users)
> > >> >>
> > >> >> On another topic, I think it would be better to avoid usage of
> Google
> > >> Doc for such kind of discussion and directly share on the mailing
> list (at
> > >> least a summary/light details).
> > >> >>
> > >> >> Regards
> > >> >> JB
> > >> >>
> > >> >> On Thursday, August 02, 2018 00:12 CEST, David Cavazos <
> > >> dcavazos@google.com> wrote:
> > >> >>
> > >> >>
> > >> >> Hi everyone!
> > >> >>
> > >> >> We wanted to migrate the examples from the core repository to a new
> > >> Beam community examples repository. As the number of examples grow, it
> > >> makes sense to modularize and decouple the core functionality from the
> > >> examples.
> > >> >>
> > >> >> We will also create some guidelines with the best practices for new
> > >> examples to be submitted.
> > >> >>
> > >> >> For more details, feel free to take a look and comment on the
> proposal.
> > >> >>
> > >> >> Cheers,
> > >> >> David
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >>
> > >
> > >
> >
>
Re: Community Examples Repository
Posted by Kai Jiang <ji...@gmail.com>.
Agreed with Rui. We could also add more SQL examples (like, different IOs ) for everyone to get started with.
Best,
Kai
On 2018/08/02 17:40:32, Rui Wang <ru...@google.com> wrote:
> I might miss it: are examples to be moved including those which are not
> under example/? For example there are some BeamSQL examples in
> org/apache/beam/sdk/extensions/sql/example
> <https://github.com/apache/beam/tree/master/sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/example>
> .
>
>
> It's better to keep BeamSQL examples in where it is because related API
> might still change.
>
> -Rui
>
> On Thu, Aug 2, 2018 at 8:58 AM Ahmet Altay <al...@google.com> wrote:
>
> > Robert, I agree with you in general. However there is also a second
> > motivation. There is an increase in new PRs that are coming to add new
> > examples. This is great however the core code (including distributions) is
> > not a great place to host such examples. An examples repo would help in
> > this case. It could also serve as an entry point for new contributors.
> >
> >
> >
> > On Thu, Aug 2, 2018 at 12:40 AM, Robert Bradshaw <ro...@google.com>
> > wrote:
> >
> >> I have to admit I'm generally -1 on moving examples to a separate
> >> repository. In particular, I think it would actually inhibit the
> >> stated goals of increasing visibility and better keeping them up to
> >> date, and for all the reasons we just migrated the beam-site directory
> >> in. It seems the primary motivation is that it's difficult in Java to
> >> have a portion of the repo that depends on another as if it were
> >> "external" (i.e. the way others would use Beam) rather than being a
> >> sub-project of Beam. Is this not doable?
> >> On Wed, Aug 1, 2018 at 10:59 PM Charles Chen <cc...@google.com> wrote:
> >> >
> >> > I would also prefer that examples be linked to releases so that we can
> >> build and test them during development; i.e. if your commit breaks
> >> wordcount, we want to know right away so we can revert. Perhaps we can
> >> keep these in the repo but more clearly modularize the artifacts we release?
> >> >
> >> > For the Python SDK, if we separate this out in any way, there is the
> >> separate issue of dealing with namespace packages (which are kind of broken
> >> and poorly supported:
> >> https://github.com/pypa/python-packaging-user-guide/issues/265), if we
> >> want to keep the examples under the apache_beam.examples module path. See
> >> also https://packaging.python.org/guides/packaging-namespace-packages/.
> >> >
> >> > On Wed, Aug 1, 2018 at 9:29 PM jb@nanthrax.net <jb...@nanthrax.net> wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> I don't have problem to move the examples in a dedicated repository.
> >> However, IMHO, we have to:
> >> >>
> >> >> 1. Keep a build of examples linked to latest core release/SNAPSHOT
> >> >> 2. Include the examples in the distribution (convenient for the users)
> >> >>
> >> >> On another topic, I think it would be better to avoid usage of Google
> >> Doc for such kind of discussion and directly share on the mailing list (at
> >> least a summary/light details).
> >> >>
> >> >> Regards
> >> >> JB
> >> >>
> >> >> On Thursday, August 02, 2018 00:12 CEST, David Cavazos <
> >> dcavazos@google.com> wrote:
> >> >>
> >> >>
> >> >> Hi everyone!
> >> >>
> >> >> We wanted to migrate the examples from the core repository to a new
> >> Beam community examples repository. As the number of examples grow, it
> >> makes sense to modularize and decouple the core functionality from the
> >> examples.
> >> >>
> >> >> We will also create some guidelines with the best practices for new
> >> examples to be submitted.
> >> >>
> >> >> For more details, feel free to take a look and comment on the proposal.
> >> >>
> >> >> Cheers,
> >> >> David
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >
> >
>
Re: Community Examples Repository
Posted by Rui Wang <ru...@google.com>.
I might miss it: are examples to be moved including those which are not
under example/? For example there are some BeamSQL examples in
org/apache/beam/sdk/extensions/sql/example
<https://github.com/apache/beam/tree/master/sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/example>
.
It's better to keep BeamSQL examples in where it is because related API
might still change.
-Rui
On Thu, Aug 2, 2018 at 8:58 AM Ahmet Altay <al...@google.com> wrote:
> Robert, I agree with you in general. However there is also a second
> motivation. There is an increase in new PRs that are coming to add new
> examples. This is great however the core code (including distributions) is
> not a great place to host such examples. An examples repo would help in
> this case. It could also serve as an entry point for new contributors.
>
>
>
> On Thu, Aug 2, 2018 at 12:40 AM, Robert Bradshaw <ro...@google.com>
> wrote:
>
>> I have to admit I'm generally -1 on moving examples to a separate
>> repository. In particular, I think it would actually inhibit the
>> stated goals of increasing visibility and better keeping them up to
>> date, and for all the reasons we just migrated the beam-site directory
>> in. It seems the primary motivation is that it's difficult in Java to
>> have a portion of the repo that depends on another as if it were
>> "external" (i.e. the way others would use Beam) rather than being a
>> sub-project of Beam. Is this not doable?
>> On Wed, Aug 1, 2018 at 10:59 PM Charles Chen <cc...@google.com> wrote:
>> >
>> > I would also prefer that examples be linked to releases so that we can
>> build and test them during development; i.e. if your commit breaks
>> wordcount, we want to know right away so we can revert. Perhaps we can
>> keep these in the repo but more clearly modularize the artifacts we release?
>> >
>> > For the Python SDK, if we separate this out in any way, there is the
>> separate issue of dealing with namespace packages (which are kind of broken
>> and poorly supported:
>> https://github.com/pypa/python-packaging-user-guide/issues/265), if we
>> want to keep the examples under the apache_beam.examples module path. See
>> also https://packaging.python.org/guides/packaging-namespace-packages/.
>> >
>> > On Wed, Aug 1, 2018 at 9:29 PM jb@nanthrax.net <jb...@nanthrax.net> wrote:
>> >>
>> >> Hi,
>> >>
>> >> I don't have problem to move the examples in a dedicated repository.
>> However, IMHO, we have to:
>> >>
>> >> 1. Keep a build of examples linked to latest core release/SNAPSHOT
>> >> 2. Include the examples in the distribution (convenient for the users)
>> >>
>> >> On another topic, I think it would be better to avoid usage of Google
>> Doc for such kind of discussion and directly share on the mailing list (at
>> least a summary/light details).
>> >>
>> >> Regards
>> >> JB
>> >>
>> >> On Thursday, August 02, 2018 00:12 CEST, David Cavazos <
>> dcavazos@google.com> wrote:
>> >>
>> >>
>> >> Hi everyone!
>> >>
>> >> We wanted to migrate the examples from the core repository to a new
>> Beam community examples repository. As the number of examples grow, it
>> makes sense to modularize and decouple the core functionality from the
>> examples.
>> >>
>> >> We will also create some guidelines with the best practices for new
>> examples to be submitted.
>> >>
>> >> For more details, feel free to take a look and comment on the proposal.
>> >>
>> >> Cheers,
>> >> David
>> >>
>> >>
>> >>
>> >>
>> >>
>>
>
>
Re: Community Examples Repository
Posted by Ahmet Altay <al...@google.com>.
Robert, I agree with you in general. However there is also a second
motivation. There is an increase in new PRs that are coming to add new
examples. This is great however the core code (including distributions) is
not a great place to host such examples. An examples repo would help in
this case. It could also serve as an entry point for new contributors.
On Thu, Aug 2, 2018 at 12:40 AM, Robert Bradshaw <ro...@google.com>
wrote:
> I have to admit I'm generally -1 on moving examples to a separate
> repository. In particular, I think it would actually inhibit the
> stated goals of increasing visibility and better keeping them up to
> date, and for all the reasons we just migrated the beam-site directory
> in. It seems the primary motivation is that it's difficult in Java to
> have a portion of the repo that depends on another as if it were
> "external" (i.e. the way others would use Beam) rather than being a
> sub-project of Beam. Is this not doable?
> On Wed, Aug 1, 2018 at 10:59 PM Charles Chen <cc...@google.com> wrote:
> >
> > I would also prefer that examples be linked to releases so that we can
> build and test them during development; i.e. if your commit breaks
> wordcount, we want to know right away so we can revert. Perhaps we can
> keep these in the repo but more clearly modularize the artifacts we release?
> >
> > For the Python SDK, if we separate this out in any way, there is the
> separate issue of dealing with namespace packages (which are kind of broken
> and poorly supported: https://github.com/pypa/python-packaging-user-guide/
> issues/265), if we want to keep the examples under the
> apache_beam.examples module path. See also https://packaging.python.org/
> guides/packaging-namespace-packages/.
> >
> > On Wed, Aug 1, 2018 at 9:29 PM jb@nanthrax.net <jb...@nanthrax.net> wrote:
> >>
> >> Hi,
> >>
> >> I don't have problem to move the examples in a dedicated repository.
> However, IMHO, we have to:
> >>
> >> 1. Keep a build of examples linked to latest core release/SNAPSHOT
> >> 2. Include the examples in the distribution (convenient for the users)
> >>
> >> On another topic, I think it would be better to avoid usage of Google
> Doc for such kind of discussion and directly share on the mailing list (at
> least a summary/light details).
> >>
> >> Regards
> >> JB
> >>
> >> On Thursday, August 02, 2018 00:12 CEST, David Cavazos <
> dcavazos@google.com> wrote:
> >>
> >>
> >> Hi everyone!
> >>
> >> We wanted to migrate the examples from the core repository to a new
> Beam community examples repository. As the number of examples grow, it
> makes sense to modularize and decouple the core functionality from the
> examples.
> >>
> >> We will also create some guidelines with the best practices for new
> examples to be submitted.
> >>
> >> For more details, feel free to take a look and comment on the proposal.
> >>
> >> Cheers,
> >> David
> >>
> >>
> >>
> >>
> >>
>
Re: Community Examples Repository
Posted by Robert Bradshaw <ro...@google.com>.
I have to admit I'm generally -1 on moving examples to a separate
repository. In particular, I think it would actually inhibit the
stated goals of increasing visibility and better keeping them up to
date, and for all the reasons we just migrated the beam-site directory
in. It seems the primary motivation is that it's difficult in Java to
have a portion of the repo that depends on another as if it were
"external" (i.e. the way others would use Beam) rather than being a
sub-project of Beam. Is this not doable?
On Wed, Aug 1, 2018 at 10:59 PM Charles Chen <cc...@google.com> wrote:
>
> I would also prefer that examples be linked to releases so that we can build and test them during development; i.e. if your commit breaks wordcount, we want to know right away so we can revert. Perhaps we can keep these in the repo but more clearly modularize the artifacts we release?
>
> For the Python SDK, if we separate this out in any way, there is the separate issue of dealing with namespace packages (which are kind of broken and poorly supported: https://github.com/pypa/python-packaging-user-guide/issues/265), if we want to keep the examples under the apache_beam.examples module path. See also https://packaging.python.org/guides/packaging-namespace-packages/.
>
> On Wed, Aug 1, 2018 at 9:29 PM jb@nanthrax.net <jb...@nanthrax.net> wrote:
>>
>> Hi,
>>
>> I don't have problem to move the examples in a dedicated repository. However, IMHO, we have to:
>>
>> 1. Keep a build of examples linked to latest core release/SNAPSHOT
>> 2. Include the examples in the distribution (convenient for the users)
>>
>> On another topic, I think it would be better to avoid usage of Google Doc for such kind of discussion and directly share on the mailing list (at least a summary/light details).
>>
>> Regards
>> JB
>>
>> On Thursday, August 02, 2018 00:12 CEST, David Cavazos <dc...@google.com> wrote:
>>
>>
>> Hi everyone!
>>
>> We wanted to migrate the examples from the core repository to a new Beam community examples repository. As the number of examples grow, it makes sense to modularize and decouple the core functionality from the examples.
>>
>> We will also create some guidelines with the best practices for new examples to be submitted.
>>
>> For more details, feel free to take a look and comment on the proposal.
>>
>> Cheers,
>> David
>>
>>
>>
>>
>>
Re: Community Examples Repository
Posted by Charles Chen <cc...@google.com>.
I would also prefer that examples be linked to releases so that we can
build and test them during development; i.e. if your commit breaks
wordcount, we want to know right away so we can revert. Perhaps we can
keep these in the repo but more clearly modularize the artifacts we release?
For the Python SDK, if we separate this out in any way, there is the
separate issue of dealing with namespace packages (which are kind of broken
and poorly supported:
https://github.com/pypa/python-packaging-user-guide/issues/265), if we want
to keep the examples under the apache_beam.examples module path. See also
https://packaging.python.org/guides/packaging-namespace-packages/.
On Wed, Aug 1, 2018 at 9:29 PM jb@nanthrax.net <jb...@nanthrax.net> wrote:
> Hi,
>
> I don't have problem to move the examples in a dedicated repository.
> However, IMHO, we have to:
>
> 1. Keep a build of examples linked to latest core release/SNAPSHOT
> 2. Include the examples in the distribution (convenient for the users)
>
> On another topic, I think it would be better to avoid usage of Google Doc
> for such kind of discussion and directly share on the mailing list (at
> least a summary/light details).
>
> Regards
> JB
>
> On Thursday, August 02, 2018 00:12 CEST, David Cavazos <
> dcavazos@google.com> wrote:
>
>
> Hi everyone!
>
> We wanted to migrate the examples from the core repository to a new Beam
> community examples repository. As the number of examples grow, it makes
> sense to modularize and decouple the core functionality from the examples.
>
> We will also create some guidelines with the best practices for new
> examples to be submitted.
>
> For more details, feel free to take a look and comment on the proposal
> <https://docs.google.com/document/d/1vhcKJlP0qH1C7NZPDjohT2PUbOD-k71avv1CjEYapdw/edit?usp=sharing>
> .
>
> Cheers,
> David
>
>
>
>
>
Re: Community Examples Repository
Posted by .
Hi,
I don't have problem to move the examples in a dedicated repository. However, IMHO, we have to:
1. Keep a build of examples linked to latest core release/SNAPSHOT
2. Include the examples in the distribution (convenient for the users)
On another topic, I think it would be better to avoid usage of Google Doc for such kind of discussion and directly share on the mailing list (at least a summary/light details).
Regards
JB
On Thursday, August 02, 2018 00:12 CEST, David Cavazos <dc...@google.com> wrote:
Hi everyone! We wanted to migrate the examples from the core repository to a new Beam community examples repository. As the number of examples grow, it makes sense to modularize and decouple the core functionality from the examples. We will also create some guidelines with the best practices for new examples to be submitted. For more details, feel free to take a look and comment on the proposal. Cheers,David