From Fedora Project Wiki

No edit summary
Line 27: Line 27:


* We will start with a basic introduction to [https://fedoraproject.org/wiki/Security_Team#Get_involved Fedora Security] by [[User:Pjp | P J P]] and then go on to the process we follow etc [Approx 30-40 mins]
* We will start with a basic introduction to [https://fedoraproject.org/wiki/Security_Team#Get_involved Fedora Security] by [[User:Pjp | P J P]] and then go on to the process we follow etc [Approx 30-40 mins]
* We will then look at the list of flaws which are open and then pick ones we want to pursue. -> [https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&keywords=SecurityTracking%2C%20&keywords_type=allwords open issues]
* We will then look at the list of flaws which are open and then pick ones we want to pursue. -> [https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&keywords=Security&keywords_type=allwords open issues]
* Rest of the day goes into actually working on them and figuring out if they can be fixed.
* Rest of the day goes into actually working on them and figuring out if they can be fixed.
* The owner of those flaws will continue pursing those flaws after the FAD and ensure they get a proper resolution.
* The owner of those flaws will continue pursing those flaws after the FAD and ensure they get a proper resolution.

Revision as of 19:18, 31 October 2014


When and Where

On Sat, 1st Nov 2014, 09:30 - 17:00 hrs in room "Sinhagad" on Level 1 at the Red Hat Pune office.

This Fedora Activity Day is aimed at collaborative triage and fixing of Fedora Security tracking bugs. It is meant for Existing Fedora contributors or folks who want to start contributing in a useful way (not just attend a FAD and then disappear). More details below.

Note:- maximum capacity for the day is about 25 participants.

Attendees

Note.png
Note
Feel free to add your name here

Activities

  • We will start with a basic introduction to Fedora Security by P J P and then go on to the process we follow etc [Approx 30-40 mins]
  • We will then look at the list of flaws which are open and then pick ones we want to pursue. -> open issues
  • Rest of the day goes into actually working on them and figuring out if they can be fixed.
  • The owner of those flaws will continue pursing those flaws after the FAD and ensure they get a proper resolution.

Useful links

Status

Blogs and Reports

Photos