Metalsmith org adoption

[webketje]

Hi there,

In a new effort to consolidate the metalsmith ecosystem under the Github and NPM metalsmith orgs, I'm reaching out to authors of contributed plugins that are so common in metalsmith builds, they could be considered core plugins and would add value to the Metalsmith org. The proposal is as follows:

• I invite you as a collaborator to the metalsmith org so you can transfer the repository. The repository will be renamed to <plugin> instead of metalsmith-<plugin> (the full url will then be https://github.com/metalsmith/<plugin>).
• After an initial (non-opinionated) dev setup alignment (dotfiles, changelog, readme format), you can choose to stay in the org and maintain the plugin if you wish, including releasing on NPM, or forfeit maintenance to the metalsmith org members. A deprecation notice would need to be pushed to https://npmjs.com/package/metalsmith-<plugin> and the plugin will be republished as @metalsmith/<plugin>.
• Your authorship will be aknowledged in the README.md. The copyright to the plugin remains yours, unless you decide to transfer the rights to webketje, copyright owner of metalsmith since Sept. 2021. If you transfer the copyright, the LICENSE would look like this:

  Copyright (c) 2022 webketje
  Copyright (c) 2015-2022 Ahmad Nassri

[ahmadnassri]

Hey @webketje happy to move forward with this, sorry for taking a while to respond ...

also consider the following packages:

• https://github.com/ahmadnassri/node-metalsmith-pug
• https://github.com/ahmadnassri/node-metalsmith-imagemin
• https://github.com/ahmadnassri/node-metalsmith-paths

[webketje]

Hey @ahmadnassri thx for responding nevertheless. I forked and updated metalsmith-imagemin (see https://github.com/ahmadnassri/node-metalsmith-imagemin/pull/120), you may still cherry-pick commits of interest. I'm not going to consider metalsmith-pug because layouts/ in-place already have adapters for it. metalsmith-paths is an interesting candidate for adoption.

Just to be clear: I much prefer the original authors continue maintaining their package (I have enough to do with metalsmith & the 15-some core plugins) but offer org adoption for essential plugins that are in danger of being abandoned

[ahmadnassri]

Just to be clear: I much prefer the original authors continue maintaining their package (I have enough to do with metalsmith & the 15-some core plugins)

oh I can relate! hopefully with the official adoption, more people are encouraged to contribute.

at least with such small / simple plug-ins, the maintenance tends to be low... so I'm happy to keep maintaining.

[ahmadnassri]

I'll check the PR and merge down, please share with me any rules/conduct/expectations on official org status.

[webketje]

Evidently I've stumbled on your plugins earlier and updated / got inspiration from them. For example, I created @metalsmith/requests which is a super-powered version of this repo, the only thing it still misses is cache. The intention is to use it for rendering the README.md's of all core plugins to a docs section in a metalsmith build on metalsmith.io.

I've sent you an invitation for a Github team where I occasionally post some "raw" ideas to get feedback from the more involved metalsmith users/plugin authors. There's also a small maintainer guide.

So going forward what you can do is propose a transfer for metalsmith-imagemin and metalsmith-paths (I think it's in repo settings -> Danger zone -> transfer this repo or something and assign to metalsmith). I will accept it, add you as a collaborator on the metalsmith org (with access to the repo's you (wish to) maintain). I will do the first republish under new name on the npm org (need to have a package to invite a team member with limited access), and after that I leave you in control (and I may step in if no new activity has happened for +1 year).

[ahmadnassri]

ok, sounds good.

I'll review all today and get the process started.