-
Notifications
You must be signed in to change notification settings - Fork 53
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
cEP metadata should include date field #61
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hi, the existing cEP metadata as outlined in cEP 0:
I'm proposing adding a date field to the list of metadata above. While it's true we can do git blame to figure out the full history of the cEP, some dates are quite useful and should be documented as part of the cEP itself, so we can refer to it quickly. As a comparison, official PEPs always have "Date Created" and "Post-History" dates. |
Adding dates inside files which are version controlled is a bit odd, and the date will usually be 'wrong' as merges occur after authoring. Which is effective? Maybe we could add dates to the README.md after #73 has created an index of cEPs? |
So lets add dates to the pre-2018 cEPs, and see what happens during the PR. That should help us formulate which dates should be used. |
need some info, i guess date it was first authored should be add in date column in README.md, correct me if not. |
This add date field to cEP metadata in README.md Fixes coala#61
This add date field to cEPs metadata in README.md Fixes coala#61
This add date field to cEPs metadata in README.md Closes coala#61
|
This add date field to cEPs metadata in README.md Closes coala#61
This add date field to cEPs metadata in README.md Closes coala#61
This add date of creation to cEPs metadata in README.md Closes coala#61
Useful dates:
Date it was first authored,
Effective date,
Last update
Thoughts?
The text was updated successfully, but these errors were encountered: