rabbit-slide-kenhys-debconf2021-online 2021.08.28.1 → 2021.08.28.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/config.yaml +1 -1
- data/debconf2021-online.md +3 -4
- data/images/debconf2021-presentation.png +0 -0
- data/pdf/debconf2021-online-debconf2021-online.pdf +0 -0
- data/short-talk-manuscript.md +176 -0
- metadata +4 -5
- data/faq.md +0 -17
- data/minidebconf-india2021.md +0 -116
- data/presentation-memo.md +0 -322
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: d56f143772e856907553bfdf3f9264dfc4474213f2881ce760ab0b1ab8d11442
|
|
4
|
+
data.tar.gz: 8761f84704fb692a006bde38dbd873ab576414edc3b5c6b0d63112caa3ddc1b5
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: b1aa2742a9cf62f0488189e02311b46e1a6d5b83823c10fca16dec3c91dc2be82ca5412e4c9b0480c621456cd2efc7a9fa1a724d660aa789b56da3605a49fb80
|
|
7
|
+
data.tar.gz: 7830710a175b650a80bdafeb6bf932ef9016de76d481b18bfb67b669db07cc13fa1ba47ee3916565159ba9f9a9055bbd5cfde32fd53517bfdd86b3abe28ccd89
|
data/config.yaml
CHANGED
data/debconf2021-online.md
CHANGED
|
@@ -20,8 +20,7 @@ theme
|
|
|
20
20
|
|
|
21
21
|
# See Rabbit Slide Show
|
|
22
22
|
|
|
23
|
-
|
|
24
|
-
* <https://slide.rabbit-shocker.org/authors/kenhys/debconf2021-online/>
|
|
23
|
+
{:relative-height="100"}
|
|
25
24
|
|
|
26
25
|
# Personal profile
|
|
27
26
|
|
|
@@ -142,11 +141,11 @@ theme
|
|
|
142
141
|
|
|
143
142
|
# Finding a FTBFS bug 🆕
|
|
144
143
|
|
|
145
|
-
{:relative-height="100"}
|
|
146
145
|
|
|
147
146
|
# Finding a security bug 🆕
|
|
148
147
|
|
|
149
|
-
{:relative-height="100"}
|
|
150
149
|
|
|
151
150
|
# Finding a architecture specific bug 🆕
|
|
152
151
|
|
|
Binary file
|
|
Binary file
|
|
@@ -0,0 +1,176 @@
|
|
|
1
|
+
# Short talk manuscript
|
|
2
|
+
|
|
3
|
+
Hi, thank you for coming to this short talk.
|
|
4
|
+
|
|
5
|
+
I'll start the presentation "Lastest topics about fabre.debian.net".
|
|
6
|
+
|
|
7
|
+
## See Rabbit Slide Show
|
|
8
|
+
|
|
9
|
+
This slide was already published at Rabbit Slide Show
|
|
10
|
+
|
|
11
|
+
So, you can see this presentation later.
|
|
12
|
+
|
|
13
|
+
## Personal profile
|
|
14
|
+
|
|
15
|
+
Let me just start by introducing myself.
|
|
16
|
+
|
|
17
|
+
I'm one of a Debian Developer since last year.
|
|
18
|
+
I'm working for ClearCode.
|
|
19
|
+
|
|
20
|
+
## ClearCode Inc.
|
|
21
|
+
|
|
22
|
+
Usually, I'm developing and supporting software as an engineer.
|
|
23
|
+
|
|
24
|
+
There is a culture to respect free software activity,
|
|
25
|
+
so I could prepare this presentation at work.
|
|
26
|
+
|
|
27
|
+
# Agenda
|
|
28
|
+
|
|
29
|
+
Here is the short talk agenda.
|
|
30
|
+
|
|
31
|
+
Maybe you don't know Fabre, I'll explain it first.
|
|
32
|
+
It is appropriate to show last year's presentation to make you know Fabre well.
|
|
33
|
+
|
|
34
|
+
Next, I'll explain the issues what I want to solve and
|
|
35
|
+
useful use cases by Fabre.
|
|
36
|
+
|
|
37
|
+
# What is Fabre?
|
|
38
|
+
|
|
39
|
+
Here is the screenshot of Fabre.
|
|
40
|
+
|
|
41
|
+
In short, It's a small web service to find untouched bugs.
|
|
42
|
+
|
|
43
|
+
# Recall DebConf20 presentation summary
|
|
44
|
+
|
|
45
|
+
In the last year's DebConf, I gave you a short talk about Fabre.
|
|
46
|
+
|
|
47
|
+
Fabre is an experiment to make a better bug tracking experience,
|
|
48
|
+
and the way to achieve such a purpose.
|
|
49
|
+
|
|
50
|
+
In this slide, I've explained the current problems and
|
|
51
|
+
the idea how to solve it, system internals about Fabre web service.
|
|
52
|
+
|
|
53
|
+
# What I want to solve
|
|
54
|
+
|
|
55
|
+
There are many services in Debian project.
|
|
56
|
+
qa, tracker, debian maintainer dashboard and so on.
|
|
57
|
+
|
|
58
|
+
But in point view of tracking bugs, there is a case that it is hard to do it.
|
|
59
|
+
This is because these services are aimed to help package maintainer.
|
|
60
|
+
|
|
61
|
+
For example,
|
|
62
|
+
It is troublesome if you find only untouched bugs.
|
|
63
|
+
or see blocked bugs at a glance.
|
|
64
|
+
It seems that these issues are not covered well.
|
|
65
|
+
|
|
66
|
+
# How to solve this situation?
|
|
67
|
+
|
|
68
|
+
Then I've started an experimental service to solve these problems.
|
|
69
|
+
|
|
70
|
+
To achieve it, I've used to mashup existing data.
|
|
71
|
+
E-mail archive is used to control syncing intervals.
|
|
72
|
+
UDD metadata is used to track status of bugs.
|
|
73
|
+
|
|
74
|
+
# fabre.debian.net
|
|
75
|
+
|
|
76
|
+
Here is the screenshot of fabre.debian.net
|
|
77
|
+
|
|
78
|
+
In the left side, most commonly used categories are put on.
|
|
79
|
+
|
|
80
|
+
In the right side, list of bugs are shown.
|
|
81
|
+
|
|
82
|
+
# Latest topics
|
|
83
|
+
|
|
84
|
+
Here is the latest topics of Fabre.
|
|
85
|
+
|
|
86
|
+
First topic is domain of Fabre.
|
|
87
|
+
The second one is about sponsorship.
|
|
88
|
+
The last one is minor improvements.
|
|
89
|
+
|
|
90
|
+
# Fabre had been deployed under debian.net
|
|
91
|
+
|
|
92
|
+
At first, Fabre was not deployed on debian.net.
|
|
93
|
+
Since I've become a Debian Developer, I've contacted DSA and
|
|
94
|
+
finally transferred subdomain ownership to me.
|
|
95
|
+
As a result, I could manage fabre.debian.net.
|
|
96
|
+
|
|
97
|
+
# Sponsorship for fabre.debian.net
|
|
98
|
+
|
|
99
|
+
Next topic is sponsorship
|
|
100
|
+
|
|
101
|
+
Fabre didn't have sponsor at first.
|
|
102
|
+
It was deployed on very small VPS instance on WebARENA, so there was a issue of limited server resources.
|
|
103
|
+
It causes out of memory frequently, sometimes it must be restarted.
|
|
104
|
+
|
|
105
|
+
But I could got sponsor - It was FOSSHOST.
|
|
106
|
+
As you know, there was a concern about continuity before,
|
|
107
|
+
I've stopped to use it and got new sponsor - Debian.net team infrastructure.
|
|
108
|
+
|
|
109
|
+
As a result, the issue of server resources are solved completely.
|
|
110
|
+
|
|
111
|
+
# Off-Topic: Request hosting sponsor
|
|
112
|
+
|
|
113
|
+
It's a off topic,
|
|
114
|
+
You can request hosting sponsorship to Debian.net team on salsa.
|
|
115
|
+
|
|
116
|
+
# And some more minor improvements
|
|
117
|
+
|
|
118
|
+
The last topic is some more improvements since last year,
|
|
119
|
+
but it is a too minor ones, so I'll show you useful use cases instead.
|
|
120
|
+
|
|
121
|
+
# Use cases about fabre.debian.net
|
|
122
|
+
|
|
123
|
+
There are 6 use cases to show you.
|
|
124
|
+
|
|
125
|
+
Finding a bug that no one working on
|
|
126
|
+
Sending control E-mail easily
|
|
127
|
+
Easy to view blocked bugs
|
|
128
|
+
Finding a FTBFS bug
|
|
129
|
+
Finding a security bug
|
|
130
|
+
Finding a architecture specific bug
|
|
131
|
+
|
|
132
|
+
# 1st: Finding a bug that no one working on
|
|
133
|
+
|
|
134
|
+
It shows the number of comments for your hints in list of bugs.
|
|
135
|
+
And Fixme tab is applied to filter bugs in this slide.
|
|
136
|
+
|
|
137
|
+
# 2nd: Sending control E-mail easily
|
|
138
|
+
|
|
139
|
+
In every bug report page, it contains mailto: buttons to control bugs.
|
|
140
|
+
If you click these buttons, it launches your E-mail client.
|
|
141
|
+
|
|
142
|
+
In this case, you can send control E-mail for tagging architecture as a bug report.
|
|
143
|
+
|
|
144
|
+
# 3rd: Easy to view blocked bugs
|
|
145
|
+
|
|
146
|
+
In contrast to bugs.debian.org, it shows blocked by bugs at a glance.
|
|
147
|
+
If there are plenty of blocked by bugs, this feature is very useful.
|
|
148
|
+
|
|
149
|
+
# 4th Finding a Fail to build from source bug
|
|
150
|
+
|
|
151
|
+
It is a new feature, I've added fail to build from source category.
|
|
152
|
+
There are over 200 untouched bugs.
|
|
153
|
+
Most of these bugs are tagged as serious or important.
|
|
154
|
+
|
|
155
|
+
# 5th Finding a security bug
|
|
156
|
+
|
|
157
|
+
It is also a new feature, I've added security category, too.
|
|
158
|
+
There are over 300 untouched bugs.
|
|
159
|
+
Most of these bugs are tagged as important or normal.
|
|
160
|
+
|
|
161
|
+
# 6th Finding a architecture specific bug
|
|
162
|
+
|
|
163
|
+
It is also a new feature, I've added architecture category, too.
|
|
164
|
+
Architecture tag was formalized recently, at most seventy bugs are registered now.
|
|
165
|
+
|
|
166
|
+
# Summary
|
|
167
|
+
|
|
168
|
+
As a summary,
|
|
169
|
+
|
|
170
|
+
Fabre had been deployed as debian.net and sponsored by Debian.net team infrastructure.
|
|
171
|
+
Fabre is continuously updated since last year, and I'll implement what I want to do in the future.
|
|
172
|
+
|
|
173
|
+
# Any questions?
|
|
174
|
+
|
|
175
|
+
And that's it, thank you.
|
|
176
|
+
Could you speak slowly when you ask, please?
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: rabbit-slide-kenhys-debconf2021-online
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 2021.08.28.
|
|
4
|
+
version: 2021.08.28.3
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Kentaro Hayashi
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2021-08-
|
|
11
|
+
date: 2021-08-15 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: rabbit
|
|
@@ -38,8 +38,8 @@ files:
|
|
|
38
38
|
- concept.md
|
|
39
39
|
- config.yaml
|
|
40
40
|
- debconf2021-online.md
|
|
41
|
-
- faq.md
|
|
42
41
|
- images/debconf2020-presentation.png
|
|
42
|
+
- images/debconf2021-presentation.png
|
|
43
43
|
- images/debian.net-team-requests.png
|
|
44
44
|
- images/easy-to-find-archtag.png
|
|
45
45
|
- images/easy-to-find-ftbfs.png
|
|
@@ -54,9 +54,8 @@ files:
|
|
|
54
54
|
- images/fabre.debian.net.png
|
|
55
55
|
- images/logo-combination-standard.svg
|
|
56
56
|
- images/profile.png
|
|
57
|
-
- minidebconf-india2021.md
|
|
58
57
|
- pdf/debconf2021-online-debconf2021-online.pdf
|
|
59
|
-
-
|
|
58
|
+
- short-talk-manuscript.md
|
|
60
59
|
- theme.rb
|
|
61
60
|
homepage: https://slide.rabbit-shocker.org/authors/kenhys/debconf2021-online/
|
|
62
61
|
licenses:
|
data/faq.md
DELETED
|
@@ -1,17 +0,0 @@
|
|
|
1
|
-
Q. When Fabre is available?
|
|
2
|
-
A. I don't have concrete schedule about it.
|
|
3
|
-
It is in very early stage of development, because I want to show proof of concept at DebConf.
|
|
4
|
-
|
|
5
|
-
Q. Where can I find the source code of Fabre?
|
|
6
|
-
A. I'll publish at Fabre code on salsa.d.o in the future.
|
|
7
|
-
|
|
8
|
-
Q. What can I help for Fabre?
|
|
9
|
-
A. I hope you will send cool logo for Fabre.
|
|
10
|
-
|
|
11
|
-
Q. Why doesn't send E-mail from system?
|
|
12
|
-
A. I think to send E-mail automatically is not appropriate because
|
|
13
|
-
the responsibility of sending E-mail should be owned by yourself.
|
|
14
|
-
|
|
15
|
-
Q. Why did you use Groonga?
|
|
16
|
-
A. Because I maintain Groonga package and I also want to support fulltext-search with it.
|
|
17
|
-
Groonga is a column store database which supports fulltext-search.
|
data/minidebconf-india2021.md
DELETED
|
@@ -1,116 +0,0 @@
|
|
|
1
|
-
# fabre.debian.net \\n Finding untouched bugs
|
|
2
|
-
|
|
3
|
-
subtitle
|
|
4
|
-
: E-mail archives + UDD metadata + Simple web front-end = 🤔
|
|
5
|
-
|
|
6
|
-
author
|
|
7
|
-
: Kentaro Hayashi
|
|
8
|
-
|
|
9
|
-
institution
|
|
10
|
-
: ClearCode Inc.
|
|
11
|
-
|
|
12
|
-
content-source
|
|
13
|
-
: MiniDebConf India 2021 January 23, 2021
|
|
14
|
-
|
|
15
|
-
allotted-time
|
|
16
|
-
: 5m
|
|
17
|
-
|
|
18
|
-
theme
|
|
19
|
-
: .
|
|
20
|
-
|
|
21
|
-
# NOTE: Presentation slide is published
|
|
22
|
-
|
|
23
|
-
* This presentation slide is available via Rabbit Slide Show
|
|
24
|
-
* <https://slide.rabbit-shocker.org/authors/kenhys/minidebconf-india2021/>
|
|
25
|
-
"fabre.debian.net - Finding untouched bugs"
|
|
26
|
-
|
|
27
|
-
# Personal profile
|
|
28
|
-
|
|
29
|
-
{:relative-height="40"}
|
|
30
|
-
|
|
31
|
-
* Newbie Debian Developer since September 2020 (@kenhys)
|
|
32
|
-
* Trackpoint(soft dome) and Wasa beef(Yamayoshi Wasabi Potato Chips) fan
|
|
33
|
-
* Working for ClearCode Inc.
|
|
34
|
-
|
|
35
|
-
# ClearCode Inc.
|
|
36
|
-
|
|
37
|
-
{:relative-height="30"}
|
|
38
|
-
|
|
39
|
-
* <https://www.clear-code.com/>
|
|
40
|
-
* Free software is important in ClearCode Inc.
|
|
41
|
-
* We develop/support software with our free software development experiences
|
|
42
|
-
* We feedback our business experiences to free software
|
|
43
|
-
|
|
44
|
-
# Lightning Talk Agenda
|
|
45
|
-
|
|
46
|
-
* Recall DebConf 2020 presentation
|
|
47
|
-
* The troublesome cases about bugs.d.o
|
|
48
|
-
* How to solve this situation?
|
|
49
|
-
* An experiment - fabre.debian.net
|
|
50
|
-
|
|
51
|
-
# Back to DebConf 2020
|
|
52
|
-
|
|
53
|
-
{:relative-height="100"}
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
# The troublesome cases about bugs.d.o
|
|
57
|
-
|
|
58
|
-
* Mainly package or maintainer oriented approach:
|
|
59
|
-
* <https://qa.debian.org/>
|
|
60
|
-
* <https://tracker.debian.org/>
|
|
61
|
-
* <https://udd.debian.org/dmd/>
|
|
62
|
-
|
|
63
|
-
* Not so easy cases: 🤔
|
|
64
|
-
* find only untouched bugs
|
|
65
|
-
* see blocked bugs at a glance 👀
|
|
66
|
-
|
|
67
|
-
# How to solve this situation?
|
|
68
|
-
|
|
69
|
-
* Mashup existing data + Simple front-end 💻
|
|
70
|
-
* E-mail archives (debian-bugs-dist,debian-bugs-closed) 📧
|
|
71
|
-
* UDD metadata (udd-mirror@udd-mirror.debian.net) 🖥
|
|
72
|
-
|
|
73
|
-
# An experiment - fabre.debian.net
|
|
74
|
-
|
|
75
|
-
* Concept
|
|
76
|
-
* *Make "unstable life" comfortable*
|
|
77
|
-
* Fix a bug (by finding a bug that no one working on)
|
|
78
|
-
* Triage a bug (by sending control E-mail easily)
|
|
79
|
-
* Avoid pitfall bugs (by finding affected important bugs)
|
|
80
|
-
|
|
81
|
-
# fabre.debian.net
|
|
82
|
-
|
|
83
|
-
{:relative-height="100"}
|
|
84
|
-
|
|
85
|
-
# View recently updated bugs
|
|
86
|
-
|
|
87
|
-
{:relative-height="100"}
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
# Focus on untouched bugs
|
|
91
|
-
|
|
92
|
-
{:relative-height="100"}
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
# Focus on blocked bugs
|
|
96
|
-
|
|
97
|
-
{:relative-height="100"}
|
|
98
|
-
|
|
99
|
-
# Updates since DebConf 2020
|
|
100
|
-
|
|
101
|
-
* Become a Debian Developer (September, 2020)
|
|
102
|
-
* Negotiated about <https://fabre.debian.net> subdomain with DSA (October, 2020)
|
|
103
|
-
* Got fabre.debian.net subdomain and deployed 🎉 (November, 2020)
|
|
104
|
-
|
|
105
|
-
# fabre.debian.net is sponsored by FOSSHOST
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
{:relative-height="80"}
|
|
109
|
-
|
|
110
|
-
* By migrating to <https://fosshost.org>, got more server resource! 🎉
|
|
111
|
-
|
|
112
|
-
# The next thing...
|
|
113
|
-
|
|
114
|
-
* Make things forward to beta:
|
|
115
|
-
* TODO: Implement cool full-text search feature
|
|
116
|
-
* TODO: Implement personalized search feature
|
data/presentation-memo.md
DELETED
|
@@ -1,322 +0,0 @@
|
|
|
1
|
-
# Presentation memo
|
|
2
|
-
|
|
3
|
-
Hi, thank you for coming to this session.
|
|
4
|
-
|
|
5
|
-
I'll start the presentation "An experiment about personalized
|
|
6
|
-
front-end of bugs.debian.org.
|
|
7
|
-
|
|
8
|
-
## NOTE
|
|
9
|
-
|
|
10
|
-
This slide was already published at Rabbit Slide Show
|
|
11
|
-
|
|
12
|
-
So, you can also download this presentation.
|
|
13
|
-
|
|
14
|
-
## Personal profile
|
|
15
|
-
|
|
16
|
-
Let me just start by introducing myself.
|
|
17
|
-
|
|
18
|
-
I'm one of the Debian maintainers. and a fan of a Trackpoint and Wasa
|
|
19
|
-
beef. I'm also working for ClearCode.
|
|
20
|
-
|
|
21
|
-
## ClearCode Inc.
|
|
22
|
-
|
|
23
|
-
Usually, I'm developing and supporting software as an engineer.
|
|
24
|
-
|
|
25
|
-
There is a culture to respect free software, my colleague gave me a
|
|
26
|
-
feedback for this talk.
|
|
27
|
-
|
|
28
|
-
## Not talk about
|
|
29
|
-
|
|
30
|
-
In this session, this presentation is related to bugs.debian.org, but
|
|
31
|
-
I will not talk about improving bugs.debian.org itself and internal
|
|
32
|
-
details.
|
|
33
|
-
|
|
34
|
-
# Agenda
|
|
35
|
-
|
|
36
|
-
Here is the session agenda.
|
|
37
|
-
|
|
38
|
-
First, I'll explain why so curious about bugs.d.o
|
|
39
|
-
and show you the troublesome case.
|
|
40
|
-
|
|
41
|
-
Next, I'll explain how to solve this situation and demonstrate an
|
|
42
|
-
actual front-end.
|
|
43
|
-
|
|
44
|
-
# We use bugs.d.o
|
|
45
|
-
|
|
46
|
-
Here is the screenshot of bugs.d.o.
|
|
47
|
-
|
|
48
|
-
I guess you are familiar with it.
|
|
49
|
-
|
|
50
|
-
# bugs.debian.org
|
|
51
|
-
|
|
52
|
-
In bugs.d.o, we need to follow the rules.
|
|
53
|
-
|
|
54
|
-
1. Communicate each other by E-mail
|
|
55
|
-
2. Change the bug status by sending E-mail
|
|
56
|
-
|
|
57
|
-
# Why so curious about bugs.d.o?
|
|
58
|
-
|
|
59
|
-
One day, I've received deprecated notification about growl-for-linux
|
|
60
|
-
package.
|
|
61
|
-
|
|
62
|
-
growl-for-linux is a notification software.
|
|
63
|
-
|
|
64
|
-
One is related to libappindicator and the other is related to
|
|
65
|
-
dbus-glib.
|
|
66
|
-
|
|
67
|
-
# How did you fixed?
|
|
68
|
-
|
|
69
|
-
About libappindicator, just migrated to libayatana-indicator.
|
|
70
|
-
|
|
71
|
-
# How did you fixed? (again)
|
|
72
|
-
|
|
73
|
-
About, dbus-glib, I need to fix changed interfaces and migrated into
|
|
74
|
-
GDBus.
|
|
75
|
-
|
|
76
|
-
# growl-for-linux was fixed
|
|
77
|
-
|
|
78
|
-
Two bugs about growl-for-linux package was fixed, but I thought what
|
|
79
|
-
about other packages?
|
|
80
|
-
|
|
81
|
-
# What about other packages?
|
|
82
|
-
|
|
83
|
-
libappindicator and dbus-glib was tracked like this.
|
|
84
|
-
|
|
85
|
-
# libappindicator: deprecated in Debian;
|
|
86
|
-
|
|
87
|
-
Against libappindicator, there are many bugs.
|
|
88
|
-
|
|
89
|
-
# libdbus-glib-1-dev: is deprecated
|
|
90
|
-
|
|
91
|
-
Against dbus-glib, there are too many blocked bugs.
|
|
92
|
-
|
|
93
|
-
# How to track many blocked?
|
|
94
|
-
|
|
95
|
-
In these case, we can use UserTags to track bugs.
|
|
96
|
-
|
|
97
|
-
# Does it work with libappindicator?
|
|
98
|
-
|
|
99
|
-
For libappindicator, ayatana-appindicator is used as UserTag
|
|
100
|
-
|
|
101
|
-
# Does it work with libdbus-glib1-dev?
|
|
102
|
-
|
|
103
|
-
It should be tagged... but, UserTag is not available for dbus-glib.
|
|
104
|
-
|
|
105
|
-
# The troublesome case about bugs.d.o
|
|
106
|
-
|
|
107
|
-
Like this, there is a case that UserTag is not always used. How to
|
|
108
|
-
solve this situation?
|
|
109
|
-
|
|
110
|
-
# Use udd.debian.org!
|
|
111
|
-
|
|
112
|
-
The answer is using udd.
|
|
113
|
-
UDD can track usertags and blocking bugs.
|
|
114
|
-
|
|
115
|
-
# In my experience, I need
|
|
116
|
-
|
|
117
|
-
So far, I've fixed or sent feedback to some bugs, I became to feel the
|
|
118
|
-
following ones are needed.
|
|
119
|
-
|
|
120
|
-
Tracking a specified bug
|
|
121
|
-
Finding a bug that no one working on
|
|
122
|
-
Sending control E-mail in required form
|
|
123
|
-
Finding affected bugs
|
|
124
|
-
|
|
125
|
-
# What I need for?
|
|
126
|
-
|
|
127
|
-
First topic is solved by using UDD.
|
|
128
|
-
|
|
129
|
-
But how about the rest issues?
|
|
130
|
-
|
|
131
|
-
# How to solve rest issues?
|
|
132
|
-
|
|
133
|
-
Surely, It is a good manner to fix a bug, but it is not easy.
|
|
134
|
-
It is also good to triage a bug, but it may be troublesome.
|
|
135
|
-
|
|
136
|
-
To know affected bugs are also important, but it is not so easy until
|
|
137
|
-
it hits you.
|
|
138
|
-
|
|
139
|
-
# Find affected bugs
|
|
140
|
-
|
|
141
|
-
In the past, there are some grave/critical bugs It had affected boot
|
|
142
|
-
sequence / logged in user session. I want to avoid these bugs.
|
|
143
|
-
|
|
144
|
-
# What about existing solution?
|
|
145
|
-
|
|
146
|
-
I've searched existing useful services via Debian wiki.
|
|
147
|
-
|
|
148
|
-
Developer Horizon seems well, but not available. Fabre also seems
|
|
149
|
-
well, but discontinued already.
|
|
150
|
-
|
|
151
|
-
I've also heard Debbugs Enhancement Suite. But it is a bit different
|
|
152
|
-
what I want.
|
|
153
|
-
|
|
154
|
-
# What about existing solution?
|
|
155
|
-
|
|
156
|
-
As a result, Debian Popularity Content and Public UDD Mirror seems
|
|
157
|
-
useful.
|
|
158
|
-
|
|
159
|
-
# Starting personal project
|
|
160
|
-
|
|
161
|
-
So I've started a personal project.
|
|
162
|
-
|
|
163
|
-
The concept of this project is: "Make unstable life comfortable" It
|
|
164
|
-
seems that it is ridiculous, but important for me.
|
|
165
|
-
|
|
166
|
-
# Starting personal project
|
|
167
|
-
|
|
168
|
-
To achieve this concept, I need to do some tasks.
|
|
169
|
-
|
|
170
|
-
counting comment for each bugs,
|
|
171
|
-
and adding separate mailto: link,
|
|
172
|
-
checking installed packages to alert affected bugs.
|
|
173
|
-
|
|
174
|
-
# How to realize concept
|
|
175
|
-
|
|
176
|
-
Furthermore, collecting E-mail archives, popcon data, installed
|
|
177
|
-
packages list and so on are also required.
|
|
178
|
-
|
|
179
|
-
# Collect bug information
|
|
180
|
-
|
|
181
|
-
To collect E-mail archives, we can use bugs-mirror with rsync. E-mail
|
|
182
|
-
archive contains *.log and *.summary.
|
|
183
|
-
|
|
184
|
-
# Extract .log and .summary
|
|
185
|
-
|
|
186
|
-
There are many Perl modules to handle bugs.d.o related pieces of
|
|
187
|
-
stuff.
|
|
188
|
-
|
|
189
|
-
# How to parse .log
|
|
190
|
-
|
|
191
|
-
For example, Log and MIME module is used to parse .log file.
|
|
192
|
-
|
|
193
|
-
# How to parse .summary
|
|
194
|
-
|
|
195
|
-
Status module is used to parse .summary file.
|
|
196
|
-
You can access these bugs's metadata.
|
|
197
|
-
|
|
198
|
-
# Collect Popcon data and so on
|
|
199
|
-
|
|
200
|
-
As UDD provides public database access,
|
|
201
|
-
|
|
202
|
-
So we can get popcon stats and investigate which bug affects unstable
|
|
203
|
-
or not.
|
|
204
|
-
|
|
205
|
-
# Collect installed packages information
|
|
206
|
-
|
|
207
|
-
As popularity-content command can collect installed binary packages
|
|
208
|
-
information. It is useful to check recently used packages.
|
|
209
|
-
|
|
210
|
-
# Process collected data and make it accessible!
|
|
211
|
-
|
|
212
|
-
After collecting these information, updating bug information is
|
|
213
|
-
required regularly.
|
|
214
|
-
|
|
215
|
-
I've used debian-bugs-dist mailing list as a trigger to
|
|
216
|
-
update and imported it into database.
|
|
217
|
-
|
|
218
|
-
# Prepared server specs for experiment
|
|
219
|
-
|
|
220
|
-
For my experiment, I've prepared small VPS instance.
|
|
221
|
-
|
|
222
|
-
# System diagrams
|
|
223
|
-
|
|
224
|
-
Here is a simple diagram for explaining the system.
|
|
225
|
-
|
|
226
|
-
Web server is nginx, Application server is puma, and backend database is Groonga.
|
|
227
|
-
|
|
228
|
-
It access external services,
|
|
229
|
-
E-mail server, UDD for metadata, Salsa for authentication.
|
|
230
|
-
|
|
231
|
-
# Named my project as Fabre
|
|
232
|
-
|
|
233
|
-
As diagram indicates,
|
|
234
|
-
I've named this personal system as Fabre.
|
|
235
|
-
|
|
236
|
-
# Why Fabre?
|
|
237
|
-
|
|
238
|
-
Fabre is famous by the study of insects.
|
|
239
|
-
I've borrowed from discontinued similar project in decades ago
|
|
240
|
-
|
|
241
|
-
# Concept of Fabre (again)
|
|
242
|
-
|
|
243
|
-
The concept is this project is Make "unstable life" comfortable.
|
|
244
|
-
|
|
245
|
-
# Finding a bug that no one working on
|
|
246
|
-
|
|
247
|
-
Here is the partial screenshot of Fabre.
|
|
248
|
-
It shows each number of comments (orange background color means no one working on yet)
|
|
249
|
-
|
|
250
|
-
# Sending control E-mail easily
|
|
251
|
-
|
|
252
|
-
I've added each mailto: button to sending control mail
|
|
253
|
-
|
|
254
|
-
# Easy to view blocked bugs
|
|
255
|
-
|
|
256
|
-
I've aligned blocked bugs.
|
|
257
|
-
|
|
258
|
-
# Finding affected important bugs
|
|
259
|
-
|
|
260
|
-
I've added a dashboard to show fire icon. It indicates that there are affected bugs.
|
|
261
|
-
|
|
262
|
-
# How Fabre is good enough to work?
|
|
263
|
-
|
|
264
|
-
I'll show you some demo about Fabre.
|
|
265
|
-
|
|
266
|
-
# Current status of Fabre
|
|
267
|
-
|
|
268
|
-
That's all about Fabre demonstration.
|
|
269
|
-
|
|
270
|
-
In this system, tracked bugs are reached to eighty-nine thousand.
|
|
271
|
-
UDD tracks 90 thousand bugs, so it covers most of them.
|
|
272
|
-
|
|
273
|
-
Currently, bug information is updated every 1 hour, and affected bugs are also updated every 1 day.
|
|
274
|
-
|
|
275
|
-
Disk usage is about 1.5 GiB.
|
|
276
|
-
|
|
277
|
-
# Weak point of Fabre
|
|
278
|
-
|
|
279
|
-
There is a one weak point about Fabre.
|
|
280
|
-
out of memory is occurred sometimes.
|
|
281
|
-
|
|
282
|
-
# Conclusion
|
|
283
|
-
|
|
284
|
-
* There is plenty room of improvement to develop, so I'll go forward this experiment furthermore.
|
|
285
|
-
* In my experiment, I've found that mashup some data sources may improve user experience.
|
|
286
|
-
|
|
287
|
-
# Any questions?
|
|
288
|
-
|
|
289
|
-
Could you speak slowly if you ask, please?
|
|
290
|
-
|
|
291
|
-
# DEMO
|
|
292
|
-
|
|
293
|
-
I'll demonstrate some features of Fabre.
|
|
294
|
-
|
|
295
|
-
If you already sign-in with salsa account,
|
|
296
|
-
You can also sign in with Fabre.
|
|
297
|
-
|
|
298
|
-
You need explicitly allow to authorize with Fabre.
|
|
299
|
-
|
|
300
|
-
After sign in, you can access the dashboard.
|
|
301
|
-
|
|
302
|
-
In the dashboard, you can see a status.
|
|
303
|
-
|
|
304
|
-
As you can see, there are three affected bugs,
|
|
305
|
-
ten bookmarked bugs, and you installed thousand and six hundred packages.
|
|
306
|
-
|
|
307
|
-
At the bottom of the dashboard, you can check the existence of newer comments since you commented finally.
|
|
308
|
-
|
|
309
|
-
Let's see the affected bugs.
|
|
310
|
-
These information is based on your installed packages.
|
|
311
|
-
|
|
312
|
-
Let's see the bookmarked bugs.
|
|
313
|
-
In every bug detail page, bookmark button is shown, so you can track bug freely.
|
|
314
|
-
|
|
315
|
-
You can see recent update bugs, release critical bugs, and newcomer bugs.
|
|
316
|
-
|
|
317
|
-
Here is the bug detail page,
|
|
318
|
-
|
|
319
|
-
You can view original bug report via clicking link,
|
|
320
|
-
tweet about bugs,
|
|
321
|
-
and send control E-mail easily.
|
|
322
|
-
|