That conversation on Saturday was epic. Thanks everyone for weighing in on that. This is exactly why I come here. Early in the discussion, @Steve Dekorte asked the following:

[With respect to] specific visions, would folks here find it helpful to have a way to collect member’s (brief) thoughts on their perspectives on FoC, and their project’s vision and implementation?

I'd love to communally decide on a "business card"-like way to share our visions and projects. Something like a 1-page (max) writeup. These could live on our personal or project websites. We could make it the norm to add this link to your Slack profile, so people can see your vision statement by clicking on your name then visiting the link. Based on that big discussion, I wrote up some thought-clarifying questions that could be used as writing prompts. These aren't meant to be directly answered, but they might be useful axes to establish in your writeup.

1) How specialized is your project — Is it for building everything from device drivers and shell scripts to web servers and WASM? Or is it focussed on one or a few specific tasks?

2) How would you describe the people who will use your project — Are they programmers? Non-programmers? Artists? Junior developers? Children?

3) What are the shortcomings in the current common practice that your project aims to address? What common shortcomings does your project choose to ignore?

4) What history are you drawing upon — Particular research? Xerox PARC? An idea tossed-off in a lighting talk?

5) How would you characterize your project's ideal role in the culture — is it a grand leap forward, a small step in the right direction, merely a suggestion for a better direction to travel?

6) What difficult tradeoffs have you been forced to make in the design of your project? In other words, what has been sacrificed to make your project better than existing projects?

In a thread (I'll start one), I'd love feedback on the idea of the 1-pager, and on these questions. Feel free to suggest different clarifying questions / writing prompts, or just to nit pick wording, if you think there's some merit to something like this.

First I totally agree with the idea! Thanks @Steve Dekorte and @Ivan Reese.

(6) is an especially good question.

If they'd be different, then I think people could write both a personal vision statement and a statement for each of their projects — personal statement on their personal site, project statement on each project site. For me, I'd just write one statement, since the vision guiding my project is more interesting than my personal vision (they're basically the same, but the project vision is more specific).

How about a google doc in the format: project title, author(s) name & slack handle, and short paragraph describing it’s perspective/approach? These would only be actively developed projects that FoC slack members are working on. At the top could be a paragraph describing the purpose of the page itself.

Yeah, I don't think this writing should go in a spreadsheet. But we could add links to our statements to @Duncan Cragg 's existing spreadsheet.

It would be SUPER helpful to just click someone's name and have a quick view of what they're about

I've been meaning to write one, but [homesteading]. Dan, you should do it and put it in your slack profile!