Re: [boost] How about a call for bug-fix volunteers?

Subject: Re: [boost] How about a call for bug-fix volunteers?
From: Krzysztof Czainski (1czajnik_at_[hidden])
Date: 2010-10-27 10:38:56

2010/10/26 Jim Bell <Jim_at_[hidden]>:
> Library authors shouldn't have to bear the burden of bug reports for
> their libraries alone. Even maintaining their regression tests across
> all platforms isn't realistic (and isn't being done).
>
> So what if we try to recruit a couple helpers for each library?
>
> I see two avenues where we can use some volunteer help to improve
> boost's quality.
>
> 1. Dandelion pickers: look at failed/yellow regression tests and try to
> fix them. Volunteers could pick a platform they have access to, and try
> to work across all libraries. You might be surprised at how easy many
> are to fix.
> 2. Ticket triage: pick a library and go through all open tickets. Change
> severity, resolve, request more information, try to map to an existing
> regression test, interact with the submitter in the comments. (I think
> Trac needs a "requesting more information" state.)  Even a brief
> 'triage' on each would be helpful, and help users feel they're being
> heard. (Trac needs to track this, too.)  Write new regressions from
> legitimate issues.
>
> Recruiting pitch: it's a great way to improve your
> skills--troubleshooting, C++, platform-specific expertise, communication.
>
> Not so glamorous, but important and great experience.
>
> Perhaps we could assign a little of each to each SoC person.
>
> Maybe put the word out on Slashdot.

I would like to try help ;-) I should be able to spend up to an hour a day.

I have two years of every-day C++ programming experience (with
attempts at template metaprogramming etc.).

My platforms are

1) Windows MinGW and msys, gcc -v:
Target: mingw32
Configured with: ../gcc-4.5.0/configure
--enable-languages=c,c++,ada,fortran,objc,obj-c++
--disable-sjlj-exceptions --with-dwarf2 --enable-shared
--enable-libgomp --disable-win32-registry --enable-libstdcxx-debug
--enable-version-specific-runtime-libs --disable-werror
--build=mingw32 --prefix=/mingw
Thread model: win32
gcc version 4.5.0 (GCC)

2) Linux (gentoo), gcc -v:
Target: x86_64-pc-linux-gnu
Configured with:
/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/gcc-4.4.4/configure
--prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.4.4
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.4/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.4.4
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.4.4/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.4.4/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.4/include/g++-v4
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu
--disable-altivec --disable-fixed-point --without-ppl --without-cloog
--enable-nls --without-included-gettext --with-system-zlib
--disable-werror --enable-secureplt --enable-multilib
--enable-libmudflap --disable-libssp --enable-libgomp
--with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.4.4/python
--enable-checking=release --disable-libgcj
--enable-languages=c,c++,fortran --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo
4.4.4-r2 p1.2, pie-0.4.5'
Thread model: posix
gcc version 4.4.4 (Gentoo 4.4.4-r2 p1.2, pie-0.4.5)

Regards,
Kris