oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi (again) Tarsis,

Okay.  I think that for HKCR development we should re-focus.  You have
not been given enough guidance on this.  

So I believe that the best thing to do is to take the knowledge you have
now about Plone and we will put it to use in a very deliberate and
staged way.  I will create blueprints this week but for now start with
this approach.  

Development Concept:
HKCR is a Plone product.

This means that we can now use the Plone installation process without
changes.  This also means that all of the experience out there can be
plugged into and used to develop HKCR.  The Plone Product development
approach is a well known commodity.

We can leverage the functionality of other Plone Products.

We can also leverage the Plone upgrade process(es).
This makes HKCR much easier to maintain and upgrade.

We will use Plone 4.x (latest version)
 
HKCR 1.0.0-alpha-1
For this version create a Product that installs a new skin, re-branding
Plone as HKCR. If you do not have the complete set of HKCR graphics
please let me know and I'll send them to you.

Can you (Tarsis) estimate how long this will take you?

Thanks,
Tim




On Mon, 2010-07-19 at 04:51 -0500, Tim Cook wrote:
> On Mon, 2010-07-19 at 03:39 -0500, Tim Cook wrote:
> > Hi Tarsis,
> > 
> > I'm going to need a little more information in order to be of much help.
> > 
> > First of all, is HKCR installable/runable under Python 2.6?
> > As I recall this was the issue that was to be corrected the last time we
> > talked.
> 
> Hi Tarsis,
> 
> Please reply to the other questions first.
> 
> Since the last commit to the hkcr trunk was 3 months ago, I am going to
> assume the answer to this question is; no.
> 
> Since there is functionality  in Python 2.5 and later that we will need
> (specifically the uuid generation) then you should take the lessons that
> you have learned and re-implement them using Plone 4.
> 
> Plone 4 is at beta 5 and requires Python 2.5 or later. 
> 
> I do not believe that attempting to upgrade from Plone 3.x is a useful
> strategy for HKCR.  Re-implementation will give us a much cleaner base
> to work from.
> 
> I say this because the requirements for hkcr have been a little vague
> until now.
> 
> We still have a few issues to work out about CCDs but I believe that
> this can be solved within the next few days while you are working on the
> Plone 4 base.
> 
> Over this coming week I will create some blueprints that will give you
> better details regarding hkcr functionality requirements.
> 
> Okay?
> 
> Cheers,
> Tim
> 
> 

-- 
***************************************************************
Timothy Cook, MSc
Project Lead - Multi-Level Healthcare Information Modeling
http://www.mlhim.org 

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

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