Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Draft design goals for CloudEvents specification (#101)
* Draft design goals for CloudEvents specification Signed-off-by: Sarah Allen <sarahallen@google.com> * address feedback, wrap at 80 cols Signed-off-by: Sarah Allen <sarahallen@google.com> * address feedback - move WG process into readme, with link to spec & goals - clarify that triggers can be custom to the system using CloudEvents - allow for run-time configuration Signed-off-by: Sarah Allen <sarahallen@google.com> * move design goals into spec Signed-off-by: Sarah Allen <sarahallen@google.com> * typo s/./:/ Signed-off-by: Sarah Allen <sarahallen@google.com> * fix link Signed-off-by: Sarah Allen <sarahallen@google.com> * Remove product references; typos Signed-off-by: Rachel Myers <rachelmyers@google.com> * Typo fixes 🎨 Signed-off-by: Rachel Myers <rachelmyers@google.com> * simplified design goals based on community discussions Signed-off-by: Sarah Allen <sarahallen@google.com> * remove non-goals from README (since it is now in the spec) also fixed formatting of non-goals section of spec Signed-off-by: Sarah Allen <sarahallen@google.com> * must => MUST Signed-off-by: Sarah Allen <sarahallen@google.com> * process language more generic to be consistent with design goals We decided to avoid terms that are in the spec in the overview and goals, at least until we align on definitions, then we can revise later if that seems helpful. This edit fixes process section of README to be consistent with that philosophy. Signed-off-by: Sarah Allen <sarahallen@google.com> * shift back to using general term (must => can) Signed-off-by: Sarah Allen <sarahallen@google.com>
- Loading branch information