-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add date to ambassadors data #836
Comments
@Relequestual |
hi @Relequestual I would also love to work on this issue, but I want to understand how can i go ahead with solving the issue as its going to be my first time solving |
Sure, go ahead with making a PR!
You should be able to work this out based on the git history on GitHub. If you're still unsure after that, do as Benja. Month and year is fine, following what we have already used. Thanks! =] |
I'll look into the git history and reach out to Benja if I have any doubts |
Thanks for your interest. If you're looking to break into open source, you may find other good first issues issues here: https://goodfirstissue.dev/ |
Fixed with #838 |
Summary: Ambassador status should be reviewed every year, so we need to log the date of issue.
Do you think resolving this issue might require an Architectural Decision Record (ADR)? (significant or noteworthy) No
It is adding data based on what was already defined for the program.
Details:
Required to resolve
We have a small number of ambassadors. They were added in one or two groups on a specific date, I forget which. @benjagm can bring clarity on the date, or it might be in the slack server history.
I believe this is the best approach as it would be nice to also track how many years they have been an ambassador vs just when they are next up for review.
Any further requirements to resolve this issue
Confirm dates are correct with evidence.
The above should be all one PR.
The text was updated successfully, but these errors were encountered: