“We” are “the community.” There is no intended “in-group.”
I suppose I’m the guy who’s sort of “responsible” for this, (Because when “everyone” is, then effectively “no one” is.) but the idea met with some enthusiasm at the meetup and the intention is for anyone who has an idea or an insight to contribute, please offer it either here or at a weekly meetup.
I’ve asked that we use the first 10 minutes of each meetup to discuss the current draft of the document and offer suggestions for improvement. Those can include new practices or tips, revisions to the structure, edits to the text and so on. Say what you will about Zoom, but these face-to-face, real-time interactions can be productive in ways that forum threads aren’t always.
At some point, I imagine this project may make a good example for using a version control system like GIT, but I think at least I’m shooting for a “minimum viable product” for the first “release.” Something that is immediately useful, but doesn’t necessarily contain an encyclopedic amount of content.
I have no experience with things like GIT, so I’m not going to lean into that.
This doesn’t replace aTbRef, or the Forum, nor is it intended to replicate them. It’s just a document a user can download and get some immediate insights on using Tinderbox, with some of the ideas being represented or demonstrated within the document itself. As I’m by no means an expert or even familiar with every dimension of Tinderbox, this will require a group effort.