Just to chime in with my 0.02$. I don't think it's really a valid point to call things 'high priority' when in fact they are not. Having to update a number of strings in a couple of files would be very low on my list of issues that need to be resolved before a 1.0 release, a fatal exception when you render a popular gadget, yeah that would be a blocking bug, but this is a world away from that kind of an priority.
One of the basic mantra's of open source is 'release early, release often' (or from an apache culture point of view, but meaning the same: "a good idea and crappy code is a great way attract new contributers"). To say that every detail has to be perfect to the last bit, for every possible use, and for every convenience seems very far away from what the open source culture is. Open source development is however also a demand driven development model, so if this is an itch you want to scratch, patches are welcome! ps, what open source products have you guys been using that you believe a 1.0 release should be perfect and include the kitchen sink too, and to top it of be completely elegantly coded too? I've been using oss for a bit over 10 years now, and i've never seen such 1.0 releases as is described in some of these emails. I must've really missed out on something. On Wed, Dec 17, 2008 at 12:04 AM, Eric Tschetter <[email protected]> wrote: > On Tue, Dec 16, 2008 at 10:30 AM, Kevin Brown <[email protected]> wrote: > > On Mon, Dec 15, 2008 at 9:14 PM, Carmen Sarlo <[email protected]> wrote: > > > >> Hello, > >> > >> We want to serve shindig using something other then the root context > (/). > >> Say something like (/shindig). I see the examples are hard coded. I can > >> live with that, but what about the rest of the code? What is needed to > get > >> this working to serve other then root context? We will be using the java > >> implementation of shindig. > > > > > > It should work just fine on any context, but there are quite a few urls > you > > have to update. There's an open issue to migrate all of this to one > place, > > but nobody's ever gotten around to it. > > > > Make sure you update all the paths in the container config > > (trunk/config/container.js) as well as the language-specific > configuration > > file (for java, it's trunk/java/common/config/shindig.properties). > > > > Once you've got that, you should be able to set web.xml appropriately. > > > Why isn't fixing this a part of the "release" version of Shindig? I > would assume that ease of integration would be a high priority in > something that is supposed to be released for external consumption. > > Also, should people looking to integrate against Shindig be > integrating against trunk? I'm assuming the paths in your message > should be pointing to the release branch. I know I wouldn't be very > happy if I were to start integrating against Shindig because I heard > it was going to release a stable version only to find out that the > version I integrated against is the unstable dev branch. > > Not trying to troll, it just struck me as odd that there was no > mentioning of fixing this integration issue in any of the release > threads. > > --Eric Tschetter >
