Hey Guys, a question for you all.
I'm currently working on a example container / SNS. The main reason
for it being that i need some small parts of the code anyhow for my
work, and i thought while I'm at it, why not make a real test case for
the PHP shindig gadget & social data server ... there's nothing like a
'real life' type situation to really test your code right :)
The goal is not to make a complete 'open source SNS', though i guess
it could serve as a base for it at some point, but more to have all
the basic open social activities represented in it, so a social graph
(with all the open social defined profile fields), activity streams
and gadgets of course :) (Adding more functionality would be easy, but
for now would take to much time away from my actual shindig work)
Now i'll release this code as open source, since i think it will be
useful in many ways, first of all it might serve as an example on how
to use shindig in a SNS to some, or even as a basis for new sites but
it also makes a great testbed for both us shindig server developers
(since the java and php versions are wire format compatible you could
use either to power the gadgets / social data part of it), could be
used to show case our work (once we have a zone or something equally
adequate to host such a showcase), and is probably a blessing for
gadget developers too where they could develop locally and privately
on their own local development SNS.
So my question is, shall i release this as my own project (no problem,
i have my own servers to host the pages and showcases on, and can put
the code on google code), or would it make sense to put this under the
'shindig' name / and in the shindig repo and make it an 'official part
of the shindig project'. I'm asking since making a demo SNS is a bit
outside of the scope of the project definition ("shindig is an open
source implementation of the open social specification and gadget
specification", but on the other hand it Just-Makes-Sense(Tm) to have
it in the shindig repo too :)
I'd love your opinions on this.
-- Chris
