[feedhenry-dev] RFC: MCP-standalone Release Process

Gerard Ryan gryan at redhat.com
Fri Oct 27 07:35:13 UTC 2017

Leigh Griffin <lgriffin at redhat.com> writes:

> Just want to throw it out there that the XML Licenser is going to be a
> requirement here. It's not a painful step in the above that you described
> but it's a step nonetheless. So if our code is anything outside of Java
> (maven based) or Node.js we might need to consider building a tool to
> create the licensing information or reach out wider to find a team already
> in flight on it.

Would that just be needed for the eventual Red Hat productization of it,
or is it also needed for the open source releases here?

In any case, I'd expect that other projects that Red Hat productizes
downstream, that are also Go projects, would also have this requirement,
right (e.g. OpenShift)? Whatever they're using, would ideally be reused
here, rather than each of us creating our own way of doing it.

More information about the feedhenry-dev mailing list