[Gluster-devel] Following up on the "Github teams/repo cleanup"

[Vijay Bellur]

On Thu, Mar 28, 2019 at 11:39 AM Sankarshan Mukhopadhyay <
sankarshan.mukhopadhyay at gmail.com> wrote:

> On Thu, Mar 28, 2019 at 11:34 PM John Strunk <jstrunk at 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.

Thanks,
Vijay

>
> >
> > On Wed, Mar 27, 2019 at 10:21 PM Sankarshan Mukhopadhyay <
> sankarshan.mukhopadhyay at gmail.com> wrote:
> >>
> >> The one at <
> https://lists.gluster.org/pipermail/gluster-infra/2018-June/004589.html>
> >> I am not sure if the proposal from Michael was agreed to separately
> >> and it was done. Also, do we want to do this periodically?
> >>
> >> Feedback is appreciated.
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20190328/ce294fa3/attachment.html>