council April 2016

council-discuss@lists.fedoraproject.org

21 participants
23 discussions

[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] #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

[council] #43: Create the Fedora Public Budget Page
by fedora-badges 07 Nov '16

07 Nov '16

#43: Create the Fedora Public Budget Page -------------------------+------------------------------------------------- Reporter: decause | Owner: decause Status: new | Priority: normal Component: General | Keywords: budget, websites, FCL, transparency, | community -------------------------+------------------------------------------------- As per the results of our council discussion here (https://lists.fedoraproject.org/pipermail/council- discuss/2015-October/013742.html) we are heretofore establishing a new page (wiki or otherwise) that will track the timeline and particulars of the Fedora Public Budget. It shall include: Budgetary Components, Projected and Adjusted for each fiscal year: - Regional Budget Allocations (APAC/EMEA/LATAM/NA) - Fedora Premier Event Budgets (FLOCK, FUDCon) - Central Discretionary Fund (approved by Council) - FAD specific Budgets Budgetary Milestones and Timelines: - August: In person meeting at FLOCK - September: Proposed budget components and metrics from each region - October: Ratification of Proposed Budget by Council - March: Confirmation of Received budget w/ Adjustment Meeting - Quarterly Check-ins with Regional Treasurers - Halfly approvals of Regional Funds, pending metrics and outcomes reporting If there are other details or resources that should be included on this page, feel free to leave them in the comments below. I would propose that this page eventually be made available at http://budget.fedoraproject.org -- Ticket URL: <https://fedorahosted.org/council/ticket/43> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 14

[council] #16: Periodic contributor survey
by fedora-badges 07 Nov '16

07 Nov '16

#16: Periodic contributor survey ---------------------+------------------- Reporter: mattdm | Owner: Status: new | Priority: normal Component: General | Keywords: ---------------------+------------------- This is a tracking ticket for establishing a process by which we get regular feedback from the Fedora contributor base. This is a companion to https://fedorahosted.org/council/ticket/1. The desired goals, methodology, and basically everything else are really different between users and contributors it will be better to track them separately. -- Ticket URL: <https://fedorahosted.org/council/ticket/16> council <https://fedorahosted.org/council> Fedora Project Board Public Tickets

1 3

[council] #42: Schedule a FLOCK Budget Planning Session w/Council
by fedora-badges 24 Aug '16

24 Aug '16

#42: Schedule a FLOCK Budget Planning Session w/Council -------------------------+------------------------------------------------- Reporter: decause | Owner: decause Status: new | Priority: minor Component: Board Meta | Keywords: FLOCK, session, budget, council, | fiscal, -------------------------+------------------------------------------------- As per our discussion about Budget Planning here, (https://lists.fedoraproject.org/pipermail/council- discuss/2015-October/013742.html) one conclusion we came to was that Budget Planning for the next fiscal year would begin during August at FLOCK with a high-bandwidth in person meeting, that continued on maillists and IRC through September, and was delivered to the FCL in October, to be presented to Red Hat via OSAS. This ticket is a reminder that we need to schedule a session at FLOCK for the high-bandwidth in person session. -- Ticket URL: <https://fedorahosted.org/council/ticket/42> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 2

[council] #50: Schedule a Flock Council Update & Town Hall for Krakow 2016
by fedora-badges 24 Aug '16

24 Aug '16

#50: Schedule a Flock Council Update & Town Hall for Krakow 2016 -------------------------+------------------------------------------------- Reporter: decause | Owner: decause Status: new | Priority: normal Component: Board Meta | Keywords: Flock, Flock 2016, Council Update, | council -------------------------+------------------------------------------------- This the is the traditional Flock session where members of the council meet with community members and update folks on the status of Objectives, as well as discuss issues and ideas for the future. -- Ticket URL: <https://fedorahosted.org/council/ticket/50> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 2

[council] #54: Design FAD 2016
by fedora-badges 17 Aug '16

17 Aug '16

#54: Design FAD 2016 ---------------------+------------------- Reporter: duffy | Owner: Status: new | Priority: normal Component: General | Keywords: fad ---------------------+------------------- Hi, the design team would like to hold a FAD in Boston at the end of July, a weekend before Flock. We have written up a proposal here: http://fedoraproject.org/wiki/FAD_DesignTeam_2016 We also had some discussion on the council list here: https://lists.fedoraproject.org/archives/list/council- discuss(a)lists.fedoraproject.org/thread/AV7WOBORDQBAQLES3CCBEZAULT2CYEF7/ Is this something the Council would be willing to fund? Thanks for your consideration1 -- Ticket URL: <https://fedorahosted.org/council/ticket/54> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 10

[council] #49: Decision FUDCon APAC 2016
by fedora-badges 20 Jun '16

20 Jun '16

#49: Decision FUDCon APAC 2016 ---------------------+------------------- Reporter: gnokii | Owner: Status: new | Priority: normal Component: General | Keywords: ---------------------+------------------- following a conversation with Matthew I write this ticket: The rules for choose a place to holding FUDCons says, that FAmSCo and Board or now Council have to agree to the recommendation the local Ambassadors do. Until yet I only saw more questions which are answered and following that a discussion, if we should keep FUDCon. Please, keep in mind how that might look to the bidders, its already the second time the cambodian community did a bid, when instead of a decision a discussion comes up to wipe it out. It might look to this community that we not want it there and we dont want cambodians in our community. We already lost 2 months where a clear statement would have the local community enabled to work on making a successful FUDCon 2016. It is legitimate to discuss if FUDCon is still needed in the regions but have an eye that the bid means there putting people work and effort into it, especially in this case as there was a lot of requirements the indian community wanted to see before agree to the bid. So please go on and make a decision, to give the local community a chance to work on it. https://fedoraproject.org/wiki/FUDCon:Bid_for_PhnomPenh_2016 -- Ticket URL: <https://fedorahosted.org/council/ticket/49> council <https://fedorahosted.org/council> Fedora Council Public Tickets

1 6

Monday meeting: Continuing with budget, FOSCo delayed
by Christoph Wickert 30 Apr '16

30 Apr '16

Hi, I was supposed to give a presentation about FAmSCo's current plans for FOSCo on Monday, but as there is not much to report yet, Matthew and I agreed to continue with the budget. FAMSCo is operational again, we have a new chair, switched to lazy consensus, so we should no longer be deadlocked by unresponsive members. Most are responsive again and Giannis just put FOSCo back on the aganda last week, so I should be able to push the topic and tell you more about it in 3 weeks. Best regards, Christoph

2 1

Re: Creating a "Fedora Incubator" brand
by Josh Berkus 29 Apr '16

29 Apr '16

On 04/28/2016 12:45 PM, Josh Boyer wrote: >> 2) I like the idea, but an example project might help illustrate here. > > Agreed, though I have some of my own ideas. > >> 3) What are the criteria for "graduating"? Who are the mentors in this >> example? (Mentors are a key part of the incubator for Apache.) > > Do projects have to graduate? I don't want this to be viewed as a > competition between initiatives, and promotion/relegaion/graduation > seem to set a competitive tone. As soon as you start talking about > graduation or promotion, you start getting into resource allocation > issues, etc. > > I'd personally be fine if a project joined the incubator and stayed > there. If they wanted to somehow because an Objective, we already > have paths for that. I can think of at least one Atomic effort (the OSTree continuous integration) which might stay in Incubator permanently. Given that, are you sure you want to call it "Incubator"? That name does imply maturation at some point, even without the Apache precendent. What about "Fedora Innovator" or "Fedora Labs"? -- Josh Berkus Project Atomic

9 10

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

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