I'm pretty sure that there are no IP-related issues for
Docker build scripts. Since you're not actually distributing
the artifacts, I believe that the existing system (which
includes an implied exempt pre-req on the OS) still works. You
just can't distribute the built artifacts from an Eclipse
Foundation-managed property.
We're just starting with DockerHub as a distribution channel,
so we haven't quite worked out the issues. This is where I can
use your help.
I've secured the "eclipse", "locationtech", and "polarsys"
organizations on DockerHub. I've connected with a few projects
to work with to sort out the issues and questions that need to
be answered.
If you want to participate in this with GeoServer, let me
know.
Wayne
On 11/08/16 12:45 PM, Jim Hughes
wrote:
Hi all,
I'm in the same boat; sorry to miss the meeting.
On the topic of Eclipse build infrastructure, I'd note that
the webmaster team has been fairly responsive to requests
regarding LocationTech HIPP / Nexus concerns. Overall, that
is working ok. Currently, GeoMesa is using the public Travis
CI servers for GitHub commits and PRs. Those builds are slow;
having dedicated Eclipse hardware would be awesome.
As a big stretch, having a cloud which would be used for
integration tests would be nice, but that's likely too big an
ask.
For Docker builds, would all the software included have to
pass the Eclipse IP guidelines? It seems like some of the
pieces of a standard Linux distribution in a Docker might be
GPL. If we can have that in a Docker image, I'd like to ship
a Docker with GeoServer in it...
Cheers,
Jim
On 08/11/2016 12:39 PM, Martin
Lippert wrote:
Hey!
Same here, sorry for missing the call.
Cheers,
Martin
Everyone,
I apologize that I missed the meeting. My
schedule got jumbled up. I will review the notes.
Jay
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
