search

usdot-jpo-ode / wzdx

The Work Zone Data Exchange (WZDx) Specification aims to make harmonized work zone data provided by infrastructure owners and operators (IOOs) available for third party use, making travel on public roads safer and more efficient through ubiquitous access to data on work zone activity.
Creative Commons Zero v1.0 Universal
90 stars 62 forks source link

Include explicit licensing information in the RoadEventFeedInfo #151

Closed DeraldDudley closed 3 years ago

DeraldDudley commented 3 years ago

Reference Issue #19

This PR assigns a Creative Commons - Public Domain License (CC0) to a feed. A license property will be added to the RoadEventFeedInfo object. Its value will be "CC0"

Defining an explicit public domain license to the WZ Data frees consumers to publish WZ information.

j-d-b commented 3 years ago

@DeraldDudley these license-related changes should be made in a new branch specific to those changes, branches off of spring-2021-release, rather than to spring-2021-release as you did here. Then, the PR should target spring-2021-release as the base branch, that it, it proposes merging your new branch with the version changes into spring-2021-release.

Thus we need to:

  1. Close this PR
  2. Roll back commit 52c4cae on spring-2021-release
  3. Create a new branch from spring-2021-release for use for these changes, called something like add-license
  4. Make the changes originally made in commit 52c4cae to add-license
  5. Make a new PR proposing merging add-license into spring-2021-release

I will do 1 and 2. Let me know if you can do the rest.

Edit: 1 and 2 complete

j-d-b commented 3 years ago

Closed as the changes should be made in a branch specific to those changes, not the base spring-2021-release branch.

DeraldDudley commented 3 years ago

Thanks Jacob.

Derald Dudley NGDA Transportationhttps://communities.geoplatform.gov/ngda-transportation/ Theme Lead FGDC Transportation Subcommitteehttps://communities.geoplatform.gov/ngda-transportation/transportation-subcommittee/ Chair Phone: 202.309.0940 Pronouns: he/him/his

The Office of Spatial Analysis and Visualizationhttp://maps.bts.dot.gov/ Bureau of Transportation Statisticshttp://www.rita.dot.gov/bts/ Office of the Assistant Secretary of Transportation for Research and Technologyhttp://www.rita.dot.gov/ United States Department of Transportationhttp://www.transportation.gov/

From: Jacob Brady [mailto:notifications@github.com] Sent: Thursday, December 17, 2020 2:23 PM To: usdot-jpo-ode/jpo-wzdx jpo-wzdx@noreply.github.com Cc: Dudley, Derald (OST) Derald.Dudley@dot.gov; Mention mention@noreply.github.com Subject: Re: [usdot-jpo-ode/jpo-wzdx] Include explicit licensing information in the RoadEventFeedInfo (#151)

CAUTION: This email originated from outside of the Department of Transportation (DOT). Do not click on links or open attachments unless you recognize the sender and know the content is safe.

@DeraldDudleyhttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDeraldDudley&data=04%7C01%7Cderald.dudley%40dot.gov%7Cfcb89d23fbeb4209ad8608d8a2c13dde%7Cc4cd245b44f04395a1aa3848d258f78b%7C0%7C0%7C637438298135863707%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=se9jwUArp2OxOyjc%2Be9udZlMXrxvB6F80SKgMftf0Cc%3D&reserved=0 these license-related changes should be made in a new branch specific to those changes, branches off of spring-2021-release, rather than to spring-2021-release as you did here. Then, the PR should target spring-2021-release as the base branch, that it, it proposes merging your new branch with the version changes into spring-2021-release.

Thus we need to:

  1. Close this PR
  2. Roll back commit 52c4caehttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fusdot-jpo-ode%2Fjpo-wzdx%2Fcommit%2F52c4cae776857df86c7ed8c010d8afc471f3134b&data=04%7C01%7Cderald.dudley%40dot.gov%7Cfcb89d23fbeb4209ad8608d8a2c13dde%7Cc4cd245b44f04395a1aa3848d258f78b%7C0%7C0%7C637438298135873660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=J5fvhHRsY7BktP2RGdbSQIiXrZBtYpk68kHRZcX90oQ%3D&reserved=0 on spring-2021-release
  3. Create a new branch from spring-2021-release for use for these changes, called something like add-license
  4. Make the changes originally made in commit 52c4caehttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fusdot-jpo-ode%2Fjpo-wzdx%2Fcommit%2F52c4cae776857df86c7ed8c010d8afc471f3134b&data=04%7C01%7Cderald.dudley%40dot.gov%7Cfcb89d23fbeb4209ad8608d8a2c13dde%7Cc4cd245b44f04395a1aa3848d258f78b%7C0%7C0%7C637438298135873660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=J5fvhHRsY7BktP2RGdbSQIiXrZBtYpk68kHRZcX90oQ%3D&reserved=0 to add-license
  5. Make a new PR proposing merging add-license into spring-2021-release

I will do 1 and 2.

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fusdot-jpo-ode%2Fjpo-wzdx%2Fpull%2F151%23issuecomment-747647407&data=04%7C01%7Cderald.dudley%40dot.gov%7Cfcb89d23fbeb4209ad8608d8a2c13dde%7Cc4cd245b44f04395a1aa3848d258f78b%7C0%7C0%7C637438298135873660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lP4fTacPROw%2FRXz7NuP8cv4VDgSlPGfWJqFIB3T0SoA%3D&reserved=0, or unsubscribehttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB2LFGWC5QY5HLYGLP46WX3SVJLDDANCNFSM4U76HGSA&data=04%7C01%7Cderald.dudley%40dot.gov%7Cfcb89d23fbeb4209ad8608d8a2c13dde%7Cc4cd245b44f04395a1aa3848d258f78b%7C0%7C0%7C637438298135883615%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=OdbSFpcPVmKhEJlSDQtIsHGKK5OIkVdPsSxBP8%2BVAXc%3D&reserved=0.