Heh, sorry, while Patricia was sending that, I was drafting a
resolution for the agenda so that you wouldn't need to later.
It is on the agenda now, but we can postpone action if there
is any doubts by next week.

....Roy

> On Jul 8, 2020, at 1:47 PM, Patricia Shanahan <[email protected]> wrote:
> 
> There seems to be a developing consensus. Ultimately, we will need a 
> resolution which would be better coming from the PMC rather than being 
> imposed by the board. You may need more time to prepare it and confirm the 
> consensus. If so, perhaps a very simple report saying something like Apache 
> DRAT is not active and the PMC plans to offer a resolution next month?
> 
> 
> On 7/8/2020 10:15 AM, Chris Mattmann wrote:
>> Thank you  Roy.
>>  Yeah just DRAT would be fine.
>> Appreciated and will  await the  outcome.
>>  Thanks,
>> Chris
>>      From: "Roy T. Fielding" <[email protected]>
>> Date: Wednesday, July 8, 2020 at 10:13 AM
>> To: Chris Mattmann <[email protected]>
>> Cc: "[email protected]" <[email protected]>
>> Subject: Re: [EXTERNAL] Missing DRAT Board Report
>>  On Jul 8, 2020, at 8:45 AM, Chris Mattmann <[email protected]> wrote:
>>  Hi,
>>  It’s possible  that we may  not in  fact have enough interest to
>> continue ASF development  on DRAT.
>>  If that is the case I would request that should the project be spun
>> down and  committee terminated that the ASF would consider simply
>> transferring the repo back  to me under my GitHub where it originally
>> came  from. To  my knowledge we never requested  trademark or
>> anything like that on it, so hopefully it’s not entangled  in anything
>> more than simple consideration there.
>>  Thank you for  your  consideration.
>>  Chris
>>  Hi Chris,
>>  Generally speaking, that's the default, since stopping further work
>> on a project is equivalent to abandoning the mark, and we always
>> allow people to fork Apache repos. I don't think anyone would mind
>> as long as it isn't packaged as "Apache DRAT". DRAT is fine.
>>  Cheers,
>>  ....Roy
>>  
> 
> -- 
> This email has been checked for viruses by AVG.
> https://www.avg.com
> 

Reply via email to