Dear Pawel,

We have voted at the today's governance meeting, and there was no majority 
to support the "VirtusLab Jenkins Operator Service" request (one +1 vote, 
two 0, and three -1s). The main reasoning behind the voting results is the 
trademark usage policy we adopted. We suggest to proceed with *"VirtusLab 
Operator Service for Jenkins"* name or a similar one.

P.S: Taking the voting results, I think it would be fair to strictly follow 
the Linux Foundation guidelines going forward. As Daniel pointed out, 
"exceptional cases" create venue for interpretation and confusion when not 
strictly documented. It is not good for any side.

Best regards,
Oleg Nenashev

On Wednesday, December 16, 2020 at 7:01:40 PM UTC+1 Daniel Beck wrote:

>
>
> > On 16. Dec 2020, at 00:06, Oleg Nenashev <[email protected]> wrote:
> > 
> > Our public doc is still behind the actual state, my bad. Will make sure 
> to file a PR tomorrow on the morning. At the Oct 14 governance meeting we 
> agreed that:
> > 
> > * We adopt Linux Foundation pre-approved trademark patterns and usage 
> guidelines
> > * We are not applying requirements retrospectively, everything remains 
> approved
> > * Until the transition to CDF is over, we may make exceptions in the 
> naming policy. Example: precedent in already approved trademarks
> > 
> > The third bullet is where we reserve some freedom at the cost of 
> ambiguity. Maybe we need stricter examples. Just forcing the LF guidelines 
> is also the option
> > 
>
> Thanks Oleg!
>
> I read the meeting notes and saw your PR, thanks for that as well.
>
> As far as I can tell, the last time we approved a name following the old 
> pattern was several years ago, before we started moving to CDF. I think 
> it's best to start with a clean slate, so I'm -1 on the trademark usage 
> request with exceptional pattern for now. The name should instead follow 
> the LF guidelines we decided to use.
>
> (And FWIW I do not consider us continuing to allow previously approved 
> trademark usages under a different ruleset to be precedent for allowing new 
> ones; if it was, why even bother adopting the new guidelines?)
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3803d311-383d-491d-9073-4fd7fc96dd96n%40googlegroups.com.

Reply via email to