-
Notifications
You must be signed in to change notification settings - Fork 3
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
Get ready for publish on Hex.pm #17
Conversation
I'll proceed later with a full review, for now I'll just leave this here: ❯ nix run nixpkgs#reuse lint
# MISSING COPYRIGHT AND LICENSING INFORMATION
The following files have no copyright and licensing information:
* .check.exs
* .credo.exs
* .github/workflows/ci.yaml
* .tool-versions |
6020d05
to
4b12b99
Compare
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.
Technically REUSE still doesn't pass because it wants the licenses under LICENSES.
Not sure if we want that (I'd say we do though?), but in case you can use reuse download --all
to let it add them for you
mix.exs
Outdated
""" | ||
A framework for handling distributed processing of data | ||
over AMQP queues. Ordering guarantees are provided. | ||
""" |
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 would personally not force a line break here
""" | |
A framework for handling distributed processing of data | |
over AMQP queues. Ordering guarantees are provided. | |
""" | |
""" | |
A framework for handling distributed processing of data \ | |
over AMQP queues. Ordering guarantees are provided. | |
""" |
Add relevant fields in mix.exs and pimp the README.md. Signed-off-by: Arnaldo Cesco <[email protected]>
Signed-off-by: Arnaldo Cesco <[email protected]>
4b8947e
to
fb1d6a7
Compare
Update copyright header everywhere and run - `reuse init` - `reuse downlad --all` Signed-off-by: Arnaldo Cesco <[email protected]>
fb1d6a7
to
3c60bb4
Compare
Standard chores for releasing and publishing on Hex.
I suggest we do this before merging #15 (even though the PR is good and ready), as moving into Erlang distribution territory is quite a huge task.
Also, some administrative tasks are to be done in the context of this PR, such as making this repo public and deciding who will publish the library