Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
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
track opam file metadata in dune-project and rewrite opam files #2017
track opam file metadata in dune-project and rewrite opam files #2017
Changes from all commits
ca0f643
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The authors list is an interesting one. I think we should encourage the listing of individual contributions as well in order to keep this accurate. What do you think about having a general
author
schema that could beThe idea here is that maintainers are always authors, and that we are flexible about how to identify someone. A string starting with @ is assumed to be github by default.
(this can probably be deferred for a future PR, but I just thought about it now!)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I always wonder what to put in this field BTW. For instance, should it be every single person who submitted a PR? The "Insights" tab is much more precise in this regard.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a value judgement of "significant contributions". So a typo fix doesnt cut it, but a reasonably small feature that adds some code does.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright. BTW, are maintainers really always authors? For instance, there are debian maintainers of the dune package that are not authors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's true for packages (since its a metadata overlay), but not (I think) ever true for source repos of the sort dune manages. It does mean we'll need a package-specific maintainer field in the package manager areas. So in the
(opam)
clause we could also allow a maintainer field in the future to override the global one in this PR.I'm thinking that in the medium term dune or extensions can make smarter use of the global fields in order to improve error messages. For instance a build failure could be automatically uploaded to a github issue in the right repo, or dune could even search online for messages from the
maintainers
who answer FAQs.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. That makes sense. So I guess the way to describe these fields is: