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

Maintaining Bitbucket.Net #28

Open
MattBussing opened this issue Dec 22, 2021 · 5 comments
Open

Maintaining Bitbucket.Net #28

MattBussing opened this issue Dec 22, 2021 · 5 comments

Comments

@MattBussing
Copy link

@lvermeulen, at the company I work for we use this library in one of our internal repos. There are some things that we would like to fix on this library. However, it doesn't appear that you spend much time actively maintaining this repo. So, could you add me as one of the maintainers of this repository please? Then I can help you maintain this library.

@lrv1668
Copy link

lrv1668 commented Dec 22, 2021

👍 to this

@roger-strain
Copy link

Great big +1 here. Would love to see an active maintainer. Forking could be an option, but just being able to keep the existing one updated would be much preferred.

@MattBussing
Copy link
Author

@lvermeulen , Two questions.

  1. Do you plan on maintaining this package?
  2. Can I help maintain this project here without forking it?

A simple no to either or both is totally fine. I really need this info as my team considers what we should do to move forward.

Thank you for your time!

@lrv1668
Copy link

lrv1668 commented Apr 17, 2023

@lvermeulen Any feedback here?

@peterder72
Copy link

With BitBucket updates there're now missing fields in the library, and it would be great if we could continue using same package for bitbucket-related work. @lvermeulen Is there any chance on reviving this repo, like the folks above were proposing, or will there need to be a fork?

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

4 participants