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.

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

Some attribution work #1276

Merged
merged 5 commits into from
Aug 10, 2016
Merged

Some attribution work #1276

merged 5 commits into from
Aug 10, 2016

Conversation

ceedubs
Copy link
Contributor

@ceedubs ceedubs commented Aug 9, 2016

This is inspired by #1275. It doesn't include a CLA, and there is
most likely more work that should be done with respect to attribution,
but I'm hoping that this is a step in the right direction.

I've added a link to the scalaz contributors page within AUTHORS.md.
I'm not sure who all out of that should and would want to be directly listed
in the authors page for Cats. I've explicitly added Brian McKenna to the
authors page, as my understanding of this
tweet
is that
he would like to be on there.

@puffnfresh, if you care to, please let me know if there is any way that I could improve this.

This is inspired by typelevel#1275. It doesn't include a CLA, and there is
most likely more work that should be done with respect to attribution,
but I'm hoping that this is a step in the right direction.

I've added a link to the scalaz contributors page within AUTHORS.md.
I'm not sure who all out of that should and would want to be directly listed
in the authors page for Cats. I've explicitly added Brian McKenna to the
authors page, as my understanding of [this
tweet](https://twitter.com/puffnfresh/status/762901748772057088) is that
he would like to be on there.
@mpilquist
Copy link
Member

👍 Thanks

@@ -98,6 +99,12 @@ possible:
* yilinwei
* Zach Abbott

Cats has been heavily inspired by [scalaz](https://github.com/scalaz/scalaz),
and some Cats code is only a slightly modified version of code originating in
scalaz. Therefore, we'd also like to credit and thank all of the
Copy link
Contributor

Choose a reason for hiding this comment

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

This is nitpicky, but maybe capitalize "scalaz" throughout for consistency with "Cats" and other project names here, and with the Scalaz README?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍 thanks good catch. I tend to capitalize Cats to make it clear that I'm talking about the project and not the group of animals, but I definitely didn't mean to be inconsistent here.

@milessabin
Copy link
Member

milessabin commented Aug 9, 2016

I'm pretty sure that NotNothing was derived from a gist of mine way back when.

@@ -98,6 +99,12 @@ possible:
* yilinwei
* Zach Abbott

Cats has been heavily inspired by [scalaz](https://github.com/scalaz/scalaz),
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggestion:

Cats has been inspired by many libraries, including Scalaz, Haskell's Prelude, and others. In particular, some Cats code is only…

To acknowledge stuff like witherable, etc.?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍 sorry I missed this when you first posted it.

@milessabin
Copy link
Member

Yes, here ... itself derived from an earlier uses of ambiguity to encode negation.

@ceedubs
Copy link
Contributor Author

ceedubs commented Aug 9, 2016

As @milessabin points out, ambiguous implicits are a Scala trick that has been around for a while and are essentially folklore at this point (and specifically his gist shows usage of checking that a type is not Nothing long before Scalaz's NotNothing). I think that what I probably should have done instead is attribute Brian on the catchOnly methods that are inspired by similar methods in Scalaz. I'll update my PR accordingly.

@codecov-io
Copy link

codecov-io commented Aug 9, 2016

Current coverage is 90.53% (diff: 100%)

Merging #1276 into master will decrease coverage by 0.02%

@@             master      #1276   diff @@
==========================================
  Files           243        243          
  Lines          3285       3286     +1   
  Methods        3228       3229     +1   
  Messages          0          0          
  Branches         55         55          
==========================================
  Hits           2975       2975          
- Misses          310        311     +1   
  Partials          0          0          

Sunburst

Powered by Codecov. Last update 97fc762...4117f4e

@travisbrown
Copy link
Contributor

👍

1 similar comment
@kailuowang
Copy link
Contributor

👍

@aloiscochard
Copy link

Thanks for the effort @ceedubs and @adelbertc, appreciated!

Just giving my opinion here as Adelbert did ask for it, just keep in mind that with only 4 commits I do not consider myself as a scalaz7 contributor at all.

That being said, in the process of writing a functional library that is fast, I steel ideas from @non whenever I can, and I would expect anybody to do the same with all the great ideas appearing in the diversity of open source projects around.

I like what you are doing here in term of attribution, and in essence it's how I did it (https://github.com/scalaz/scalaz/blob/series/8.0.x/meta/src/main/scala/Ops.scala#L6), once we'll move forward formalizing more the approach, I'll definitely push into following a similar process as the one put in place here.

👍

@ceedubs
Copy link
Contributor Author

ceedubs commented Aug 10, 2016

@aloiscochard thank you, I really appreciate the feedback.

I'm going to go ahead and merge this, and if @puffnfresh has any further feedback, I can address it in a separate PR.

@ceedubs ceedubs merged commit f2bfecb into typelevel:master Aug 10, 2016
@ceedubs ceedubs deleted the attributions branch August 10, 2016 13:15
@raulraja raulraja mentioned this pull request Aug 11, 2016
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants