Skip to content
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.

Status of this project #21

Open
runeflobakk opened this issue Feb 19, 2020 · 9 comments
Open

Status of this project #21

runeflobakk opened this issue Feb 19, 2020 · 9 comments

Comments

@runeflobakk
Copy link
Contributor

Hello,

I was wondering if this project is maintained, as there seems to not be that much activity going on. There are some old issues, and a couple of pull-requests just lying around.

I think this is a very useful library, and I actively use it on a daily basis, so I am wondering about what are the possibilities of me to become a maintainer of this repository, as opposed to be working on my own fork and send pull-requests? The last merged pull-request was mine, and approved by @mrwilson , so I am shamelessly mentioning you to maybe provide som insights on this matter :)

For reference, this is my previous contributions to this library:

@CliveEvans
Copy link
Contributor

It's a good question. I certainly still use it, but no longer have the keys to do much to it, since I left. Tagging @bruceeddy and @jahed as other people who might be able to answer ...

@jahed
Copy link
Contributor

jahed commented Feb 20, 2020

I left Unruly too so I'm no longer in a position to transfer ownership.

What I can say is that the package is tied to co.unruly so that is likely a problem in terms of authenticating releases and general company branding.

If no one at Unruly is maintaining this repo, maybe it's best and easiest if @runeflobakk forked the project and released under another domain/namespace. That seems to be the common approach with Java libraries.

@bruceeddy
Copy link
Contributor

bruceeddy commented Feb 20, 2020 via email

@runeflobakk
Copy link
Contributor Author

The currently open pull-requests are just two small ones.
But it is good to hear that there is interest in further maintaining it. I am hoping I will find some time to fix the small amount of currently registered issues (if no one beats me to it 😉), and I also want to do some housekeeping chores to Maven pom-file, and such. I also have som ideas for enhancing the Java8Matchers.where variants. I'll just ping you when I have something ready 👍

@runeflobakk
Copy link
Contributor Author

@bruceeddy If possible, I would appreciate if #20 , #23 and #22 (the last one includes #19 as well) could be reviewed and merged. :)

@runeflobakk
Copy link
Contributor Author

@bruceeddy It would be really nice to have the mentioned pull-requests merged before starting on the remaining registered issues.

@runeflobakk
Copy link
Contributor Author

@bruceeddy Sorry to nag, but are there any new info regarding #22 (comment) ?

@mrwilson
Copy link
Contributor

@runeflobakk Hi, I'm one of the original contributors and I've hard-forked (and released) this repo at https://github.com/mrwilson/java-8-matchers - the current version on Central is now 1.8, which is the same as the original 1.6

If you raise your changes as PRs against the fork (the package is now uk.co.probablyfine.matchers rather than co.unruly.matchers) I will aim to merge and release them soon.

@runeflobakk
Copy link
Contributor Author

@mrwilson Great! I'll get around to this soon, as I am on vacation at the moment 👍

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

No branches or pull requests

5 participants