On Wed, 2008-04-09 at 19:57 +0200, Axel Dörfler wrote: > "Jorge G. Mare" <koki@xxxxxxxxxxxxxx> wrote: > > > Not sure if I understand what you're saying, but in the long run, > > > if we > > > intend to keep our user databases separate, we definitely should > > > have > > > some mechanism to synchronize them automatically from time to time. > > Besides the fact that for security reasons we may not be allowed the > > two > > systems sitting on different server to access each other's DBs, we > > are > > making the conscious decision to avoid any dependencies between two > > different systems with a totally different code base and serving > > different purposes, in order to make each of them easier to > > maintain/upgrade independently of the other. > > > > In other words, think of it as two different systems, each with their > > own (separate) login/user registration mechanisms, just like the > > website > > and Berlios, for example. :) > > I know what you are getting at, but IMO it's just a poor excuse to do > it right (which might be perfectly explained by limited resources, > though). The reasoning behind the decision is definitely not an excuse. It was actually based on the available resources/skill set, what we think is best in terms of reliability and (future) maintainability, and by weighing pros and cons. Moreover, Trac and the website will be on separate servers, and for security reasons we are not allowed to access DBs/systems accross servers; this is not a self-imposed restriction, nor something that we can do anything about (short of declining ISC's offer, which would be a waste). Sure, there is a trade-off, but it us minimal, considering that creating an account with Trac would take you only a few seconds (iIt's not like we are forcing Trac users a 10 minute registration process). > Of course they are different services, as is Google mail, Blogger, you > name it. But there is only one provider of the service, and having to > create more than one account is just annoying. It's perfectly fine to > have a user database that serves different purposes. Well, we are not Google, are we? :) As you very well know, this is an open source project sustained by volunteers, and we all live and accept the limitations that that entails. In an ideal world, many things would be different; but open source projects are far from ideal, and we all live with it. > In any case, having two different user accounts is not an acceptable > solution for me if it's not just a short-term temporary arrangement. I think you come in a bit late. This was discussed and agreed upon on this list several weeks ago, and Niels has since then put quite a bit of work to make it happen. Can you please show some flexibility here? It would really make it a lot easier for all of us. :) Cheers, Koki ----------------------------------------------------------------------- haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List