Clarify what duffle is intended for #739
Conversation
Duffle is the reference implementation of the spec. Point people to some of the community tools if they want to build new bundles.
carolynvs
requested review from
bacongobbler,
glyn,
jeremyrickard,
radu-matei,
silvin-lubecki and
vdice
as code owners
ghost
assigned 
|
I am not sure I like the way this is phrased. I don't feel like we should say that we don't recommend using Duffle for the things that it is built to be able to do. It is fine with me if you state that Duffle is a low-level tool designed to show how the specification should work, and that there are other tools that make bundle building easier. But it is not good to imply that one should not use the tool (or even imply that). To that point, if Duffle is that bad at building bundles, it really should be fixed. (Though the feedback I got was that it was the documentation that was misleading.) |
README.md
Outdated
|
|
||
| The community has created implementations of the CNAB spec with | ||
| [opinionated takes on authoring bundles][cnab-tools]. Some even use Duffle's | ||
| [libraries][cnab-go] to handle the CNAB implementation. If you want to make your own CNAB tooling, that is a great place to start! |
There was a problem hiding this comment.
Shouldn't the link libraries point to the libraries list on cnab.io, as there are multiple libraries (rust, python, .net) other than go?
There was a problem hiding this comment.
Oops! Yes, thank you good catch!
Duffle is the reference implementation of the spec. We should point people to the the community tools if they want to build new bundles so that they don't assume that duffle is the official tool for that, and get frustrated when it's super hard. 馃榾
We keep a list of community run projects, like Docker Apps and Porter, that we can point to so that people can find a tool to fit their needs. I have an open PR to add Docker Apps to that page, but would like a review from someone at Docker first before I merge it. Maybe @silvin-lubecki can take a look?