On Thu, May 07, 2015 at 09:25:19AM -0400, Matthew Miller wrote:
Actually, on review, there is an existing policy
<
https://fedoraproject.org/wiki/Trademark_approval_policy>, which
states that specific trademark approvals can be delegated to various
SIGs. In this case, that "SIG" would be FESCo; I'll look at updating
Oh, no, wait, that policy also includes a "submit to Council" step. I
guess the idea is to reduce Council (formerly Board) involvement to
oversight and approval of something already vetted?
*digs into thread linked at the bottom of that message*
Yeah, okay, to quote David Nalley, the intent is "it gets the board
out of the 'QA/Design/Rel-eng/Spins' business", and that seems relevant
reasonable today is well. And I guess I don't see a huge reason to not
just keep the stamp-of-approval-from-the-council step. I don't think
there will be a big increased workload from thousands of new spins
appearing.
A lot of the previous concern was over the private Board ticket system,
and since we now have a _public_ ticket system, that shouldn't be a
worry. The one thing I might suggest is that the Council (possibly
through the Engineering Representative) probably should be notified
when the FESCo process _begins_, so that if there are any concerns,
they can be relayed back _before_ all of the rest of the work. (For
example, if someone proposes a Fedora Kitten Murder Spin, the Council
could indicate skepticism _before_ a lot of work is put into it, even
if FESCo thinks the _technical_ details are perfectly fine.)
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader