Skip to content
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

Change the hard-coded current year to the current year #1436

Merged
merged 2 commits into from Jan 2, 2019
Merged

Change the hard-coded current year to the current year #1436

merged 2 commits into from Jan 2, 2019

Conversation

Joeventures
Copy link
Contributor

@Joeventures Joeventures commented Jan 1, 2019

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Documentation Update

Description

The current year is hard-coded in _footer.html.erb and _profile.html.erb. This PR makes the current year dynamic in both places.

Related Tickets & Documents

This tweet

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

  • docs.dev.to
  • readme
  • no documentation needed

@CLAassistant
Copy link

CLAassistant commented Jan 1, 2019

CLA assistant check
All committers have signed the CLA.

@pr-triage pr-triage bot added the PR: unreviewed bot applied label for PR's with no review label Jan 1, 2019
Copy link

@hugmanrique hugmanrique left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dynamic year code LGTM 😀

@@ -2,7 +2,7 @@
<div id="footer-container" class="container <%= "centered-footer" unless current_page.include?("stories-show") %>">
<div class="inner-footer-container">
<a href="/">Home</a> <a href="/about">About</a> <a href="/privacy">Privacy Policy</a> <a href="/terms">Terms of Use</a> <a href="/contact">Contact</a> <a href="/code-of-conduct">Code of Conduct</a>
DEV Community copyright 2018 🔥
DEV Community copyright 2016 - <%= Time.new.year %> 🔥

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would just display the current year, the same way it was before

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I probably would've done well to ask first. Might not be a bad idea to consult with an IP attorney, out of an abundance of caution, assuming the organization's intent to enforce the copyright. I have found multiple attorneys who offer similar guidance on their respective blogs and reference sites: https://danashultz.com/2013/10/09/copyright-notice-with-multiple-years-legitimate/

It's up to you. Thanks for the opportunity to contribute!

@pr-triage pr-triage bot added PR: reviewed-approved bot applied label for PR's where reviewer approves changes and removed PR: unreviewed bot applied label for PR's with no review labels Jan 1, 2019
@pr-triage pr-triage bot added PR: unreviewed bot applied label for PR's with no review and removed PR: reviewed-approved bot applied label for PR's where reviewer approves changes labels Jan 2, 2019
Copy link
Contributor

@benhalpern benhalpern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This update makes sense to me

@pr-triage pr-triage bot added PR: reviewed-approved bot applied label for PR's where reviewer approves changes and removed PR: unreviewed bot applied label for PR's with no review labels Jan 2, 2019
@benhalpern benhalpern merged commit c47253f into forem:master Jan 2, 2019
@pr-triage pr-triage bot added PR: merged bot applied label for PR's that are merged and removed PR: reviewed-approved bot applied label for PR's where reviewer approves changes labels Jan 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: merged bot applied label for PR's that are merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants