Writing a post abut our motivations for Opire's blog

[David King]

The folks at Opire are asking if we'd be willing to collaborate on a
post for their blog on what the AutoKey project is all about and our
reasons for using Opire.  I don't feel qualified to do this myself.  Is
there anyone out there who does feel qualified? I sent Joe an e-mail ~24
hours ago and haven't heard back.  Maybe he's off doing whatever it was
he was going to be doing?  Anyway, let me know if you feel like you want
to step up and work with Opire's blog writer so that I can close the
loop with Iván.

Thanks,
Dave
da...@daveking.com

-------- Forwarded Message --------
Subject:     AutoKey Project on Opire's Blog
Date:     Tue, 10 Sep 2024 16:16:43 +0200
From:     Opire <he...@opire.dev>
To: da...@daveking.com



Hi David,

I hope this message reaches you well. My name is Ivan and I am the
co-founder of Opire <https://opire.dev>. I saw that you recently created
a bounty for issue #87
<https://app.opire.dev/issues/01J73BXYSGA83XKW25TPF2QMK0> on the AutoKey
project. First of all, I want to thank you for placing your trust in
Opire. We are delighted to have you on board.

I have been researching the project and the comments on the issue and I
find the situation with AutoKey to be quite interesting.

At Opire, we are currently collaborating with a writer to create blog
content (mainly on dev.to <https://dev.to/opire>) so that more people
know about Opire and help open-source projects. We are trying to build a
community and this is one of the ways we use to have more reach.

We would like to be able to create a post talking about AutoKey, what it
is, how it works and the problems it currently has due to not having
developers. We believe that it can be beneficial for you as it can
attract many developers interested in collaborating on the project.

We don't want to publish anything without your consent, so I'm
contacting you, I'm not sure who would be the best contact to get this
permission. Of course we take care of the writer's costs. Let me know if
this is something that would interest you.

I look forward to your response.

Kind regards,

Iván
Co-founder of Opire

--
David King
dave at daveking dot com

[Elliria]

Hey there,

David King wrote:

>The folks at Opire are asking if we'd be willing to collaborate on a
>post for their blog on what the AutoKey project is all about and our
>reasons for using Opire.

I'm not in charge, but AutoKey is an open-source project, so anyone
can do anything.

>I don't feel qualified to do this myself. Is there anyone out there
>who does feel qualified? I sent Joe an e-mail ~24 hours ago and
>haven't heard back.  Maybe he's off doing whatever it was he was
>going to be doing?  Anyway, let me know if you feel like you want to
>step up and work with Opire's blog writer so that I can close the
>loop with Iván.

Joe wrote a post in response to a Stack Exchange request that sums up
AutoKey nicely:

https://askubuntu.com/questions/1348517/run-command-inside-application/1349319#1349319

The AutoKey wiki also offers lots of information:

https://github.com/autokey/autokey/wiki

If something is missing from the wiki that would be helpful, I'd be
willing to write it.

As to the development problems, AutoKey has always had small groups
of contributors and developers and even as few as one or no
developers. Despite this, it's a valuable program that's loved by
presumably many people and there's always the hope that development
will pick back up again. Meanwhile, members of the community are
still actively supporting one another.

Most recently, we ended up in a situation where only a few of us
remained and we were lacking an understanding of vital tasks like
sorting out what all of the steps should be for putting out a new
release when working with our branching strategy or understanding how
dependencies work and are determined for installations. I'm a junior
developer who's eager to learn, but AutoKey needs more than that.

Major headway was somewhat-recently made on the pressing issue of
getting AutoKey to play nicely on Wayland, but there was a shortage
of testing and feedback which could have helped to move that forward.
I include myself as being guilty of contributing to that shortage
since I've never installed Wayland and was just hoping others would
do the testing.

The fact that AutoKey can automate any program or script that you
could ever dream up and write or make any replacements that you
could ever come up with makes it an incredibly helpful, powerful, and
useful tool. As such, it's loved by those of us who use it and it
deserves to be saved, if only we could drum up some excitement about
it in the form of senior developers who know their way around in
Python, git, and GitHub.

--
Elliria

There is no spoon.