Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confirm current list of authors/maintainers #689

Open
dbarnett opened this issue Aug 22, 2024 · 11 comments
Open

Confirm current list of authors/maintainers #689

dbarnett opened this issue Aug 22, 2024 · 11 comments
Assignees
Labels
development Internal issues that mostly affect maintainers vs. end users

Comments

@dbarnett
Copy link
Collaborator

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...

@dbarnett dbarnett self-assigned this Aug 22, 2024
@chasecovello
Copy link

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.

@dbarnett
Copy link
Collaborator Author

@michaelmhoffman

@dbarnett
Copy link
Collaborator Author

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. =)

@dbarnett dbarnett added the development Internal issues that mostly affect maintainers vs. end users label Aug 23, 2024
@mdengler
Copy link
Collaborator

Would love to help out

@insanum
Copy link
Owner

insanum commented Aug 23, 2024

@mdengler I sent you a collaborator invite. You got keys to the kingdom if you accept. 😎

@mdengler
Copy link
Collaborator

@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.

@dbarnett dbarnett pinned this issue Aug 27, 2024
@jamespo
Copy link
Collaborator

jamespo commented Sep 2, 2024

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.

@dbarnett
Copy link
Collaborator Author

dbarnett commented Sep 9, 2024

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?

@insanum
Copy link
Owner

insanum commented Sep 9, 2024

Collaborator invite sent to @jamespo

@dbarnett
Copy link
Collaborator Author

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?

@insanum
Copy link
Owner

insanum commented Sep 12, 2024

I suggest leaving it as-is. Creating an organization makes sense if there are multiple different repos hosted underneath it.

@dbarnett dbarnett unpinned this issue Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Internal issues that mostly affect maintainers vs. end users
Projects
None yet
Development

No branches or pull requests

5 participants