Re: [proposal] Private Branches
Il giorno 29/lug/04, alle 20:20, Stefano Mazzocchi ha scritto: My proposal is to create a private branch for every committer that wants it and place it in http://svn.apache.org/repos/asf/cocoon/private/[id] +1 For example, I have a new version of linotype I'm working on that I would like to host there instead of my own CVS server. Why can't you just upgrade the current linotype block? Ugo -- Ugo Cei - http://beblogging.com/ smime.p7s Description: S/MIME cryptographic signature
Re: [proposal] Private Branches
Stefano Mazzocchi wrote: My proposal is to create a private branch for every committer that wants it and place it in http://svn.apache.org/repos/asf/cocoon/private/[id] +1 -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
Re: [proposal] Private Branches
On 29 Jul 2004, at 23:50, Stefano Mazzocchi wrote: fine, what about http://svn.apache.org/repos/asf/cocoon/ (whiteboard|scratchpad|research) Much better. But you are suggesting a branch for all these, no? I'm not so sure about that - branches tend to hide things away. Of course, branching is better|easier than scratchpad areas, so this might be the better solution. For the record: I'm -1 on any labelling or classification system which includes the name|id|alias of a contributor. Anything else which is workable, facilitates creativity, groups common work areas under a single name, and doesn't create code islands, I'm violently +1. /Steven -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source Java XMLAn Orixo Member Read my weblog athttp://blogs.cocoondev.org/stevenn/ stevenn at outerthought.orgstevenn at apache.org
Re: [proposal] Private Branches
Steven Noels wrote: On 29 Jul 2004, at 23:50, Stefano Mazzocchi wrote: fine, what about http://svn.apache.org/repos/asf/cocoon/ (whiteboard|scratchpad|research) We had already discussed (was it 1, 2 years ago) that personal playgrounds are bad... Much better. But you are suggesting a branch for all these, no? I'm not so sure about that - branches tend to hide things away. Of course, branching is better|easier than scratchpad areas, so this might be the better solution. If something is a branch, it should actually be a branch (ie copy from the main code), so it can merge. If not it can still reside in branches, as in subversion it's just a dir. For the record: I'm -1 on any labelling or classification system which includes the name|id|alias of a contributor. Same here. Anything else which is workable, facilitates creativity, groups common work areas under a single name, and doesn't create code islands, I'm violently +1. If someone wants to experiment on a branch, just say so and do it, and label the branch with a significant name. When/if time to merge back will occur, we will vote. Simple IMHO. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: [proposal] Private Branches
Stefano Mazzocchi wrote: http://svn.apache.org/repos/asf/cocoon/(whiteboard|scratchpad|research) I like research or playground best. Anyway, let's make it more concrete: These days I started to work on the Cocoon BlockDeployer and I plan to share my work within the next two or three weeks. I would put it into http://svn.apache.org/repos/asf/cocoon/playground/block-deployer (I don't think putting it into the branches directory is appropriate because it is definitly no branch.) Any objections or other proposals? -- Reinhard
Re: [proposal] Private Branches
Reinhard Poetz wrote: Stefano Mazzocchi wrote: http://svn.apache.org/repos/asf/cocoon/(whiteboard|scratchpad|research) I like research or playground best. Anyway, let's make it more concrete: These days I started to work on the Cocoon BlockDeployer and I plan to share my work within the next two or three weeks. I would put it into http://svn.apache.org/repos/asf/cocoon/playground/block-deployer (I don't think putting it into the branches directory is appropriate because it is definitly no branch.) Any objections or other proposals? No objections, just that 'playground' seems like kids playing... better would be 'whiteboard' IMHO. Not that I oppose to any name, you can even name it SGdfgDSGDSFG as long as it gets in there :-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: [proposal] Private Branches
On Thu, 29 Jul 2004, Stefano Mazzocchi wrote: ..snipped inspiring text about using SNV features and perhaps changing things so it fits our patterns better now that we 'can'. ... My proposal is to create a private branch for every committer that wants it and place it in http://svn.apache.org/repos/asf/cocoon/private/[id] 1) allow people to experiment in their own place 2) allow stuff to happen without giving the impression that it is a fork or that the status quo is in danger 3) give the feeling of some privacy This would worry me somewhat; within the ASF we try to help the community develop software and value that a project survive an individuals slant on it. It is the fact that the whole community follows all commits (by and large), there is comprehensive peer review and that the whole community stands behind a release which gives the ASF code that unique slant on quality and liability. Encouraging[*] this would in my opinion: - give rise to personal slants - allow certain takes of the code to be less of a group product; but instead to be driven by 1 or 2 individuals - increase the risk that a wholesale chunk of code which is developed without sufficient peer review is subsequently introduced into the main brach without enough appropriate oversight by the whole community. which seems contrary to a certain spirit I personally hold dear when it comes to the ASF. A more neutral name; say 'note pad', 'scratrchpad' or 'skunk works' would perhaps be more appropriate; as one stresses that it is people working _together_ that counts. Finally I personally would expect that -if- the ASF see a situation where significant chunks of code are developed outside the normal main peer reviewed track, and see such chunks suddenly imported in a main branch -then- I do expect a discussion about exactly what peer review and oversight is, and what the limits between 2.0 license, CLA and a Software Grant really is. Dw *: Of course we would never disallow this. People can always make their own private forks.
Re: [proposal] Private Branches
On 30 Jul 2004, at 19:18, Dirk-Willem van Gulik wrote: This would worry me somewhat; Ditto here: +1. /Steven -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source Java XMLAn Orixo Member Read my weblog athttp://blogs.cocoondev.org/stevenn/ stevenn at outerthought.orgstevenn at apache.org
Re: [proposal] Private Branches
On 29 Jul 2004, at 20:20, Stefano Mazzocchi wrote: My proposal is to create a private branch for every committer that wants it and place it in http://svn.apache.org/repos/asf/cocoon/private/[id] Thoughts? I know I'm at the verge of becoming a traditionalist, but IMHO we should never create personal freewheeling areas for reasons of false ownership feelings and oversight. Who has still some sort of semi-complete knowledge coverage over the Cocoon source trees? Wouldn't that become even harder with these private directories? We should be able to contain such stuff into a clearly marked, but not-tied-to-a-person area. The ASF infrastructure shouldn't serve as a personal backup solution, no? /Steven -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source Java XMLAn Orixo Member Read my weblog athttp://blogs.cocoondev.org/stevenn/ stevenn at outerthought.orgstevenn at apache.org
Re: [proposal] Private Branches
Steven Noels wrote: On 29 Jul 2004, at 20:20, Stefano Mazzocchi wrote: My proposal is to create a private branch for every committer that wants it and place it in http://svn.apache.org/repos/asf/cocoon/private/[id] Thoughts? I know I'm at the verge of becoming a traditionalist, but IMHO we should never create personal freewheeling areas for reasons of false ownership feelings and oversight. Who has still some sort of semi-complete knowledge coverage over the Cocoon source trees? Wouldn't that become even harder with these private directories? We should be able to contain such stuff into a clearly marked, but not-tied-to-a-person area. fine, what about http://svn.apache.org/repos/asf/cocoon/(whiteboard|scratchpad|research) ? The ASF infrastructure shouldn't serve as a personal backup solution, no? that's uncalled for. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: [proposal] Private Branches
Stefano Mazzocchi wrote:
I've been a strong believer in 'internal innovation', which means to
give room for people to experiment.
We have now migrated onto SVN, which unlike CVS, has a great deal of
support for moving things around and merging different parts of the
tree together.
My proposal is to create a private branch for every committer that
wants it and place it in
http://svn.apache.org/repos/asf/cocoon/private/[id]
The reason for this is:
1) allow people to experiment in their own place
2) allow stuff to happen without giving the impression that it is a
fork or that the status quo is in danger
3) give the feeling of some privacy
For example, I have a new version of linotype I'm working on that I
would like to host there instead of my own CVS server.
And Ugo is playing with Butterfly, which should be there instead on
branches alongside the cocoon 2.1.6 branch!!
Thoughts?
-1 for people-private places. They will refrain non-owners to dig in
and eventually work with the owner, and can lead to code ownership
islands and one man shows.
What we need is a cocoon/experiments/[name] branch where name is
schecoon, linotype, butterfly, etc.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
RE: [proposal] Private Branches
What about playground? Works for us over here, and give people somewhere to throw their toys ;) -Original Message- From: Vadim Gritsenko [mailto:[EMAIL PROTECTED] Sent: Friday, 30 July 2004 1:58 p.m. To: [EMAIL PROTECTED] Subject: Re: [proposal] Private Branches Stefano Mazzocchi wrote: fine, what about http://svn.apache.org/repos/asf/cocoon/(whiteboard|scratchpad|research ) ? No objections. But we should not use scratchpad - we already have one. Vadim CAUTION: This e-mail and any attachment(s) contains information that is intended to be read only by the named recipient(s). It may contain information that is confidential, proprietary or the subject of legal privilege. This information is not to be used by any other person and/or organisation. If you are not the intended recipient, please advise us immediately and delete this e-mail from your system. Do not use any information contained in it. For more information on the Television New Zealand Group, visit us online at http://www.tvnz.co.nz
