Best Regards,
Strahil Nikolov
On Tue, Feb 2, 2021 at 14:00, gluster-devel-request@xxxxxxxxxxx<gluster-devel-request@xxxxxxxxxxx> wrote:Send Gluster-devel mailing list submissions toTo subscribe or unsubscribe via the World Wide Web, visitor, via email, send a message with subject or body 'help' toYou can reach the person managing the list atWhen replying, please edit your Subject line so it is more specificthan "Re: Contents of Gluster-devel digest..."Today's Topics:1. Archiving old projects (Michael Scherer)2. Re: Archiving old projects (sankarshan)----------------------------------------------------------------------Message: 1Date: Mon, 01 Feb 2021 13:55:46 +0100From: Michael Scherer <mscherer@xxxxxxxxxx>To: Gluster Devel <gluster-devel@xxxxxxxxxxx>Subject: [Gluster-devel] Archiving old projectsMessage-ID:Content-Type: text/plain; charset="utf-8"Hi,So, it is this time of the year again, do we want to archive the olderprojects on github ?I already archived:- gluster/cockpit-gluster (listed as unmaintained)- gluster/gluster-plus-one-scale (just a readme)- gluster/samba-glusterfs (listed as unmaintained)- gluster/anteater (empty, except 1 bug to say to remove it)Unless people say "no" this week, I propose thoses :I can't find my last mail, but that's everything that wasn't changed in2019 nor 2020. Repo who are used just for bug tracking are ok.--Michael Scherer / He/Il/Er/?lSysadmin, Community Infrastructure-------------- next part --------------A non-text attachment was scrubbed...Name: signature.ascType: application/pgp-signatureSize: 836 bytesDesc: This is a digitally signed message partURL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20210201/3e2b73a0/attachment-0001.sig>------------------------------Message: 2Date: Mon, 1 Feb 2021 18:40:06 +0530From: sankarshan <sankarshan@xxxxxxxxx>To: Michael Scherer <mscherer@xxxxxxxxxx>Cc: Gluster Devel <gluster-devel@xxxxxxxxxxx>Subject: Re: Archiving old projectsMessage-ID:<CAAwt65D1F733SXej3-w5C5s89PTZbneG5ugchEq=wG9LzADGSA@xxxxxxxxxxxxxx>Content-Type: text/plain; charset="UTF-8"Seems reasonable to do this spring cleaning. I'd like to suggest thatwe add this as an agenda topic to an upcoming meeting and have it onrecord prior to moving ahead? Do you mind terribly to track this viaan issue which can be referenced in the meeting?On Mon, 1 Feb 2021 at 18:26, Michael Scherer <mscherer@xxxxxxxxxx> wrote:>> Hi,>> So, it is this time of the year again, do we want to archive the older> projects on github ?>> I already archived:>> - gluster/cockpit-gluster (listed as unmaintained)> - gluster/gluster-plus-one-scale (just a readme)> - gluster/samba-glusterfs (listed as unmaintained)> - gluster/anteater (empty, except 1 bug to say to remove it)>>>> Unless people say "no" this week, I propose thoses :>> I can't find my last mail, but that's everything that wasn't changed in> 2019 nor 2020. Repo who are used just for bug tracking are ok.>>>> --> Michael Scherer / He/Il/Er/?l> Sysadmin, Community Infrastructure>>>> ------->> Community Meeting Calendar:> Schedule -> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC> Bridge: https://meet.google.com/cpu-eiue-hvk>> Gluster-devel mailing list>--sankarshan@xxxxxxxxx | TZ: UTC+0530 | +91 99606 03294 (voice/messaging)kadalu.io : Making it easy to provision storage in k8s!------------------------------_______________________________________________Gluster-devel mailing listEnd of Gluster-devel Digest, Vol 83, Issue 1********************************************
------- Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
