[prev in list] [next in list] [prev in thread] [next in thread]
List: gluster-devel
Subject: Re: [Gluster-devel] Following up on the "Github teams/repo cleanup"
From: Sankarshan Mukhopadhyay <sankarshan.mukhopadhyay () gmail ! com>
Date: 2019-03-28 19:59:14
Message-ID: CAJWA-5YmP+Qs_EOGqKcf-fdDfFHX+fqTu5m3be+VC6R4Y7gzBA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Fri 29 Mar, 2019, 01:04 Vijay Bellur, <vbellur@redhat.com> wrote:
>
>
> On Thu, Mar 28, 2019 at 11:39 AM Sankarshan Mukhopadhyay <
> sankarshan.mukhopadhyay@gmail.com> wrote:
>
>> On Thu, Mar 28, 2019 at 11:34 PM John Strunk <jstrunk@redhat.com> wrote:
>> >
>> > Thanks for bringing this to the list.
>> >
>> > I think this is a good set of guidelines, and we should publicly post
>> and enforce them once agreement is reached.
>> > The integrity of the gluster github org is important for the future of
>> the project.
>> >
>>
>> I agree. And so, I am looking forward to additional
>> individuals/maintainers agreeing to this so that we can codify it
>> under the Gluster.org Github org too.
>>
>
>
> Looks good to me.
>
> While at this, I would also like us to think about evolving some
> guidelines for creating a new repository in the gluster github
> organization. Right now, a bug report does get a new repository created and
> I feel that the process could be a bit more involved to ensure that we
> host projects with the right content in github.
>
The bug ensures that there is a recorded trail for the request. What might
be the additional detail required which can emphasize on greater
involvement? At this point, I don't see many fly-by-night projects. Just
inactive ones and those too for myriad reasons.
>
>
[Attachment #5 (text/html)]
<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Fri 29 Mar, 2019, 01:04 Vijay Bellur, <<a \
href="mailto:vbellur@redhat.com">vbellur@redhat.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div \
dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On \
Thu, Mar 28, 2019 at 11:39 AM Sankarshan Mukhopadhyay <<a \
href="mailto:sankarshan.mukhopadhyay@gmail.com" target="_blank" \
rel="noreferrer">sankarshan.mukhopadhyay@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Mar 28, 2019 \
at 11:34 PM John Strunk <<a href="mailto:jstrunk@redhat.com" target="_blank" \
rel="noreferrer">jstrunk@redhat.com</a>> wrote:<br>><br>> Thanks for \
bringing this to the list.<br>><br>> I think this is a good set of guidelines, \
and we should publicly post and enforce them once agreement is reached.<br>> The \
integrity of the gluster github org is important for the future of the \
project.<br>><br> <br>I agree. And so, I am looking forward to \
additional<br>individuals/maintainers agreeing to this so that we can codify \
it<br>under the Gluster.org Github org \
too.<br></blockquote><div><br></div><div><br></div><div>Looks good to me. \
</div><div><br></div><div>While at this, I would also like us to think about \
evolving some guidelines for creating a new repository in the gluster github \
organization. Right now, a bug report does get a new repository created and I feel \
that the process could be a bit more involved to ensure that we host projects with \
the right content in github.</div></div></div></blockquote></div></div><div \
dir="auto"><br></div><div dir="auto">The bug ensures that there is a recorded trail \
for the request. What might be the additional detail required which can emphasize on \
greater involvement? At this point, I don't see many fly-by-night projects. Just \
inactive ones and those too for myriad reasons.</div><div dir="auto"><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div \
class="gmail_quote"><div></div></div></div></blockquote></div></div><div \
dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div \
class="gmail_quote"><div><br></div></div></div> </blockquote></div></div></div>
_______________________________________________
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic