council November 2016

council-discuss@lists.fedoraproject.org

8 participants
25 discussions

Election: Better explain roles of Council
by Dhanesh B. Sabane 08 Dec '16

08 Dec '16

Greetings everyone! CommOps recently took up the task of improving the election process[1]. With respect to that and based on the conversations which took place in FLOCK 2016, we believe that bringing more exposure to the Council's roles and responsibilities will hopefully encourage more nominations and candidates in elections[2]. One way we can accomplish this is by updating the wiki[3] to provide more comprehensive information about the *roles*, *responsibilities*, *benefits* and *skills needed* to be a Council member. A request to all the members to provide feedback on how this can be better handled to benefit the upcoming elections. [1] https://pagure.io/fedora-commops/issue/90 [2] https://pagure.io/fedora-commops/issue/93 [3] https://fedoraproject.org/wiki/Council#Responsibilities Regards, Dhanesh B. Sabane [dhanesh95]

3 4

Open Floor Fedora Council IRC meeting today in #fedora-meeting (18:00 UTC)
by Matthew Miller 28 Nov '16

28 Nov '16

... but I have a conflicting meeting today and won't be there. One suggested topic: coordinating post-F25 elections. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

2 2

meeting today 18:00 UTC -- can someone else set up the hangouts-on-air?
by Matthew Miller 21 Nov '16

21 Nov '16

Adam Miller is going to talk to us about the Layered Image Build Service. ICan someone else set up the hangouts-on-air? I have two hours of meetings directly before. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 3

open floor meeting today in #fedora-meeting (18:00 UTC)
by Matthew Miller 14 Nov '16

14 Nov '16

Today is our open-floor meeting. I'm working on migrating the tickets to pagure, and hopefully it'll be done by then. Not helped by a pre-coffee typo with rm -rf this morning. (Yay, backups!) -- Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/> Fedora Project Leader mattdm(a)fedoraproject.org <http://fedoraproject.org/>

1 0

action items from last meeting
by Matthew Miller 12 Nov '16

12 Nov '16

I excitingly forgot that #action doesn't give any context, so I've added it: Action items, by person: bexelbie bexelbie: help deterimine if the Storyteller role concept is still useful/functional, and further develop it if so jwb take ownership of code of conduct discussion, make proposal with teeth langdon poke at advancing firefox privacy issue ask ambassadors to write up a proposal for IRC SIG mattdm trac migration send these action items finish and send msg on why PRDs are important to Cloud and Workstation schedule PRD review meeting for Dec or so -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

2 1

[council] #40: Enforcing the code of conduct
by fedora-badges 10 Nov '16

10 Nov '16

#40: Enforcing the code of conduct -------------------+--------------------------------- Reporter: duffy | Owner: Status: new | Priority: normal Component: Legal | Keywords: coc, code of conduct -------------------+--------------------------------- See this post from the outreach-list regarding the actual enforcement of the code of conduct as currently written: https://lists.fedoraproject.org/pipermail/outreach/2015-July/000067.html Langdon asked that this be made a ticket for council discussion, with the concern that an unenforceable / consequence without an SOP is a threat and isn't the right way to go: https://lists.fedoraproject.org/pipermail/outreach/2015-August/000073.html For reference, the actual text is: "FUDCon brings together contributors and users from all over the world and this diversity is one of our greatest strengths. This diversity however can also lead to communication issues and unhappiness. Attendees are required to be considerate and respectful of each other. This includes, but is not limited to: - "Refraining from rude behaviour - "Refraining from any sort of harassment or discrimination (based on ethnic background, religion, gender, sexuality, body shape, disability, geographic location, sports team, preferred operating system or anything else) - "Obeying local laws "Attendees who are in violation of this policy may be subject to removal and banning from FUDCon (and future Fedora events). Whether an attendee is in violation is at the sole discretion of the conference organizers. Anyone with a possible concern relating to the code of conduct is encouraged to either email Rupali Talwatkar or talk directly to one of the designated FUDCon volunteers. Designated FUDCon volunteers will have a dark blue coloured VOLUNTEER badge." The line of particular concern here is: "Attendees who are in violation of this policy may be subject to removal and banning from FUDCon (and future Fedora events)." -- Ticket URL: <https://fedorahosted.org/council/ticket/40> council <https://fedorahosted.org/council> Fedora Council Public Tickets

