overall, I would personally like to see a full working site - complete with
db etc - integrated very seamlessly with shindig. at the same time, we don't
want to introduce db dependencies on the core code and should definitely
have a clear line between the gadget rendering/social data serving parts and
the implementing a site from scratch part.
it would be fantastic if shindig could just have a sub apache project that
depended on the core shindig project and added all of this goodness. if we
can't do this for incubator reasons i suppose you can put the code wherever
you like for now and then we can hopefully introduce it as a full sub
project once we get out of incubator?
mentors - can we make a sub project?
if so, how?
- cassie
On Mon, Apr 28, 2008 at 3:13 PM, Chris Chabot <[EMAIL PROTECTED]> wrote:
> I'm not sure if i fully grasp what you suggested, or i probably failed to
> explain properly.
>
> Currently we have a sample container, which is primarily build in
> javascript/html/xml, with a few hooks in shindig to make-it-work.
>
> What I'm currently developing is a 'real site', with a basic lightweight
> mvc structure, templates, mysql database access, etc
>
> While both serve the same conceptual purpose (being a sample container),
> the scope of things and the requirements to get it working is quite
> different between the two .. one is simply served by shindig's jetty server,
> the other requires setting up a 'site' and 'database' (although the
> requirements will be very simple: mysqladmin create shindig && mysql <
> shindig, plus dump the php files in a directory and point your apache/php
> server to it).
>
> So it's not an extension to the current sample container code (the
> html/js/xml based one), but a new code base on its own, so while it's the
> same it's also quite different. Hence my question if it should be a part of
> the svn repo, and if so .. where to put it?
>
> -- Chris
>
>
> On Apr 28, 2008, at 2:18 PM, Cassie wrote:
>
> +1 on the start it as shindig. we already have a small part of this with
>> the
>> sample container code and i was hoping to extend the sample container over
>> time. can you simply build more functionality into that part of shindig
>> and
>> branch later on if you find life too constraining?
>>
>> thanks.
>>
>> - cassie
>>
>>
>>
>> On Sat, Apr 26, 2008 at 6:09 PM, David Glazer <[EMAIL PROTECTED]> wrote:
>>
>> Seems slightly different from Caja to me -- one is related technology
>>> that
>>> will be integrated and used by many of the same 'customers'; the other is
>>> sample code showing how to be a customer. Either way, the idea of having
>>> a
>>> very rich sample container in the shindig project, both to show users how
>>> to
>>> build on shindig, and to help make sure we don't break any common
>>> container
>>> use cases, passes my Just-Makes-Sense filter also.
>>>
>>> (And, as Ropu says, "start as part of shindig" and, if necessary later,
>>> "just branch it" seems like an easy way to start.)
>>>
>>> - dG
>>>
>>> On Sat, Apr 26, 2008 at 4:54 AM, Ropu's iPhone <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>> I think it will be something like CAJA
>>>> Is part of shindig but also a separated project ,
>>>>
>>>> Perhaps we can start it as part of shindig and we its mature we just
>>>>
>>> branch
>>>
>>>> it
>>>>
>>>> My 2 cents
>>>>
>>>> Ropu
>>>>
>>>> Sent from Ropu's iPhone
>>>>
>>>>
>>>> On Apr 26, 2008, at 7:34, Chris Chabot <[EMAIL PROTECTED]> wrote:
>>>>
>>>> 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
>>>>>
>>>>>
>>>>
>>>
>
