Re: [council] #1: Periodic user/contributor survey
by fedora-badges
#1: Periodic user/contributor survey
---------------------+-----------------------
Reporter: mattdm | Owner: decause
Status: closed | Priority: major
Component: General | Resolution: deferred
Keywords: |
---------------------+-----------------------
Changes (by mattdm):
* status: accepted => closed
* resolution: => deferred
Comment:
Closing this due to lack of movement. I still think it's a good idea, but
this is incarnation isn't going anywhere. We can start again if there's
interest at a later time.
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:23>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
6 years, 10 months
[council] #65: Create standard operating procedure for how
treasurers interact with budget
by fedora-badges
#65: Create standard operating procedure for how treasurers interact with budget
---------------------+-------------------
Reporter: jflory7 | Owner:
Status: new | Priority: major
Component: General | Keywords: budget
---------------------+-------------------
'''Prenote''': Another form of this ticket is also filed in the
[https://pagure.io/fedora-budget fedora-budget] repository as
[https://pagure.io/fedora-budget/issue/18 fedora-budget#18].
= Problem =
It is unclear how Ambassador regional treasurers are expected to interact
and participate in reporting expenses with regards to the Fedora Budget.
= Analysis =
A lot of work was done in setting up this repository as a method for
publicly tracking expenses. I think using Pagure is an effective solution
and if properly taken care of, it will be an effective tool for us. But
right now, there is no clear information for how a treasurer is expected
to contribute to this repository or what the expectations even are.
A high priority item for this should be to create a standard operating
procedure (SOP) either as a separate DOC or in the README about '''what'''
treasurers will do with this repository, '''how''' they are expected to
contribute information, and maybe any details / information about
'''when''' this information is expected each fiscal year.
I think it's important that the Council helps take charge and action on
this to help maintain a healthy, active, and maintained version of the
Fedora budget. I see a lot of work that was put into this and I'm fearful
that it will be forgotten / left behind until it reaches a point where it
might be easier to start all over again with a different solution.
= Implementation =
1. Understand how treasurers reported this information in the past for
background context
2. Discuss with treasurers / regional representatives about how to help
make it easier to contribute this information and what their needs are
3. Begin drafting a first set of guidelines for how to contribute to the
fedora-budget repository
4. Share and put to vote with the Fedora Council
5. Begin following this SOP for all future engagements in this repository
--
Ticket URL: <https://fedorahosted.org/council/ticket/65>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
6 years, 10 months
Fedora Council IRC meeting today (Nov 7, 2016) in #fedora-meeting
(18:00 UTC)
by Matthew Miller
Note that despite the switch from Daylight Saving Time in the US, we
are keeping the meeting time the same in UTC. This means that the
meeting is now an hour earlier in wall-clock time in the US (so, for
example, 1PM EST).
This is a "tickets and ongoing" meeting. The full list of open
tickets is at <https://fedorahosted.org/council/report/1>. There are 17
of them -- I suggest we take this time to go through the list spending
no more than three (3) minutes on each, not necessarily resolving each
issue but deciding what action needs to be taken next (which in some
cases may be "close with no action"). That way we aren't building up
another backlog of unhandled tickets.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
6 years, 10 months
[council] #62: Fedora Security: possible trademark violation
by fedora-badges
#62: Fedora Security: possible trademark violation
-------------------+-----------------------------
Reporter: potty | Owner: potty
Status: new | Priority: normal
Component: Legal | Keywords: legal, trademark
-------------------+-----------------------------
Hello Council!
Abdel, from Panama is writing.
There is a website called Fedora Security [1] which is not related to the
Fedora Security Lab [2]. As I understand from the Trademark Guidelines
[3], it is a violation. Quote: "Fedora®, the Fedora word design, the
Infinity design logo, Fedora Remix, and the Fedora Remix word design,
'''either separately or in combination''', are hereinafter referred to as
"Fedora Trademarks" and are trademarks of Red Hat, Inc."
Correct me if I am wrong.
Thanks in advance.
Regards!
Reference:
[1] http://fedorasecurity.com
[2] https://labs.fedoraproject.org/en/security/
[3]
https://fedoraproject.org/wiki/Legal:Trademark_guidelines?rd=Legal/Tradem...
--
Ticket URL: <https://fedorahosted.org/council/ticket/62>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets
6 years, 10 months
Meeting today
by Robert Mayr
I'm still in Phnom Penh and cannot make it today.
Will look at the minutes tomorrow and if needed vote on tickets.
Robert
6 years, 10 months
