Hi,
a number of questions:
- Are the proposed committers, people "assigned to work on the project"
or are they genuinely interested in this software.
IAW, will they stick around or leave as soon as they are reassigned to
other projects or their grants run out?
The wording for the Yahoo! "slot" sounded to me like there has been a
decision at management level that CMU, Intel and Yahoo! want to do some
work on that subject and they like to have the soft, warm glow of
Apacheness on their effort for a (PR?) reason. So there is an engineer
from each group assigned to "work on this" until further notice. From
thirteen names on the proposal, only two will be committers? I know
about Doug, who are the other ten?
That is not exactly the kind of project that we want. The whole Tashi
proposal sounds to me like an abstract to a scientific paper, which has
the tendency that as soon as the paper is done, the interest in the
subject goes down.
- The sentence "A number of events at Yahoo, Carnegie Mellon, and Intel
Research Pittsburgh motivated the development of Tashi and convinced us
to work together in the context of an open-source community" makes me
wonder, what these events were and why specifically the Apache Incubator
was chosen.
- And finally: from your proposal and your concept, it is very clear to
me that you *will* be cutting very very close to proprietary open source
(i.e. GPL licensed) code and you will need to interface with such code.
Are you aware of our strict rules about non-Apache licensed code and how
will you amend this? Has your current code (which is not visible
anywhere) hard dependencies on Apache-incompatible software that you
will need to change/rewrite? XEN e.g. is GPLv2 licensed and you can not
host any code at Apache that needs to be linked with XEN.
Ciao
Henning
On Wed, 2008-07-23 at 10:36 -0400, David O'Hallaron wrote:
> No worries. I've removed the entry on the wiki version of the proposal
> at http://wiki.apache.org/incubator/TashiProposal. It now reads
> simply:
>
> Initially, there will be one committer each from Carnegie Mellon and
> Intel Research:
> * Michael Stroucken ([EMAIL PROTECTED])
> * Michael Ryan ([EMAIL PROTECTED])
>
>
>
>
> Dave
>
>
> On Tue, Jul 22, 2008 at 8:36 PM, William A. Rowe, Jr.
> <[EMAIL PROTECTED]> wrote:
> > Doug Cutting wrote:
> >>
> >> Noel J. Bergman wrote:
> >>>
> >>> With respect to "Initially, we plan to start with one committer each from
> >>> Carnegie Mellon and Intel Research, with a Yahoo committer to be
> >>> determined
> >>> later", that's awkwardly phrased. It appears to imply a corporate
> >>> representative doing commits for "hidden" people, something that we
> >>> consider
> >>> to be an anti-pattern.
> >>
> >> That is not the intent. The intent is for Yahoo! to assign someone to
> >> work on this project as a direct contributor. But that person has not yet
> >> been identified.
> >>
> >>> Whomever is to be actively involved in development
> >>> should be on the committer list. If it is just a community of just The
> >>> Two
> >>> Michaels, fine, but the wording should be rephrased.
> >>
> >> +1 If Y! does not name someone soon, then that entry should be removed. A
> >> committer from Y! can always be added later, based on merit.
> >
> > No; the entry should be removed now.
> >
> > Yahoo the Company cannot place a reservation on a place at the table for
> > an unnamed body. This is not how the ASF works. Nor are committers
> > expressed as delegates of the institutions the work for/study at.
> > This places a cloud over the acceptance of this particular project, and
> > I would encourage everyone to be sure their mentors/champions review the
> > text before posting a proposal for incubation..
> >
> > Bill
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
