Re: [ANN] tentacles fork on clojars - raynes' legacy lives on!

2017-03-18 Thread James Laver
Oops, that went out with a boot-test dependency (thanks for the spot, coda 
hale!)

Please find [irresponsible/tentacles "0.6.1"] on clojars.

And this time I'll spell 'github' correctly: 
https://github.com/irresponsible/tentacles

/j

On Saturday, March 18, 2017 at 9:19:08 AM UTC+1, James Laver wrote:
>
> Hi all,
>
> Further to previous discussions, we (the irresponsible clojure guild) have 
> forked tentacles and intend to keep it maintained and improved.
>
> This is our first release of tentacles under the irresponsible group and 
> we have resumed versioning from Raynes' versions.
>
> github: https://gthub.com/irresponsible/tentacles/
> dep coord: [irresponsible/tentacles "0.6.0"]
>
> Changelog:
>
>- Reviewed every open bug and pull request
>- Merged the majority of PRs, did the rest ourselves
>- Bumped deps and updated docs
>- Started keeping changelog
>- Fixed reported documentation issues
>- Moved to boot so we can ship it like any other irresponsible lib
>
> Bugs fixed:
>
>- Requests error out when the body is not json 
>
>- Update to new watch endpoint 
>
>- Conditional request and :all-pages true option didn't play nicely 
>
>- Collection responses have an extra empty map as the last element 
>
>
> Features added:
>
>- Notifications api 
>- Reactions api  (GET 
>only at present)
>
>
> Finally, a massive shout out to the other main contributor of the ICG, 
> Kent Fredric, who managed to get this release out despite tripping over a 
> bunch of boot failure in the process.
>
>
> Cheers,
>
> James
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ANN] tentacles fork on clojars - raynes' legacy lives on!

2017-03-18 Thread James Laver
Hi all,

Further to previous discussions, we (the irresponsible clojure guild) have 
forked tentacles and intend to keep it maintained and improved.

This is our first release of tentacles under the irresponsible group and we 
have resumed versioning from Raynes' versions.

github: https://gthub.com/irresponsible/tentacles/
dep coord: [irresponsible/tentacles "0.6.0"]

Changelog:

   - Reviewed every open bug and pull request
   - Merged the majority of PRs, did the rest ourselves
   - Bumped deps and updated docs
   - Started keeping changelog
   - Fixed reported documentation issues
   - Moved to boot so we can ship it like any other irresponsible lib

Bugs fixed:

   - Requests error out when the body is not json 
   
   - Update to new watch endpoint 
   
   - Conditional request and :all-pages true option didn't play nicely 
   
   - Collection responses have an extra empty map as the last element 
   

Features added:

   - Notifications api 
   - Reactions api  (GET 
   only at present)


Finally, a massive shout out to the other main contributor of the ICG, Kent 
Fredric, who managed to get this release out despite tripping over a bunch 
of boot failure in the process.


Cheers,

James

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Raynes' legacy

2017-02-27 Thread James Laver
Hi Matthew,

On Monday, February 27, 2017 at 5:11:19 AM UTC+1, Matthew Boston wrote:
>
> I'm happy to hear that others are willing to step up to the plate in 
> regards to continuing Anthony's legacy.
>
> I started a thread specifically about tentacles a month ago here: 
> https://groups.google.com/forum/#!searchin/clojure/tentacles%7Csort:relevance/clojure/15x_LWE2IMM/CGULJTXLBQAJ
>

Ah yes, I remember it, I had merely forgotten it was about tentacles :)
 

> We, at CircleCI, have built our entire business around the use of 
> tentacles, so seeing this library succeed is paramount to our success. 
> Right now, we're on an older version of tentacles and we're currently 
> working to upgrade to the latest so we can begin to maintain a fork; or at 
> the very least, help others in maintaining a "de facto fork".
>

This is for an open source project I will be starting work on soon, not 
something business critical, but on the bright side, it'll be "up to date" 
when I start. 

Personally I'd be quite happy to see CircleCI take over maint of tentacles. 
You have a trusted name and reputation and you have a good incentive to 
keep improving the code. We will still offer to take whatever of Raynes' 
modules people haven't started maintaining de facto forks of.

Cheers,
James

