> -----Original Message----- > From: Chris Chabot [mailto:[EMAIL PROTECTED] > > 1) The best way to do this .. is by just doing it! Dive in and don't > give up until it's done! :-) Once you have a somewhat working, well > coded version (doesn't have to be complete or without bugs mind you, > just in style with our project goals: good quality and preferably > readable code:) and you feel your ready to show it to the world. go > and submit a patch in our jira with the .net implementation.
Thank you for your response. The time for this will be sponsored from my employer, so there are still a few things to get approved of on this end... The main project I am working on is .Net driven, and we are experimenting with the possibility of using the Java front end as-is, and serving the gadgets from the .Net side... so, it just depends on some experiments this coming week. > 2) Shindig is an apache project so very open ... all contributions are > welcomed with open arms and happiness! So don't ever worry about that, > we'll never refuse from good code that fits our project's goals (and > being language neutral aka supporting shindig in many languages is > indeed part of our goal) Thank you for this insight... I know that some open projects are more, or less, so than others. Which is my main reason for asking. > 3) As long as you don't mind releasing the code under the apache > license v2, and the quality is good (and you intend to keep supporting > it and help build a community for it), it's very welcome! Once the > patch has been accepted, and you show your ability by your code and > involvement, you can join the committers ranks, get a vote in the > projects direction, etc ... apache works with 'meritocracy' ... > apache.org has a lot of pages explaining this so i won't :) Understandable, I've submitted a few patches before on various f/oss projects, just never had the opportunity to be as involved as this may be with one. > 4) It's not really the 'Shindig .net implementation' until shindig has > accepted it. However no harm in saying "to be a part of shindig" while > working on that :) Understandable... that is the hopeful intent though, and will probably follow most of the Java namespacing. Though implementation may be a bit different. > 5) Don't be afraid to ask questions, we're usually very friendly folk > :) Oh, I'm sure I will be asking quite a bit. ;) > 6) Don't forget there's a Java and PHP version, they will often be the > only map you have to figure out what to do and how to do it and in > what order .. while the client facing spec is well documented, the > server side isn't. So get friendly with one of the 2 versions, and > learn how it works internally and use that as either a reference or at- > least a inspiration of what to do Yeah, that was a large part of the plan... Are both versions using the same client-side implementation? I haven't looked at the PHP version yet. > Hope that answers your questions, Yes, it was very helpful. > -- Chris > > > On Jun 19, 2008, at 11:52 PM, Michael Ryan (Software Developer) wrote: > > > > > What would the ramifications be of starting a .Net (C#) > implementation > > of OpenSocial... Is calling it say "Shindig .Net" out of the > question, > > and what is the possibility of having it hosted with the Java and PHP > > versions? > > > > I know there is an "OpenSocial" .Net project on CodePlex, but it seem > > that hasn't been touched in some time now... I've attempted to > > contact > > the author on that project, but haven't seen a response yet, will > give > > it a few more days. > > > > Just wanting some input/advice before I begin down this path... > > > > -- > > Michael J. Ryan -- Software Developer -- Apollo Group > > > > > > > > This message is private and confidential. If you have received it in > > error, please notify the sender and remove it from your system. This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
