-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update for 2023 Q1 #685
Comments
A few blog posts
|
What is the deadline for contributing content? |
Let's say in one week, so Wednesday, April 5th. For content, what is most useful would be 1-3 of the most notable things that have happened, as well as short links to any issues/PRs/websites/blog posts/etc that you'd like to highlight. |
EngineeringNOTE: This is just a subjective and short list of things we have done during Q1. I am probably forgetting a few things and purposely avoiding very granular stuff. Complete information about what we have done lives in the Sprint board for each of our sprints (1-6). Several new hubs:
Events:Migration from Auth0 into CILogon
Improving support process:Maintenance:
Fulfilling support-related requests such as:
New engineers and manager:
Docs improvements:GESIS-related work: |
Thanks @damianavila, this is great. @colliand and @jmunroe please share your updates ASAP. (it doesn't need to be as large as the one above!) |
Hey all - I am sifting through the list above and wanted to note a few things that we should reflect on in the coming months. This is mostly just me reflecting and generating some data, I am not sure what actions to take next but wanted to get the ideas written down. I've captured them in the retrospective issue linked below: |
Blog post draft is upHere's a PR with a blog post draft: I'm happy to iterate with feedback from folks this week if others have thoughts, otherwise will plan to post at the end of the week. |
We should provide an update about what we've been up to in 2023 to our team and our external stakeholders.
Example structure
Actions
Tasks
The text was updated successfully, but these errors were encountered: