Hi all -- a few of us were discussing how we might improve on our current state, where we put meeting agendas and minutes in the meetings/
subdirectory of the wasmtime repo.
The issue that came up is that as we were discussing various CI gating mechanisms, it became increasingly clear that (i) we don't want to waste CI time on a meetings
-only change, but (ii) it is hard or impossible to special case subdirectories with many gating mechanisms.
The cleanest solution is probably to separate out the meetings/
subdirectory into a meetings
repo in the BA GitHub org. This keeps separate things separate, which makes policy simpler.
Does anyone have any objections to this, or other suggestions?
cc @Alex Crichton @fitzgen (he/him)
So I've discovered that I can't create a repo named meetings
under the BA org (presumably already exists and is private); anyone have better suggestions for name? project-meetings
maybe?
I can see the meetings
repo and it's quite small with just 5 commits and no recent activity, so I'll see if it can be renamed
checking with the owners I guess? thanks!
ok the meetings
name should now be open if you'd like to try again @Chris Fallin
OK, repo now exists, and by the magic of git filter-repo --subdirectory
, it contains the full commit history of meetings/
I'll do a PR to delete that from wasmtime
now
Last updated: Dec 23 2024 at 12:05 UTC