Sha256: 835000d8d412b5853e30f6a3363cf6304a3e4d6509bbaabdb1cb34c289843644
Contents?: true
Size: 1.11 KB
Versions: 1
Compression:
Stored size: 1.11 KB
Contents
An experiment about personalized front-end of bugs.debian.org ### An experiment about personalized front-end of bugs.debian.org 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, udd.debian.org, or qa.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. #### References * "An experiment about personalized front-end of bugs.debian.org" https://slide.rabbit-shocker.org/authors/kenhys/debconf2020-online/
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
rabbit-slide-kenhys-debconf2020-online-2020.08.25.3 | cfp.md |