oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi All,
Please provide some feedback on the following proposal(s).

Over the past several days I have had the opportunity to sit with
several people and watch them go through the OSHIP installation process
on different platforms.   What "I" thought was rather straight forward;
I now realize can be very arduous and confusing.  The bad part is that
none of these people were totally clues about OSHIP or computers in
general.  Something must be done to make this easier.

I have spent some time figuring out the file release process on
Launchpad. So, I will first of all be doing a Python 2.6 compatibility
test today.  I think we are there with a few minor changes.  Then I want
to release .zip source files tagged as oship-1.0a5 that are platform
specific and include all of the eggs. 

I will initially release:
oship-1.0a5-linux-x86.zip
oship-1.0a5-linux-x86_64.zip
oship-1.0a5-win-x86.zip
oship-1.0a5-win-x86_64.zip

Then the installation procedure will be something like:
OSHIP requires Python 2.5 or Python 2.6
1) Download the source for your platform
2) Unzip the oship source file into a directory in your home directory
3) Go into the oship directory containing the file bootstrap.py
4) Execute python bootstrap.py
5) Execute bin/buildout
6) Start your OSHIP server with bin/oship-ctl fg
   * Windows users should use bin/paster serve etc/deploy.ini
7) In your browser go to http://localhost:8080
8) In the Add Applications box for oship.oship; enter 'oship (w/o
quotes) click the create button
9) Now click the new oship link at the top of the page.

These probably need some touch up but you get the idea of how much
simpler this is?

Does anyone see any problems with this approach?

Then OSHIP Developers will have a separate set of instructions that
includes setting up a shared eggs directory and virtual environments for
testing under different Python versions.  
But even then not all developers will need to do that.  Maybe only the
core team will do that kind of testing before allowing a merge to the
trunk?

Thoughts?

--Tim






-- 
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook 
***************************************************************
*You may get my Public GPG key from  popular keyservers or    *
*from this link http://timothywayne.cook.googlepages.com/home *
***************************************************************

Attachment: signature.asc
Description: This is a digitally signed message part