Transfer the Multer package to the express organization on NPM.

[bjohansebas]

This is just a reminder that the Multer package has not been transferred to the Express organization.

https://www.npmjs.com/org/expressjs

cc: @expressjs/express-tc

[UlisesGascon]

It will be great to do a deep review, just in case that we are missing other packages 🤔

[bjohansebas]

Good idea, I can do it this afternoon when I get home

[bjohansebas]

These are the packages that are in npm but are not in the npm organization, yet their repositories live in one of the three GitHub organizations we have.

api-error-handler connect-markdown connect-rid domain-middleware express-expose express-namespace express-paginate flash multer restful-router urlrouter extend-proto re2js-legendary templation spdy-push

[wesleytodd]

Some of this we need to just deprecate. We can archive many of the repos I think as well.

[LinusU]

Which Team should own multer? Should I create a pkg_multer team?

edit: there was already a pkg_multer team, I think I managed to add the package! 🎉

(the UI for the teams is a bit clunky 😅)

[bjohansebas]

Now that multer is already in the npm organization, what are we going to do with the rest of the packages that are not in the organization? Even if they are not important, they are in our GitHub organization, which means we should have control to deprecate them on npm if we want to.

[ctcpip]

this is done! 🙏

[bjohansebas]

@expressjs/express-tc what is the decision on the other packages?