Proper home for Editor repo
The editor currently lives in a fork on Alve’s personal account. We need to bring it into the Amethyst org.
Action: @erlend_sh is strongly in favor of starting a fresh repo for the active fork and archiving our two legacy repos. I believe @fletcher is the only active member around who’s been involved in both of those prior efforts, so imo if he s this plan of action and no one objects, we’re good to go.
Completing MVP doc
MVP doc is still being fleshed out and is the most important precursor to further development and a sensible onboarding process for new contributors.
Action: I suggest @mralve reposts their notes in the GDoc as a topic in #development:editor so we can reach a consensus on essential MVP features to shoot for. There appeared to be a general consensus around “I wanna edit levels and prefabs, starting with Pong as a working example” as the gist of the MVP.
Afterwards we will close the topic and repost the MVP as a GitHub issue where it can double as a tracking issue for the MVP milestone.
The roadmap doc is already well underway. The plan is to map out where we are headed with the editor, going from short-term realism to long-term and .
Action: @erlend_sh, @fletcher, @mralve and @nothingismagick will (a)sync up in the near future to finalize the basic structure and initial contents of the roadmap. Once done, I suggest the roadmap should exist as a GitHub issue. I want it to live in the repo (i.e. as close as possible to the “start here” of the editor) and an
.md is just a bit too cumbersome to edit that it can more easily go stale.
Central point of information
@Sakerdot rightly pointed out that we’re lacking a central point of information.
Action: @erlend_sh is drafting an expansion for the readme here: Editor readme additions
Our readme will serve as the
In the future we will naturally have a presence for the editor on our website and book as well, but we’ll revisit that once we have a working MVP in our hands.
Thanks again to everyone who set time aside to attend!