rabbit-slide-kenhys-debconf2020-online 2020.08.25.1 → 2020.08.25.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7c4a6656a968b56fb12bbac07cdf2ac7cd7bde498bebfd7fd2ed490ae1f2e18e
-  data.tar.gz: cf839104319c975ed6420c4150ce5a97690ab5ae9cdfd2a180a2870d14d82438
+  metadata.gz: 3cbc1fad7f39cc01cbf17f0e566ad0b9dda16bc840536383e6aba5a8c79bec5a
+  data.tar.gz: e76c4a4aa19a95da2a17794b42cdd6ecfb473b31a59d09654ae2b9af58d6c611
 SHA512:
-  metadata.gz: 63418802b608c1429ebbdb1995a9580b9cd44b10df3920720164ff35bb6c9046d346db7133b38f2073449bd89db8006748468012b02f329f98dde6ea1b8115a2
-  data.tar.gz: 5760305af4357bd4a1b62769264a1f68147f29331f32913f9a2cd8ed56fc3691ff98ab97ea54c00f3770a19bbb0fbecb2692721f14def421175de48d32f2af08
+  metadata.gz: f777c712317fa1774a4d3ef32ca5d5c7d2f830fd2939a0624d5351943fa0b20861d151e0ebf48cf884801ee41b4bad58590353b49456dd50c5e0dd4b8da9e971
+  data.tar.gz: 30346462c6ee33a580dd7ddcee135aefbcc5724f51b799a28e2e4c16072da4b507b01547ebdf2987994752dad6f6ad596adb98bfeab1aab9a9d4559b7a5f0deb

data/.rabbit

@@ -1 +1 @@
-debconf2020-online.md
+--size=1280,720 debconf2020-online.md

data/config.yaml

@@ -1,12 +1,15 @@
 ---
 id: debconf2020-online
 base_name: debconf2020-online
-tags: []
-presentation_date: 
+tags:
+- rabbit
+- debconf20
+- bugs.debian.org
+presentation_date: 2020-08-25
 presentation_start_time: 
 presentation_end_time: 
 slideshare_id: 
-version: 2020.08.25.1
+version: 2020.08.25.2
 licenses:
 - CC-BY-SA-4.0
 slideshare_id: kenhys
@@ -14,7 +17,7 @@ speaker_deck_id:
 vimeo_id: 
 youtube_id: 
 author:
-  markup_language: :rd
+  markup_language: :md
   name: Kentaro Hayashi
   email: kenhys@gmail.com
   rubygems_user: kenhys

data/debconf2020-online.md

@@ -50,7 +50,7 @@ theme
 
 * Why so curious about bugs.d.o?
 * The troublesome cases about bugs.d.o
-* What is Fabre and why is it needed?
+* How to solve this situation?
 * Demonstrate a front-end
 * Conclusion
 
@@ -196,7 +196,7 @@ theme
   * <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*
+    * *...But It is a bit different what I want*
 
 # What about existing solution?
 
@@ -362,7 +362,7 @@ cite: <https://en.wikipedia.org/wiki/Jean-Henri_Fabre>
 
 * Now ready to DEMO
 
-# More things about Fabre
+# Current status of Fabre
 
 * Tracked bugs: about 89,000 (UDD: 90,780)
   * {::note}Archived bugs: 720,000 (UDD: 85,0331){:/note}
@@ -370,6 +370,12 @@ cite: <https://en.wikipedia.org/wiki/Jean-Henri_Fabre>
 * Update affected bugs: every 1 day
 * Disk usage (Database): about 1.5 GiB
 
+# Weak point about Fabre
+
+![](images/killed-by-oom.png)
+
+* Sometimes Killed by OOM, need more memory!
+
 # Conclusion
 
 * There are plenty room of improvements to develop

data/presentation-memo.md

@@ -1,390 +1,322 @@
 # Presentation memo
 
+Hi, thank you for coming to this session.
+
+I'll start the presentation "An experiment about personalized
+front-end of bugs.debian.org.
+
 ## NOTE
 
