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

Committer approval for transfer of copyright #588

Closed
kdubb opened this issue Apr 3, 2023 · 29 comments
Closed

Committer approval for transfer of copyright #588

kdubb opened this issue Apr 3, 2023 · 29 comments

Comments

@kdubb
Copy link
Member

kdubb commented Apr 3, 2023

In furtherance of #587 & #579, the project will be moving to the PostgreSQL organization (once all requirements are met) for future 9.0 release. This will involve transferring the copyright to that organization. This issue is to secure the approval of the transfer from project committers.

Ideally we would have explicit approval from all committers but given the nature of GitHub and the project, I am only requiring that the major committers explicitly approve. If any committer explicitly disapproves they can voice that here and we will deal with it as needed.

After 30 days from the opening of this issue it will be assumed that any non-major contributor that has not responded is giving tacit approval.

I'm mentioning all contributors below to notify each one of them. I sincerely thank you all for the help with the project over the years!

Major Contributors:

Remaining (still very important 😉) Contributors:

@kdubb
Copy link
Member Author

kdubb commented Apr 3, 2023

I'll get this started...

I approve the transfer of the copyright for all contributions I have made to this project to the PostgreSQL organization.

@kdubb kdubb pinned this issue Apr 3, 2023
@jesperpedersen
Copy link
Contributor

👍

@kdubb kdubb unpinned this issue Apr 3, 2023
@brcolow
Copy link
Contributor

brcolow commented Apr 3, 2023

I am only a minor contributor, but, I approve the transfer of the copyright for all contributions I have made to this project to the PostgreSQL organization.

@asmarcz
Copy link
Contributor

asmarcz commented Apr 3, 2023

I approve, thank you for asking, like to see the project flourish.

@yrashk
Copy link
Contributor

yrashk commented Apr 3, 2023

My contributions were minor, but just in case, I do explicitly approve this transfer of the copyright.

@oscerd
Copy link
Contributor

oscerd commented Apr 3, 2023

Hello, I approve the transfer of the copyright for the minor contributions I have made to this project to the PostgreSQL organization. Thanks for asking.

@andreak
Copy link
Contributor

andreak commented Apr 3, 2023

I approve. I hope this project will flourish and I think that handing it over to the PostgreSQL org. is the long term best thing.

@kwesterfeld2
Copy link
Contributor

kwesterfeld2 commented Apr 3, 2023 via email

@pkolaric
Copy link
Contributor

pkolaric commented Apr 3, 2023

I approve. Only did some bugfixing..

@davidwheeler123
Copy link
Collaborator

Awesome I approve! 👍

@davidwheeler123
Copy link
Collaborator

davidwheeler123 commented Apr 3, 2023

Any chance you could rename it, once you take it over? pgjdbc-ng is a mouthful!

@kdubb
Copy link
Member Author

kdubb commented Apr 3, 2023

@davidwheeler123 Please discuss in #587

@davsclaus
Copy link
Contributor

davsclaus commented Apr 4, 2023 via email

@moio
Copy link
Contributor

moio commented Apr 4, 2023

I approve the transfer of the copyright for all contributions I have made to this project to the PostgreSQL organization.

Thanks and best of luck for the future of this excellent project!

@gsmet
Copy link
Contributor

gsmet commented Apr 4, 2023

Hi!

I approve the transfer of the copyright for all contributions I have made to this project to the PostgreSQL organization.

@tlewowski
Copy link
Contributor

Hi, awesome news! I approve the transfer of copyright to whatever I've done here ;)
Best of luck in the future development!

@RoelVR
Copy link
Contributor

RoelVR commented Apr 19, 2023

I approve the transfer of the copyright for all contributions I have made to this project to the PostgreSQL organization.

Best of luck for the future!

@frode-carlsen
Copy link

I approve the transfer of the copyright for all contributions I have made to this project to the PostgreSQL organization.

@davidwheeler123
Copy link
Collaborator

davidwheeler123 commented Oct 19, 2023

Anyone here willing to continue to show support by signing up as a maintainer? See #587

@davecramer
Copy link

Actually what is required is to be the maintainer.

@kdubb
Copy link
Member Author

kdubb commented Oct 19, 2023

The biggest thing needed is general maintenance. Bug triage and reproduction, dependency updates, scheduled release, etc. Secondarily, documentation updates and edits.

If all these tasks were off my plate, I could find the time pitch in on the things that need my expertise.

As I just laid out in #587, I would love to use this driver in our Quarkus applications and the promise of Loom Virtual Threads is something I want to work on.

@kdubb
Copy link
Member Author

kdubb commented Oct 19, 2023

Also... specific features would need a sponsor.

I'm thinking along the lines of Windows support, Kerberos Authentication, etc. These are examples of things I have neither the time, inclination, or even ability to properly support & test.

@davecramer
Copy link

Windows support ?

Kerberos Auth is relatively easy to implement. Ridiculously hard to test.

@kdubb
Copy link
Member Author

kdubb commented Oct 19, 2023

As far as the copyright issue goes, it's settled. The copyright transfer is "approved".

@kdubb
Copy link
Member Author

kdubb commented Oct 19, 2023

Windows support ?

There are/were a number of issues related to locales specifically on Windows. I could never track them down myself and I worked them out by proxy. The driver is not currently tested on Window as I ran out of time.

Kerberos Auth is relatively easy to implement. Ridiculously hard to test.

Exactly. The auth is "implemented". I have no idea if it works.

@davidwheeler123
Copy link
Collaborator

The biggest thing needed is general maintenance. Bug triage and reproduction, dependency updates, scheduled release, etc.

Should I get started with some dependency updates in this repo? I've kinda been holding my breath to see what happens with the copyright transfer

@davecramer
Copy link

I'm pretty sure everyone has given permission to move the copyright. The question is who will maintain it?

@kdubb
Copy link
Member Author

kdubb commented Oct 25, 2023

Permission Granted

From the responses of the contributors, permission has been granted. Most grants were explicit with a few passive grants via no feeback/objection.

@kdubb kdubb closed this as completed Oct 25, 2023
@kdubb
Copy link
Member Author

kdubb commented Oct 25, 2023

This does not imply any sort of immediate action or timeline, only that if/when a move is made we have permission to do it. Many details are still to be worked out and are being tracked via #587.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests