Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need guidance on publishing to public registries #41

Open
ben-sagar opened this issue May 10, 2017 · 3 comments
Open

Need guidance on publishing to public registries #41

ben-sagar opened this issue May 10, 2017 · 3 comments
Labels
feature New feature or request

Comments

@ben-sagar
Copy link

We've done a bit of this with the NPM and RubyGems registries, but it would be good to capture the guidance on when and how we should do it.

@Cruikshanks
Copy link
Member

Cruikshanks commented May 10, 2017

One of the things that would be a big help is an agreed email address. Ideally not a person, but one that some of us could monitor.

Would you know how to go about arranging it @bensagar-ea ? The alternative is we speak with @davidblackburn and create a envagency.co.uk address. We created one when I setup DMARC on a few services, we'd just need someway to monitor it.

I'll try and draft something in the meantime.

@Cruikshanks Cruikshanks added the feature New feature or request label May 10, 2017
@ben-sagar
Copy link
Author

@Cruikshanks Fish are looking at exactly this issue right now. They are going to use a temporary email address for now (probably gmail) until we have a generic Environment Agency email account.

@pwadmore-ea
Copy link

@bensagar-ea and @Cruikshanks - An NPM publishing account has been created. It is linked to a temporary email address until a generic Environment Agency email account is created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants