Skip to content

move references out of the specification into supporting material#89

Closed
ultrasaurus wants to merge 2 commits into
cloudevents:masterfrom
ultrasaurus:references
Closed

move references out of the specification into supporting material#89
ultrasaurus wants to merge 2 commits into
cloudevents:masterfrom
ultrasaurus:references

Conversation

@ultrasaurus
Copy link
Copy Markdown
Contributor

addresses #19

  • named directory /about since that is the name of the directory in work-in-progress PR starter doc explaining key concepts from the spec #53
  • proposed /landscape sub-directory, since I thought it would be nice to refactor this later into an area with a page for each product/software that implements this type of a system -- currently is for historical context, but in the future could contain references to systems that implement the spec

Signed-off-by: Sarah Allen sarahallen@google.com

Signed-off-by: Sarah Allen <sarahallen@google.com>
Comment thread about/landscape/README.md Outdated
@@ -0,0 +1,129 @@
Prior to the CloudEvents specification, many systems implemented similar models for events that allowed late-binding of services to actions.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

can you wrap this at 80 cols?

@duglin
Copy link
Copy Markdown
Collaborator

duglin commented Feb 20, 2018

Do we need a 2-level dir structure just for one file? I'd prefer to not create dirs until we have more than one file that lives in the dir.

Also, we'll need some kind of pointer to that file (e.g. from top README?), otherwise its just dangling and no one will find it.

@duglin
Copy link
Copy Markdown
Collaborator

duglin commented Feb 20, 2018

travis error looks real:

Running href checker:
> ./about/landscape/README.md
> ./CONTRIBUTING.md
> ./GOVERNANCE.md
> ./README.md
> ./roadmap.md
> ./spec.md
./spec.md: Can't find section '#reference' in ./spec.md

Signed-off-by: Rachel Myers <rachelmyers@google.com>
@duglin
Copy link
Copy Markdown
Collaborator

duglin commented Mar 14, 2018

@ultrasaurus can you fix the bad href?

@duglin
Copy link
Copy Markdown
Collaborator

duglin commented Mar 14, 2018

oh and a rebase is needed

@duglin
Copy link
Copy Markdown
Collaborator

duglin commented Mar 24, 2018

I believe this one can be closed - all of the edits appear to already be done via some other PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants