oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi Roger & All,

On Fri, 2010-07-02 at 15:57 +0200, Roger Erens wrote:
> If Zope2 is more or less another word for Plone, than I'm very
> confident that the ZTK will have a bright future.
> 
> Roger

This is probably a good point.  I'm sure that there are several
applications out there based on Zope2 that we do not even know about
publicly. But from an 'open' point of view, Plone (though very
widespread) is about it.

Just while we are talking about changing the name from 'Zope 3' to 'ZTK'
I also realized (prompted by an email on the grok-doc list) that it is
not obvious from the email below that ZTK was actually named
'BlueBream'. 

I think 'OUR' life going forward will be much easier if we just
reference Grok and not worry about keeping track of the names
underneath. :-)

Other Thoughts?

Cheers,
Tim

> 
> On Fri, Jul 2, 2010 at 14:22, Tim Cook <timothywayne.cook@xxxxxxxxx> wrote:
> > Hi OSHIPers,
> >
> > Below is an email regarding the infrastructure of OSHIP that will affect
> > all of us.  If you are not on the Grok-Dev list and have not read it, I
> > suggest that you do.  Even if you do not understand the implications at
> > this time, the knowledge may be important to you in the future.
> >
> > My synthesis is that we have no serious concerns.  In fact, it will mean
> > an even more stable OSHIP.
> >
> > I would appreciate it very much if the experienced Python developers
> > (Diego, Eduardo, etc.) voiced their opinions on this issue.  Even if it
> > means that you concur with my reading and ESPECIALLY if you have
> > additional input.
> >
> > Thanks,
> > Tim
> >
> > -------- Forwarded Message --------
> >> From: Jan-Wijbrand Kolman <janwijbrand@xxxxxxxxx>
> >> Reply-to: janwijbrand@xxxxxxxxx
> >> To: grok-dev@xxxxxxxx
> >> Subject: [Grok-dev] the ztk release and how that relates to Grok
> >> Date: Fri, 02 Jul 2010 14:09:08 +0200
> >>
> >> Hi,
> >>
> >> As you know (or not know) I'm the representative for the Grok community
> >> in the ztk-release-team.
> >>
> >> In the last few weeks Hanno Schlichting (representative for Zope2) and
> >> Christophe Combelles (representative for Bluebream) and myself have been
> >> discussing and working on what a ztk release would look like and how it
> >> would help each of the respective communities.
> >>
> >> As a result of this work Hanno was able to make an ztk-1.0 alpha release
> >> last wednesday!
> >>
> >> The "official" announcement is here:
> >>
> >>    http://permalink.gmane.org/gmane.comp.web.zope.devel/24738
> >>
> >> If you want to read about all the details that the team discussed, you
> >> can go here:
> >>
> >>    http://docs.zope.org/zopetoolkit/releaseteam/index.html
> >>
> >> What does this release mean for Grok?
> >>
> >> Well, in a way it doesn't change all that much for us. The practical
> >> outcome of the release is a set of *.cfg files that pin all the versions
> >> of the packages that comprise the ZTK.
> >>
> >> Grok (and its family of libraries) have been depending on specific
> >> revsions of the ztk for a while now already. So, my job now is to update
> >> Grok (and its family of libraries) to use this particular alpha release
> >> and report to the other members of the ztk-release-team whether is will
> >> give us a working Grok. They will do the same for Zope2 and Bluebream.
> >>
> >> I'm fairly confident this will give us working Grok without too much
> >> trouble. The release team can then work towards a 1.0 proper that is
> >> planned sometime at the beginning of september.
> >>
> >> I will continue to help Hanno and Christophe towards a ztk 1.0 release
> >> of course and after that in deciding how we will make bugfix releases
> >> and feature releases of the ztk. With three frameworks that official
> >> "consume" the ztk and maybe more to come, I think we helping giving it a
> >> solid future.
> >>
> >> kind regards, jw
> >>
> >> _______________________________________________
> >> Grok-dev mailing list
> >> Grok-dev@xxxxxxxx
> >> https://mail.zope.org/mailman/listinfo/grok-dev
> >
> > --
> > ***************************************************************
> > 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
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~oship-dev
> > Post to     : oship-dev@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~oship-dev
> > More help   : https://help.launchpad.net/ListHelp
> >
> >

-- 
***************************************************************
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