Should we have a public-facing mission statement doc?

[knod]

and where should it go? Should it be combined with new member on-boarding material? Here is a currently archived more public-ish facing doc:
https://docs.google.com/document/d/1O6n3DWepjArcmX1cPbxzxztC8CY3sxa0pg76YBKHeK0/edit#

Should we use that? Have some separate material? Etc.

[mikemahoney218]

I'd say yes, but I'd especially propose using the readme for it. Version controlled and the most obvious public face for our project == win all around

[knod]

There are some thoughts about the pros and cons of using the README for this. We'll wait till more folks are back to discuss this. We'll try to put our notes about our thoughts in here, but they should at least be in the Meeting Notes doc.

[knod]

The README is public-ish facing. Other public materials will be made separately.

[jeremylang]

BLOCKED on decision where to put the documentation.

Current proposals appear to be along the lines of repo's README vs a document like https://docs.google.com/document/d/1O6n3DWepjArcmX1cPbxzxztC8CY3sxa0pg76YBKHeK0/edit#