search

jupyterlab / frontends-team-compass

A repository for team interaction, syncing, and handling meeting notes across the JupyterLab ecosystem.
https://jupyterlab-team-compass.readthedocs.io/en/latest/
BSD 3-Clause "New" or "Revised" License
59 stars 30 forks source link

Organization repositories maintenance #200

Closed fcollonval closed 1 year ago

fcollonval commented 1 year ago

We have lots of repositories in the organization that did not see much activities for a while. It will be good to decide what to do with them.

Here is a list of the repositories that we should look at:

It has been decided at the weekly call of June 21st to leave a week for people to build an opinion on those projects and decide of their fate at the next call (June 28th).

Comments from the weekly meeting:

jtpio commented 1 year ago

cc @jupyterlab/jupyterlab-council since not everybody in the council can attend the weekly calls

ivanov commented 1 year ago

I support archiving all of these. It's pretty easy to un-archive should the need arise, see

image

It would be nice to update the README in each o these referring back to this team compass issue that it is being archived due to inactivity.

fcollonval commented 1 year ago

The follow up on this discussed at the weekly meeting is the following action:

[Fred] I'll open an issue on those repositories to notify subscribers that may be willing to take over the maintenance with a two weeks notice. After this 2 weeks, if no reaction to the issue, I will update the project README to add a notice of archiving the code linking to the team-compass issue. And then archive the projects.

krassowski commented 1 year ago

Just a note: user experience suffers if organization has lots of archived repositories. Having a second organization like https://github.com/jupyter-attic (or just moving some of those repositories over there) may be better than just archiving for some (not necessarilly all) of the repos.

ivanov commented 1 year ago

Just a note: user experience suffers if organization has lots of archived repositories

Hi @krassowski, can you be more specific about the way in which user experience suffers when there are lots of archived repositories?

echarles commented 1 year ago

Hi @krassowski, can you be more specific about the way in which user experience suffers when there are lots of archived repositories?

I don't think one answer is better than the other as this is very linked to our you perceive the repos in orgs (like files in folders). On my side, I am in favor to moving all archived repos to jupyter-attic (moving to a new jupyterlab-attic would be another alternative a bit overkill imho), just because I like working on a clean naked desktop with as less items as possible.

krassowski commented 1 year ago

Some specific scenarios I experienced:

krassowski commented 1 year ago

On the other hand we should probably prominently link to wherever we would decide to move the archived repos so that they are still discoverable.

ellisonbg commented 1 year ago

Note, we created the attic org before GitHub implemented the repo-level archive ability. I don't think we would have done that is GitHub had repo-level archives, as it requires a lot more work to do cross-org transfers across Jupyter.

On Sat, Jul 1, 2023 at 1:00 AM Michał Krassowski @.***> wrote:

On the other hand we should probably prominently link to wherever we would decide to move the archived repos so that they are still discoverable.

— Reply to this email directly, view it on GitHub https://github.com/jupyterlab/team-compass/issues/200#issuecomment-1615622301, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAGXUFETQULD6W6RKIOM5DXN7KIFANCNFSM6AAAAAAZPACDOI . You are receiving this because you are on a team that was mentioned.Message ID: @.***>

-- Brian E. Granger

Senior Principal Technologist, AWS AI/ML @.***) On Leave - Professor of Physics and Data Science, Cal Poly @ellisonbg on GitHub

ellisonbg commented 1 year ago

Oh, please don't archive the commenting extension though, we plan on starting to work on that again this year.

On Wed, Jul 5, 2023 at 3:12 PM Brian Granger @.***> wrote:

Note, we created the attic org before GitHub implemented the repo-level archive ability. I don't think we would have done that is GitHub had repo-level archives, as it requires a lot more work to do cross-org transfers across Jupyter.

On Sat, Jul 1, 2023 at 1:00 AM Michał Krassowski @.***> wrote:

On the other hand we should probably prominently link to wherever we would decide to move the archived repos so that they are still discoverable.

— Reply to this email directly, view it on GitHub https://github.com/jupyterlab/team-compass/issues/200#issuecomment-1615622301, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAGXUFETQULD6W6RKIOM5DXN7KIFANCNFSM6AAAAAAZPACDOI . You are receiving this because you are on a team that was mentioned.Message ID: @.***>

-- Brian E. Granger

Senior Principal Technologist, AWS AI/ML @.***) On Leave - Professor of Physics and Data Science, Cal Poly @ellisonbg on GitHub

-- Brian E. Granger

Senior Principal Technologist, AWS AI/ML @.***) On Leave - Professor of Physics and Data Science, Cal Poly @ellisonbg on GitHub

fcollonval commented 1 year ago

@krassowski as mentioned by @ellisonbg doing cross org transfer is adding some complexity; especially if at a later stage someone wants to revive a repository.

What do you think of renaming the project by prefixing them with archived as part of the archive process? GitHub is good at redirecting and as for org transfer the old URLs will still work but the hopefully the link will give a hint to the reader about the repo status.

krassowski commented 1 year ago

Prefixing them would only address one of the points. I think it is safe to proceed with archiving and we can rename or move them later if there is a need and wider consensus.

jtpio commented 1 year ago

Maybe it could be worth mentioning some of the top contributors in each of the repos explicitly in these issues, as they might not be actively watching the repository and getting notifications when new issues are opened.

fcollonval commented 1 year ago

Closing this as the repositories maintenance has been done.