On Saturday, February 25, 2017 at 12:09:02 AM UTC-7, James Laver wrote:
>
> I'm pleased we've dealt with a new maintainer for a couple of Raynes' 
> modules, but Raynes contributed a lot of things and half the community 
> depends on one or more of his modules at this point.
>
> My current focus is tentacles, which has been gathering issues and PRs 
> recently and is something I'm about to use in a project. If no-one else 
> steps forward, we at the irresponsible clojure guild ( 
> https://github.com/irresponsible ) will take on the maintenance for it, 
> but we don't want to end up causing multiple forks.
>
> I think it would be awesome if *somebody* would step up and take care of 
> Raynes' remaining modules. Aside from being his legacy, they're really 
> useful and too many of rely on them. Irresponsible is a community-run 
> organisation (currently just three of us). If more people were willing to 
> pitch in with reviewing PRs and issues and such, we would be happy to 
> assume responsibility for releases. In effect, we're happy to keep Raynes' 
> work alive rather than bitrotting. But we can't do all of that alone, it's 
> just too much work (something other contributors have noted). We are happy 
> to give them a home and push releases, but there are simply too many of 
> them to take up proper maintenance without more volunteers
>
> So, with that:
>
> 1. Does this seem like a good idea?
> 2. Can you help with reviewing the backlog on Raynes' modules?
> 3. Is this going to be enough to prevent multiple forks of everything?
>
> Cheers,
> James
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Raynes' legacy

2017-02-26 Thread Matthew Boston
I'm happy to hear that others are willing to step up to the plate in 
regards to continuing Anthony's legacy.

I started a thread specifically about tentacles a month ago 
here: 
https://groups.google.com/forum/#!searchin/clojure/tentacles%7Csort:relevance/clojure/15x_LWE2IMM/CGULJTXLBQAJ

We, at CircleCI, have built our entire business around the use of 
tentacles, so seeing this library succeed is paramount to our success. 
Right now, we're on an older version of tentacles and we're currently 
working to upgrade to the latest so we can begin to maintain a fork; or at 
the very least, help others in maintaining a "de facto fork".

On Saturday, February 25, 2017 at 12:09:02 AM UTC-7, James Laver wrote:
>
> I'm pleased we've dealt with a new maintainer for a couple of Raynes' 
> modules, but Raynes contributed a lot of things and half the community 
> depends on one or more of his modules at this point.
>
> My current focus is tentacles, which has been gathering issues and PRs 
> recently and is something I'm about to use in a project. If no-one else 
> steps forward, we at the irresponsible clojure guild ( 
> https://github.com/irresponsible ) will take on the maintenance for it, 
> but we don't want to end up causing multiple forks.
>
> I think it would be awesome if *somebody* would step up and take care of 
> Raynes' remaining modules. Aside from being his legacy, they're really 
> useful and too many of rely on them. Irresponsible is a community-run 
> organisation (currently just three of us). If more people were willing to 
> pitch in with reviewing PRs and issues and such, we would be happy to 
> assume responsibility for releases. In effect, we're happy to keep Raynes' 
> work alive rather than bitrotting. But we can't do all of that alone, it's 
> just too much work (something other contributors have noted). We are happy 
> to give them a home and push releases, but there are simply too many of 
> them to take up proper maintenance without more volunteers
>
> So, with that:
>
> 1. Does this seem like a good idea?
> 2. Can you help with reviewing the backlog on Raynes' modules?
> 3. Is this going to be enough to prevent multiple forks of everything?
>
> Cheers,
> James
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Raynes' legacy

2017-02-24 Thread James Laver
I'm pleased we've dealt with a new maintainer for a couple of Raynes' 
modules, but Raynes contributed a lot of things and half the community 
depends on one or more of his modules at this point.

My current focus is tentacles, which has been gathering issues and PRs 
recently and is something I'm about to use in a project. If no-one else 
steps forward, we at the irresponsible clojure guild ( 
https://github.com/irresponsible ) will take on the maintenance for it, but 
we don't want to end up causing multiple forks.

I think it would be awesome if *somebody* would step up and take care of 
Raynes' remaining modules. Aside from being his legacy, they're really 
useful and too many of rely on them. Irresponsible is a community-run 
organisation (currently just three of us). If more people were willing to 
pitch in with reviewing PRs and issues and such, we would be happy to 
assume responsibility for releases. In effect, we're happy to keep Raynes' 
work alive rather than bitrotting. But we can't do all of that alone, it's 
just too much work (something other contributors have noted). We are happy 
to give them a home and push releases, but there are simply too many of 
them to take up proper maintenance without more volunteers

So, with that:

1. Does this seem like a good idea?
2. Can you help with reviewing the backlog on Raynes' modules?
3. Is this going to be enough to prevent multiple forks of everything?

Cheers,
James

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.