From: Stephen W. <st...@ic...> - 2008-01-28 23:31:12
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This looks good. I should add that the assignee should arrange to monitor the PR if not already. If anybody wants to claim a bug report but is not in the drop-down list, that person can be added as a developer to the iverilog project on sourceforge. Cary R. wrote: > I believe we all agree that the "Assigned To" field should be used to > indicate ownership of a particular report. Here is some elaboration on > what I think this should signify and how other should interact with a > claimed report. > > 1. The "Assigned To" person is responsible for submitting the patch and > updated test code if the original is inadequate or missing. > > 2. A claimed patch should be something you plan to actively work on within > the next week. If for some reason your plans change you should change the > "Assigned To:" field back to None or at least add a comment stating that > you are being delayed for a SPECIFIED amount of time. > > 3. If you want to help out on a claimed patch you should contact the > person who claimed the patch originally. This allows both parties to know > where the other is in tracking down and fixing the problem. I believe this > communication should not be over the iverilog-devel list. I think that conversations in the comments of the PR should certainly be avoided, but I wouldn't necessarily keep it off the iverilog-devel list. Conversations like "What is your schedule?" or "Can I help?" can be kept point-to-point, but technical discussions amongst those who choose to collaborate (or critique) on a PR fix make good sense for the iverilog-devel list. Preserving the lore may prove useful in unanticipated ways. > 4. Ownership can be given to a different person, but it should normally > only be taken if a reasonable effort (email AND a post to the report) > fails to generate a reply in one week. Obviously for bugs that are or > become critical some flexibility is required. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHnmXErPt1Sc2b3ikRAkReAJ0YI/i7Z9ipEgyn2qv97u2XDrlbnwCfTbuM qylWCQJnyEAuxSsVUU6JPIo= =6i4p -----END PGP SIGNATURE----- |