-This slide is published at Rabbit Slide Show
+This slide was already published at Rabbit Slide Show
+
+So, you can also download this presentation.
+
+## Personal profile
+
+Let me just start by introducing myself.
+
+I'm one of the Debian maintainers.  and a fan of a Trackpoint and Wasa
+beef.  I'm also working for ClearCode.
 
 ## ClearCode Inc.
 
-* My collegue gave me a feedback for this talk
+Usually, I'm developing and supporting software as an engineer.
+
+There is a culture to respect free software, my colleague gave me a
+feedback for this talk.
 
 ## Not talk about
 
-In this session, I won't talk about bugs.debian.org internal in details.
+In this session, this presentation is related to bugs.debian.org, but
+I will not talk about improving bugs.debian.org itself and internal
+details.
 
 # Agenda
 
-* Why so curious about bugs.d.o?
-* The troublesome case about bugs.d.o
-* What is Fabre and why is it needed?
-* Demonstrate a front-end
-* Conclusion
+Here is the session agenda.
 
-# As a Maintainer
+First, I'll explain why so curious about bugs.d.o
+and show you the troublesome case.
 
-* Maintain some packages
-  * <https://qa.debian.org/developer.php?login=kenhys>
-    * groonga (Upstream releases monthly updates)
-    * fcitx-imlist
-    * libhinawa
-    * ...
+Next, I'll explain how to solve this situation and demonstrate an
+actual front-end.
 
 # We use bugs.d.o
 
-![](images/bugs-d-o.png){:relative-height="100"}
+Here is the screenshot of bugs.d.o.
+
+I guess you are familiar with it.
 
 # bugs.debian.org
 
-* Communicate each other by E-mail
-* Change the bug status by sending E-mail
-  * Sending E-mail to control@bugs.d.o
-  * Use control command in E-mail reply
+In bugs.d.o, we need to follow the rules.
+
+1. Communicate each other by E-mail
+2. Change the bug status by sending E-mail
 
 # 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
+One day, I've received deprecated notification about growl-for-linux
+package.
+
+growl-for-linux is a notification software.
+
+One is related to libappindicator and the other is related to
+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
-    * Fixed pkg-config target and include path
+About libappindicator, just migrated to libayatana-indicator.
 
 # 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
-    * Fixed a potential Rhythmbox related bug, too
+About, dbus-glib, I need to fix changed interfaces and migrated into
+GDBus.
 
 # growl-for-linux was fixed
 
-* But...What about other packages? 🤔
+Two bugs about growl-for-linux package was fixed, but I thought 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 and dbus-glib was tracked like this.
 
 # libappindicator: deprecated in Debian;
 
-![](images/libappindicator-blocked-by.png){:relative-height="80"}
-
-* Many blocked bugs
+Against libappindicator, there are many bugs.
 
 # libdbus-glib-1-dev: is deprecated
 
-![](images/libdbus-glib-blocked-by.png){:relative-height="80"}
-
-* *Too many* blocked bugs (Need to scroll)
-
-# Can you track blocked bugs?
-
-![](images/libdbus-glib-blocked-by.png){:relative-height="80"}
-
-* Feel dizzy 😵
+Against dbus-glib, there are too many blocked bugs.
 
 # How to track many blocked?
 
-* Use UserTags?
-  * <https://wiki.debian.org/bugs.debian.org/usertags>
-  * <https://udd.debian.org/cgi-bin/bts-usertags.cgi>
+In these case, we can use UserTags to track bugs.
 
 # Does it work with libappindicator?
 
-![](images/user-tag-ayatana-appindicator.png){:relative-height="80"}
-
-* UserTag is: *ayatana-appindicator*
+For libappindicator, ayatana-appindicator is used as UserTag
 
 # Does it work with libdbus-glib1-dev?
 
-* It is a case that UserTag is *not available*
-* It should be tagged...
+It should be tagged... but, UserTag is not available for dbus-glib.
 
 # The troublesome case about bugs.d.o
 
-* UserTag is not always used
-* Many blocked bugs may be difficult to see
-* *How to solve this situation?*
+Like this, there is a case that UserTag is not always used.  How to
+solve this situation?
 
 # Use udd.debian.org!
 
-![](images/udd-blocking-and-usertag.png){:relative-width="80"}
-
-  * Can track usertags
-  * Can track blocking bugs
+The answer is using udd.
+UDD can track usertags and blocking bugs.
 
 # In my experience, I need
 
-* Easy to:
+So far, I've fixed or sent feedback to some bugs, I became to feel the
+following ones are needed.
 
-  * Track a specified bug (tagged/not tagged)
-  * Find a bug that no one working on
-  * Send control/submitter E-mail
-  * Find affected bugs
+Tracking a specified bug
+Finding a bug that no one working on
+Sending control E-mail in required form
+Finding affected bugs
 
 # What I need for?
 
-* Easy to:
+First topic is solved by using UDD.
 
-  * ~~Track a specified bug (tagged/not tagged)~~ *Use UDD!*
-  * Find a bug that no one working on 🤔
-  * Send control/submitter E-mail 🤔
-  * Find affected bugs 🤔
+But how about the rest issues?
 
-# Starting personal project
+# How to solve rest issues?
 
-* Concept
-  * Make unstable life comfortable
-    * Find a bug that no one working on
-    * Easy to send control E-mail
-    * Easy to find blocking bugs
-    * Easy to find affected bugs
+Surely, It is a good manner to fix a bug, but it is not easy.
+It is also good to triage a bug, but it may be troublesome.
 
-# Starting personal project
+To know affected bugs are also important, but it is not so easy until
+it hits you.
 
-* Concept
-  * Make unstable life comfortable
-    * Find a bug that no one working on
-      *Count comment in bug#NNNNNN*
-    * Easy to send control E-mail
-      *Add mailto: link explicitly*
-    * Easy to find blocking bugs
-      *List blocking bugs*
-    * Easy to find affected bugs
-      *Alert affected bugs*
+# Find affected bugs
 
-# What should I do?
+In the past, there are some grave/critical bugs It had affected boot
+sequence / logged in user session.  I want to avoid these bugs.
 
-* Name the project 😀
-* Integrate with salsa.d.o account (optional)
-* Sync bug information
-* Import additional metadata
-* Make it accessible!
+# What about existing solution?
 
-# What should I do?
+I've searched existing useful services via Debian wiki.
 
-* *Name the project 😀*
-  {::note}Naming is important!{:/note}
-* Integrate with salsa.d.o account (optional)
-* Sync bug information
-* Import additional metadata
-* Make it accessible!
+Developer Horizon seems well, but not available.  Fabre also seems
+well, but discontinued already.
 
-# Named as Fabre
+I've also heard Debbugs Enhancement Suite.  But it is a bit different
+what I want.
 
-  ![](images/345px-Jean-henri_fabre.jpg){:relative-height="80"}
+# What about existing solution?
 
-cite: <https://en.wikipedia.org/wiki/Jean-Henri_Fabre>
+As a result, Debian Popularity Content and Public UDD Mirror seems
+useful.
 
-# Why Fabre?
+# Starting personal project
 
-* Reuse previous (maybe) similar project
-  * <http://fabre.debian.net>
-    * Around 2005, fulltext search service had been hosted
-    * Undocumented Debian "debbugs internal" {::note}written in Japanese{:/note}
-      * <https://tokyodebian-team.pages.debian.net/pdf2005/debianmeetingresume2005-fuyu.pdf>
+So I've started a personal project.
 
-# What should I do?
+The concept of this project is: "Make unstable life comfortable" It
+seems that it is ridiculous, but important for me.
 
-* Name the project 😀
-  {::note}Naming is important!{:/note}
-* *Integrate with salsa.d.o account (optional)*
-* Sync bug information
-* Import additional metadata
-* Make it accessible!
+# Starting personal project
 
