rabbit-slide-kenhys-debconf2020-online 2020.08.25.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 7c4a6656a968b56fb12bbac07cdf2ac7cd7bde498bebfd7fd2ed490ae1f2e18e
+  data.tar.gz: cf839104319c975ed6420c4150ce5a97690ab5ae9cdfd2a180a2870d14d82438
+SHA512:
+  metadata.gz: 63418802b608c1429ebbdb1995a9580b9cd44b10df3920720164ff35bb6c9046d346db7133b38f2073449bd89db8006748468012b02f329f98dde6ea1b8115a2
+  data.tar.gz: 5760305af4357bd4a1b62769264a1f68147f29331f32913f9a2cd8ed56fc3691ff98ab97ea54c00f3770a19bbb0fbecb2692721f14def421175de48d32f2af08

data/.rabbit

@@ -0,0 +1 @@
+debconf2020-online.md

data/README.md

@@ -0,0 +1,14 @@
+# DebConf20
+
+## How to show
+
+  % rabbit
+
+## How to install
+
+  % gem install rabbit-slide-kenhys-debconf2020-online
+
+## How to create PDF
+
+  % rake pdf
+

data/Rakefile

@@ -0,0 +1,17 @@
+require "rabbit/task/slide"
+
+# Edit ./config.yaml to customize meta data
+
+spec = nil
+Rabbit::Task::Slide.new do |task|
+  spec = task.spec
+  # spec.files += Dir.glob("doc/**/*.*")
+  # spec.files -= Dir.glob("private/**/*.*")
+  # spec.add_runtime_dependency("rabbit-theme-YOUR-THEME")
+end
+
+desc "Tag #{spec.version}"
+task :tag do
+  sh("git", "tag", "-a", spec.version.to_s, "-m", "Publish #{spec.version}")
+  sh("git", "push", "--tags")
+end

data/cfp.md

@@ -0,0 +1,22 @@
+Experiment about Debian's bug tracking front-end
+
+### Experiment about Debian's bug tracking front-end
+
+Debian has a bug tracking system and bugs.debian.org is a key infrastructure for Debian project.
+It tracks many reports and the bug number is assigned to each reports.
+You can view such a report via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=NNNNNN.
+
+This bug tracking mechanism is working well for a long time.
+It is very cool but it may be not friendly for newcomers.
+
+#### Target audience
+
+* Debian contributor or maintainer who want to fix bugs not only the bugs which
+is related to maintained packages by you
+
+It may not interesting for Debian developer because DD is already familiar with bugs.debian.org.
+
+#### What will talk about
+
+In this session, I’ll talk about one experiment about Debian's bug tracking mechanism.
+It is constructed on traditional E-mail archives and simple front-end for it.

data/config.yaml

@@ -0,0 +1,22 @@
+---
+id: debconf2020-online
+base_name: debconf2020-online
+tags: []
+presentation_date: 
+presentation_start_time: 
+presentation_end_time: 
+slideshare_id: 
+version: 2020.08.25.1
+licenses:
+- CC-BY-SA-4.0
+slideshare_id: kenhys
+speaker_deck_id: 
+vimeo_id: 
+youtube_id: 
+author:
+  markup_language: :rd
+  name: Kentaro Hayashi
+  email: kenhys@gmail.com
+  rubygems_user: kenhys
+  slideshare_user: kenhys
+  speaker_deck_user: 

data/debconf2020-online.md

@@ -0,0 +1,383 @@
+# An experiment about personalized front-end of bugs.debian.org
+
+subtitle
+:  E-mail archives + UDD + Simple web front-end = 🤔
+
+author
+:  Kentaro Hayashi
+
+institution
+:  ClearCode Inc.
+
+content-source
+:  DebConf20 online August 25, 2020
+
+allotted-time
+:   15m
+
+theme
+:  .
+
+# NOTE: Presentation slide is published
+
+* This presentation slide is available via Rabbit Slide Show
+  * <https://slide.rabbit-shocker.org/authors/kenhys/debconf20-online/>
+    "An experiment about personalized front-end of bugs.debian.org"
+
+# Personal profile
+
+![](images/profile.png){:relative-height="40"}
+
+* Debian Maintainer (@kenhys)
+* Trackpoint(soft dome) and Wasa beef(Yamayoshi Wasabi Potato Chips) fan
+* Working for ClearCode Inc.
+
+# ClearCode Inc.
+
+![](images/logo-combination-standard.svg){:relative-height="30"}
+
+* <https://www.clear-code.com/>
+  * Free software is important in ClearCode Inc.
+  * We develop/support software with our free software development experiences
+  * We feedback our business experiences to free software
+
+# Not talk about
+
+* Improving bugs.debian.org (debbugs) itself
+* Explaining bugs.debian.org (debbugs) internal in details
+
+# Agenda
+
+* Why so curious about bugs.d.o?
+* The troublesome cases about bugs.d.o
+* What is Fabre and why is it needed?
+* Demonstrate a front-end
+* Conclusion
+
+# We use bugs.d.o
+
+![](images/bugs-d-o.png){:relative-height="100"}
+
+# Usage of bugs.debian.org - prerequisite
+
+* Communicate each other by E-mail
+* Change the bug status by sending E-mail
+  * Send E-mail to control@bugs.d.o
+  * Use control command in E-mail reply
+
+# Why so curious about bugs.d.o?
+
+* I've received deprecated notification bugs
+  * Bug# 956770 growl-for-linux: Depends on deprecated libappindicator
+  * Bug# 955899 growl-for-linux: Depends on deprecated dbus-glib
+
+# How did you fixed?
+
+* Bug# 956770 growl-for-linux: Depends on deprecated libappindicator
+  * <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956770>
+  * Migrated to libayatana-indicator
+    * It is easy because there are enough compatibility
+    * I've fixed pkg-config target and include path
+
+# How did you fixed? (again)
+
+* Bug# 955899 growl-for-linux: Depends on deprecated dbus-glib
+  * <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955899>
+  * Migrated to GDBus
+    * Use d-feet to detect interface change (Rhythmbox plugin)
+    * Fixed a interface to follow GDBus API
+  * Send PR to upstream <https://github.com/mattn/growl-for-linux/>
+    * Fixed a potential Rhythmbox related bug, too
+
+# growl-for-linux was fixed
+
+* But...What about other packages? 🤔
+
+# What about other packages?
+
+* libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
+  * <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895037>
+* libdbus-glib-1-dev: is deprecated
+  * <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895291>
+
+# libappindicator: deprecated in Debian
+
+![](images/libappindicator-blocked-by.png){:relative-height="80"}
+
+* Many blocked bugs
+
+# libdbus-glib-1-dev: is deprecated in Debian
+
+![](images/libdbus-glib-blocked-by.png){:relative-height="80"}
+
+* *Too many* blocked bugs (Need to scroll!) 😵
+
+# How to track many blocked?
+
+* In this case, UserTags is recommended
+  * <https://wiki.debian.org/bugs.debian.org/usertags>
+  * <https://udd.debian.org/cgi-bin/bts-usertags.cgi>
+
+# Does it work with libappindicator?
+
+![](images/user-tag-ayatana-appindicator.png){:relative-height="80"}
+
+* UserTag is: *ayatana-appindicator*
+
+# Does it work with libdbus-glib1-dev?
+
+* It is a case that UserTag is *not available*
+* It should be tagged...
+
+# The troublesome cases about bugs.d.o
+
+* UserTag is not always used
+* It may be difficult to see many blocked bugs
+* *How to solve this situation?*
+
+# Use udd.debian.org!
+
+![](images/udd-blocking-and-usertag.png){:relative-width="80"}
+
+  * UDD can track usertags
+  * UDD can track blocking bugs
+
+# In my experience through contribution, I need
+
+* I need easy to:
+
+  * Track a specified bug (tagged/not tagged)
+  * Find a bug that no one working on
+  * Send control E-mail
+  * Find affected bugs
+
+# In my experience through contribution (again)
+
+* I need easy to:
+  * ~~Track a specified bug (tagged/not tagged)~~ *Use UDD!*
+  * Find a bug that no one working on 🤔
+  * Send control E-mail 🤔
+  * Find affected bugs 🤔
+
+# How to solve rest issues?
+
+* Find a bug that no one working on 🤔
+  * It's a good attitude to fix a bug
+* Send control E-mail easily 🤔
+  * It's a good attitude to triage a bug
+* Find affected bugs 🤔
+  * Remember misery bugs #932855, #965164
+
+# Supplementary explanation: Find affected bugs 🤔
+
+* Sometimes grave/critical bug was found
+  * 2019, critical, e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
+    * <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932855>
+  * 2020, grave, policykit-1: fails to install
+    * <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965164>
+
+# What about existing solution?
+
+<https://wiki.debian.org/Services>
+
+* Developer Horizon - A dashboard for developers
+  * <http://horizon.debian.net/> *Not available*
+
+# What about existing solution?
+
+* Fabre - fulltext search service
+  * <http://fabre.debian.net> Around 2005, *Discontinued*
+  * Undocumented Debian "debbugs internal" {::note}written in Japanese{:/note}
+    * <https://tokyodebian-team.pages.debian.net/pdf2005/debianmeetingresume2005-fuyu.pdf>
+
+# What about existing solution?
+
+* Debbugs Enhancement Suite
+  * <https://salsa.debian.org/lamby/debbugs-enhancement-suite>
+  * A Chrome extension to enhance using Debbugs
+  * Tidy up each bug rendering, it's cool (Thanks @lolamby FYI:)
+    * *...But It is not what I want*
+
+# What about existing solution?
+
+* Debian Popularity Contest
+  * <http://popcon.debian.org/>
+  * It provides a method to collect installed packages information
+
+* Public UDD Mirror
+  * <https://udd-mirror.debian.net/>
+  * It provides a statistical information about packages
+
+# Starting personal project
+
+* Concept
+  * *Make "unstable life" comfortable*
+    * Fix a bug (by finding a bug that no one working on)
+    * Triage a bug (by sending control E-mail easily)
+    * Avoid affected bugs (by finding affected important bugs)
+
+# Starting personal project (again)
+
+* Concept
+  * Make "unstable life" comfortable
+    * Fix a bug (by finding a bug that no one working on) *Count comment in bug#NNNNNN*
+    * Triage a bug (by sending control E-mail easily) *Add mailto: link explicitly*
+    * Avoid affected bugs (by finding affected important bugs) *Alert recent grave bugs*
+
+# How to realize concept?
+
+* Collect bug information regularly (E-mail archives)
+* Collect Popcon data (Fix a bug with your familiar packages)
+* Collect your installed packages information (popularity-contest)
+* Process collected data and make it accessible!
+
+# Collect bug information
+
+* Get E-mail archive with rsync
+  * <https://salsa.debian.org/debbugs-team/debbugs>
+  * rsync -av rsync://bugs-mirror.debian.org/bts-spool-db/
+    {::note}It requires 15GiB!{:/note}
+* Use *.log and *.summary
+
+# Extract .log and .summary
+
+* Use perl module which is used for bugs.d.o (Debbugs)
+  * Debbugs::Log, Debbugs::Status, Debbugs::MIME and so on
+  * *.log contains multiple raw E-mail content with control sequence
+  * *.summary contains metadata of each bug
+
+# How to parse .log
+
+    my $log = Debbugs::Log->new(log_name => $path);
+    my @records = $log->read_all_records();
+    for my $record (@records) {
+      ...
+      my $entity = Debbugs::MIME::parse_to_mime_entity($record);
+      print "From: " . $entity->head->get("From");
+      print "To: " . $entity->head->get("To");
+      print "Subject: " . get_field($entity, "Subject");
+      print "Date: " . $entity->head->get("Date");
+    }
+{: lang="perl"}
+
+# How to parse .summary
+
+    Format-Version: 3
+    Submitter: Nis Martensen <nis.martensen@web.de>
+    Subject: libexo-helpers: starting thunderbird fails for some mailto URIs
+    Found-In: exo/0.12.4-1
+    Tags: patch
+    Package: libexo-helpers
+    Message-Id: <159439678897.3833.10774950364480956704.reportbug@siamos.nes.net>
+    Severity: normal
+    Date: 1594396982
+
+    my $summary = Debbugs::Status::read_bug(summary => $path);
+    print $summary->{"tags"}
+{: lang="perl"}
+
+# Collect Popcon data and so on
+
+* UDD: UltimateDebianDatabase
+  * <https://wiki.debian.org/UltimateDebianDatabase>
+  * You can access with:
+    psql --host=udd-mirror.debian.net --user=udd-mirror udd --password
+  * Schema is available: <https://udd.debian.org/schema/udd.html>
+    * Import popcon and package data
+
+# Collect installed packages information
+
+    POPULARITY-CONTEST-0 TIME:1596711793 ID:XXX ARCH:amd64 POPCONVER:1.70 VENDOR:Debian
+    1596672000 1570622400 libgail-common /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libgail.so
+    1596672000 1596585600 libavcodec58 /usr/lib/x86_64-linux-gnu/libavcodec.so.58.91.100 <RECENT-CTIME>
+    1596672000 1586736000 libgoa-1.0-0b /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0.0.0
+    ...
+    1596672000 1586217600 libzvbi0 /usr/lib/x86_64-linux-gnu/libzvbi.so.0.13.2
+    1596672000 1590624000 udisks2 /usr/share/locale/ja/LC_MESSAGES/udisks2.mo
+    END-POPULARITY-CONTEST-0 TIME:1596711817
+
+* Just upload popcon file
+  * /usr/sbin/popularity-contest --su-nobody
+
+# Process collected data and make it accessible!
+
+* Polling subscribed debian-bugs-dist@lists.debian.org
+* Importing latest E-mail archives from bugs-mirror.debian.org
+* Merging metadata + Web front-end
+
+# Prepared server specs for experiment
+
+* Start with small VPS instance (about 3.26 USD/mo)
+  * 1vCPU
+  * 1GiB memory
+  * 20GiB disk space
+  * Max 100Mbps bandwidth
+
+# System diagrams
+
+![](images/fabre-internals.png){:relative-height="100"}
+
+# Named my project as Fabre
+
+  ![](images/345px-Jean-henri_fabre.jpg){:relative-height="80"}
+
+cite: <https://en.wikipedia.org/wiki/Jean-Henri_Fabre>
+
+# Why Fabre?
+
+* Fabre is "The father of modern entomology" - the study of insects(bugs)
+* Just reuse previous (maybe) similar project (fabre.debian.net)
+
+# Concept of Fabre (again)
+
+* *Make "unstable life" comfortable*
+  * Fix a bug (by finding a bug that no one working on)
+  * Triage a bug (by sending control E-mail easily)
+  * Avoid affected bugs (by checking installed packages)
+
+# Finding a bug that no one working on
+
+![](images/easy-to-find-no-one-working.png){:relative-height="80"}
+
+* Show each number of comments (orange background color means no one working on yet)
+
+# Sending control E-mail easily
+
+
+![](images/easy-to-send-control-email.png)
+
+* Show each mailto: button to control bugs
+
+# Easy to view blocked bugs
+
+![](images/easy-to-view-blocking.png){:relative-height="80"}
+
+* List blocked bugs appropriately
+
+# Finding affected important bugs
+
+![](images/fabre-dashboards.png){:relative-height="100"}
+
+# How Fabre is good enough to work?
+
+* Now ready to DEMO
+
+# More things about Fabre
+
+* Tracked bugs: about 89,000 (UDD: 90,780)
+  * {::note}Archived bugs: 720,000 (UDD: 85,0331){:/note}
+* Import bugs: every 1 hour
+* Update affected bugs: every 1 day
+* Disk usage (Database): about 1.5 GiB
+
+# Conclusion
+
+* There are plenty room of improvements to develop
+* In my experiment, mashup some data sources may improve UX
+  * bug report (E-mail archives)
+  * UDD metadata (Popcon and package metadata)
+  * installed packages list (popularity-contest)
+
+# Any questions?
+
+Could you speak slowly if you have a question, please?