OK. Bringing an important update on licensing to this thread for
consideration. Discussion on https://issues.apache.org/jira/browse/LEGAL-601
has concluded with key takeaways. These are things that were already true
and people who are good at this stuff already may know, but I'm just going
to say
I always get mixed up myself. The policies are at
https://www.apache.org/legal/src-headers.html#notice and there's some step
by step at https://infra.apache.org/licensing-howto.html
TL;DR the contents should be like so:
Apache Beam
Copyright [2022-] The Apache Software Foundation
I like the goal: for things where the build has extra setup, have an
example that is fully functional on its own. There is of course the problem
of "where does it end?" since this is infinity things.
The other piece is that a user wanting to know some of these bits may be
past the "clone and go"
Hi,
This is great!
What do folks think about also having a less minimal set of starters? For
Java I am thinking about protobuf / autovalue. For Python maybe an
opinionated setup with tox etc... Again this would just contain 'hello'
world samples to get folks going.
Regards
Reza
On Wed, 9 Feb
Based on discussion on https://issues.apache.org/jira/browse/LEGAL-601 I
think it will be simplest to license it under ASL2 and include a NOTICE
file. The user will be free to "clone and go".
I would bring these points back to the dev list:
- ASL2 is what people expect from an ASF project, so
And I've created the repos just now.
Kenn
On Mon, Feb 7, 2022 at 10:39 AM Kenneth Knowles wrote:
> Legal question asked at https://issues.apache.org/jira/browse/LEGAL-601
>
> Kenn
>
> On Fri, Feb 4, 2022 at 7:58 AM Danny McCormick
> wrote:
>
>> Sure - I'm happy to help out with the Actions
Legal question asked at https://issues.apache.org/jira/browse/LEGAL-601
Kenn
On Fri, Feb 4, 2022 at 7:58 AM Danny McCormick
wrote:
> Sure - I'm happy to help out with the Actions setup (and/or with the Go
> template). I will say though, the Actions config should be pretty darn
> simple for
I'm convinced on all points. My main motivation was to keep it simple. But
of course we should keep it simple for users, not us :-)
I can take on the task of asking about MIT license and requesting the repos
be created. Not sure if it needs my level of privileges but I'm happy to do
it anyhow.
+1 to starters for Kotlin and Scala too. Scala at least as sbt as the
idiomatic build tool (as of like 10 years ago...) so a fully idiomatic repo
would look different and be helpful.
On Tue, Jan 25, 2022 at 10:54 AM David Cavazos wrote:
> We could also have Kotlin and Scala starter projects. I
I want to clarify one thing: I am not certain the requirement of ASL2
applies to example code snippets. I am also not sure if it makes a material
difference to users. I _am_ sure we would need to deal with some process to
use something other than ASL2, so I'd rather not.
Kenn
On Tue, Jan 18,
Agree with Luke here. "Just git clone and go" is a big part of it.
But also the answer to "I simply don't know what one would put in a Python
repo than, other than a bare setup.py that lists a dependency on
apache_beam" is answered by David's initial email and his repo, namely:
- GitHub Actions
11 matches
Mail list logo
