Move lesson state to beta

[tobyhodges]

Update the lesson life cycle stage to beta, and add a note to the README and landing page to help us recruit volunteers to pilot the lesson.

[tobyhodges]

To do when this is merged:

• [x] adjust repository topics to reflect the change
• [x] @tobyhodges to update internal table of Incubator Lessons to reflect new life cycle stage
• [ ] send an email to the wider community, post to the lesson Slack channel, calling for beta testers

[tobyhodges]

Pinging @sstevens2 @anenadic @annefou @unode - any objections to merging this? We do not have to make the call for beta tests if you all do not have the capacity to process the questions, feedback, and PRs that may come with that, but I think it would be good to update the site banner etc before I go on parental leave at the end of the summer.

[unode]

No objections on my part.

If we do the beta call do you expect a big increase of PR/questions/feedback? I've never been through the process so don't know what to expect...

I'm counting on August to be a lighter month on other fronts.

[annefou]

Thanks @tobyhodges No objections too. And same questions as @unode Not sure what we should expect as the process is very new to me too!

[anenadic]

It's a 'yes' from me 🎉 !

We can always see how maintenance of the lesson goes and learn in the process, as it is new for some/most of us. We can also look into recruiting more lesson maintainers in the future (which would be great) and remember that lesson authors can also retire from active lesson maintenance.

We can also perhaps look to schedule maintenance team meetings, e.g. once every 2-3 months (depending on how people feel), to set some fixed time aside to go though issues that need bigger discussions and to review PRs that are not handled in between the meetings?

[tobyhodges]

My experience so far suggests that we should anticipate some interest from other Instructors wishing to try teaching the material. We should be prepared to collect feedback from those pilot workshops and to process issues/pull requests that come from them. But I do not expect it to be a flood.

The main motivation for asking was to make sure that we do not put out an email announcement and blog post calling for feedback/engagement that we are not ready to handle during the period that I am on parental leave. E.g. I am fine with merging this and updating the life cycle stage in The Carpentries systems, but leaving the blog post/email announcements/community discussions, etc to January, if you all are happy to wait.

[sstevens2]

Sorry i'm late to this party but I'm in for moving it to beta! 🎉 Looking forward to seeing pilots and feedback! Agree with Alek's suggestion about regular maintenance meetings/co-working.

[tobyhodges]

Thanks everyone, I will merge this now 🚀