-# Integrate with salsa.d.o account (optional)
+To achieve this concept, I need to do some tasks.
 
-* Use GitLab(salsa.d.o) as an OAuth2 provider
-  * <https://docs.gitlab.com/ee/api/oauth2.html>
-* No need to store sensitive password
+counting comment for each bugs, 
+and adding separate mailto: link,
+checking installed packages to alert affected bugs.
 
-# What should I do?
+# How to realize concept
 
-* Name the project 😀
-  {::note}Naming is important!{:/note}
-* Integrate with salsa.d.o account (optional)
-* *Sync bug information*
-* Import additional metadata
-* Make it accessible!
+Furthermore, collecting E-mail archives, popcon data, installed
+packages list and so on are also required.
 
-# Sync bug information
+# 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
+To collect E-mail archives, we can use bugs-mirror with rsync.  E-mail
+archive contains *.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
+There are many Perl modules to handle bugs.d.o related pieces of
+stuff.
 
 # 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"}
+For example, Log and MIME module is used to parse .log file.
 
 # 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"}
-
-# What should I do?
-
-* Name the project 😀
-  {::note}Naming is important!{:/note}
-* Integrate with salsa.d.o account (optional)
-* Sync bug information
-* *Import additional metadata*
-* Make it accessible!
-
-# Import additional metadata
-
-* 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
-
-# What should I do?
-
-* Name the project 😀
-  {::note}Naming is important!{:/note}
-* Integrate with salsa.d.o account (optional)
-* Sync bug information
-* Import additional metadata from UDD
-* *Make it accessible!*
+Status module is used to parse .summary file.
+You can access these bugs's metadata.
 
-# Prepared server specs for experiment
+# Collect Popcon data and so on
 
-* Start with small VPS instance (about 3.26 USD/mo)
-  * 1vCPU
-  * 1GiB memory
-  * 20GiB disk space
-  * Max 100Mbps bandwidth
+As UDD provides public database access, 
 
-# Fabre internals
+So we can get popcon stats and investigate which bug affects unstable
+or not.
 
-![](images/fabre-internals.png){:relative-height="100"}
+# Collect installed packages information
 
-# What is the trigger of syncing
+As popularity-content command can collect installed binary packages
+information.  It is useful to check recently used packages.
 
-* Subscribe debian-bugs-dist@lists.debian.org
-* Poll subscribed E-mail account
-* Fetch latest E-mail archives on bugs-mirror.debian.org
-* Convert & import E-mail archive data
+# Process collected data and make it accessible!
 
-# Concept of Fabre
+After collecting these information, updating bug information is
+required regularly.
 
-* Easy to find a bug that no one working on
-  * Count comment in bug#NNNNNN
-* Easy to send control E-mail
-  * Add mailto: link explicitly
-* Easy to view blocking bugs
-  * List blocking appropriately
+I've used debian-bugs-dist mailing list as a trigger to
+update and imported it into database.
 
-# Easy to find a bug that no one working on
+# Prepared server specs for experiment
 
-![](images/easy-to-find-no-one-working.png){:relative-height="80"}
+For my experiment, I've prepared small VPS instance.
 
-* Show each number of comments (yellow background color means no one working on yet)
+# System diagrams
 
-# Easy to send control E-mail
+Here is a simple diagram for explaining the system.
 
-![](images/easy-to-send-control-email.png){:relative-height="80"}
+Web server is nginx, Application server is puma, and backend database is Groonga.
 
-* Show each mailto: button to control
+It access external services,
+E-mail server, UDD for metadata, Salsa for authentication.
 
-# Easy to view blocking bugs
+# Named my project as Fabre
 
-![](images/easy-to-view-blocking.png){:relative-height="80"}
+As diagram indicates,
+I've named this personal system as Fabre.
 
-* List blocking appropriately
+# Why Fabre?
 
-# What comes to next?
+Fabre is famous by the study of insects.
+I've borrowed from discontinued similar project in decades ago
 
-* It looks useful, isn't it?
+# Concept of Fabre (again)
 
-# Personalize Fabre!
+The concept is this project is Make "unstable life" comfortable.
 
-* Add bookmark
-* Show affected bugs
-* Followup newer comments
+# Finding a bug that no one working on
 
-# Personalize Fabre!
+Here is the partial screenshot of Fabre.
+It shows each number of comments (orange background color means no one working on yet)
 
-* Add bookmark
-  * *Link account and bug*
-* Show affected bugs
-  * *Link account and installed packages list*
-* Followup newer comments
-  * *Link account and search comment information*
+# Sending control E-mail easily
 
-# How to collect installed packages list?
+I've added each mailto: button to sending control mail
 
-    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
+# Easy to view blocked bugs
 
-* Just upload popcon file
-  * /usr/sbin/popularity-contest --su-nobody
+I've aligned blocked bugs.
 
-# Personalized Fabre on dashboard
+# Finding affected important bugs
 
-![](images/fabre-dashboards.png){:relative-height="100"}
+I've added a dashboard to show fire icon. It indicates that there are affected bugs.
 
 # How Fabre is good enough to work?
 
-* Now ready to DEMO if there is a time to do
+I'll show you some demo about Fabre.
+
+# Current status of Fabre
+
+That's all about Fabre demonstration.
+
+In this system, tracked bugs are reached to eighty-nine thousand.
+UDD tracks 90 thousand bugs, so it covers most of them.
+
+Currently, bug information is updated every 1 hour, and affected bugs are also updated every 1 day.
+
+Disk usage is about 1.5 GiB.
+
+# Weak point of Fabre
+
+There is a one weak point about Fabre.
+out of memory is occurred sometimes.
 
 # Conclusion
 
-* In my experiment, mashup some data sources may improve UX
-  * bug report
-  * UDD metadata
-  * installed packages list
-* There are plenty room of improvements to develop
+* There is plenty room of improvement to develop, so I'll go forward this experiment furthermore.
+* In my experiment, I've found that mashup some data sources may improve user experience.
 
 # Any questions?
 
 Could you speak slowly if you ask, please?
+
+# DEMO
+
+I'll demonstrate some features of Fabre.
+
+If you already sign-in with salsa account,
+You can also sign in with Fabre.
+
+You need explicitly allow to authorize with Fabre.
+
+After sign in, you can access the dashboard.
+
+In the dashboard, you can see a status.
+
+As you can see, there are three affected bugs,
+ten bookmarked bugs, and you installed thousand and six hundred packages.
+
+At the bottom of the dashboard, you can check the existence of newer comments since you commented finally.
+
+Let's see the affected bugs.
+These information is based on your installed packages.
+
+Let's see the bookmarked bugs.
+In every bug detail page, bookmark button is shown, so you can track bug freely.
+
+You can see recent update bugs, release critical bugs, and newcomer bugs.
+
+Here is the bug detail page,
+
+You can view original bug report via clicking link,
+tweet about bugs,
+and send control E-mail easily.
+

data/theme.rb

@@ -1,3 +1,5 @@
 @default_font = "Ubuntu"
 @monospace_font = "Ubuntu"
 include_theme("debian")
+@slide_show_span = 1800
+@slide_show_loop = true

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rabbit-slide-kenhys-debconf2020-online
 version: !ruby/object:Gem::Version
-  version: 2020.08.25.1
+  version: 2020.08.25.2
 platform: ruby
 authors:
 - Kentaro Hayashi
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-08-13 00:00:00.000000000 Z
+date: 2020-08-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rabbit
@@ -45,6 +45,7 @@ files:
 - images/fabre-dashboards.png
 - images/fabre-internals.png
 - images/fabre-internals.svg
+- images/killed-by-oom.png
 - images/libappindicator-blocked-by.png
 - images/libdbus-glib-blocked-by.png
 - images/logo-combination-standard.svg