In the workflow that has been evolving of late, contributions are first entered into the CWE-ou-minkata and MOULSCRIPT-ou-minkata repositories, then tested on the Minkata shard, and finally added to CWE-ou/MOULSCRIPT-ou for possible pulling by Cyan.
For a contribution that comes in as a pull request against CWE-ou, such as #5: Avatar clothing fix or #6: Basic clipboard functionality, this has two awkward consequences:
- The pull request is left open with no activity, neither accepted nor rejected, for a long time (until the change is ready to enter CWE-ou). Prompt action on a pull request is a way of signaling recognition to the author, while long inactivity is likely to frustrate and detract contributors.
- To get the contribution into CWE-ou-minkata for testing, it must be cherry-picked or moved around in the form of a patch. The latter in particular I consider a tedious and error-prone step, as results like the following unhelpful commit message show: