Skip to content
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.

Chaotic directory structure of eventing-contrib #508

Closed
daisy-ycguo opened this issue Aug 6, 2019 · 1 comment · Fixed by #526
Closed

Chaotic directory structure of eventing-contrib #508

daisy-ycguo opened this issue Aug 6, 2019 · 1 comment · Fixed by #526
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Comments

@daisy-ycguo
Copy link
Member

daisy-ycguo commented Aug 6, 2019

Expected Behavior

All event sources are stored in clear directory structure and easy to locate.

Actual Behavior

There are several event sources. Some are in eventing-contrib repo, some are in eventing repo, and some are in both. Even the structure of sources in eventing-contrib repo is chaotic. It's hard for new comers to locate. And new contributors don't know which directory to contribute.

Sources under eventing-contrib are in chaotic structure:

  • camel/source
  • gcppubsub
  • kafka/source
  • contrib/awssqs
  • contrib/github

Sources under eventing are in good shape structure:

  • contrib/gcppubsub
  • contrib/kafka
  • contrib/natss

gcppubsub and kafka are in both.

Steps to Reproduce the Problem

  1. Review the directory structure of eventing-contrib

Additional Info

  1. The directory structure of every event source is in good shape. So we just need to restructure eventing-contrib and get a clear structure.
  2. Better to clear document which directory an event source contributor shall go to.
@grantr
Copy link
Contributor

grantr commented Aug 6, 2019

/kind cleanup

@knative-prow-robot knative-prow-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Aug 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants