www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies" <bimargul...@gmail.com>
Subject Re: How do things get resolved
Date Tue, 25 Nov 2008 21:33:29 GMT
I'm sorry to be a bit dense. Should I go ahead and open a JIRA to get
an up-or-down resolution on just checking it where I can check it in,
or does your proposal for a Coventry in svn take precedence?

On Tue, Nov 25, 2008 at 3:47 PM, Henri Yandell <bayard@apache.org> wrote:
> How do things get resolved?  -   Opening a JIRA issue is a good way to
> force the resolution step, questions on the list tend to be more
> consultation than permission by the nature of the forum.
>
> I've replied on the other thread. For this thread, using JIRA was our
> mechanism for driving resolution and it might be that we need to start
> moving to a "Post that in JIRA" response to non-easy questions.
>
> Hen
>
> On Sun, Nov 23, 2008 at 12:48 PM, Benson Margulies
> <bimargulies@apache.org> wrote:
>> Please forgive a committer on his first visit to legal-discuss.
>>
>> A few days ago I posted a question about the svn-ability of test cases
>> from the W3C with a messy license. That attracted two responses.
>>
>> Were I to be an optimist, I could construct an interpretation of those
>> answers as follows:
>>
>> So long as (a) they are just test cases that we don't ever need or
>> want to modify, and (b) we check them in to their very own directory,
>> and (c) don't incorporate them in any sort of build results, they can
>> be checked in.
>>
>> However, I'm not an optimist, and more to the point I don't know the
>> rules. Is there some legal-discuss analog to a vote? Or does this list
>> just exist to give advice to committers and in the event that push
>> comes to shove there's some other process for getting a formal answer
>> to a question.
>>
>> ---------------------------------------------------------------------
>> DISCLAIMER: Discussions on this list are informational and educational
>> only.  Statements made on this list are not privileged, do not
>> constitute legal advice, and do not necessarily reflect the opinions
>> and policies of the ASF.  See <http://www.apache.org/licenses/> for
>> official ASF policies and documents.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail: legal-discuss-help@apache.org
>>
>>
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only.  Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF.  See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>

---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message