======================================
#fedora-blocker-review: fedoraqa-devel
======================================
After much fun with finding an open channel for the meeting, we did get
through a bunch of stuff. At the moment, no more meetings are planned
and we will schedule more as needed/appropriate.
Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-01-13/fedoraqa-…
Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2014-01-13/fedoraqa-…
Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-01-13/fedoraqa-…
Meeting summary
---------------
* Roll Call (tflink, 17:12:50)
* Taskotron Status (tflink, 17:19:29)
* Taskotron Phase 1 is due to be delivered 2014-03-01 (tflink,
17:20:07)
* LINK:
https://fedoraproject.org/wiki/User:Tflink/taskotron_development_plan#Phase…
(tflink, 17:20:35)
* phase 0 is mostly complete, tickets need a bit of updating, still
(tflink, 17:21:46)
* LINK: https://phab.qadevel.cloud.fedoraproject.org/T7 (tflink,
17:21:54)
* Depcheck rewrite status (tflink, 17:24:47)
* LINK: https://bitbucket.org/fedoraqa/depcheck-mk-2
(handsome_pirate, 17:25:30)
* initial depcheck scenarios have been coded up (tflink, 17:27:38)
* LINK: https://bitbucket.org/fedoraqa/depcheck_scenarios (tflink,
17:27:44)
* current depcheck-mk-2 code is passing some of the depcheck
scenarios, rest are being worked on (tflink, 17:29:58)
* Documentation (tflink, 17:35:32)
* LINK: https://phab.qadevel.cloud.fedoraproject.org/T39 (tflink,
17:37:11)
* roshi is looking into using dexy (tflink, 17:40:01)
* LINK: http://dexy.it (tflink, 17:40:09)
* ACTION: roshi to write up comparison between dexy and sphinx, send
out to list when complete (tflink, 17:55:38)
* Taskotron Tasks/Checks (tflink, 17:56:32)
* initial tasks will be the checks from AutoQA PUATP (minus depcheck,
which is being rewritten) (tflink, 17:57:18)
* the target checks for phase 1 are: rpmlint, upgradepath, depcheck
(mk 2) (tflink, 18:01:30)
* ACTION: tflink to move repoclosure to later phase in wiki docs
(tflink, 18:02:27)
* LINK: https://phab.qadevel.cloud.fedoraproject.org/T15 (tflink,
18:05:14)
* LINK: https://phab.qadevel.cloud.fedoraproject.org/T14 (tflink,
18:05:26)
* possible checks for a future phase: repoclosure, rpmguard, abicheck
(tflink, 18:10:25)
* Taskotron Runner (tflink, 18:11:11)
* demo code is public, but incomplete (tflink, 18:12:59)
* LINK: https://bitbucket.org/fedoraqa/libtaskotron-demo (tflink,
18:13:15)
* ACTION: tflink to move repo from libtaskotron-demo to libtaskotron
(tflink, 18:17:05)
* Fedora Beaker Installation (tflink, 18:20:56)
* LINK:
https://lists.fedoraproject.org/pipermail/infrastructure/2014-January/01388…
(tflink, 18:24:42)
* Devops and Infrastructure (tflink, 18:32:08)
* LINK: http://phabricator.org/ (tflink, 18:35:31)
* LINK: https://phab.qadevel.cloud.fedoraproject.org/ (tflink,
18:35:46)
* LINK: https://qadevel-stg.cloud.fedoraproject.org/builds/ (tflink,
18:37:16)
* LINK: https://bitbucket.org/tflink/fedoraqa-ansible (tflink,
18:41:22)
* ACTION: tflink to update playbooks and docs so that folks can setup
dev systems (tflink, 18:44:22)
* Coding Policy/Strategy Going Forward (tflink, 18:47:59)
* LINK: http://nvie.com/posts/a-successful-git-branching-model/
(tflink, 18:50:25)
* LINK: https://github.com/nvie/gitflow (tflink, 18:50:35)
* LINK: http://python-future.org/index.html (tflink, 18:54:07)
* Short Term Plans (tflink, 18:56:12)
* get a new demo system up and running to start testing taskotron as a
whole (tflink, 18:56:39)
* get docs and planning done (tflink, 18:56:48)
* continue with the work described earlier (checks, runner etc.)
(tflink, 18:57:07)
* Open Floor (tflink, 18:59:22)
Meeting ended at 19:04:11 UTC.
Action Items
------------
* roshi to write up comparison between dexy and sphinx, send out to list
when complete
* tflink to move repoclosure to later phase in wiki docs
* tflink to move repo from libtaskotron-demo to libtaskotron
* tflink to update playbooks and docs so that folks can setup dev
systems
Action Items, by person
-----------------------
* roshi
* roshi to write up comparison between dexy and sphinx, send out to
list when complete
* tflink
* tflink to move repoclosure to later phase in wiki docs
* tflink to move repo from libtaskotron-demo to libtaskotron
* tflink to update playbooks and docs so that folks can setup dev
systems
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* tflink (225)
* handsome_pirate (53)
* kparal (36)
* roshi (30)
* Viking-Ice (15)
* mkrizek (10)
* shisatum (5)
* zodbot (5)
* danofsatx (4)
* adamw (1)
* pschindl (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
==================================
#fedora-meeting: Fedora QA meeting
==================================
Meeting started by adamw at 16:00:59 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-01-13/fedora-qa.2014-0…
.
Meeting summary
---------------
* Roll call (adamw, 16:01:09)
* Previous meeting follow-up (adamw, 16:09:13)
* "adamw to send a mail to test@ about the ten year t-shirt thing" -
clearly, that happened:
https://lists.fedoraproject.org/pipermail/test/2014-January/120006.html
(adamw, 16:09:36)
* EOL process handling (adamw, 16:12:48)
* there has been a bit of a debate about the EOL (end-of-life)
process, which is documented on the Wiki in a QA-ish space
(Bugzappers), but which in practice has been handled by the program
manager (adamw, 16:13:36)
* thread started at
https://lists.fedoraproject.org/pipermail/devel/2013-December/193094.html
(adamw, 16:15:58)
* LINK: https://fedoraproject.org/wiki/End_of_life_SOP does list it
under Bugzappers, so we need to straighten that out whichever way it
goes. (adamw, 16:25:54)
* LINK: http://johnpoelstra.com/five-months-of-bug-triage/ is
interesting (adamw, 16:33:51)
* https://fedoraproject.org/wiki/End_of_life_SOP still shows the bug
closure to be the responsibility of 'Bugzappers' (adamw, 16:36:55)
* http://johnpoelstra.com/five-months-of-bug-triage/ implies the
history of the EOL process - it was developed as part of the
Bugzappers effort and originally done by poelcat with his Bugzappers
hat on, not his Program Manager hat (adamw, 16:37:34)
* LINK: https://fedorahosted.org/fesco/ticket/1198 (jreznik,
16:39:17)
* EOL scripts are available at
https://git.fedorahosted.org/cgit/fedora-project-schedule.git/tree/scripts/…
(adamw, 16:40:06)
* viking-ice's suggestions that QA should own the process and perhaps
drop the closing of bugs on EOL releases is noted but not supported
by a consensus (adamw, 16:50:38)
* ACTION: adamw to summarize the discussion for a fesco ticket note on
https://fedorahosted.org/fesco/ticket/1198 (adamw, 16:58:41)
* 10 year anniversary t-shirt (adamw, 16:59:09)
* open floor (adamw, 17:04:18)
* it's fine to propose blockers for f21 already (adamw, 17:07:55)
Meeting ended at 17:09:02 UTC.
Action Items
------------
* adamw to summarize the discussion for a fesco ticket note on
https://fedorahosted.org/fesco/ticket/1198
Action Items, by person
-----------------------
* adamw
* adamw to summarize the discussion for a fesco ticket note on
https://fedorahosted.org/fesco/ticket/1198
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* adamw (91)
* cmurf (51)
* jreznik (41)
* Viking-Ice (38)
* roshi (18)
* kparal (14)
* tflink (7)
* danofsatx (6)
* zodbot (4)
* jsmith (4)
* yachironi (2)
* mkrizek (1)
* pwhalen (1)
* pschindl (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
====================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
https://fedoraproject.org/wiki/Docs_Project_meetings
====================================================================================================
Meeting started by randomuser at 14:00:18 UTC. The full logs are
available athttp://meetbot.fedoraproject.org/fedora-meeting/2014-01-13/fedora_docs.20…
.
Meeting summary
---------------
* Roll Call (randomuser, 14:00:18)
* Guide Status (randomuser, 14:07:19)
* pbokoc has updated IG for f20 and is prepping POTs now (randomuser,
14:07:53)
* LINK:
https://fedoraproject.org/wiki/Category:Docs_Project_tasks?rd=Docs_Project_…
(randomuser, 14:14:03)
* If you have or want tasks, use the tasks page (randomuser,
14:14:15)
* Capesteve is creating a Networking Guide, starting with Networking
content from Sysadmin guide (randomuser, 14:26:04)
* LINK:
https://git.fedorahosted.org/cgit/docs/power-management-guide.git/plain/pot…
(pbokoc, 14:26:22)
* Publican4 thing (randomuser, 14:30:43)
* Docs FAD (randomuser, 14:36:40)
* nb nominates randomuser to continue as docs lead (nb, 14:48:09)
* ACTION: randomuser to send mail to list regarding 21MAR-23MAR FAD
scheduling (randomuser, 14:49:51)
* bz tickets (randomuser, 14:51:21)
Meeting ended at 15:00:17 UTC.
Action Items
------------
* randomuser to send mail to list regarding 21MAR-23MAR FAD scheduling
Action Items, by person
-----------------------
* randomuser
* randomuser to send mail to list regarding 21MAR-23MAR FAD scheduling
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* randomuser (86)
* pbokoc (25)
* Sparks (19)
* yruseva (13)
* jjmcd (9)
* misc (7)
* lnovich (6)
* nb (6)
* zodbot (4)
* Capesteve (4)
* pkovar (2)
* gomix (1)
* jhradilek (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
=================================
#fedora-meeting-2: fedoraqa-devel
=================================
We didn't quite get through everything today, so we'll continue after
the QA meeting on Monday.
I'll be sending an announcement for that meeting shortly.
Minutes: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-09/fedoraqa-devel…
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-09/fedoraqa-devel…
Log: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-09/fedoraqa-devel…
Meeting summary
---------------
* Roll Call (tflink, 16:01:31)
* Current Project Status (tflink, 16:06:34)
* Not much is going on with blockerbugs for the short term - we're
waiting to see how f21 and/or fedora.next shape out before working
on any new features beyond the small changes ready for review
(tflink, 16:08:54)
* LINK: https://phab.qadevel.cloud.fedoraproject.org/project/view/1/
(tflink, 16:11:22)
* Current Status and Plans - resultsdb and testdays (tflink, 16:19:33)
* the reduced re-implementation for resultsdb is up and running at
http://resultsdb.qa.fedoraproject.org/resultsdb (tflink, 16:21:57)
* resultsdb browsing is available at:
http://resultsdb.qa.fedoraproject.org/resultsdb_frontend/ (tflink,
16:22:22)
* resultsdb API docs are at: http://docs.resultsdb.apiary.io/
(tflink, 16:22:45)
* the new resultsdb is (comparing to the old concept) quite simplified
on the data level - we stripped all the un-used tables from the old
concept, and adapted the data to what we actually used with the
autoqa reporting (tflink, 16:28:11)
* old and new resultsdb schema displayed at:
https://fedoraproject.org/wiki/AutoQA_resultsdb_schema (tflink,
16:29:18)
* Current Status - Testday App (tflink, 16:38:15)
* the testdays app is IMHO quite self-confined, and I have no
immediate goals for changing what it does (apart of bug-fixes). This
is because it's using the 'old' resultsdb, and uses TurboGears2
(tflink, 16:40:28)
* The plans for the future are to re-write it with Flask & New
Resultsdb but it is (at the moment) quite low-priority (tflink,
16:42:29)
* Current Status - Support Tools (tflink, 16:43:31)
* the main support tools that we have are phabricator (code review,
issue tracking etc.) and buildbot (in progress)/ jenkins (existing,
not quite working) for ci (tflink, 16:47:03)
* phabricator is deployed at
https://phab.qadevel.cloud.fedoraproject.org/ (tflink, 16:47:22)
* LINK: http://phabricator.org/ (Viking-Ice, 16:47:46)
* ACTION: tflink to write up docs on code review with phabricator
(tflink, 16:49:01)
* buildbot for qa project CI is deployed to staging at
https://qadevel-stg.cloud.fedoraproject.org/builds/ (tflink,
16:51:59)
* there is still work to do on buildbot so that we have CI and
hopefully autogenerated and autodeployed docs for qa devel projects
(tflink, 16:56:57)
* Priorities (tflink, 17:00:36)
* AGREED: As we have a longer break between releases for now,
automation is a higher priority because it is more disruptive and
needs to be done soon (tflink, 17:16:42)
* Fedoraproject Beaker Instance Status (tflink, 17:17:26)
* we have a dev instance of beaker deployed at
https://beaker-dev.fedoraproject.org/bkr/ (tflink, 17:18:11)
* due to security concerns, it is currently locked down by IP
(tflink, 17:18:29)
* ACTION: kparal and tflink to sync up on beaker.fp.o status and come
up with some ideas on moving forward (tflink, 17:29:49)
* Taskotron status (tflink, 17:29:52)
* The hope was to have taskotron phase 0
(https://fedoraproject.org/wiki/User:Tflink/taskotron_development_plan#Phase…)
done by now (tflink, 17:30:47)
* task description format was proposed and sent out to qa-devel@.
response has been mostly positive and it is ready to start moving
forward (tflink, 17:31:36)
* initial fedmsg reliability investigation indicates that it will be
reliable enough to use for automation scheduling but we should
continue to keep an eye on it (tflink, 17:32:27)
* LINK: https://phab.qadevel.cloud.fedoraproject.org/T2 (tflink,
17:32:43)
* there was a proof-of-concept system running in the fedora cloud, but
it seems to be having issues ATM (tflink, 17:37:54)
* The big remaining task for phase 0 is discussion/investigation into
notifications (tflink, 17:39:25)
* the proof-of-concept runner does work locally and does produce
output to the console, it can't report to resultsdb (yet) and needs
some refactoring (tflink, 17:40:29)
* ACTION: tflink to finish notificaitons email and send it out to
qa-devel@ (tflink, 17:42:28)
* depcheck scenarios have been drafted up and fake rpms have been
coded up for testing (tflink, 17:45:34)
* LINK: https://bitbucket.org/fedoraqa/depcheck_scenarios (tflink,
17:47:26)
* Deadlines and Milestones (tflink, 17:49:04)
* Current deadline for taskotron phase 1 is 2013-03-01 (tflink,
17:49:25)
* LINK:
https://fedoraproject.org/wiki/User:Tflink/taskotron_development_plan#Phase…
(tflink, 17:49:47)
* Meetings (tflink, 17:55:59)
* ACTION: tflink to schedule followup meeting after monday's qa
meeting (tflink, 17:58:37)
* Open Floor (tflink, 17:58:57)
Meeting ended at 18:06:44 UTC.
Action Items
------------
* tflink to write up docs on code review with phabricator
* kparal and tflink to sync up on beaker.fp.o status and come up with
some ideas on moving forward
* tflink to finish notificaitons email and send it out to qa-devel@
* tflink to schedule followup meeting after monday's qa meeting
Action Items, by person
-----------------------
* kparal
* kparal and tflink to sync up on beaker.fp.o status and come up with
some ideas on moving forward
* tflink
* tflink to write up docs on code review with phabricator
* kparal and tflink to sync up on beaker.fp.o status and come up with
some ideas on moving forward
* tflink to finish notificaitons email and send it out to qa-devel@
* tflink to schedule followup meeting after monday's qa meeting
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* tflink (231)
* Viking-Ice (64)
* handsome_pirate (34)
* kparal (30)
* jskladan (23)
* zodbot (7)
* mkrizek (6)
* croberts (5)
* roshi (2)
* pschindl (2)
* nirik (1)
* satellit (1)
* danofsatx (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
=============================================
#fedora-meeting: IRC Support SIG (2014-01-09)
=============================================
Meeting started by nirik at 18:00:22 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-01-09/irc-support-sig.…
.
Meeting summary
---------------
* init process (nirik, 18:00:22)
* Week(s) in review (nirik, 18:03:52)
* ticket #165: EvilBob excessive complaining about my away nick changer
(nirik, 18:06:30)
* revisit 'excessive' nick change policy (nirik, 18:09:22)
* ACTION: nirik to write up new plan for nick change policy (nirik,
18:17:31)
* Open Floor (nirik, 18:17:36)
Meeting ended at 18:24:26 UTC.
Action Items
------------
* nirik to write up new plan for nick change policy
Action Items, by person
-----------------------
* nirik
* nirik to write up new plan for nick change policy
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (33)
* Khaytsus (10)
* zodbot (3)
* kc8hfi (3)
* triad (1)
--
18:00:22 <nirik> #startmeeting IRC Support SIG (2014-01-09)
18:00:22 <zodbot> Meeting started Thu Jan 9 18:00:22 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:22 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:22 <nirik> #meetingname irc-support-sig
18:00:22 <nirik> #topic init process
18:00:22 <zodbot> The meeting name has been set to 'irc-support-sig'
18:00:45 <nirik> any folks around for a irc support sig meeting?
18:01:14 * Khaytsus burps
18:01:21 <kc8hfi> i'm here, watchin
18:01:50 * nirik will wait a few min for folks.
18:03:39 <nirik> ok, I guess lets go ahead
18:03:52 <nirik> #topic Week(s) in review
18:04:18 <nirik> anything to bring up from over the holidays or recently?
18:04:24 <nirik> common bugs, issues, etc?
18:04:44 <nirik> it seemed overall pretty quiet.
18:04:56 <nirik> f20 went out pretty smoothly aside from a few hiccups right at release.
18:06:30 <nirik> #topic ticket #165: EvilBob excessive complaining about my away nick changer
18:06:32 <triad> hanging around; don't know what the topic means exactly
18:06:54 <nirik> this ties into the next topic as well somewhat
18:07:45 <nirik> triad: well, this group organizes support and management of #fedora... so the previous topic was to see if anyone had issues to bring up that they had seen a lot of recently.
18:08:57 <nirik> anyhow, I spoke my thoughts in this ticket already... I think we just close it at this point peding changes in the overall policy
18:09:03 <Khaytsus> The noise _from_ nick chnages has exceeded the actual nick changes recently.
18:09:14 <nirik> Khaytsus: yeah, thats the next topic.
18:09:22 <nirik> #topic revisit 'excessive' nick change policy
18:09:31 <Khaytsus> Some common sense needs to be employed when giving warnings
18:09:34 <nirik> so, our current policy is somewhat vuage and subjective.
18:09:55 <nirik> in particular some folks feel 'once' is 'excessive and anoying
18:10:17 <nirik> I think thats crazy. :)
18:10:33 <nirik> so, I guess we should draft a change and get folks to discuss/agree with it.
18:10:57 <Khaytsus> If it's happpening frequently, sure, put an end to it. If it happens once or once a day. It's noise, disruption, and just plane looks bad to yell at the user about it.
18:11:02 <nirik> we don't really have enough of us here today to change anything now, but I would like to soon.
18:11:11 <Khaytsus> plain.. ahem
18:11:25 <kc8hfi> plane, plain!
18:11:26 <nirik> I was thinking... 5 times in an hour
18:11:34 <nirik> the plane! the plane!
18:11:43 * Khaytsus walks on his knees
18:11:54 * Khaytsus coughs
18:12:18 <nirik> 5 times -> warn/tell them to stop, another time, kick/temp ban
18:12:59 <nirik> but I can file a ticket on it.
18:13:09 * kc8hfi doesn't see anything wrong with that
18:13:59 <Khaytsus> Everyone 20 minutes seems like it's condusive to auto away nick changes, which we'd ideally avoid. But otherwise tracking frequency isn't easy I suppose.
18:15:04 <nirik> yeah.
18:16:45 <Khaytsus> I'd +1 5/hr over 1 ever, no question :)
18:17:05 <nirik> yeah,
18:17:31 <nirik> #action nirik to write up new plan for nick change policy
18:17:36 <nirik> #topic Open Floor
18:17:42 <nirik> any items for open floor?
18:19:44 <nirik> alright then... will close out in a minute if nothing else.
18:20:38 <Khaytsus> :)
18:24:26 <nirik> #endmeeting