-
-
Notifications
You must be signed in to change notification settings - Fork 880
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
docs: update maintainers #559
Conversation
Codecov Report
@@ Coverage Diff @@
## main #559 +/- ##
=======================================
Coverage 99.34% 99.34%
=======================================
Files 1920 1920
Lines 176414 176414
Branches 904 904
=======================================
Hits 175257 175257
Misses 1101 1101
Partials 56 56 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please have a look into line 7 of this file, there is a date.
So I'm not sure if we want to preserve this document as a history/changelog or if we should update the timestamp and maybe link to the git history or somewhat
@JessicaSachs What are your thoughts about this?
a32d600
to
2077fd9
Compare
I don't think having a timestamp on this would be helpful. At some point we should probably remove the notice entirely or put it at the bottom of the website, etc and have a more prominent Teams page with nice photos and an emeritus section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's fine with me to add your name here because you were there during this entire statement period. For future members I don't think that placing their names here would make a lot of sense and we should get a teams page.
Special thanks to https://aequitas-software.de/