Closed Bug 1915579 Opened 1 year ago Closed 1 year ago

Un-archive the fluent.vim repository

Categories

(mozilla.org :: Github: Administration, defect)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: caleb, Assigned: cknowles)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0

Steps to reproduce:

The repository with Project Fluent (FTL) syntax highlighting for VIM has been marked as archived:

https://github.com/projectfluent/fluent.vim

I realize this happened due to inactivity and plugins don't require frequent changes, but they do occasionally need tweaking.

Actual results:

This sends the wrong message to potential users and raises warnings in many plugin managers.

Expected results:

The repository should be un-archived and existing issues/prs if any restored.

Additionally feel free to invite me (@alerque on GitHub) to the repository as the maintainer. I am already a maintainer in the org on the fluent-rs project which is far more sensitive than the vim plugin, so this isn't a huge risk. Additionally I am both a user of the fluent.vim plugin and experienced with maintaining many other much more popular vim plugins. For example I admin the @preservim org on GitHub and maintain vim-pandoc, vim-ledger, nerdcommenter, and many others.

So, to do the unarchive, we need to hear from one of the existing admins of the repo, who were informed of the upcoming archival effort when it happened.

For that purpose I'm poking the admins of the repo in the team "project-fluent-admins" as likely folk with knowledge/awareness

Once we have any approval/questions out of the way, I'm happy to reverse the archive process. (though I note there were no open issues or PRs at time of archive)

Assignee: nobody → cknowles
Flags: needinfo?(francesco.lodolo)
Flags: needinfo?(earo)

Thanks Chris. I think the project-fluent-admins will know who I am.

And it's nice there were no open issues/PRs, but I'll also should have mentioned in the original request that this plugin is by far the defacto plugin for VIM support of Fluent syntax. There is also a tree-sitter plugin archived at the same time but I'm not as familiar with the ecosystem or current usage of plugins.

I wasn't even the first one to notice, it was brought up on Matrix here: https://matrix.to/#/!ySSPMdkjuQYlSmDDcB:mozilla.org/$yR7_foG7nPL0ynDIotG0IG7RdO5Itd71GwN0I-VyrKI?via=matrix.org&via=mozilla.org&via=wfxlabs.com

Yup. Once I get word from an existing admin (or they make you an admin) I'm happy to reverse the archive. (and that goes for any repo that was archived for 3+ years of inactivity)

We're fine with unarchiving the projectfluent/fluent.vim and projectfluent/tree-sitter-fluent repositories, and assigning Caleb maintainer rights on them. Neither of these repositories has had any activity since 2018, and I don't expect much activity going forward either.

Flags: needinfo?(francesco.lodolo)
Flags: needinfo?(earo)

Alright.

Both https://github.com/projectfluent/fluent.vim and https://github.com/projectfluent/tree-sitter-fluent have been unarchived.

Note that when we next do a sweep for inactive repos, if nothing's changed these will be caught again. Emails will be sent to all admins of the repos, so any one of them can contest the archive. But the surest method of avoiding this is to have some activity within the last 3 years.

And finally, I've send OC invites to Caleb's user alerque as a maintainer for these repos.

As always, let me know if there's any questions or concerns.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.