How can a fork join commonhaus?

[velo]

Project information

This is more a curve ball than other projects.

A while back I forked querydsl and got it alive and kicking. Current developers are neither interested in continuing querydsl, nor handing over, nor accepting help.

https://github.com/OpenFeign/querydsl/

In the past 3 years, the only activity you will see is a single torpedo release around the time my fork made enough noise.

I would love to bring that code into commonhaus too, but I double that would be straight forward.

• Project name: Querydsl? OpenDSL? OpenQuery? GeneralQuery?
• Project website: https://github.com/OpenFeign/querydsl/
• Code repository: https://github.com/OpenFeign/querydsl/
• License: Apache License 2

Do you have authority to represent this project?

• I own or maintain this project

Describe your project

Querydsl is a framework which enables the construction of type-safe SQL-like queries for multiple backends including JPA, MongoDB and SQL in Java.

Instead of writing queries as inline strings or externalizing them into XML files they are constructed via a fluent API.

Things that must be done (bootstrap phase)

• Review the bylaws, especially sections about projects, decision making, and voting for significant decisions.

• Read the bootstrapping agreement.

• If all is well, and you agree to participate in the bootstrapping phase to help us build this thing, then create a PR with the following:

  1. A filled out copy of the bootstrapping agreement. You can make a copy of bootstrapping.md file and check that in, or checkin a filled out pdf. Please follow naming conventions.
  2. An updated CONTACTS.yaml that names your project representative in the EGC section
  3. An updated PROJECTS.yaml that provides details / describes your project
  4. An updated TRADEMARKS.md that adds your project name and project logo (if you have one). Please include the footnote reference, as we are using your project name and logo with your permission until we have a formal agreement in place and resources are transferred.

  The commit should be "Signed-off-by" your GH login (git commit -s -m "<project> bootstrapping agreement, yyyy-mm-dd")

[maxandersen]

Trying to grok more - is https://github.com/OpenFeign/querydsl/ the original or the fork? if the fork where is the original?

[ebullient]

It isn't completely moribund.. only mostly moribund, which makes it harder.

[velo]

Na, it's completely moribund.

There was a single torphaedo release and that was it. Not even release notes

[velo]

Would rebranding it solve the issue?

CommonDSL?

Can publish old querydsl-* modules with API compatible classes

[ebullient]

Yes, I think that would help.. it would also make it easier to describe. "Which version of QueryDSL" becomes a hard question to answer if they keep the same name (and that's without considering Copyright or Trademark issues)

[evanchooly]

If we're rebranding it, might I suggest QueryDiesel?

[maxandersen]

@velo is there any trace of response from the original founders on why they aren't interested in handing over?

[maxandersen]

okey - so it is always a delicate matter when a project in such a situation. We can't really know for sure if the original authors are okey or not by it being forked.

In general I would suggest to at least consider do one final outreach to get ack that it is okey to use the name/move the project; if not or no reply you would have do to a significant enough rename/rebranding to make sure there is no confusion.

[gavinking]

We can't really know for sure if the original authors are okey or not by it being forked.

By definition, when one releases open source code, one is explicitly making it OK to fork.

[ebullient]

right... but making it ok to fork != making it ok to keep the same name

[gavinking]

Sure.

[maxandersen]

yes, by fork here means keeping name which is the problematic part.

[velo]

Will keep as is, forked without any relationship with commonhaus for the next year or so.