Keeping track of dated events
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 93
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
There are a number of things that need to happen in the future at a certain date or period.
For instance, end of contracts, expiration of certificates, decommissioning of resources, etc.
Tickets have no date so it's not enough.
Until now, we've been mostly relying on assigning those things to one person and she's in charge of tracking it (via an event in one's calendar I guess).
We've also created workflows to be triggered at specific times, but it's very cumbersome to create.
Another idea is to add it to the monthly routine check but it's extra work every month and that only applies to technical stuff.
We thus need a tool where one can set a date and we get reminded later.
That sounds like a Calendar? Sure but we have no shared Calendar ATM. Should we create one? Is there a better tool for this job? @Popolechien are you using something already?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or implementation entry points are named. Start by resolving whether a shared calendar or another tool is preferred, then define the reminder, date/period, ownership, and notification requirements. Done means the project has an agreed approach for tracking future events and a clear implementation scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100