-
Notifications
You must be signed in to change notification settings - Fork 1
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
update to draft-dejong-remotestorage-03 #1
Comments
Hey! I am currently rather offline due to being on parental leave. If you find someone who is interested in working on it, I'm happy to add contributions and contributors - otherwise I'm not certain when I'll take a look at it. |
@relet Wanna take a look at this again sometime? Can I help with updating this server? The new spec is being released in a couple days, so we could try to bring it to |
I'd like to take this project over and get it up to date with -05. @relet What's your stance on introducing dependencies for this server? I'd like to start depending on Flask (or at least Werkzeug). |
Great to hear. I'm totally open to sensible dependencies. What I would suggest to keep things democratic is that you just fork the project, and I'm happy to defer to whichever implementation is most active or popular, or link to several. |
I'm not sure if it makes sense to scatter around more forks, since this is rather confusing to users. If you agree with the changes, I'd like to merge that fork back sometime. |
Ok, that'll work. I'm also totally happy to give contributors access when On Wed, 19 Aug 2015 20:11 Markus Unterwaditzer [email protected]
|
Hi!
Great to see you wrote a remoteStorage server in python! We want as many different implementations as possible to exist, this is important for the process of getting the spec more stable on its way from Internet-Draft to (hopefully) RFC.
Can we help you update this server to the newest spec? Here's an example of how it works in nodejs: https://github.com/remotestorage/remotestorage-server/blob/master/lib/requests.js#L322-L369
The text was updated successfully, but these errors were encountered: