Skip to content

Conversation

@daviddias
Copy link
Member

No description provided.

@daviddias daviddias requested a review from alanshaw January 4, 2019 06:47
@ghost ghost assigned daviddias Jan 4, 2019
@ghost ghost added the status/in-progress In progress label Jan 4, 2019
```
[commit]
template = /home/user/git-commit-template
```
Copy link
Member Author

@daviddias daviddias Jan 4, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not required anymore as instructed by @ianjdarrow

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, what is the reason?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW I'm +1 on this - it's a significant hurdle to also ask a new contributor to add a commit sign off message.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just FYI for anyone else reading this, it's not required if we switch to a dual MIT+Apache2 licence since the Apache2 licence states:

Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if it should be still part of the guide until we've switched to MIT+Apache.

"test"
]
```

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think our guideline should be to have a lint task run on pre-commit/push. It's a quick thing to run and saves a big round trip waiting for CI to fail. We don't need to mandate the specific module to use.

It appears to be in approval from the team ipfs/js-ipfs#1705

### Commits

We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the change log.
We have very precise guidelines over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the change log.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is the correct sentiment - I do not enforce this with new/existing contributors and it's trivial to correct in github with a squash+merge.

```
[commit]
template = /home/user/git-commit-template
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, what is the reason?

We suggest either of these:

- [david-dm](https://david-dm.org/)
- [greenkeeper](http://greenkeeper.io/) to keep your dependencies up to date.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to add the Greenkeeper works well for IPLD. So we might reconsider using it. It changed a lot since it abandoned the last time.

```
[commit]
template = /home/user/git-commit-template
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if it should be still part of the guide until we've switched to MIT+Apache.

@daviddias
Copy link
Member Author

Missing License update coming with ipfs/team-mgmt#849

@daviddias daviddias removed their assignment Jan 27, 2019
@terichadbourne
Copy link
Contributor

Just flagging the existence of this issue since it seems like it was awaiting the switch to MIT + Apache licensing that's now underway elsewhere. :)

@alanshaw
Copy link
Member

alanshaw commented Nov 27, 2019

ipfs/js-ipfs#2624 and ipfs-inactive/js-ipfs-http-client#1189 but they are the tip of the iceberg.

@daviddias daviddias closed this Feb 25, 2020
@daviddias daviddias deleted the daviddias-patch-2 branch February 25, 2020 06:20
@alanshaw alanshaw mentioned this pull request Mar 3, 2020
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants