Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

Thanks @asmacdo. I made the PRs and linked to them in a comment on that issue: https://pulp.plan.io/issues/3734#note-4 If anyone is able to go through and lgtm and possibly merge that would be good. On Mon, Jun 4, 2018 at 9:30 AM, Austin Macdonald wrote: > Ive created an issue to track this wo

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

Ive created an issue to track this work. https://pulp.plan.io/issues/3734 On Mon, Jun 4, 2018 at 9:25 AM, Brian Bouterse wrote: > With no blocking votes, one +0,and five +1's this pup has passed. Thank > you to everyone who contributed to this PUP, especially @richardfontana. > > As a next step,

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

With no blocking votes, one +0,and five +1's this pup has passed. Thank you to everyone who contributed to this PUP, especially @richardfontana. As a next step, we need to add the COMMITMENT file to all the right repos. If anyone wants to do that feel free and maybe reply on-thread, otherwise I'll

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

+1 Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Fri, Jun 1, 2018 at 6:11 PM, Austin Macdonald wrote: > +1 > > On Fri, Jun 1, 2018 at 8:54 AM, Dana Walker wrote: > >> +1 >> >>

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

+1 On Fri, Jun 1, 2018 at 8:54 AM, Dana Walker wrote: > +1 > > Dana Walker > > Associate Software Engineer > > Red Hat > > > > > On Thu, May 31, 2018 at 4:08 PM, Daniel Alley wrote: > >> +0 >> >> On Thu, May 31, 2018 at 3:49 PM, Robin Chan wrote: >

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

+1 Dana Walker Associate Software Engineer Red Hat On Thu, May 31, 2018 at 4:08 PM, Daniel Alley wrote: > +0 > > On Thu, May 31, 2018 at 3:49 PM, Robin Chan wrote: > >> Voting closes June 2nd. >> >> I have read this through and appreciate @richa

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

+0 On Thu, May 31, 2018 at 3:49 PM, Robin Chan wrote: > Voting closes June 2nd. > > I have read this through and appreciate @richardfontana's > response/explanation to questions: https://github.com/pulp/pups/ > pull/9#issuecomment-393317027 > > +1 > > On Wed, May 23, 2018 at 11:29 AM, Dennis Kli

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

Voting closes June 2nd. I have read this through and appreciate @richardfontana's response/explanation to questions: https://github.com/pulp/pups/pull/9#issuecomment-393317027 +1 On Wed, May 23, 2018 at 11:29 AM, Dennis Kliban wrote: > +1 > > On Wed, May 23, 2018 at 10:41 AM, Brian Bouterse >

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

+1 On Wed, May 23, 2018 at 10:41 AM, Brian Bouterse wrote: > Through feedback on the issue and discussion in #pulp-dev, one small > language revision [0] was added to PUP5 [1]. I believe we are ready to call > a vote. > > Voting for PUP5 is open and will close on June 2nd. Please respond with >

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

Through feedback on the issue and discussion in #pulp-dev, one small language revision [0] was added to PUP5 [1]. I believe we are ready to call a vote. Voting for PUP5 is open and will close on June 2nd. Please respond with your vote to this thread if you feel so inclined (lazy consensus). Barrin

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

@ipanova, I think of the core team as only maintaining pulp/pulp and pulp/devel so I limit the scope of this to those repos only. I think pulp_rpm (or any plugin) could adopt the CCRC without a PUP by following the "Displaying the CRCC section

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

Other than the noted point that it takes time, is there any reason why Pulp should stay on the current license instead of moving to GPLv3 (one of the stated alternatives in this PUP)? I don't know much about the differences currently, but it strikes me that our new Pulp 3 using Python 3 would be a

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

*understanding Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, May 14, 2018 at 12:27 PM, Ina Panova wrote: > To make a concrete example to prove my understating: > > Since p

Re: [Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

To make a concrete example to prove my understating: Since pulp_rpm is maintained by core team we could adopt this change, meanwhile pulp_deb is beyond our control and we( core team) cannot enforce or influence this change. Yes? Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc

[Pulp-dev] PUP5 -- Adopting the "Common Cure Rights Commitment" for Pulp Core

A Pulp Update Proposal (PUP) pull request has been opened by the go-to-lawyer for the Pulp community, Richard Fontana. The PUP is PUP5 [0]. I don't want to paraphrase it here, so please read it [0] if you are interested to understand what it does. I am proposing a period of questions/discussion vi