Rb-appscript: requesting ownership

I reached out to the original author, Hamish, about taking
ownership on RubyGems. He's given his consent. All the necessary
context is in this Github
discussion. The earlier links are just provided for context.
Could someone please help transfer ownership to myself and RubyGems
user BrendanThompson?

Let me know if I can do anything more with this issue to move it
forward. Thanks!

to me
hhas
Hengist Podd sent you a message:
If Brendan wants it he's totally welcome to it; surprised he never asked
before posting his fork. Or Matt, but I think Brendan's version has made
more progress. Honestly, they should throw in together if they really care
about it. He'll need to contact the RubyGems maintainers to get it
transferred as I can't log into it any more. As far as modernizing the C
portion, replacement Cocoa APIs are available in NSAppleEventDescriptor
(10.11+) and NSWorkspace. It's years since I did any Ruby, and never did
much like it or have a clue how to build [Obj-]C extensions for it (I just
nicked that bit from RubyOSA), so can't offer you any advice beyond 1.
refer to SwiftAE [https://bitbucket.org/hhas/swiftae/] for pointers [sic]
on using the relevant Cocoa APIs, and 2. Apple doesn't give a crap about
Mac Automation any more and seems perfectly happy letting it die off from
mismanagement and neglect, so caveat emptor as far as long-term prospects
are concerned. HTH has

In reply to Eric Hu
Eric Hu sent you a message on Bitbucket: Hi there, I'm writing this for
Hamish Sanderson, original author of Appscript. If this is you, please read
on. If not, you can stop here (though I would appreciate a short note
letting me know I've reached the wrong person). First off, I'd like to say
I'm a happy user of your work. I used rb-appscript for years without
realizing it, via the Consular gem. Over the last several months, I've been
tracking down an issue with Consular that depends on rb-appscript. I
eventually tracked down the issue and reported it in what I thought was the
source repo.[1] It turns out that I reported it to a fork, and the issue
was actually resolved in that repo. Unfortunately other gem developers
don't benefit from this change since it's not reflected on Rubygems. If you
still have control of the rb-appscript gem on Rubygems.org, would you be
open to transferring it to someone else? Two viable candidates would be
Matt Neuburg and Brendan Thompson. Matt forked appscript and ported it to
Github[2]. Brendan forked just the Ruby portion of the repo[3] and created
his own gem to solve his problem with jira-omnifocus[4]. It looks like
there's lots of users who have benefitted from your past work, myself among
them. I'm hoping that I'll be able to easily use your work in the future as
well. In any event, thank you for taking the time to read this message and
thank you for your hard work on appscript. Cheers, Eric [1]
https://github.com/mattneub/appscript/issues/12#issuecomment-164085415 [2]
https://github.com/mattneub/appscript [3]
https://github.com/BrendanThompson/rb-scpt [4]
https://github.com/devondragon/jira-omnifocus/issues/13

I found your email on your Github profile after using your rb-scpt
gem. Thank you for forking it, separating the Ruby source, and
publishing a new gem. I was trying to fix an issue with
consular-iterm and your repo helped make that possible.

I don't know what your intentions are for rb-scpt, but would you be
open to taking over rb-appscript on Rubygems? I already have
permission from Hamish: that conversation is included below. Taking
the actual gem will require talking to the people at Rubygems. I'm
happy to take care of that to see that rb-appscript gets some
continuity.

Matt Neuberg maintains a fork of Hamish's code on Github as well.
I've had this conversation with him as well, though he hasn't
expressed much interest in maintenance going forward.[1]

What do you think? Just say the word and I'll reach out to the
Rubygems people. If it'll make the decision easier, I'm happy to help
maintain the gem and review pull requests.

Hengist Podd sent you a message:
If Brendan wants it he's totally welcome to it; surprised he never
asked before posting his fork. Or Matt, but I think Brendan's version
has made more progress. Honestly, they should throw in together if
they really care about it. He'll need to contact the RubyGems
maintainers to get it transferred as I can't log into it any more. As
far as modernizing the C portion, replacement Cocoa APIs are available
in NSAppleEventDescriptor (10.11+) and NSWorkspace. It's years since I
did any Ruby, and never did much like it or have a clue how to build
[Obj-]C extensions for it (I just nicked that bit from RubyOSA), so
can't offer you any advice beyond 1. refer to SwiftAE
[https://bitbucket.org/hhas/swiftae/] for pointers [sic] on using the
relevant Cocoa APIs, and 2. Apple doesn't give a crap about Mac
Automation any more and seems perfectly happy letting it die off from
mismanagement and neglect, so caveat emptor as far as long-term
prospects are concerned. HTH has
View inbox
In reply to Eric Hu
Eric Hu sent you a message on Bitbucket: Hi there, I'm writing this
for Hamish Sanderson, original author of Appscript. If this is you,
please read on. If not, you can stop here (though I would appreciate a
short note letting me know I've reached the wrong person). First off,
I'd like to say I'm a happy user of your work. I used rb-appscript for
years without realizing it, via the Consular gem. Over the last
several months, I've been tracking down an issue with Consular that
depends on rb-appscript. I eventually tracked down the issue and
reported it in what I thought was the source repo.[1] It turns out
that I reported it to a fork, and the issue was actually resolved in
that repo. Unfortunately other gem developers don't benefit from this
change since it's not reflected on Rubygems. If you still have control
of the rb-appscript gem on Rubygems.org, would you be open to
transferring it to someone else? Two viable candidates would be Matt
Neuburg and Brendan Thompson. Matt forked appscript and ported it to
Github[2]. Brendan forked just the Ruby portion of the repo[3] and
created his own gem to solve his problem with jira-omnifocus[4]. It
looks like there's lots of users who have benefitted from your past
work, myself among them. I'm hoping that I'll be able to easily use
your work in the future as well. In any event, thank you for taking
the time to read this message and thank you for your hard work on
appscript. Cheers, Eric [1]
https://github.com/mattneub/appscript/issues/12#issuecomment-164085415[2] https://github.com/mattneub/appscript [3]
https://github.com/BrendanThompson/rb-scpt [4]
https://github.com/devondragon/jira-omnifocus/issues/13