Hi Chris,
> For what it's worth, in the Pylons Project, we decided to continue
> requiring the signing of a contributor's agreement (more or less the
> same contributor agreement as Zope requires). But instead of signing
> via paper, we ask that folks "sign" the contributor agreement by adding
>
On Wed, 2012-02-01 at 16:29 +0100, Jens Vagelpohl wrote:
> On Feb 1, 2012, at 15:53 , Charlie Clark wrote:
> > Currently the hurdle to getting involved is signing and sending the
> > committer agreement. A hurdle which I think is worth keeping.
>
> For any code released under the Zope Foundation
This is the summary for test reports received on the
zope-tests list between 2012-01-31 00:00:00 UTC and 2012-02-01 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/01/2012 09:57 AM, Michael Howitz wrote:
> Am 01.02.2012 um 02:00 schrieb Zope tests summarizer: [...]
>> [1]FAILED ZTK 1.0 / Python2.4.6 Linux 64bit
>> https://mail.zope.org/pipermail/zope-tests/2012-January/057143.html
>> [2]FAILED Z
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Apologies in advance for the cross-post: we need this to reach the
whole Zope community).
The Zope Foundation board is pleased to announce the regular 2012
general meeting of the foundation will be held on Friday, 16 March
2012, at 15:00 UTC. The
On 26 January 2012 04:29, Christopher Lozinski
wrote:
> Thank you for the sprint report.
>
> I think it is great that you are working on upgrading the ZMI.
>
> I am also turning my attention to this problem. Clearly ZMI needs an
> upgrade.
> I need an upgraded ZMI.
>
> Today I fired up my old ver
On Feb 1, 2012, at 15:53 , Charlie Clark wrote:
> Currently the hurdle to getting involved is signing and sending the committer
> agreement. A hurdle which I think is worth keeping.
For any code released under the Zope Foundation umbrella that hurdle cannot be
removed, anyway.
To be frank, I
On 1 February 2012 14:35, Jonathan Ballet wrote:
> On Wed, Feb 01, 2012 at 02:21:32PM +0100, Lennart Regebro wrote:
>>
>> What we would like to do, of course, is to have a self-hosted github.
>> :-) (And that exists. Buuut... it costs $250 per commiter and
>> year, so that's not an option, ob
Am 01.02.2012 um 02:00 schrieb Zope tests summarizer:
[...]
> [1]FAILED ZTK 1.0 / Python2.4.6 Linux 64bit
> https://mail.zope.org/pipermail/zope-tests/2012-January/057143.html
> [2]FAILED ZTK 1.0 / Python2.5.5 Linux 64bit
> https://mail.zope.org/pipermail/zope-tests/2012-Janua
Am 01.02.2012, 15:40 Uhr, schrieb Alexandre Garel
:
All I see here is usability not religion
Which is pretty much what Jens said originally.
To me, much of the argument seems to be trying to solve a different
problem: getting more people involved in contributing to Zope or at least
main
Le 01/02/2012 14:21, Lennart Regebro a écrit :
I do think the big issue is where to host it. Yes, fine, people have
opinions on git vs svn vs hg, etc. But that boils down to 25%
technical arguments, 25% what you are used to 25% what everyone else
uses and then 30% religion to make sure the bucke
On Wed, Feb 01, 2012 at 02:21:32PM +0100, Lennart Regebro wrote:
>
> What we would like to do, of course, is to have a self-hosted github.
> :-) (And that exists. Buuut... it costs $250 per commiter and
> year, so that's not an option, obviously.)
Just to be sure I keep the fire on: what abou
On 02/01/2012 02:29 PM, Alex Clark wrote:
Actually, they introduced improved Subversion client support late last
year:
- https://github.com/blog/966-improved-subversion-client-support
Unfortunately it is too unstable to be usable.
Wichert.
___
Zo
On 2/1/12 8:21 AM, Lennart Regebro wrote:
On Wed, Feb 1, 2012 at 13:03, Alex Clark wrote:
- what RCS software to use
- where to host it
It may be easier if we disentangled them.
Traditionally it was easier, but now-a-days with github and bitbucket they
are harder to disentangle.
It is enta
On Wed, Feb 1, 2012 at 13:03, Alex Clark wrote:
>> - what RCS software to use
>> - where to host it
>>
>> It may be easier if we disentangled them.
>
> Traditionally it was easier, but now-a-days with github and bitbucket they
> are harder to disentangle.
It is entangled, but it is important to n
On 2/1/12 6:08 AM, Jens Vagelpohl wrote:
On Feb 1, 2012, at 00:05 , Alex Clark wrote:
Bottom line: Zope stands to benefit greatly if the current active developers
keep an open mind about how/where/when development of Zope software should
occur. There are plenty of people that still think Zope
On Feb 1, 2012, at 00:05 , Alex Clark wrote:
> Bottom line: Zope stands to benefit greatly if the current active developers
> keep an open mind about how/where/when development of Zope software should
> occur. There are plenty of people that still think Zope software is cool, and
> plenty of sk
17 matches
Mail list logo
