Updating the repository's actual 'ACTIVE'ness status

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Updating the repository's actual 'ACTIVE'ness status

Amar Tumballi-3
Hi all,

We have 101 repositories in gluster org in github. Only handful of them are being actively managed, and progressing.

After seeing https://github.com/gluster/gluster-kubernetes/issues/644, I feel we should at least keep the status of the project up-to-date in the repository, so the users can move on to other repos if not maintained. Saves time for them, and they wouldn't form a opinion on gluster project. But if they spend time on setting it up, and later find that its not working, and is not maintained, they would feel bad about the overall project itself.

So my request to all repository maintainers are to mark a repository as 'Archived'. And update the README (or description) to reflect the same.

In any case, On April 1st week, we should actively mark them inactive if no activity is found in last 15+ months. For other repos, maintainer's can take appropriate action.

Regards,
Amar


_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: [Gluster-Maintainers] Updating the repository's actual 'ACTIVE'ness status

Aravinda VK-2
I archived the following projects

- gluster/restapi
- gluster/glusterd2
- gluster/gcs
- gluster/gluster-csi-driver
- gluster/gluster-block-restapi
- gluster/python-gluster-mgmt-client

Please let me know if anyone interested to unarchive and maintain any project from the above list.

regards
Aravinda Vishwanathapura

On 25-Mar-2020, at 5:49 PM, Amar Tumballi <[hidden email]> wrote:

Hi all,

We have 101 repositories in gluster org in github. Only handful of them are being actively managed, and progressing.

After seeing https://github.com/gluster/gluster-kubernetes/issues/644, I feel we should at least keep the status of the project up-to-date in the repository, so the users can move on to other repos if not maintained. Saves time for them, and they wouldn't form a opinion on gluster project. But if they spend time on setting it up, and later find that its not working, and is not maintained, they would feel bad about the overall project itself.

So my request to all repository maintainers are to mark a repository as 'Archived'. And update the README (or description) to reflect the same.

In any case, On April 1st week, we should actively mark them inactive if no activity is found in last 15+ months. For other repos, maintainer's can take appropriate action.

Regards,
Amar

_______________________________________________
maintainers mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/maintainers






_______________________________________________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968




Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel