Just one dev list. Later, when use of shindig is more widespread, it may make sense to have user lists that are language specific.
davep On Thu, Jun 5, 2008 at 9:10 AM, Ropu <[EMAIL PROTECTED]> wrote: > +1 to have JUST ONE shindig list. > > On Thu, Jun 5, 2008 at 12:29 AM, Chris Chabot <[EMAIL PROTECTED]> wrote: > >> Shindig it's self is intended to be 'language neutral', sure we only have 2 >> languages right now, but i think as far as the web goes we do happen to >> cover at least the 2 languages with the highest reach.. So partially we are >> already meeting that goal, and who knows that might expand somewhere in the >> future. >> >> As such, most of the talk here is about things that concern both versions.. >> the javascript samples, the features and the container configuration are all >> shared, so is the conceptual architecture; And that's not completely >> surprising since both versions implement the same open social specification. >> >> Hence i think you'll find most of the questions on this list are about >> 'shindig', and are relatively language neutral.. And the questions that are >> about specific implementations, i think you'd be surprised how many php >> questions are answered by the 'java guys', and how many java questions by >> the 'php guys' and the question how to solve a problem, and most of concepts >> and apply to both versions of shindig. >> >> Separating this out would mean you get less support, less knowledge shared, >> less peer review and having to discuss and solve a lot of problems twice.. >> so from my personal point of view i'd have to say 'please no!' :-) >> >> -- Chris >> >> >> On Jun 5, 2008, at 8:55 AM, Ram Sharma wrote: >> >> Hi, >>> >>> Do we have separate mailing list for Shindig PHP implementation. Why I am >>> asking this question is because I think it could be a better way to >>> concentrate on 1 product and separating out the problems significantly. >>> >>> -- >>> Ram Sharma >>> Software Engineer >>> Impetus Infotech (India) Pvt Ltd >>> Indore >>> >> >> > > > -- > .-. --- .--. ..- > R o p u >
