[Pulp-dev] Plugin teams problem statement
rchan at redhat.com
Tue Oct 24 14:44:12 UTC 2017
Looks good. I did add a statement between the "<>" in the next
sentence. Please feel free to update - just trying to help articulate
the un-stated for clarity and evaluation of the proposed solution.
Without clear ownership, feature implementation, bugfixes, and code
review all become more difficult because< it is unclear who needs to
be involved in the resolution of concerns and who has the final say in
On Tue, Oct 24, 2017 at 9:43 AM, David Davis <daviddavis at redhat.com> wrote:
> Thanks Robin. I’ve updated the PUP based on your feedback and with the help
> of some other folks on IRC. Please feel free to look it over again.
> I’ll wait until about Monday October 30th before I proceed with working on
> the rest of the PUP.
> On Mon, Oct 23, 2017 at 4:22 PM, Robin Chan <rchan at redhat.com> wrote:
>> Hi David,
>> I've added some comments - trying to mostly articulate what I heard
>> you guys saying last week. I agree this is a good summary, just would
>> like to work on stating the obvious a little more obviously.
>> My comments are in red (or whatever this weird muddy pink color is.
>> Thanks for getting us started on this.
>> On Thu, Oct 19, 2017 at 4:54 PM, David Davis <daviddavis at redhat.com>
>> > Last week we talked about forming teams for each Pulp plugin and I
>> > wanted to
>> > open up a community discussion around that idea. @bmbouter and I have
>> > come
>> > up with a proposed problem statement  to kick off this discussion.
>> > We’re looking for feedback from everyone so please feel free to check
>> > the
>> > statement out and make edits. Or respond to this email with any thoughts
>> > about it.
>> > After about a week or so, I’ll try to create a PUP based on any feedback
>> > we
>> > get.
>> >  http://pad-theforeman.rhcloud.com/p/pulp-plugin-pup
>> > David
>> > _______________________________________________
>> > Pulp-dev mailing list
>> > Pulp-dev at redhat.com
>> > https://www.redhat.com/mailman/listinfo/pulp-dev
More information about the Pulp-dev