tag:help.rubygems.org,2010-01-19:/discussions/problems/21526-rb-appscript-requesting-ownershipRubyGems.org: Discussion 2018-10-18T19:51:27Ztag:help.rubygems.org,2010-01-19:Comment/390084512016-05-12T17:20:20Z2016-05-12T17:20:20ZRb-appscript: requesting ownership<div><p>Sorry about the delay here. I'm not seeing the "consent" on that
github thread - mind linking/forwarding it? We could also add an
email to this conversation too if that's easier.</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/390084512016-05-13T11:01:49Z2016-05-13T11:01:49ZRb-appscript: requesting ownership<div><p>Hi Nick,</p>
<p>Thanks for getting back to me. No worries about the delay, I
know this is<br>
volunteer work for you.</p>
<p>The specific post from Hamish I was referring to is this
post:<br>
<a href="https://github.com/mattneub/appscript/issues/12#issuecomment-165600509">
https://github.com/mattneub/appscript/issues/12#issuecomment-165600509</a></p>
<p>That's his response to me on Bitbucket. I'll quote that
conversation below:</p>
<p>Hengist Podd <a href="mailto:notifications-noreply@bitbucket.org">notifications-noreply@bitbucket.org</a><br>
12/12/15</p>
<p>to me<br>
hhas Hengist Podd sent you a message:<br>
If Brendan wants it he's totally welcome to it; surprised he never
asked<br>
before posting his fork. Or Matt, but I think Brendan's version has
made<br>
more progress. Honestly, they should throw in together if they
really care<br>
about it. He'll need to contact the RubyGems maintainers to get
it<br>
transferred as I can't log into it any more. As far as modernizing
the C<br>
portion, replacement Cocoa APIs are available in
NSAppleEventDescriptor<br>
(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<br>
nicked that bit from RubyOSA), so can't offer you any advice beyond
1.<br>
refer to SwiftAE [<a href="https://bitbucket.org/hhas/swiftae/">https://bitbucket.org/hhas/swiftae/</a>]
for pointers [sic]<br>
on using the relevant Cocoa APIs, and 2. Apple doesn't give a crap
about<br>
Mac Automation any more and seems perfectly happy letting it die
off from<br>
mismanagement and neglect, so caveat emptor as far as long-term
prospects<br>
are concerned. HTH has</p>
<p>In reply to Eric Hu<br>
Eric Hu sent you a message on Bitbucket: Hi there, I'm writing this
for<br>
Hamish Sanderson, original author of Appscript. If this is you,
please read<br>
on. If not, you can stop here (though I would appreciate a short
note<br>
letting me know I've reached the wrong person). First off, I'd like
to say<br>
I'm a happy user of your work. I used rb-appscript for years
without<br>
realizing it, via the Consular gem. Over the last several months,
I've been<br>
tracking down an issue with Consular that depends on rb-appscript.
I<br>
eventually tracked down the issue and reported it in what I thought
was the<br>
source repo.[1] It turns out that I reported it to a fork, and the
issue<br>
was actually resolved in that repo. Unfortunately other gem
developers<br>
don't benefit from this change since it's not reflected on
Rubygems. If you<br>
still have control of the rb-appscript gem on Rubygems.org, would
you be<br>
open to transferring it to someone else? Two viable candidates
would be<br>
Matt Neuburg and Brendan Thompson. Matt forked appscript and ported
it to<br>
Github[2]. Brendan forked just the Ruby portion of the repo[3] and
created<br>
his own gem to solve his problem with jira-omnifocus[4]. It looks
like<br>
there's lots of users who have benefitted from your past work,
myself among<br>
them. I'm hoping that I'll be able to easily use your work in the
future as<br>
well. In any event, thank you for taking the time to read this
message and<br>
thank you for your hard work on appscript. Cheers, Eric [1]<br>
<a href="https://github.com/mattneub/appscript/issues/12#issuecomment-164085415">
https://github.com/mattneub/appscript/issues/12#issuecomment-164085415</a>
[2]<br>
<a href="https://github.com/mattneub/appscript">https://github.com/mattneub/appscript</a>
[3]<br>
<a href="https://github.com/BrendanThompson/rb-scpt">https://github.com/BrendanThompson/rb-scpt</a>
[4]<br>
<a href="https://github.com/devondragon/jira-omnifocus/issues/13">https://github.com/devondragon/jira-omnifocus/issues/13</a></p></div>hu.erictag:help.rubygems.org,2010-01-19:Comment/390084512016-05-13T11:07:15Z2016-05-13T11:07:15ZRb-appscript: requesting ownership<div><p>And this is the conversation with Brendan and me</p>
<p>Forwarded conversation</p>
<h2><a name="subject-rb-scpt-" class="anchor" href="#subject-rb-scpt-"></a>Subject:
Rb-scpt</h2>
<p>From: <em>Eric Hu</em> <a href="mailto:hu.eric@gmail.com">hu.eric@gmail.com</a><br>
Date: Tue, Dec 15, 2015 at 6:32 PM<br>
To: <a href="mailto:brendan@btsystems.com.au">brendan@btsystems.com.au</a></p>
<p>Hi Brendan,</p>
<p>I found your email on your Github profile after using your
rb-scpt<br>
gem. Thank you for forking it, separating the Ruby source, and<br>
publishing a new gem. I was trying to fix an issue with<br>
consular-iterm and your repo helped make that possible.</p>
<p>I don't know what your intentions are for rb-scpt, but would you
be<br>
open to taking over rb-appscript on Rubygems? I already have<br>
permission from Hamish: that conversation is included below.
Taking<br>
the actual gem will require talking to the people at Rubygems.
I'm<br>
happy to take care of that to see that rb-appscript gets some<br>
continuity.</p>
<p>Matt Neuberg maintains a fork of Hamish's code on Github as
well.<br>
I've had this conversation with him as well, though he hasn't<br>
expressed much interest in maintenance going forward.[1]</p>
<p>What do you think? Just say the word and I'll reach out to
the<br>
Rubygems people. If it'll make the decision easier, I'm happy to
help<br>
maintain the gem and review pull requests.</p>
<p>Cheers,<br>
Eric Hu</p>
<p>[1] <a href="https://github.com/mattneub/appscript/issues/12">https://github.com/mattneub/appscript/issues/12</a></p>
<p>--------- Coversation with Hamish ------------</p>
<p>Hengist Podd sent you a message:<br>
If Brendan wants it he's totally welcome to it; surprised he
never<br>
asked before posting his fork. Or Matt, but I think Brendan's
version<br>
has made more progress. Honestly, they should throw in together
if<br>
they really care about it. He'll need to contact the RubyGems<br>
maintainers to get it transferred as I can't log into it any more.
As<br>
far as modernizing the C portion, replacement Cocoa APIs are
available<br>
in NSAppleEventDescriptor (10.11+) and NSWorkspace. It's years
since I<br>
did any Ruby, and never did much like it or have a clue how to
build<br>
[Obj-]C extensions for it (I just nicked that bit from RubyOSA), so
can't offer you any advice beyond 1. refer to SwiftAE<br>
[<a href="https://bitbucket.org/hhas/swiftae/">https://bitbucket.org/hhas/swiftae/</a>]
for pointers [sic] on using the relevant Cocoa APIs, and 2. Apple
doesn't give a crap about Mac<br>
Automation any more and seems perfectly happy letting it die off
from<br>
mismanagement and neglect, so caveat emptor as far as long-term<br>
prospects are concerned. HTH has<br>
View inbox<br>
In reply to Eric Hu<br>
Eric Hu sent you a message on Bitbucket: Hi there, I'm writing
this<br>
for Hamish Sanderson, original author of Appscript. If this is
you,<br>
please read on. If not, you can stop here (though I would
appreciate a<br>
short note letting me know I've reached the wrong person). First
off,<br>
I'd like to say I'm a happy user of your work. I used rb-appscript
for<br>
years without realizing it, via the Consular gem. Over the last<br>
several months, I've been tracking down an issue with Consular
that<br>
depends on rb-appscript. I eventually tracked down the issue
and<br>
reported it in what I thought was the source repo.[1] It turns
out<br>
that I reported it to a fork, and the issue was actually resolved
in<br>
that repo. Unfortunately other gem developers don't benefit from
this<br>
change since it's not reflected on Rubygems. If you still have
control<br>
of the rb-appscript gem on Rubygems.org, would you be open to<br>
transferring it to someone else? Two viable candidates would be
Matt<br>
Neuburg and Brendan Thompson. Matt forked appscript and ported it
to<br>
Github[2]. Brendan forked just the Ruby portion of the repo[3]
and<br>
created his own gem to solve his problem with jira-omnifocus[4].
It<br>
looks like there's lots of users who have benefitted from your
past<br>
work, myself among them. I'm hoping that I'll be able to easily
use<br>
your work in the future as well. In any event, thank you for
taking<br>
the time to read this message and thank you for your hard work
on<br>
appscript. Cheers, Eric [1]<br>
<a href="https://github.com/mattneub/appscript/issues/12#issuecomment-164085415">
https://github.com/mattneub/appscript/issues/12#issuecomment-164085415</a><br>
[2] <a href="https://github.com/mattneub/appscript">https://github.com/mattneub/appscript</a>
[3] <a href="https://github.com/BrendanThompson/rb-scpt">https://github.com/BrendanThompson/rb-scpt</a>
[4]<br>
<a href="https://github.com/devondragon/jira-omnifocus/issues/13">https://github.com/devondragon/jira-omnifocus/issues/13</a></p>
<hr>
<p>From: <em>Brendan Thompson</em> <a href="mailto:brendan@btsystems.com.au">brendan@btsystems.com.au</a><br>
Date: Fri, Dec 18, 2015 at 7:28 AM<br>
To: Eric Hu <a href="mailto:hu.eric@gmail.com">hu.eric@gmail.com</a></p>
<p>Hey Eric,</p>
<p>I could be interested. I’m not too sure I would have too
much time to be<br>
able to do much though. I also prefer the name of my forked gem as
well :).</p>
<p>However, if you’re willing to assist then I may be
inclined to do it.</p>
<p>Thanks,</p>
<p>Brendan</p></div>hu.erictag:help.rubygems.org,2010-01-19:Comment/390084512017-05-10T02:13:43Z2017-05-10T02:13:43ZRb-appscript: requesting ownership<div><p>Eric,<br>
Are you still interested in taking over this gem name?<br>
-David</p></div>David Radcliffetag:help.rubygems.org,2010-01-19:Comment/390084512017-05-10T18:21:47Z2017-05-10T18:21:47ZRb-appscript: requesting ownership<div><p>Hi David,</p>
<p>Thanks for following up. I'm no longer interested in taking over this<br>
gem. You can close this request.</p>
<p>Regards,<br>
Eric</p></div>hu.eric