New Hooks to be approved

[tredondo]

Ping events for new hooks received on autopublish.meteor.com will be reported here.

At the same time, anyone being aware of the imminent creation of a new hook (e.g. after a PR for a new integration was merged) should write here to have admin users notified about it.

Admin users should revise all new hooks end eventually approve them from this page.

After the new hook is approved, please delete all related messages to keep this track clear!

[tredondo]

Received from hoppas/meteor-plugin-stylus to be revised!

@ViZhe, thank you for testing autopublish: could you explain how you would like to use it?

[tredondo]

Received from hoppas/meteor-plugin-stylus to be revised!

@ViZhe, thank you for testing autopublish: could you explain how you would like to use it?

[tredondo]

Received from hoppas/meteor-plugin-stylus to be revised!

@ViZhe, thank you for testing autopublish: could you explain how you would like to use it?

[tredondo]

Received from codetheweb/zxcvbn to be revised!

@codetheweb, thank you for testing autopublish: could you explain how you would like to use it?

[tredondo]

Received from mizsha/meteor-user-settings to be revised!

@mizsha, thank you for testing autopublish: could you explain how you would like to use it?

[tredondo]

Received from formly-js/angular-formly-templates-material to be revised!

@kamilkisiela, thank you for testing autopublish: could you explain how you would like to use it?

[kamilkisiela]

@meteorpublish This is official package and I need to auto publish it.

[trusktr]

It'd be nice if we didn't have to go through this manual step.

[zimme]

@kamilkisiela Approved.
@trusktr, Yeah that would be great, the problem is that the publish bot is added to all meteor packages projects which are approved for autopublish, which means that any user who have and approved package for autopublish have the ability to just change the name in package.js to another package which is setup for auto publish and they will be able to publish new versions of that package.

This is why we have a manual approve process.

What we've talked about before but no one have had time to actually look into at depth is generating a .meteorsession file for each package when doing this setup, when logging in with their meteor developer account.

If that works the publish server should be able to publish as the user setting up the auto publish. and the publishbot isn't needed to be a maintainer of the package.

[kamilkisiela]

@zimme I'm going to move all packages from formly-js to atmosphere. Can I message you or somebody else directly or each time has to write in this issue?

[zimme]

just start moving and as I see the package popup in this thread I'll approve them 👍

[kamilkisiela]

@zimme ok, thanks

[tredondo]

Received from wieldo/meteor-autoformly to be revised!

@kamilkisiela, thank you for testing autopublish: could you explain how you would like to use it?