Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider how to document and manage OSS vs proprietary taps #13

Open
MeltyBot opened this issue Apr 16, 2021 · 1 comment
Open

Consider how to document and manage OSS vs proprietary taps #13

MeltyBot opened this issue Apr 16, 2021 · 1 comment
Labels
kind/Risk migrated from gitlab valuestream/Ecosystem

Comments

@MeltyBot
Copy link
Contributor

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/12

Originally created by @tayloramurphy on 2021-04-16 19:25:56

It came up in discussion about how people might want to use the hub for proprietary and unlisted use cases. The spec and the base design of the SingerHub should be built thinking about this at the start.

I'd estimate the following % for each type:

Code-type Listed Unlisted
OSS 90% <1%
Proprietary 5% <5%

We're going to focus most of our effort on the open source community, but will build will related use cases in mind.
@MeltyBot
Copy link
Contributor Author

View 1 previous comment from the original issue on GitLab

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/Risk migrated from gitlab valuestream/Ecosystem
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MeltyBot