You are not logged in.
Pages: 1
Stumbled on this while searching the wiki...... Do we still have this ?? Or is it dead? Or is it that we dont have enough bugs? Or enough volunteers??? Or is it just useless?
Offline
Stumbled on this while searching the wiki...... Do we still have this ?? Or is it dead? Or is it that we dont have enough bugs? Or enough volunteers??? Or is it just useless?
If it is dead, I give you my full mental support to resurrect it ![]()
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Same here
Although it'll be tough, since that would be tomorrow, and everyone's scrambling to release 2009.01 today...
Offline
@Ranguvar..... Dude...see the glass half full...we have more than a month ahead of us to plan for it ![]()
Offline
They got the url wrong.. it's not http://bugs.archlinux.org/index.php?project=1, it's http://bugs.archlinux.org/index.php?project=6 ![]()
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
@Ranguvar..... Dude...see the glass half full...we have more than a month ahead of us to plan for it
Whoops, miscalculated dates.
Still, there's only two days left if we're gonna make 2009.01, and then the next Sunday is the 1st of February. More than a month? Technically only ![]()
Unless we want to wait until March... a Bug Squashing Day sounds good though, will all the recent chaos (2.6.28, ext4, AMD/ATI drivers, KDE 4.2 / NVIDIA drivers, Intel driver chaos coming with 2.6.29 and GEM...)
Offline
That came up recently among the devs. Everyone seemed to be in favor but nothing was decided yet. We'll make an announcement if we decide to do one.
Offline
People can help out get prepared for a bug day by going through the bug tracker and adding bug with fixes of bugs whose fixes are trivial to this page: http://wiki.archlinux.org/index.php/Bug_Day_TODO
Or is it that we dont have enough bugs?
Definitely enough bugs... I remember when the bug track had less that 400 only about 1 year ago.
Offline
sadly, sundays are when freegeek/chicago is open, or i'd be totally down.
[23:00:16] dr_kludge | i want to invent an olfactory human-computer interface, integrate it into the web standards, then produce my own forked browser.
[23:00:32] dr_kludge | can you guess what i'd call it?
[23:01:16] dr_kludge | nosilla.
[23:01:32] dr_kludge | i really should be going to bed. i'm giggling madly about that.
Offline
sadly, sundays are when freegeek/chicago is open, or i'd be totally down.
[bump] You're getting a Free Geek in your area? Sweet! I'm applying yet again for Portland's. [/bump]
Offline
I should also add that anybody can have their own mini bug day at any time they want. It is easy:
1. Look at bugs in the bug tracker. Old bugs or low priority bugs probably get less attention from devs these days so they may be a good place to start. You might also want to search for bugs from your favourite piece of software for that extra bit of motivation.
2. Can you replicate the bug? Especially check if the software involved has been updated as the bug may be silently fixed. Post and successes/failures in replicating. However, do not clutter the bug tracker if it has already been repeatedly replicated...
3. Can you find a patch to fix the issue? Google, upstream and other distros are good places to look. Post links to relevant discussions on how to fix the issue. Posting a patch without providing its source requires more work from the dev to check the patch does not have any unwanted consequences.
4. If you find a patch, adjust the PKGBUILD and test. Post the updated PKGBUILD and patch files to the bug tracker. Add the bug to the Bug Day TODO page with a fix provided tag.
5. If someone else has posted a fix and you can replicate the bug, confirm the fix works. Report success or failure.
Each bit of work the community does in the bug tracker gives the devs more time to update and improve Arch.
As a challenge, my record for number of bug reports requested to be closed in one day is somewhere in the high twenties.
Offline
I just finished browsing a part of the flyspray. There are quite a few bugs which have been requested to be closed but noone has closed. I know theres at least 3 i have done so, but noticed others too.
Also from 27 pages of bugs in Arch Linux project 16 are marked as low severity. For those who like statistics.
Last edited by dolby (2009-02-01 09:35:49)
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
I should also add that anybody can have their own mini bug day at any time they want. It is easy:
<snip>
Wiki request ![]()
Offline
Also someone should reassign all bugs assigned to Damir Perisa, Travis Willard & Alexander Baldeck. Although the last one is still listed as an Archlinux developer, i dont think he works on anythng other than PPC.
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
kludge wrote:sadly, sundays are when freegeek/chicago is open, or i'd be totally down.
[bump] You're getting a Free Geek in your area? Sweet! I'm applying yet again for Portland's. [/bump]
at the risk of high-jacking the thread, we've had one in chicago for, oh, geez, three years and change. we're a lot smaller and lower-fi than pdx, but we're getting there. just today, i was tyring to figure out how to make three old, icandy laptops work, and my first thought was, "isn't there an arch ppc?"
[23:00:16] dr_kludge | i want to invent an olfactory human-computer interface, integrate it into the web standards, then produce my own forked browser.
[23:00:32] dr_kludge | can you guess what i'd call it?
[23:01:16] dr_kludge | nosilla.
[23:01:32] dr_kludge | i really should be going to bed. i'm giggling madly about that.
Offline
Also someone should reassign all bugs assigned to Damir Perisa, Travis Willard & Alexander Baldeck. Although the last one is still listed as an Archlinux developer, i dont think he works on anythng other than PPC.
I went through these and reassigned the bugs to the current maintainer. I didn't touched the bugs for orphaned packages or for packages they still own (Alexander Baldeck).
Offline
At least those has to be reassigned as well. I left a msg for Daenyth in some report but he assigned them to the wrong people
http://bugs.archlinux.org/task/11012 => tpowa
http://bugs.archlinux.org/task/9425 => thayer
http://bugs.archlinux.org/task/10566 => tpowa
http://bugs.archlinux.org/task/10558 => dsa
http://bugs.archlinux.org/task/10515 => dsa
http://bugs.archlinux.org/task/9589 => thayer
Thanks in advance to the one who fixes them ![]()
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
BTW in my opinion it would be preferable having a "Taking Care of Orphans in extra day" instead of a Bug Squashing one. At least when it comes to the developers. Theres quite a lot of them.
The bugs in the bug tracker are mostly related to a) mkinitcpio,klibc and packages in base, b) website feature requests c) upstream d) solved in next rebuild & e) fixed but not closed yet
Last edited by dolby (2009-02-02 07:35:37)
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
At least those has to be reassigned as well. I left a msg for Daenyth in some report but he assigned them to the wrong people
http://bugs.archlinux.org/task/11012 => tpowa
http://bugs.archlinux.org/task/9425 => thayer
http://bugs.archlinux.org/task/10566 => tpowa
http://bugs.archlinux.org/task/10558 => dsa
http://bugs.archlinux.org/task/10515 => dsa
http://bugs.archlinux.org/task/9589 => thayerThanks in advance to the one who fixes them
done.
Offline
BTW in my opinion it would be preferable having a "Taking Care of Orphans in extra day" instead of a Bug Squashing one. At least when it comes to the developers. Theres quite a lot of them.
A couple of weeks ago, we removed the very low popularity orphans. Ther's still a lot remaining. I think it would be better to wait a bit. The community repo is supposed to switch to the main repo tools. Once that'll be done, moving a package from extra to community repo (if a TU wants to maintain it) would be a breeze. Right now it's more work. The orphans and bugs are both important.
Offline
Thanks for taking care of the reassignments.
As far as orphans i only said that cause i consider those much more important than the bugs. After all some of the bug reports are about them.
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
Pages: 1