GoogleContainerTools/skaffold

Should Event API follow CNCF's Cloud Events

Open

#4,259 opened on May 26, 2020

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Go (1,416 forks)batch import
area/eventinggood first issuehelp wantedidekind/feature-requestpriority/p2

Repository metrics

Stars
 (12,822 stars)
PR merge metrics
 (Avg merge 3d 6h) (16 merged PRs in 30d)

Description

We should consider standardizing our Event API to follow CNCF's https://cloudevents.io/ standard.

Benefits: better alignment with the space, standardized format which aligns better with best practices Cons: IDEs will need to restructure their clients

Thoughts?

Contributor guide

Research direction
Study the CNCF CloudEvents specification and compare with Skaffold's current Event API. Identify gaps and propose a migration plan.
Tech stack
go
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoCloudEvents
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65