Re: [Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
Christian Theune wrote: > On 09/18/2009 02:04 PM, Stephan Richter wrote: >> On Friday 18 September 2009, Christian Theune wrote: I've also taken the liberty to update the ZTK policy to say that this should be done. (other steering group members can call me back if they don't like this policy change :) >>> I'm happy with that change, except that it might be worthwhile to >>> announce policy changes in a separate thread. >> Sounds good to me too, but I think the setup.py file is sufficient. > > I'm not sure I understand your comment correctly. The setup.py doesn't > generally need touching. I think there was some misunderstanding. I understood Christian to mean I shouldn't announce ZTK policy changes hidden in some thread. If there is new/changed policy we should announce it in a new thread so that people can pick up on it. I'm not sure we can *always* do this. For instance, I just edited the guidelines for when a package should be in the ZTK or not slightly, but it's not really a major policy change. I hope the SVN changelog is enough for this. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
On 09/18/2009 09:21 AM, Martijn Faassen wrote: > Hi there, > > Christian Theune wrote: >> I'm happy with that change, except that it might be worthwhile to >> announce policy changes in a separate thread. > > Good point. I'll do that in the future; please remind again if it > doesn't happen. I'll try to. I'll record that in the documentation about decisions. -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
On 09/18/2009 02:04 PM, Stephan Richter wrote: > On Friday 18 September 2009, Christian Theune wrote: >>> I've also taken the liberty to update the ZTK policy to say that this >>> should be done. (other steering group members can call me back if they >>> don't like this policy change :) >> >> I'm happy with that change, except that it might be worthwhile to >> announce policy changes in a separate thread. > > Sounds good to me too, but I think the setup.py file is sufficient. I'm not sure I understand your comment correctly. The setup.py doesn't generally need touching. My goal is to keep developers updated on changing policies. Whereas the setup.py change is a one-time thing that allows developers to identify which policy set is valid for a given package. Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
On Friday 18 September 2009, Christian Theune wrote: > > I've also taken the liberty to update the ZTK policy to say that this > > should be done. (other steering group members can call me back if they > > don't like this policy change :) > > I'm happy with that change, except that it might be worthwhile to > announce policy changes in a separate thread. Sounds good to me too, but I think the setup.py file is sufficient. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
Hi there, Christian Theune wrote: > I'm happy with that change, except that it might be worthwhile to > announce policy changes in a separate thread. Good point. I'll do that in the future; please remind again if it doesn't happen. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes
On 09/11/2009 05:58 PM, Martijn Faassen wrote: > Fred Drake wrote: >> On Fri, Sep 11, 2009 at 8:53 AM, Martijn Faassen >> wrote: >>> So, could you please follow this policy for ZTK packages in SVN? >> >> I suspect it would help if packages that are part of the ZTK have that >> indicated somewhere convenient, like near where the version number is >> specified in the setup.py file. Possibly with a link to the ZTK >> release policies. >> >> When making changes, we're often considering the relevant packages in >> isolation or in the context of our own applications, so a pointer to >> additional policies that apply is helpful. > > That's a good idea. > > The extreme version of this reminder would to mark it in a lot of places > in the package - in every python file and in setup.py near the version > and near the dependencies listing and every aspect that could possibly > be affected by ZTK policy. That is unworkable. > > I figured a reference to the ZTK policies on the top of the setup.py > would be enough to remind people. > > I've just committed these changes. > > I've also taken the liberty to update the ZTK policy to say that this > should be done. (other steering group members can call me back if they > don't like this policy change :) I'm happy with that change, except that it might be worthwhile to announce policy changes in a separate thread. Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
