Hey peeps,
I'm catching up on some old list traffic, and I thought I'd comment
since I was too busy when this first came up. I just want a little
clarification:
Stefano originally wrote:
The closest thing that we have in place for that is Pier's kernel (that
was development with my
Tony Collen wrote:
Hey peeps,
I'm catching up on some old list traffic, and I thought I'd comment
since I was too busy when this first came up. I just want a little
clarification:
Stefano originally wrote:
The closest thing that we have in place for that is Pier's kernel (that
was development
Stefano Mazzocchi wrote:
nononononon
when I said somebody elses I meant somebody else rather than people
in the cocoon community.
Tani will be based on Pier's code... even if probably we'll have to
rewrite it from scratch anyway [more on this soon].
10-4. :) Everything cleared up. That's
On Sat, 28 Aug 2004 10:15:29 -0400, Stefano Mazzocchi
[EMAIL PROTECTED] wrote:
Torsten Curdt wrote:
+1 for the branch
and although I really like the name tani
I think we should stick to what we decided.
no fancy names.
+1 for keeping the new-kernel (or naming
it block-kernel)
On 29 Aug 2004, at 02:53, Stefano Mazzocchi wrote:
in case it wasn't clear, new-kernel will be renamed Tani.
Fair enough. Maybe you should have posted a [request] rename of the
new-kernel branch then. :-)
I'm not going to try and understand why a mere change of a directory
name is necessary to
Stefano Mazzocchi wrote:
snip/
Just like Ugo, I feel the need for a clean slate and a place where I
can work without breaking everybody else's code. I personally don't
care if the code will be used or not, what I care is to create a
prototype to show to this community and to my group at MIT,
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
snip/
Just like Ugo, I feel the need for a clean slate and a place where I
can work without breaking everybody else's code. I personally don't
care if the code will be used or not, what I care is to create a
prototype to show to this community and
On 28 Aug 2004, at 06:44, David Crossley wrote:
However, remember the fate of our woody ... we decided
no fanciful names in released components.
Yup. +1 on keeping the new-kernel branch.
/Steven
--
Steven Noelshttp://outerthought.org/
Outerthought - Open Source Java
+1 for the branch
and although I really like the name tani
I think we should stick to what we decided.
no fancy names.
+1 for keeping the new-kernel (or naming
it block-kernel)
cheers
--
Torsten
Torsten Curdt wrote:
+1 for the branch
and although I really like the name tani
I think we should stick to what we decided.
no fancy names.
+1 for keeping the new-kernel (or naming
it block-kernel)
Hmmm, what about butterfly then?
The problem with calling it new-kernel is that the new kernel is
Stefano Mazzocchi wrote:
This is, in fact, a cocoon internal fork and, as for the rules of
revolutionaries, every committer is allowed to ask for it with the name
that he/she pleases.
How it's so, if it is planned (and discussed, and to some point
designed) feature? Hence, no need for invoking
The problem with calling it new-kernel is that the new kernel is just
part of what that branch will host and this will create naming issues.
Well, ok... thought you wanted to call the kernel
itself tani.
I don't want to appear pushy, but this is not a vote.
Well, I guess we all understood ...but
On 28 Aug 2004, at 16:15, Stefano Mazzocchi wrote:
Just like Ugo, I feel the need for a clean slate and a place where I
can work without breaking everybody else's code.
Let's all use our own hard disk then. :-)
More seriously: there's Butterfly, new-kernel, 2.1_X, trunk, and now
Tani. I'm
Steven Noels wrote:
On 28 Aug 2004, at 16:15, Stefano Mazzocchi wrote:
Just like Ugo, I feel the need for a clean slate and a place where I
can work without breaking everybody else's code.
Let's all use our own hard disk then. :-)
We already are, but you don't see SVN commits from my HD, nor I
I've been away from the real cocoon development for a while, but my day
job requires me to build a prototype using cocoon but with real blocks
implemented.
Therefore, I need to get real blocks working on cocoon.
The closest thing that we have in place for that is Pier's kernel (that
was
Stefano Mazzocchi wrote:
I hereby request
the creation of the tani effort, which is the codename for what I hope
it will become Cocoon 2.2, even if this will have to be decided by the
community once we feel confident enough.
One of my goals for such a new framework is transparent migration:
On 27 Aug 2004, at 19:04, Vadim Gritsenko wrote:
I don't understand what tani means
(from an old email)
Tani is the Japanese word for Valley.
http://www.nuthatch.com/kanji/demo/8c37.html
Its kanji is also quite nice:
http://ww1.baywell.ne.jp/fpweb/drlatham/nihongo/kanji/less10/tani.gif
/ \
/ /\
Pier Fumagalli wrote:
On 27 Aug 2004, at 19:04, Vadim Gritsenko wrote:
I don't understand what tani means
(from an old email)
Tani is the Japanese word for Valley.
http://www.nuthatch.com/kanji/demo/8c37.html
Its kanji is also quite nice:
Il giorno 27/ago/04, alle 18:38, Stefano Mazzocchi ha scritto:
I don't need a vote to make this happen, but I'm asking for comments.
No comments, just a go ahead from me and a question: what does tani
stand for?
Ugo
--
Ugo Cei - http://beblogging.com/
smime.p7s
Description: S/MIME
Pier Fumagalli wrote:
Tani is the Japanese word for Valley.
snipped the excellent portrayal in ascii art
because the house fell down in the email reply :-
It looks like a house (the block) in the middle of a valley (the
container)..
The combination is what I really like: the name valley
Le 27 août 04, à 18:38, Stefano Mazzocchi a écrit :
...I don't need a vote to make this happen...
But still: big +1 here. I like the name and kanji as well.
-Bertrand, who was lately (pessimistically) wondering whether someone
would need real blocks bad enough to actually implement them ;-)
21 matches
Mail list logo
