gcalcli
gcalcli copied to clipboard
insanum
Confirm current list of authors/maintainers
I found quite a few authors/maintainers listed in the metadata here and in a fork. Let's confirm who all still wants to be listed...
Hi all,
I was mentioned in #688 but didn't have a chance to reply before it was closed. My fork just integrates commits from various other forks, most importantly the new Google OAuth code from @jamespo. I haven't written any code yet myself but I'm happy to help out now to the extent I can.
As others noted, Google's user-hostile OAuth setup hurts the usability of this project, as well as other open source projects. That's the primary reason I don't regularly use gcalcli. I don't know what's involved in getting a production-ready authentication flow working for gcalcli, but I consider that the top priority. I'm sure many users are turned away by needing to set up their own Google OAuth application -- I almost was.
I've reached out to folks and heard back from Eric (@insanum), Brian (@tresni), and Joshua (@jcrowgey), all busy with other things and not looking to be active maintainers.
And @michaelmhoffman @jamespo @chasecovello @mdengler @kyokley all had some commits/activity on the project, may be interested to be more explicitly involved. It would be nice to have at least one other active maintainer involved. =)
@mdengler I sent you a collaborator invite. You got keys to the kingdom if you accept. 😎
@mdengler I sent you a collaborator invite. You got keys to the kingdom if you accept. 😎
Thanks -- let me know anything small I can help with and I'll get on it asap...big things might be a little slower but worth a shot.
Hi, I've been on holiday, as mentioned I changed the oauth code and would be happy to help out when I have the time.
Hi, I've been on holiday, as mentioned I changed the oauth code and would be happy to help out when I have the time.
@insanum could you help with sending @jamespo a collaborator invite?
Oh @insanum another thing I was wondering: would it make sense to set up a GitHub "organization" like https://github.com/pallets and move the repo under that? Or would you prefer to keep it where it is?
I suggest leaving it as-is. Creating an organization makes sense if there are multiple different repos hosted underneath it.