search

cta-wave / content-specification-task-force

13 stars 0 forks source link

2018 Content Spec - CTA Legal Boilerplate #4

Closed johnsim closed 6 years ago

johnsim commented 6 years ago

CTA legal boilerplate. I did not adopt the proposed change – but instead will advise CTA that they need to review the use of CEA versus CTA in their boilerplate.

johnsim commented 6 years ago

Bill Rose to follow up with Mike to see if this is resolved.

gitwjr commented 6 years ago

Emailed Mike. Waiting to hear back.

Bill

From: John Simmons notifications@github.com Sent: Wednesday, April 25, 2018 10:34 AM To: cta-wave/content-specification-task-force content-specification-task-force@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [cta-wave/content-specification-task-force] 2018 Content Spec - CTA Legal Boilerplate (#4)

Bill Rose to follow up with Mike to see if this is resolved.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cta-wave/content-specification-task-force/issues/4#issuecomment-384308934 , or mute the thread https://github.com/notifications/unsubscribe-auth/APEdgkO4xcohh75gp3LapTEBOPAqjxIqks5tsIlGgaJpZM4Ti5rM . https://github.com/notifications/beacon/APEdgt4uqakKEYqD47cNXJADuto4L4JTks5tsIlGgaJpZM4Ti5rM.gif

johnsim commented 6 years ago

This issue was resolved before publication of the April 2018 draft.