Re: Digest for autokey-users@googlegroups.com - 3 updates in 1 topic

[Sven Mason]

Hi Joe

I would be ok to take care of the credentials. I have not been active in the group/repos recently but have previously.

I have experience managing git repos, mediawiki, forums.



Sven

On 8/29/24 02:45, autoke...@googlegroups.com wrote:

autoke...@googlegroups.com

Google Groups

Topic digest
View all topics

• Admin Access - 3 Updates

Admin Access

jos...@main.nc.us: Aug 28 11:43AM -0400 SECOND NOTICE   Soon I may be away for an indefinite period.   There are no other active members with admin access here or on GitHub.   If no one steps up to share access, this project may become locked.   Please consider requesting admin access to keep the project alive.   Joe

Gil Brand <gb9...@gmail.com>: Aug 28 10:49AM -0500 Joe, I'm not a coder, but might be able to help. I love Autokey. What is involved? Gil Brand 214-282-2581 p.s., I used Autokey to type my name and phone number!

jos...@main.nc.us: Aug 28 12:44PM -0400 Thanks for responding!   I don't recall seeing you posting here before.   I have a long background in programming, but I don't know much Python and am not an AutoKey developer. I'm just a very long term user who stepped in when no one else was managing the project.   There are two "levels".   The essential level is holding the credentials (passwords...) so you can grant access to someone else who knows more so they can do things. This involves decisions about who you can trust and how much access to give them. (everyone/contributor/admin)   There are a few different things and I'd have to detail them.   It also involves getting notices of non-members trying to post on our Google Groups forum and approving their posts and membership requests. This is mainly just for blocking spam. We haven't had to ban anyone yet in well over a decade. These requests occur randomly, one or two a month at most.   So far we have never encountered a bad actor who requested access. We were getting some spam before I turned on the approval process.   Ideally, whoever does this should have a basic familiarity with our wiki so they can point users to the resources there, but that's not essential.   The other level is actually doing technical stuff like reviewing PRs, merging them, and making new releases... That's less essential because there's no need for it until active members who understand such things make contributions. Hopefully, one or more of them will be motivated enough to ask for access so they can do these things themselves. As long as someone can grant them access, then we're good.   Again, the main thing is figuring out who to trust with access. Git/GitHub is easy to screw up with bad practices. And the whole project could be deleted or infected with something.   Generally, we're too small/specialized a project for bad actors to bother with, but we do have some issues with how to use Git/GitHub optimally which have caused some sync problems between the main (release) branch and our development branch that seem hard to fix.   Joe

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to autokey-user...@googlegroups.com.