Comments (16)
Hi @Fristi
I'm glad you found sttp-oauth2 useful! To my best knowledge @zstoychev and his team are the current maintainers of the library. I reached out to the team to ask if they are willing to transfer the project and will update you when they respond.
Would it be an idea to integrate this into sttp it self?
I think sttp-oauth2 makes sense as a separate project. The main benefit being the separate release process and versioning. Those projects evolve at different rate and common versioning wouldn't make a lot of sense.
Or propose to transfer their repository?
Should both sides decide for the transfer, I'm happy to help
Disclaimer: I'm no longer with Ocado Technology, speaking solely for myself as ex-maintainer of sttp-oauth2
from sttp.
Thanks for reaching out. While I'm not sure if the current maintainers would want any ownership transfer in the first place, so that's all very hypothetical, but even if, I can't say that we would have any capacity to evolve the project further. We could plug it into our automated update / release processes (that would be a one-off task), but I wouldn't want to make any promises or take responsibility for fixing issues / adding features. So just FYI :)
from sttp.
If we are to maintain the project (with the help of others in Polyvariant), it would be best to do it within our own organization. We are not affiliated with SoftwareMill and do not want to give the false impression that there is any responsibility on their side.
As per visibility - transferring the project on Github should automatically redirect all links so bookmarks and search results should remain relevant. This will require a proper communication with the community as well of course.
from sttp.
@Fristi I discussed that with Zdravko and I'll be doing the transfer. I want to put up a migration plan today. If all goes well we should finish migration+housekeeping this week 😉
from sttp.
Hi everyone,
I am from Ocado Technology, the maintainers of the library. Michal got in contact with us. We discussed this internally and we would be happy if sttp-ouath2
can find a home closer to the community and to transfer ownership if there is interest to take it as we are low in capacity to be able to maintain it well.
Let us know what your thoughts are.
from sttp.
I understand, was hoping to bring more people together to bundle the efforts in all the work which has been done so far!
I think it's already great that the work of sttp-oauth
will continue somewhere else ❤️
from sttp.
@zstoychev When would you able to transfer the repository? I've got a ZIO PR ready :)
from sttp.
I reached out to the team to ask if they are willing to transfer the project and will update you when they respond.
Let's see what they would like :)
I think sttp-oauth2 makes sense as a separate project. The main benefit being the separate release process and versioning. Those projects evolve at different rate and common versioning wouldn't make a lot of sense.
Agreed, but having it integrated in one active project with a release cycle which is regular, the dependencies and new features (if they get contributed) are being released
We could plug it into our automated update / release processes (that would be a one-off task), but I wouldn't want to make any promises or take responsibility for fixing issues / adding features. So just FYI :)
I think having updated dependencies and an automatic release process in place is already valuable!
Thing is with some integration modules in open source (no matter what eco system) world is that they are incredible valuable, it happens quite a lot that the maintainers stop it. If it's still being released and updated within another library I think it's a great win for the eco system
from sttp.
I agree with @Fristi, having automated updates + releases is a value on it's own. The project could be marked as contribution-first.
Let's hear from current maintainers first.
from sttp.
Thanks, @zstoychev!
Due to the limited capacity @adamw mentioned on their side, we can transfer the project to https://github.com/polyvariant/ where we can provide low-effort maintenance. This makes sense, considering I am the initial author of this code. If that works we can discuss the transfer details in private.
What do you think?
from sttp.
What if we would transfer it to softwaremill anyway and get contributor permissions or alternatively integrate it into the build of sttp? Having at softwaremill has better publicity reach and therefore more likelihood to get more contributions :) Of course softwaremill would want to do this of course :)
from sttp.
I think keeping it as a separate project makes most sense. The build of sttp is big enough already :)
Also, maybe the decision would be best made by the new maintainers? I can of course give contributor permissions if the project were to end up on our account, but https://github.com/polyvariant/ seems to be a great place as well. For publicity, we'll for sure link from the docs (I think we do already), so that should be taken care of :)
from sttp.
was hoping to bring more people together
We are very open to contributions!
from sttp.
The transfer plan is ready polyvariant/sttp-oauth2#477. Looking forward for your input before I proceed.
I think we can close this issue and continue there
from sttp.
Polyvariant looks a great option, thank you Michal for driving this!
from sttp.
Repository has been migrated, thanks everybody for your input !
from sttp.
Related Issues (20)
- [BUG] HEAD request times out using Http4s backend HOT 2
- Http proxy problem with async-http-client-backend-zio:3.9.1
- Uri interpolation incorrectly percent-encodes some characters HOT 2
- where is basicRequest? HOT 1
- AbstractFetchBackend does not support manual cancellation/interruption
- Expose AsyncHttpClient when creating AsyncHttpClientBackend HOT 2
- Preserve request-metadata in SttpBackendStub HOT 2
- is `null` valid header field value? HOT 5
- add support Tethys json HOT 2
- Add Scala 3 support for play-json HOT 4
- quickRequest: Unexpected behaviour dependent on method order HOT 4
- Refactor metrics names according to standards
- Metrics caching rework
- No json4s release for scala 3 HOT 4
- Add Ox integration: SSE & WebSockets? HOT 2
- Spray json support for scala 3 HOT 3
- enable logback logging for sttp 1.7.x HOT 2
- Missing content type on Multipart HOT 2
- typo (jeager) in build.sbt HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sttp.