Re: [Zope-dev] DISCUSS: Community checkins for CVS
On Fri, 2001-09-21 at 15:51, Paul Everitt wrote: > > I'll reply in more depth later (on the way out for my b-day dinner) Hey, happy birthday, Paul! Michael Bernstein. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] DISCUSS: Community checkins for CVS
I'll reply in more depth later (on the way out for my b-day dinner), but in short: I think the issue of overhead on patches is something for us to consider. We won't do something that breaks the integrity of the code base, but there might be ample discussion directions. Thanks! --Paul Dieter Maurer wrote: > R. David Murray writes: > > ... > > So, the many small contributions that make a bazaar software project > > tend rapidly toward high quality, which is one of the things I got > > the impression you are trying to achieve by opening up the CVS > > repository, may not materialize under this Agreement. We'll have > > just about the same situation we have now, except that there will > > be more committers and therefore, one hopes, an increase in the > > pace of (controlled) change. An improvement, yes, but can we do > > even better? > I think (and indeed I really hope) that your anxiety is not founded. > > The Zope Contribution Initiative took Python as model. > There, you have beside contributors a bug tracking system > where problems can be reported and patches posted to. > > I do not know the details of Python development process, > especially the legal agreements behind it. > But somehow, it seems to work... > > > > Dieter > ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] DISCUSS: Community checkins for CVS
R. David Murray writes: > ... > So, the many small contributions that make a bazaar software project > tend rapidly toward high quality, which is one of the things I got > the impression you are trying to achieve by opening up the CVS > repository, may not materialize under this Agreement. We'll have > just about the same situation we have now, except that there will > be more committers and therefore, one hopes, an increase in the > pace of (controlled) change. An improvement, yes, but can we do > even better? I think (and indeed I really hope) that your anxiety is not founded. The Zope Contribution Initiative took Python as model. There, you have beside contributors a bug tracking system where problems can be reported and patches posted to. I do not know the details of Python development process, especially the legal agreements behind it. But somehow, it seems to work... Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Simple question about namespaces
Sidnei da Silva writes: > Im trying to do something like this: > when a user access: > http://www.mysite.com/somefolder > i wish to return: > http://www.mysite.com/onefolder/anotherfolder/somefolder > but do this in a transparent form, without redirecting the user. I guess, by Seems to call for a SiteAccess2 AccessRule Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] DISCUSS: Community checkins for CVS
This is a good point, and one that we need to settle on pretty quickly. The language is an artifact from the Mozilla contributor form, which served as the starting point for this. We intended to follow it, but with the advent of the joint ownership idea (which came late in the process), we might want to revisit it. Either way, I'll get an answer for you, thanks! --Paul Morten W. Petersen wrote: > On Thu, 20 Sep 2001, Paul Everitt wrote: > > >>So, let's begin what I'm sure will be a lively and illuminating >>discussion. :^) >> > > First man out? :-) > > Will a ZPL-ish license [1] be accepted (declared, ref. paragraph > 4 of the Zope Contributor Agreement) by the Zope Corporation? > > [1] http://www.thingamy.org/tpl > > -Morten > > ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] DISCUSS: Community checkins for CVS
Hi Paul! Hi list! In the last couple of weeks I have really looked forward for the CVS to be finally opened. Not that I would be the first to be accepted as a contributor (my Python is still lousy, as Stephan Richter could tell you ...), but I read things from ZC like "We are too busy to get contributed patches from the tracker into the CVS!" and on the other hand guys like Martijn Faassen begging for being allowed to help ... So this decision will be the beginning of a new Zope age ;-) What I haven't found on the CVS site yet is anything about peer-reviewing contributions before they go into the main tree. While I sometimes have the feeling that there are fixes from ZC people that should NOT have made it into a release, there are many patches from the community that are not getting into a release for a long time (this is not a very scientific statement, just my personal feeling). We need rules like "NO FIXES BETWEEN FINAL BETA AND RELEASE" (Absolutely no fixes I mean) -- and those rules should apply to everybody. We maybe also need an improved process for designing new API extensions etc. One case for that is the Zope Internationalization Project (http://www.eurozope.org/zip/FrontPage), which better sooner than later should become a core project. I have the feeling that with the current Wiki approach it will take ages to agree on a syntax for internationalization in Zope. I don't mean that we need a single implementation. But we need an agreed-on syntax that is part of the standard Zope package, so that a ZPT or DTML Method will not break if it uses translation tags. Joachim ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Simple question about namespaces
Hello Antonio, Actually, the problem can not be solved by the Virtual Host Product, for what i know. Let me explain the situation: Im trying to create something like a Template Folder, that contains some folders with images, some DTML Methods that create menus and the like, and a Content Folder, that contains the Content itself. I can have Templates that have just specialized parts of the template and look over at the Main Template folder, in case of not found some object at the Specialized Template. Im having trouble at two points: * First, in making the Specialized Template look over at the Main Template under not found some content (like i said, the specialized content may containt one or two images inside a images folder). Ive tried doing this by overriding the __bobo_traverse__ method of the Specialized Template, but it not worked. * Second, when i call the Content Folder, it is needed to apply the template to it. The content has a property that says what is the Specialized Template that has to be applied when calling it, so, when i call: http://www.mysite.com/ContentFolder i need to apply the template to the folder, maybe calling: http://www.mysite.com/MainTemplate/SpecializedTemplate/ContentFolder But i wish to do this by code, instead of redirecting the user to this url. Hope you understand what ive explained here, and if cannot help me, maybe can tell me who can help me. Thanx Em Friday 21 September 2001 10:00, you wrote: > This is not an answer. But you can find information, in how to´s, Zope Help, > or Products Help. Look for Virtual Host Product. > > Antonio Carrasco > > ¿The other question? > > - Original Message - > From: "Sidnei da Silva" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, September 21, 2001 2:08 PM > Subject: [Zope-dev] Simple question about namespaces > > > > Hello everyone, > > > > Im trying to do something like this: > > when a user access: > > http://www.mysite.com/somefolder > > i wish to return: > > http://www.mysite.com/onefolder/anotherfolder/somefolder > > but do this in a transparent form, without redirecting the user. I guess, > by > > calling the "somefolder" in the context of "onefolder/anotherfolder". > Maybe > > by overriding "__bobo_traverse__" > > > > Hope you can help me this time, cause the other questions I have asked to > > this list where not answered by anyone. > > > > Thanx in advance. > > > > -- > > Sidnei da Silva > > X3ng Consultoria e Desenvolvimento Ltda. > > [EMAIL PROTECTED] > > > > ___ > > Zope-Dev maillist - [EMAIL PROTECTED] > > http://lists.zope.org/mailman/listinfo/zope-dev > > ** No cross posts or HTML encoding! ** > > (Related lists - > > http://lists.zope.org/mailman/listinfo/zope-announce > > http://lists.zope.org/mailman/listinfo/zope ) > > > > -- Sidnei da Silva X3ng Consultoria e Desenvolvimento Ltda. [EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] DISCUSS: Community checkins for CVS
On Thu, 20 Sep 2001, Paul Everitt wrote: > So, let's begin what I'm sure will be a lively and illuminating > discussion. :^) First, would it be possible to put up a copy of the Contributor Agreement in html format? If you feel the only legal version for signing is the PDF one fine, but it would be a lot easier for people to check it out if there is an html version to read. Second, I suppose you should be aware of my biases before reading anything more. I don't believe in intellectual property, either copyright or patent. On the other hand, they are currently the law of the land; and, within what seems to me to be fair use kinds of standards, I try to respect copyrights while encouraging people to use vehicles that make use of as few of the restrictions imposed by copyrights and patents as possible. (You will guess that I am *not* a fan of the GPL, though I consider it far superior to a traditional copyright .) Also, I am not a lawyer and don't pretend to be very up on the subtleties of copyright law, so my concern may turn out to be naive. I very much like the intent stated in the Introduction, that of getting maximal rights into the hands of both the contributors and Zope Corporation to do things in the future with the code without having to get an endless set of sign-offs. However, I have a concern about the Agreement that isn't covered in the Introduction or the FAQ. I'm worried that the Agreement may exclude us from some of the benefits of the bazaar model of open source development. My key concern is summed up in this statement from the Introduction: "Essentially, a committer signs an agreement stating that all code that the committer submits has been created by her." The actual agreement does *not* say this, but "essentially" it does require it, since the things the committer has to swear to in submitting the code are very difficult to swear to unless he or she is the author of the code. Now, I have only contributed small amounts of code to Open Source projects so far. But I'm sure there are a lot more people out there who have "only contributed small amounts" than those who have contributed whole modules, and that there are even fewer people who do so much work that jumping through these kinds of legal hoops, and agreeing to a certain amount of liability, is worth while. In the cases where I have contributed, it's just been, "oh, cool, thanks for the patch", with no legal discussion and maybe an acknowledgment in the contributors file. My concern here is that under a regime such as this one, if I write ten lines of code that adds a feature I and a few other people really need in Zope, it is *not* going to get committed. I'm certainly not going to sign that agreement and become a committer just for ten lines of code, and I much doubt that Zope Corporation is going to want to go to the overhead of vetting my application just for ten lines of code. But if I wrote those ten lines, it hardly seems that any other contributor can commit them, since they don't own any rights to them that they can assign to Zope Corporation. I suppose that I could assign them those rights, but personally I find that idea repugnant since I don't believe in intellectual property . (Hmm. If I put my stuff in the public domain, how would that play in?) But aside from that, jumping through legal hoops (there would presumably have to be some sort of written assignment of rights) for ten lines of code is at the very least going to have a dampening effect on small contributions. Of course, you could get around this problem by having the committer rewrite the small submissions, but this seems a bit disingenuous, and it seems to me it might be legally questionable. In other words, under this Agreement, exactly what is the legal status of a one or two line patch? So, the many small contributions that make a bazaar software project tend rapidly toward high quality, which is one of the things I got the impression you are trying to achieve by opening up the CVS repository, may not materialize under this Agreement. We'll have just about the same situation we have now, except that there will be more committers and therefore, one hopes, an increase in the pace of (controlled) change. An improvement, yes, but can we do even better? Of course, I could be completely wrong in my guesses about the dynamics, but I figured somebody should play the devil's advocate here . --RDM ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Simple question about namespaces
Hello everyone, Im trying to do something like this: when a user access: http://www.mysite.com/somefolder i wish to return: http://www.mysite.com/onefolder/anotherfolder/somefolder but do this in a transparent form, without redirecting the user. I guess, by calling the "somefolder" in the context of "onefolder/anotherfolder". Maybe by overriding "__bobo_traverse__" Hope you can help me this time, cause the other questions I have asked to this list where not answered by anyone. Thanx in advance. -- Sidnei da Silva X3ng Consultoria e Desenvolvimento Ltda. [EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Structure-text :
On Thu, 20 Sep 2001, Jens Vagelpohl wrote: > AFAIK this is the right behavior and not a bug. you ask for the > StructureText document to be rendered and you inform the rendering > machinery that the document is in structured text. the rendering process > will output HTML. > > i think what you want is to simply say without > the "fmt" flag. that should get you the raw structured text. the rendering > process then assumes the document is already in some kind of HTML format > and does not try to generate HTML tags. > > On Thursday, September 20, 2001, at 07:14 , Sin Hang Kin wrote: > > When I use > > > > I got in the result. Are there any reason that it should be > > there? I wounder how can structured text generate valid html or be used in > > wap applications. I think you misread what Sin Hang Kin was getting at. Consider: Yes, you want StructuredTextDoc to be output using html formatting. But what you *don't* want is to have (or header or body) tags; those are all handled by standard_html_header/footer. Unless nesting html documents inside html documents is allowed by the html standards? And supported "correctly" (for some useful definition of "correctly") by almost all browsers? --RDM ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] DISCUSS: Community checkins for CVS
>>> "Morten W. Petersen" wrote > Will a ZPL-ish license [1] be accepted (declared, ref. paragraph > 4 of the Zope Contributor Agreement) by the Zope Corporation? > [1] http://www.thingamy.org/tpl Um, this license would seem to have the "obnoxious advertising clause" problem - it requires you to put the "This product... blah blah" in. If you end up with 25 different contributors with the same sort of clause, you're going to have a complete shambles. Anthony ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