2 15

[council] #73: Diversity Team FAD 2017
by fedora-badges 10 Nov '16

10 Nov '16

#73: Diversity Team FAD 2017 ---------------------+------------------- Reporter: jflory7 | Owner: Status: new | Priority: normal Component: General | Keywords: fad ---------------------+------------------- = Summary = The Fedora [https://fedoraproject.org/wiki/Diversity Diversity team], led by the [https://fedoraproject.org/wiki/Diversity_Adviser Diversity Adviser], would like to hold a FAD in early 2017 to work on key tasks and goals to our mission. = At a glance = * **When**: January 27-29 (proposal 1) or May 13-14 (proposal 2) * **Where**: Brno, Czech Republic (proposal 1) or Tirana, Albania (proposal 2) = Full details = * [https://fedoraproject.org/wiki/FAD_Diversity_2017 Full FAD proposal] * [https://pagure.io/fedora-diversity/issue/8 Pagure ticket] (for discussion/planning) We were hoping to receive further feedback from the Council about whether there would be enough budget to host this event or if one proposal is more feasible than another. Thank you for your consideration! -- Ticket URL: <https://fedorahosted.org/council/ticket/73> council <https://fedorahosted.org/council> Fedora Council Public Tickets

2 7

Re: [council] #1: Periodic user/contributor survey
by fedora-badges 09 Nov '16

09 Nov '16

#1: Periodic user/contributor survey ---------------------+----------------------- Reporter: mattdm | Owner: decause Status: closed | Priority: major Component: General | Resolution: deferred Keywords: | ---------------------+----------------------- Comment (by jflory7): Replying to [comment:23 mattdm]: > 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. For what it's worth, I think the idea behind this survey is a current objective identified by the [https://fedoraproject.org/wiki/Diversity Diversity team], and it's also a target item for our FAD to move closer to [https://fedoraproject.org/wiki/FAD_Diversity_2017#Diversity_survey deploying a survey] targeted to better understanding how our contributor community is composed. Even if this ticket is closed, I think this idea is still being worked on in other places too. -- Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:24> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 0

[council] #74: Moving off of Trac to someting
by fedora-badges 09 Nov '16

09 Nov '16

#74: Moving off of Trac to someting ------------------------+------------------- Reporter: bex | Owner: Status: new | Priority: normal Component: Board Meta | Keywords: ------------------------+------------------- It looks like most people are trying to make pagure.io work. My initial impression is it is going to be a rough around the edges. We need to decide what we want to do and whether we want to talk to infra about possibly standing up an issue tracker more like trac. I will ask @jflory7 to post in this ticket about his experiences using pagure.io with commops. -- Ticket URL: <https://fedorahosted.org/council/ticket/74> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 13

[council] #53: privacy policy should be updated to describe the privacy of Fedora installations, not participation in Fedora events
by fedora-badges 08 Nov '16

08 Nov '16

