Add deprecation notice to repo

[ctro]

Add deprecation note

[waldoj]

I recommend going to the repo settings and choosing Archive this repository. That is GitHub's formal method of deprecating a repository.

[ctro]

Ooh, I didn't know about an Archive feature Waldo.

cc @mheadd @sztaylorakgov to get you both in here. I don't really care what happens here, just trying to help clean up the DHSS github space.

[mheadd]

➕ 1️⃣ to archiving, would just want to make sure that any links to the DevOpsMVP repo in the main project repo are updated.

[waldoj]

AFAIK, archiving doesn't affect any URLs. Everything should continue to function. The only difference is that it's labeled as no longer being maintained, and it's no longer possible to open new issues, edit files, etc.

[mheadd]

That makes sense than. Maybe merge this PR to add the message, and then archive the repo..?

[sztaylorakgov]

Thinking about the statement "Current tools, standards and practices are now maintained in a private VSTS Git repo and is shared with vendors engaged on projects." In concert with my own experience digging back into this repo occasionally for examples, I'm wondering if there is some set of needs that the new DevSecOps repo doesn't support. A better library of starter examples for folks on the team who need them, and also some transparency for vendors considering bidding on future RFPs. I think we should move forward with this PR, but wonder if we should chat briefly about this possible gap and whether/how to fill it going forward.

[mheadd]

@sztaylorakgov Agreed - I think it would be good to chat about this. I really like the idea of providing more resources for folks on the teams and also for interested vendors.

Merging this PR and creating a new PBI in VSTS for this work makes sense to me.