Daniel Mendler

@progfolio That doesn't seem very relevant for this issue. We are talking about packages, in particular libraries, which care about versioning and which specify proper versions in their version header....

As a data point, libraries like dash, s, f, ht and compat specify version headers. I'd say it is a win if these were checked. Btw I wonder how well...

I've also noticed that there are issues where users have pinned Compat to a specific commit, which is incompatible with other unpinned packages. It would be great if Straight could...

> Move repositories/wiki If a transfer is not possible, all we can do is to add a link to the README here, pointing to the new fork. > Notify GNU...

Regarding the transfer button, see https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository: > Note: You can only transfer issues between repositories owned by the same user or organization account. A private repository issue cannot be transferred...

monnier ***@***.***> writes: >>> Notify GNU ELPA admins about new maintainers >> In principle one could add multiple names to the `Maintainer:` package >> header. Unfortunately the current version of...

monnier ***@***.***> writes: >> I've got a report, where multiple maintainers in the header field >> prevented package installation. This has affected the Compat package in >> the past. See...

medranocalvo ***@***.***> writes: > I updated the copyright years but not the Maintainers field, due to the issue you > point out, @minad. I worry that using multiple maintainers will...

medranocalvo ***@***.***> writes: > I've successfully avoided this decision in the past years and am prepared to > continue avoiding it. Motivation is lack of time, energy and fear that...

@medranocalvo I've finished a few tasks from the list: - [X] Move exwm wiki - [X] Change the wiki to a Main page explaining the move and new location -...