Collaboration about aspnetredisproviders HOT 12 OPEN

I'm interested. What's the next step?

from aspnetredisproviders.

I'm in. What's next?

from aspnetredisproviders.

I'm game. I'm in the process of converting from using Booksleeve to StackExchange.Redis but we can break that out into tasks. Also, we need more unit tests.

from aspnetredisproviders.

I'm interested too. What's next?

from aspnetredisproviders.

Good to hear that everyone is interested.

First thing, in terms of hosting the project, how does everyone want to do it? Should there be a separate repo for each provider or should they be under one repo like this one? Also where should the repo be hosted?

from aspnetredisproviders.

I think we should have a repo per provider, all with a similar naming convention. (I'm looking at the use case of picking and choosing what provider one would want to use) Thoughts on naming is appreciated.

from aspnetredisproviders.

A repo for each provider approach doesn't look good because there will be around 10 classes. If you look at existing code you will see that there is not so much code. Single repo for all providers will be a better approach. It is possible to implement a WebEventProvider in separate project because it has additional dependencies. So my suggestion is to have a single repo with two projects. And then we will publish two nuget packages: one for WebEventProvider and one for others.
And choosing a necessary provider is already implemented by ASP.NET and web.config.

-----Исходное сообщение-----
От: "George McKenzie" [email protected]
Отправлено: ‎14.‎05.‎2014 21:35
Кому: "kylesonaty/AspNetRedisProviders" [email protected]
Копия: "Alexander Simonov" [email protected]
Тема: Re: [AspNetRedisProviders] Collaboration (#4)

I think we should have a repo per provider, all with a similar naming convention. (I'm looking at the use case of picking and choosing what provider one would want to use) Thoughts on naming is appreciated.
—
Reply to this email directly or view it on GitHub.

from aspnetredisproviders.

I agree with @alex-simonov

from aspnetredisproviders.

I'm good with that, the dependencies were a primary concern.

from aspnetredisproviders.

I also agree with @alex-simonov. As far as where we host it we can do it here. I added everyone that said they were interested as a collaborator to this repo.

from aspnetredisproviders.

Would it make sense if everyone took responsibility for a specific provider? It's not meant to limit contributions to that person or anything but we can create tasks and people can volunteer. Thoughts?

from aspnetredisproviders.

I am going to add some issues based on looking at the other projects and people can feel free to take them if they want. For example this repo doesn't have an output cache provider and some of the other session state providers use non locking sessions instead the standard way that asp.net locks session.

from aspnetredisproviders.