-
Notifications
You must be signed in to change notification settings - Fork 44
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
Looking for Maintainer #107
Comments
As mentioned in the other issue, I am ready to step in a a (co-)maintainer. I really would like to have others with me, since I cannot guarantee for how long I can work on this, so running this as a one-man show would be too much of a risk, IMHO. |
I would say we should just start. Perhaps we can move it to the main repository, when we are done with the migration... |
I am happy to help Markus maintain this project. We use this project in production at work so I should be able to dedicate some hours to it. |
So squidex isn't using Orleans anymore? |
Hi all, I've been maintaining a fork of @jeremylcarter v4 work within our organisation as we've been using it with Orleans v4 preview in production for a while now. |
I think we need a main maintainer. Just create a PR for now and we can have a look together. |
@MarkusGeigerDev Do you have a Nuget account? I can add you as package owner. |
Not yet :) I'll create one over the weekend. Thanks! |
PR crerated #109, if I get a bit more time, I'll create a separate one for serialization refactor work. |
I didn't want to make a contest ... |
Yeh, I only noticed @MarkusGeigerDev had raised a PR after I posted mine. |
@wassim-k Do you have a nuget account? |
|
I just created an account |
Awesome. Everybody is invited. |
Hi together,
I am not using Orleans anymore. It is a great framework, but there are some challenges which made it overly complicated in my use case.
Therefore I would like to find a maintainer for this library. Any applications are welcome. As an application, an update to Orleans 4 would be great.
The text was updated successfully, but these errors were encountered: