Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
Dear MariaDB community,
I'm the original creator (many years ago) and still active maintainer of https://github.com/vorburger/MariaDB4j, a project which refuses to die 
and on the contrary keeps getting end-user developer interest with issues, pull requests from strangers, etc.
The MariaDB community and the MariaDB4j project have previously had some (very light) touch points e.g. in CONJ-87 and MDEV-16836 and I believe occasionally over on Stack Overflow.
In the context https://github.com/vorburger/MariaDB4j/issues/213 (read the linked issues and my blog post...) and https://github.com/vorburger/MariaDB4j/issues/238, I was wondering whether you would have any interest / be willing to accept a move https://github.com/vorburger/MariaDB4j/ to under https://github.com/MariaDB/ ?
I would have no expectations of any "work" or active contributions from any of you. I would commit to continuing to engage on "my" project as I have for the past years when I can (in some periods more actively than others) - I'm not trying to "dump" this on you. Of course I would very much welcome contributions from existing MariaDB committers, I'm guess notably people working on mariadb-connector-j, as from anyone outside - but I'm not proposing this move expecting a sudden avalanche of PRs. I would be happy to promote anyone who has made a notable number of useful contributions as an additional commiter. (I would expect to be the initial committer privilege on the moved repo.)
For the record: MariaDB4j is a personal home project, always has been and always will be, and is in no way "endorsed" or supported by (or whatever else anyone may think) by where I (currently) work, which happens to be a very large professional open source company.
It's just a suggestion for discussion - I'm open to whatever the outcome!
Best,
M.
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Diego Dupin [ diego dupin ] | Vicentiu Ciorbaru [ cvicentiu ] |
Hello!
> The tricky parts are making sure we get commit privileges right.
How so? How do you guys manage permissions on https://github.com/MariaDB/ .. does everyone get committer privilege on all repos? That seems overly broad and unnecessary.. why not simply use GitHub's Teams thing to create a few sub-groups? I don't know how your community is organized, but perhaps something like "core MariaDB" VS "CONJ" VS "MariaDB4j" groups would make sense?
> For the record: MariaDB4j is a personal home project, always has been and always will be, and is in no way "endorsed" or supported by (or whatever else anyone may think) by where I (currently) work, which happens to be a very large professional open source company.
This has actually changed since I opened this issue, and I now work somewhere else, but it's still completely irrelevant. If anything, I'll have less time to maintain MariaDB4j going forward...
> Should we create a specific project for MariaDB4J on jira.mariadb.org or do we reuse CONJ?
Neither - would you object to simply keep using GitHub issues (for MariaDB4j), like I have since the beginning? I suspect that if you were to to require that I close https://github.com/vorburger/MariaDB4j/issues and ask users to use https://jira.mariadb.org instead, this would significantly raise the bar for people to chime in with ideas, questions and contributions... uses don't like to have to create accounts on other sites than GitHub - as easy as it may seem. Thoughts?
What I meant with making sure we get the commit privileges right is to be sure that everyone is ok with the setup. My assumptions are:
a) You want to have push rights to the repository.
b) You may want to be able to grant push rights to proven contributors from the community. I do not know if you can do this without being an admin over whole github.com/MariaDB, will check.
Follow up question:
Are you comfortable with MariaDB developers getting push rights to your repository? Ideally, we want the move to github.com/MariaDB to act as a catalyst towards building a community around the project. We can not afford (right now at least) to actively maintain the project, but we do want to have the option of helping you with pull requests, bug fixes, etc. You would be the main maintainer for the time being, but if you are not around for a while, MariaDB developers should be able to help.
I agree to just use Github's issue tracker. We want to market this as a project we support, however the MariaDB Foundation and Corporation can not offer any guarantees like we do for the rest of the projects. Using just Github's tracking makes it easier to represent exactly this.
If you agree with all this, we can start the process next week. All should be done in a day or less I assume.
Reading https://help.github.com/en/enterprise/2.15/user/articles/transferring-a-repository, it seems we need to grant you permission to create repositories under github.com/MariaDB and the process is quite straightforward. serg Can we grant mike.vorburger.ch this right?
| Workflow | MFWA: Task Management Workflow [ 118233 ] | MariaDB v4 [ 162235 ] |
| Status | To Do [ 10003 ] | Open [ 1 ] |
Hello! It's been a while. Sorry for my, erm... 2.5 years silence here? 
Are you guys still up for this?
I can see that I have the permission to move repos under https://github.com/MariaDB/ now, but I'm still slightly reluctant to actually click move... what if I loose access?! #paranoia
Do you mind if I temporarily create and move some empty test repo to explore this? Would that be cool, and not cause too much confusion?
PS: Do you guys hang out on some chat room? Some Slack or IRC - or whatever you use.
BTW A sort of related possible future issue here would be Java package "namespacing", and the Maven Central release stuff.
MariaDB4j is currently `package ch.vorburger.mariadb4j` and on https://repo1.maven.org/maven2/ch/vorburger/mariaDB4j/
If we do indeed go ahead here, do I "have" to, do you "need" me to move the package? It would make my next "mvn deploy" more... involved. Or can I just keep it as-is?
Great to hear from you. No worries, we can still look into this. If it makes you more comfortable, we can do the process live. I take it you're in one of Europe's timezones so it shouldn't be too hard to find a convenient time. We can also do a test-repo first. We can easily drop the repo afterwards.
I'm not familiar with the Java ecosystem enough to offer a good enough answer atm for the "ch.vorburger.mariadb4j" issue. Our usuall approach is to favor backwards-compatibility if possible, but it would be ideal if we can have "org.mariadb.mariadb4j" as part of the name space. I'll educate myself a bit on this and we can decide how best to approach this and not cause users too much pain.
You can find us on: https://mariadb.zulipchat.com/. And if it helps put your mind at ease we can also do a video call at some point.
| Component/s | None [ 18105 ] | |
| Fix Version/s | N/A [ 27305 ] | |
| Resolution | Won't Fix [ 2 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Remaining Estimate | 0d [ 0 ] |
| Workflow | MariaDB v4 [ 162235 ] | MariaDB Foundation v1 [ 188321 ] |
| Component/s | None [ 18105 ] |
Hi mike.vorburger.ch
We believe it would really benefit both of us if this happened. The tricky parts are making sure we get commit privileges right.
There are some bug-tracking and other related aspects that need to be decided. Should we create a specific project for MariaDB4J on jira.mariadb.org or do we reuse CONJ? How was your workflow within the project thus far?
There are probably other details that I am missing now, should we brainstorm all things that you believe need to change for this to be successful? The key point here is we should do this right, such that everyone is happy with the end result.