On Mon, Aug 22, 2011 at 02:09:23PM -0400, Sam Bull wrote: > Here are some of the questions we've come across:
Whew, those are very general questions where there are no right and wrong answers (like "how should we run our business" -- which you should know better), just advantages and disadvantages. > - What will we ultimately be delivering to our clients (a tarball of > the code, a physical server, a VM image, a WAR file, etc.)? I'd go for the software package alone. > - Who is responsible for the upkeep of the server? I'd leave that to the customer, and offer to do that for an additional fee. > - How will new versions of the product (new code and new content) be > provided? If you're asking about the technical side (not about cost models for upgrade versions), this depends on how you delivered it in the first place. If it's a package, I'd supply a new package. > - How will python dependencies be maintained? I don't see other choices other than document it or require it technically. The latter is possible if you deliver a distro-specific package. > - Can we assume that the server can access the Internet? If the software isn't something requiring Internet, I wouldn't assume that. > - Can we assume that we can access the server from the Internet? In general, I wouldn't assume that. However, this could be an option that has to be agreed with the customer (I've heard about large organizations allowing this for 24/7 support of their financial software). With kind regards, Baurzhan,. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
