[Pulp-dev] Proposed Update to PUP-4
dawalker at redhat.com
Tue Jul 24 17:55:10 UTC 2018
Personally, I think those are important suggestions for ensuring a
welcoming environment across the Pulp landscape, but I would prefer that
this update focus on getting the CoC itself publicly discoverable for the
first time without further delay <Display>. I welcome you to submit a PR
with another update, even at the same time, that deals with requirements
for plugin writers <Enforcement>.
If others would prefer this to be bundled, we can work together on an
Associate Software Engineer
On Tue, Jul 24, 2018 at 1:20 PM, Austin Macdonald <amacdona at redhat.com>
> On Tue, Jul 24, 2018 at 12:20 PM, Austin Macdonald <amacdona at redhat.com>
>> I'm not sure how to phrase this, but maybe something like "For a plugin
>> to be officially recognized by the Pulp community*, it must adopt this code
>> of conduct in its entirety, though it is their prerogative to extend it."
>> * Official recognition is not official endorsement, but does include some
>> 1. ability to track plugin issues on the Pulp redmine
>> 2. plugin source may live in the Pulp org on github
>> 3. Plugin will be listed on the Plugin table
>> ^ This could be a separate PUP revision, if preferred.
>> On Tue, Jul 24, 2018 at 11:37 AM, Dana Walker <dawalker at redhat.com>
>>> A PR  is up with a proposed update to PUP-4: Code of Conduct .
>>> The proposal changes the details of where the Code of Conduct is to be
>>> Please review and provide any comments, suggestions, and +/- 1's to the
>>> proposed changes by Sunday August 5.
>>>  https://github.com/pulp/pups/pull/12
>>>  https://github.com/pulp/pups/blob/master/pup-0004.md
>>> Dana Walker
>>> Associate Software Engineer
>>> Red Hat
>>> Pulp-dev mailing list
>>> Pulp-dev at redhat.com
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev