[Embedlets-dev] Re [management] Pitching in...

[Ted K. <tk...@ya...>]

Sheesh!  You guys were really flying fast and furious there with the posts for
about an hour or so!  And wouldn't you know I had just bumped into a girl I use
to know in high school just before it started and I was chatting with her (and
I almost *never* chat with anyone but for her I made an exception ;-)  Your
posts kept popping up over top of my chat session and messing up my
concentration!


<private list idea>

Anyway, as for the private list idea, after spending a significant amount of
time combing through the Apache developer lists in preparation for starting up
the Embedlets project I discovered that it appears to be normal practice for
*almost all* development traffic to be placed on the open developer's list for
the whole world to see.  Some of Stefano Mazzocchi's candid posts were
especially illuminating and to me they illustrated nicely that open source
development can get rough at times but that this is normal.  And believe me,
our development traffic has been extremely civil when compared to some of the
traffic that other well known projects have generated... 


<developer credit>

Actually, I thought that we had already had the beginnings of a discussion on
the developer credit topic when the licensing issue first came up.  The
conclusion was that ultimately we would need to create an Embedlets legal
entity to hold the Embedlets license but until that time one of us would need
to put our name on the source code in order to make the license stick.  Since
Andrzej took it upon himself to sling the seed code base, he said that he would
take responsibility for the license for now until the legal entity was set up. 
Perhaps some of this discussion went on off list which is yet another good
reason to have as much development traffic go through the main development list
as possible I guess...

Anyway, Andrzej also said that the code he was posting was for discussion
purposes only and it was more like a very detailed illustration of what
Embedlets and an Embedlet container might look like rather than an official
code base.  This was probably also a good reason for not officially placing the
code under version control because none of these issues had been worked out
yet.  In fact, perhaps we should hold off on officially placing the code into
the CVS until we create the Embedlets legal entity and get the license and
credits arranged the way we want them?  

From my perspective, I would not mind having my name listed on the architecture
document as an idea contributor but I do not think my name should go on any of
the core Embedlets or Outpost code unless I actually end up contributing some
code or critical thinking to these pieces at some point in time.  The Embedlets
Container and code base is definitely Gregg's, Chris's and Andrzej's baby and I
would imagine that their names would be the primary ones to appear in this
code.  Actually, I have been studying the code this week in order to finally
figure out what the heck you three have been cooking up over the past month or
so.  It is slowly started to sink in though...

I am just happy to be helping out with this effort and I feel privlidged to be
able to learn all of these cutting-edge technologies from people who have had
years of experience in this area.   And of course I hope to make a significant
code contribution with the Wiring Tool too just as Brill will be making one
with the JAPL Cork implementation.


So, does anyone know how we about creating an Embedlets legal entity?


Ted


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/