Hi Alexandro, > Ok then my answer is, the application was an example, I would like to > see if its possible to work with the domain from a third party server > and see if we can document the process on interacting with internal > process (on the wiki at least).
well, I am not the decision maker, but before having a server under the OOo domain, I would love to see the application up and running on a machine. That's how we did it in the past -- QATrack first had a different domain name, so did the MirrorBrain instance. > CRM was an example of an application a project already worked on or need > to use, but you can call it whatever you want. From your answer is > evaluated on case by case basis. Then I would want you to tell me what > is the criteria for this evaluation and what goals does it need to take > care of. I am not aware of a fixed criteria, we handle it on a case-by-case basis, as in the past, not many people were in need for a OOo domain name. However, I as said, I'd love to see the application up and running before we issue a domain name for it. First the running system, the the domain -- not vice versa. > How do we know is supported by the community? > Is there any legacy emails documenting (mailing list discussions, chat > logs) this process, that we can go back through? Not that I'm aware of. However, without asking, we do not know. :-) This is the first time I hear of a CRM you plan, and I don't know what should be hosted there. Post your concrete ideas, set up the system, so everyone can see, then we can decide. Getting a domain name for "something", that does not make much sense. Florian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
