Can newbies come along? I would like to learn more programming and don't know where to expand beyond the "hello world" stage. Jason On Wed, 2004-03-10 at 14:53, Chad Walstrom wrote: > A question was posed by some of the people who will be attending the > TCLUG BSP on Saturday on what type of general information they would > need for the event. So, here you go: > > GENERAL BUGS > ============ > Most software packages have some sort of bug tracking software > associated with their respective projects. Information can usually be > found in the README or similar document for the package itself. For > example, projects hosted at Source Forge have bug reports published for > all to see. The best way to approach this might be to join the > developer's email list or send email to the software author(s) and ask > what type of help you could provide. You don't want to work on a bug > that might already be fixed in some development branch of the software. > > Another tip that is helpful is to check out the upstream CVS and inspect > the log files for yourself. In any case, communication is the key. Let > the developers of the software know you're going to put some time in to > solving Problem X or Y. > > DEBIAN BUGS > =========== > For every package that Debian distributes, a corresponding bug tracking > category is created. Debian's Release Critical (RC) bugs are those with > a severity greater than "Normal", which includes "Important", "Grave", > and "Critical". Debian bug and RC bugs can be found at the following > URIs: > > http://bugs.debian.org/ > http://bugs.debian.org/release-critical/ > > A list of QA chosen Bug Squashing Party bugs are here: > > http://bugs.qa.debian.org/ > > The Debian Quality Assurance page holds more general info and reference > links to different types of bugs and help that is needed: > > http://qa.debian.org/ > > For example, there is a link for bugs labeled "help" at > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=help > > For bugs that we want to squash, the Release Manager, Anthony Towns, > announced[1] a special little CGI program for claiming bugs. > > 1. http://lists.debian.org/debian-devel-announce/2003/debian-devel-announce-200308/msg00010.html > > To help coordinate RC bug fixing and BSPs, you can make use of the > "BugSquash Claims" page, at: > > http://bugs.debian.org/cgi-bin/claims.cgi > > It's populated by creating files in > > master:/org/bugs.debian.org/bugsquash/claims/ > > named after your username @debian.org, and entering one bug number > per line. Developers who're participating in the BSP should enter > the bugs they're working on into there, and might like to check to > see if anyone else has "claimed" the bug to avoid duplication of > work. Once you've got the bug patched and NMUed, it'll remain on the > page for a while, for bragging rights. Also interesting might be > urls such as: > > http://bugs.debian.org/cgi-bin/claims.cgi?include=ajt@d.o > http://bugs.debian.org/cgi-bin/claims.cgi?exclude=pending,fixed > > Remember, we're not prospecting for gold here: claims are advisory > only; if you really want to fix a bug, and can't seem to get a hold > of whoever's got a claim, don't worry about it -- fix the bug > yourself, and mail your findings to the bug report. If you want to > do duplicate work, that's your business. > > There will be at least two Debian Developers at the BSP, myself and Ken. > We can sponsor any bugs that you might want to work on and participate > in the BugSquash Claims page (if it's still up). > > Well, I hope that helped people a little. _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list