8000 Consider removing spaces in date range expressions · Issue #915 · fsfe/reuse-tool · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Consider removing spaces in date range expressions #915

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

Closed
BigBlueHat opened this issue Feb 15, 2024 · 4 comments
Closed

Consider removing spaces in date range expressions #915

BigBlueHat opened this issue Feb 15, 2024 · 4 comments

Comments

@BigBlueHat
Copy link
Contributor

Finding the YYYY - YYYY change (from the more typical) YYYY-YYYY format a bit sad (which is of course certainly idiosyncratic). 😄

So, what if REUSE offered a standard time interval format such as ISO 8601's YYYY/YYYY or YYYY--YYYY? Both are relatively uncommon (in my experience at least), but would be parse-able by any ISO 8601 implementation.

Just an idea.
🎩

@BigBlueHat
Copy link
Contributor Author

Thought about this one some more...I think it's too weird.

The bigger thing I want is to have date ranges match what I've observed most places over the last two decades: YYYY-YYYY vs. what the tool generates now which is YYYY - YYYY. I know it's silly and small (like #913), but it's literally blocked my use of REUSE on projects...which is very sad.

At this point, though, it'd probably need to be another config or made possible through more capable templating perhaps as part of #581.

@carmenbianca
Copy link
Member

I'm happy to re-open this to look at it. Not sure why the spaces are there when they're not very common.

@carmenbianca carmenbianca reopened this Mar 4, 2024
@BigBlueHat BigBlueHat changed the title Use standard time interval format for dates Consider removing spaces in date range expressions Mar 6, 2024
Copy link

Thank you for your time and contributions! Unfortunately, this issue has been inactive for quite a while which means we probably can't manage the time to deal with it. That's why we're marking it as stale. We want to keep things tidy and focus on active discussions, but we’re always happy to revisit if this is still relevant!

If you’d like to keep this open, please add a comment to let us know and remove the label stale. Otherwise, this issue will most likely be automatically closed soon.

@github-actions github-actions bot added the stale label Apr 10, 2025
Copy link

Since there hasn't been any recent activity after the last message, we're going to go ahead and close this issue. Feel free to reopen this and remove the labels stale and unresolved if it's urgent.

We truly appreciate your contributions and engagement!

Thank you and happy hacking!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
0