Concepts and documentation

[Eugen Tudorancea]

I've read the mailing list, also looked on github over the code.

You said someone needs to be fluent in OAuth 1&2, but I tried to read about them and there's a ton of information and MANY different approaches on how to do something. I'm new and never wrote a OAuth server implementation only clients that interact with FB & Twitter.

Isn't there any way I can learn what you're trying to build? I started a project and have 2 options, use OAuth and implement something that I will want to change or try to learn OZ, but I have no docs.

I watched the video and tried to grasp at the concept, but is not that easy to get it right. Maybe you don't have the time, but please make some notes and some sketches on a pice of paper when you have some spare time, to show the basic concepts and I'll take the time to properly make some useful designs and documentation.

We can share a Google Document, there you can add notes and update images and I'll transform them into G. Drawings so anyone can understand the approach and use it as a draft. 

There's not too much action on the mailing list, in my opinion, mostly because people don't understand what needs to be done; at least for me that's the case, but I want to help where I can.

Thank you

[Eran Hammer]

The short answer is that Oz isn’t ready. At this point participation is probably limited to those who can read the code and understand what it’s trying to do (or at least ask questions based on the code). Previous OAuth experience helps a lot. Once Oz is more feature complete, it will have an actual readme…

 

EH

--