Maintainer wanted!

[madand]

It's been quite a while since I stopped using PaleMoon and Pentadactyl. In fact, it was long enough that their extension delivery infrastructure has been upgraded and my forum account got auto-purged. This means I am not able to test nor publish updates into the official channel (https://addons.palemoon.org/addon/pentadactyl/) anymore.

Since #7 already has a fixing PR #8, we need someone to take over the extension maintenance and create corresponding account(s) on PaleMoon sites to be able to push updates.

Ping to persons who contributed recently: @zhihaoy, @BillyIII, @jackrosenthal

[jackrosenthal]

Willing to help with some of the maintenance, but not sure if I want to commit to being the official maintainer.

Is anyone else interested in setting up a repo in a new GitHub org where we can co-participate in maintaining?

[jackrosenthal]

Made a github org and pushed the repository here:

https://github.com/pentadactyl/pentadactyl

Please let me know if you want to help with maintenance. I'll add you to the org.

[madand]

@jackrosenthal, thank you for prompt reaction. Good work!

Let me suggest a few first steps with the new repo, namely:

• Remove Reporting issues sections from the README, since it makes no sense because upstream is essentially dead.
• Update repo URL in the Build XPI from sources section of the README.
• Compile and publish XPI file on the Releases page.
• Add a temporary note that the latest XPI version is not yet available from the official Pale Moon channel.

[john-x]

I started using Pentadactyl a couple of months ago and have found it to be one of my favorite addons. Thank you, @jackrosenthal, for the patches that made it usable again. I wish I could contribute but I'm an absolute novice at coding.
Has anyone made a related post on Pale Moon's extensions forum? You might find some interested parties in there as well.

[jackrosenthal]

I wish I could contribute but I'm an absolute novice at coding.

I think you'd be surprised how much you can offer. I'm not super familiar with JavaScript and have been able to work my way around the codebase just by noting line numbers, reading definitions, etc. until uncovering the problem.

Even without code, finding and reporting issues can be helpful, or even other things (e.g., gathering people on the extensions form).

I've got a full schedule this week, so I may not get around to looking at some of the open issues.