Re: Charm Store Policy Update: Propritary applications usage of Terms and Resources

It can probably be there as a recommendation until 2.0 lands, where it can be made a requirement. On 07/05/2016 09:17 AM, Charles Butler wrote: This has been on the list for > 1 month with a little activity. I'm poking this thread to see if there are any remaining outliers that wish to chime

Re: Charm Store Policy Update: Propritary applications usage of Terms and Resources

This has been on the list for > 1 month with a little activity. I'm poking this thread to see if there are any remaining outliers that wish to chime in. Just a reminder: we have an open issue on the documentation to make this formally accepted into the charm store policy. This will affect any

Re: Charm Store Policy Update: Propritary applications usage of Terms and Resources

On 27/05/16 01:00, Antonio Rosales wrote: > I think most software require acceptance of the License. Perhaps the > point here is weather the acceptance has to be active or passive. If > this is the intent should the policy state: Any software which > requires active user acceptance of a license or

Re: Charm Store Policy Update: Propritary applications usage of Terms and Resources

I don't think this needs to be scoped to just proprietary charms. It can be better scoped to: Any software which requires acceptance of a license or EULA has to have that as a term on the charm Any software which installs components from outside of a distributions archive needs to represent that

Re: Charm Store Policy Update: Propritary applications usage of Terms and Resources

I'm +1 to requiring terms and resources for prop. applications. This will effectively funnel our new onboarding efforts of these vendors into the juju 2.0 path, and start them off using best practices - which will really lend a hand to the robustness of their deployment (see: behind the corp

Re: Charm Store Policy Update: Propritary applications usage of Terms and Resources

On 26/05/16 00:21, Tom Barber wrote: > > I think Terms are good but terms for open source is overkill. > > For example if I apt install openjdk I wouldn't accept any terms > during the install process, but if I apt install oracle-jdk I would. > > Agreed, no acknowledgement of terms should be

Re: Charm Store Policy Update: Propritary applications usage of Terms and Resources

I think Terms are good but terms for open source is overkill. For example if I apt install openjdk I wouldn't accept any terms during the install process, but if I apt install oracle-jdk I would. Tom On 26 May 2016 00:18, "Antonio Rosales" wrote: > Hello, > > As

Charm Store Policy Update: Propritary applications usage of Terms and Resources

Hello, As we close in on Juju 2.0 I would like to propose an update the Charm Store policy to require Charms deploying proprietary applications to use Terms and Resources (where applicable). Terms help Juju users understand and accept the EULA so they may properly deploy the software and adhere