I created a wg-traits repository -- should I move the minutes and things there?
I'd actually like us to take a second to talk about how we are organizing our efforts here --
I've been enjoying the way the meeting is structured, in terms of having "projects we are working towards", and giving a brief update on how it went, and setting a new goal for the week in that context.
I was thinking that maybe we should overlay a kind of "sprint structure" -- i.e., we set our initial projects, work on them for N weeks, then take a look and see if we want to adjust those projects.
As far as the repository goes, I'm not sure if we should try to have files per project? Maybe we don't need that for most things.
To be more specific. I could imagine a file hierarchy like:
ROADMAP.md, defines the things we are presently working on
minutes/..., contains minutes from each meeting touching on the active projects
rfcs/..., contains drafts and things
where we have notes about each of the active projects there, or I could imagine something like
ROADMAP.md, as above
generic-closures/minutes/-- contains any updates (maybe none?)
generic-closures/rfcs/-- contains any draft rfcs
Or, I suppose, a hybrid, with a single
minutes directory but per-project directories containing notes and other files. At minimum, a README.md with links to paper docs and things. This could probably replace the DropBox paper directory by and large, though, and it doesn't suffer from the weird permissions model.
Now that I think more on it, I think I like the hybrid model.
I'll wait to get a bit of feedback though before I take any drastic action. =)
hybrid seems good
@nikomatsakis let's try it; we can iterate on the process here
yeah, what @centril said
OK, I moved the minutes onto that repository. I think documents related to specific purposes should go into directories named after those purposes.