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

Change Mission Statement #772

Open
karianna opened this issue Apr 14, 2019 · 2 comments
Open

Change Mission Statement #772

karianna opened this issue Apr 14, 2019 · 2 comments

Comments

@karianna
Copy link
Contributor

Some wording to indicate that we are Infrastructure as Code for other 3rd parties and that we should always make sure to be open for extension.

@karianna karianna added this to the 2019 April milestone Apr 14, 2019
@sxa
Copy link
Member

sxa commented Apr 15, 2019

I'll copy in here what I said in slack on this topic :-)

"I would be nervous about doing that until we've finalised the docs on how to run it. I don't want another of these: #626 - it's fairly safe now (if you skip a couple of tags) and the Vagrant files are in place to make it easier to deploy in VMs but the docs aren't fully up to date and I think it still tries to change the hostname on the machine."

Once the docs are happy, and safeguards are in place, and a few people have tested them I'd be totally happy with such a change and it's definitely where we'd like to be :-)

@Willsparker
Copy link
Contributor

The documentation around Vagrant (and PBTests) has been greatly worked on since the latest comment. I believe (from my look at the wikipedia article) that we are 'infrastructure as code', so I don't think it's unreasonable to put it in the docs now :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

3 participants