You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm happy to announce that @agoose77 is joining the core team of Executable Books! Angus has worked in this ecosystem for several years (first via the jupyterlab-myst project and more recently via several other efforts in the MySTJS and MEP ecosystems). He has also spent a lot of time helping the team think through improvements on the MEP process and syntax.
A few weeks back, @rowanc1 sent an e-mail to the to the @executablebooks/steering-council recommending @agoose77 for membership. Since we do not have a formal process for adding new team members yet, Rowan provided a rationale for this decision via a Google Form (which we may adapt for broader use later). The steering council discussed and all agreed that this was a good decision.
@agoose77 rightly pointed out that the responsibilities for "core team" status were under-specified, and we discussed that in these early days, a big part of being on that team is helping the group decide on responsibilities that are equitable and realistic for all. He said that he is excited to serve with the Executable Books @executablebooks/core-team in an official capacity, and to do what he can for this community!
So exciting, been a pleasure working with you over the last year @agoose77, and especially our focused work together on JupyterLab MyST!! Excited for what is next! 🚀
@choldgraf I opened a PR here: #15 --- I think that is all that is necessary for the todo list?!
I'm happy to announce that @agoose77 is joining the core team of Executable Books! Angus has worked in this ecosystem for several years (first via the
jupyterlab-myst
project and more recently via several other efforts in the MySTJS and MEP ecosystems). He has also spent a lot of time helping the team think through improvements on the MEP process and syntax.A few weeks back, @rowanc1 sent an e-mail to the to the @executablebooks/steering-council recommending @agoose77 for membership. Since we do not have a formal process for adding new team members yet, Rowan provided a rationale for this decision via a Google Form (which we may adapt for broader use later). The steering council discussed and all agreed that this was a good decision.
@agoose77 rightly pointed out that the responsibilities for "core team" status were under-specified, and we discussed that in these early days, a big part of being on that team is helping the group decide on responsibilities that are equitable and realistic for all. He said that he is excited to serve with the Executable Books @executablebooks/core-team in an official capacity, and to do what he can for this community!
To do
A few actions we need to take:
The text was updated successfully, but these errors were encountered: