Open Stack

So far, this discussion has taken a path similar to the review guide that
everyone ignores. Whatever we decide, let's clearly advertise and enforce
it.

On Tue, Feb 24, 2015 at 2:26 PM, Nick Chase <nchase at mirantis.com> wrote:

>
> On 2/23/2015 9:56 PM, sean roberts wrote:
>
>> I like the idea in general. It's could help with individual momentum for
>> new contributors. The idea to me says, we create a sense of belonging and a
>> path to learning more step by step.
>>
>> If we committed to pushing patches faster, and then created more bugs,
>> then I would say that each bug creating patch would need to be owned by the
>> patch approver and the patch contributor. The patch approver in the role of
>> a mentor.
>>
>
> I like the idea in principle.  Is there a way to mark bugs as "available"
> even if they're assigned to someone?  Maybe call them "cleanup" bugs or
> something, and have a way that people can claim them to help out?
>
> ----  Nick
>
>
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20150224/40fbe89a/attachment.html>