#53: privacy policy should be updated to describe the privacy of Fedora installations, not participation in Fedora events ---------------------+------------------- Reporter: zbyszek | Owner: Status: new | Priority: normal Component: General | Keywords: ---------------------+------------------- == How the privacy policy is specified == /usr/lib/os-release contains PRIVACY_POLICY_URL=https://fedoraproject.org/wiki/Legal:PrivacyPolicy. PRIVACY_POLICY_URL is documented to "refer to the main privacy policy page for the operati[ng] system" [1]. This line was added to allow Gnome to display a link to the privacy policy without hardcoding the text or URL. It is currently shown by gnome-initial-setup [2]. [1] https://www.freedesktop.org/software/systemd/man/os- release.html#HOME_URL= [2] https://in.waw.pl/~zbyszek/fedora/gnome-i-s-privacy-policy- screenshot.png == Recent attempts at updating == There have been two drafts that I'm aware of: - https://fedoraproject.org/wiki/User:Pfrields/PrivacyPolicyRedux discussed at [3] - https://fedoraproject.org/wiki/User:Spot/PrivacyPolicyProposal discussed at [4] [3] https://lists.fedoraproject.org/pipermail/desktop/2015-March/011700.html [4] https://lists.fedoraproject.org/pipermail/council- discuss/2015-September/013633.html Neither of those significantly address issues that have been raised in response to both proposals. == What is wrong with current policy == [This part is subjective of course, please read it as prefixed with "IMO" everywhere] As stated in $subject, it's a policy for a different purpose. The privacy policy used as "the privacy policy for the OS" should primarily and prominently describe what information is collected (or otherwise made public) when Fedora is installed, when a user account on the Fedora machine is created, and in normal use of Fedora. Crafting a clear and simple policy will make a good impression that Fedora Project cares about it's users privacy, and is safe to use in situations where preserving personal information is important. A general problem is that existing policy and proposed draft do not make a clear distinction between a) installing Fedora and downloading updates, b) creating accounts for Fedora development and using the bug tracker, c) participating in Fedora conferences and such. Those three broad categories have completely different privacy implications. Without being clear to which of those the policy pertains means that the policy greatly overstates the types of information being collected. In effect the policy is much more relaxed (i.e. bad for the users) than it could be. Specific issues raised: Should there be mention of NetworkManager-config-connectivity-fedora? (ie, checking http://fedoraproject.org/static/hotspot.txt for captive portal) [5] In the section about 'Cookies and other Browser information', it might be useful to mention that the 'User Agent ID' of Browsers that are packaged in Fedora is configured to identify the system as running Fedora. [6] For example, the list in "Publicly Available Personal Information" really isn't palatable. A better way of showing this might be to say: "the information you give when creating your account will be public by default. You can see what data is publicly visible <here> (link to the public page for the user), modify your privacy settings <here>, and request deletion of the account <here>" [7] I also don't like the "Personal Information" vs. "Non-Personal Information". It might be how a lawyer works, but just because it pertains to a computer and not to a person doesn't make it less identifying. [7] the privacy policy needs to refer to "user account" in such way that it'll be clear that it's talking about accounts for contributors (FAS) and not a user account on your system or an online account you add via GOA, to make it clear Fedora doesn't scrape your name (or other identifying details) from Google / Facebook accounts added via GOA, nor the "Full Name" field of user accounts on your computer. [8] > we may disclose personally identifiable information about you to third parties > in limited circumstances, including: > ... > - for research activities, including the production of statistical reports (such > aggregated information is used to describe our services and is not used to > contact the subjects of the report). > "" AFAIK, in Germany, it's the laws that any such "passing on personal information" needs to be opt-in - "Opt-out" and "always-on" would be unlawful. [10] What procedures are being put in place so that EU residents (and hopefully everyone) can contact Fedora or Red Hat to obtain/understand/verify/delete their machine data, beyond obviously personal data? [5] https://lists.fedoraproject.org/pipermail/council- discuss/2015-September/013643.html [6] https://lists.fedoraproject.org/pipermail/desktop/2015-March/011703.html [7] https://lists.fedoraproject.org/pipermail/desktop/2015-March/011727.html [8] https://lists.fedoraproject.org/pipermail/desktop/2015-March/011729.html [9] https://lists.fedoraproject.org/pipermail/council- discuss/2015-September/013637.html [10] https://lists.fedoraproject.org/pipermail/council- discuss/2015-September/013637.html [11] https://lists.fedoraproject.org/pipermail/council- discuss/2015-September/013649.html == tl; dr == The policy is too complicated, yet lacks detail and does not provide strong guarantees. Statements like "The Information We Collect ... your Fedora Account password .. your SSH public key ... your affiliation" are not appropriate for a page linked to from the "Privacy Policy" link displayed during installation. I hope the Council can help to push towards a better policy document. Currently things seem to be stuck in minimal edits over the last year and half. Maybe the document should be opened for public editing on a wiki somewhere so that people can rearrange the text and take it further from current form. If the Council accepted the general idea of providing strong privacy guarantees things could move forward. -- Ticket URL: <https://fedorahosted.org/council/ticket/53> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 9

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

MOVED to https://discussion.fedoraproject.org/tag/council November 2016