Open kariljordan opened 3 years ago
Instead of waiting for PR, should we fork the lesson and then teach from the updated fork?
Then send the PR after teaching the workshop as by then most of the rough edges would have been smoothened out.
This complaint seems fair, and I think we could develop some better tagging / triaging of PRs and issues for lessons.
Maybe even an annual audit of lessons and listing out any areas that are outdated / need prompt attention. Like in July say? A month that is not worldwide national holidays and not that month of August that Europeans vacation!
However, I also think it's important to advance a community approach in the Carpentries: we are in this together and we are developing the lessons and the teaching at the same time. Maintainers are providing a volunteer service that is in the support of workshops and the Carpentries mission, but they are not paid employees at the urgent command to support all instructors. Being a Carpentries Instructor might include some tolerance for "work in progress," and if it's too frustrating, then maybe it's just not the right fit for the moment.
I think @lexnederbragt has a good suggestion about moving toward "releases" for stable lessons.
In general, I'm advocating for more responsiveness and more understanding.
*signed, your newest maintainer
On December 30, 2019, @rgaiacs raised an issue in the private Executive Council repository. The text is provided below
The question @rgaiacs asked to explore is: How to make teaching enjoyable again for long time instructors, however @amyehodge offered the following:
@lexnederbragt offered the following:
@rgaiacs shared:
The Program Committee of the Executive Council has asked that this issue be addressed in the maintainer-RFC repo.