Consider shutting down project

[twolfson]

foundry was written at a time when I was significantly more prolific and active in publishing tools and releases.

Now that I'm on the less actively engaged side of things, it's showing its flaws where it's harder to iterate/update content as underlying dependencies and integrations (e.g. CI) require maintenance.

Most recently this came about in twolfson/foundry-release-pypi#3 and needing to add an additional common command, yet Travis CI was broken and Vagrant is now more obscure than common vs Docker for the same container purpose.

I'm considering alternatives which dial back the "Operational Processes" complexity by 1 level (i.e. migrating from scripts to "document as you go" documentation)

It's definitely less ideal from a code reuse/update perspective, but I don't really touch my repos often (maybe 1x every 1-3 months) and it doesn't seem many others found this that library useful.

[twolfson]

Some additional notes as I was going to bed last night:

• Repo name should be foundry-scripts
• Can workaround complex "update version in a file" pieces via [python -](https://stackoverflow.com/a/30703682) and node --eval as needed with << EOF heredocs
• foundry-scripts can be versioned as a common setup, like git-extras, no need for individual releases like our current foundry-release-* split
• Scripts likely best done in a code fenced blocks with documentation as .md, vs something like a .sh file, since the target is more documentation than scripting (otherwise, it'd still be foundry-release-pypi and such still)