From mint-bounce@lists.fishpool.fi Mon Dec 21 16:36:32 2009 X-Authority-Analysis: v=1.0 c=1 a=yQCb1FHEAAAA:8 a=RoKlbr57_zDWEQtx6JEA:9 a=31YWjVod9mqw5JAHRPQA:7 a=P0xg4ISyp4YoftjeAVd1dId5ra0A:4 a=Vj4bdtAgx4AA:10 a=yNZQEwSNmWxPnnvx:21 a=RyiMx0SUHkRi30bF:21 Message-ID: <4B2FE9F4.8070409@charter.net> Date: Mon, 21 Dec 2009 16:34:44 -0500 From: Rob Mahlert User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "mint@lists.fishpool.fi" Subject: Re: [MiNT] Bugtracker References: <1472E2BC2F174EEA94B8AC698BEABC39@mercatus.local> <4B2FB6ED.4020409@charter.net> <4B2FDE8E.6080907@online.no> In-Reply-To: <4B2FDE8E.6080907@online.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: rmahlert@charter.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Jo Even Skarstein wrote: > Rob Mahlert skreiv: > >>> 1. There must be atleast one person that keeps track of what's >>> happening, someone to make sure that cases are closed when they >>> should be etc. Right now there are lots of cases that should have >>> been closed, which makes the situation look worse than it is. There >>> are also some very old cases which are worthless by now. >> A few have permission to do this.. if they don't, let me know and >> I'll make sure they do. You know who you are when you log onto it, >> just e-mail me and I can update the accounts. > > Well, they don't ;-) And I don't think the people that are actually > fixing bugs are using the bugtracker that much either. I found several > cases today that I know have been fixed, but the people who has done > the fixes has not resolved the cases. Integration between cvs and the > bugtracker would help here. > Like I said.. if anyone needs it.. just let me know. I just recently (last month?) updated Alan and Vincent to manager level so they can close bugs. If someone else needs it.. just let me know. >>> 2. It must be very easy for the average user to report bugs. Either >>> through email or a simple form that does not require registration. >>> The reporter must get feedback about the status of the bugreport. >> SPAMMERS and hackers! To protect the system, I have to keep the >> registrations and even that is not enough! The server was hacked in the > > Then Mantis must be very vulnerable if it can be hacked by receiving > an email with attachments. it was an OLD version.. they have patched the security issue. It was my fault for not updating the script in a few years. I really didn't enjoy the letter from the US Department of Defense!!! And it was uploading attachments to the bug report. > > At work we're using FogBugz both internally and also as a support > system to out customers. Everybody can send a mail to FogBugz, yet > spam is not a problem at all. The spamfilter takes care of this. > > If ordinary users has to either subscribe to the mailing list or ask > for a bugtracker-account just to report a bug, then it won't be done. > Without simple, anonymous bug-reporting the value of the bugtracker is > limited. > All that's needed is a valid e-mail account to register.. it's not that hard. I can understand viewing the bugtracker and when I find the config line to allow that, I'll switch it on. I did look at >>> 3. The roadmap-feature must be used. >> This is for Frank to decide or if enough agree.. but who will >> maintain it?? > > There must of course be a project manager. Either a single person or a > team. > >>> 4. The CVS integration must be used. >> Same as above.. for Frank. > > So what do you say Frank? Integration with CVS makes it much easier to > track bugs, especially when some newcomer needs to figure out what the > hell happened three years ago. > Is this an add-on for mantis? Looking quickly in the config file I see nothing about this.. but it's a LONG config file! >>> 5. Attachments must be allowed in both anonymous (screenshots, logs >>> etc) and registered bug-reports. Then patches can be submitted to >>> the relevant case if the developer does not have CVS write access. >> Maybe for registered.. but NEVER anonymous! They are already trying >> to hack into the system. > > Then there must be a more robust tool than Mantis. Teams all over the > world are doing these kinds of things, so it must be possible? > I can see for registered users turning this on. >>> 6. The routines regarding development, patching, bugtracking etc >>> must be documented and the documents must be easily obtained. >>> >> If someone wants to write it.. it can be easily placed on the >> sparemint.org website. Which if you have CVS write access.. you can >> update the site. > > Not many have CVS write access. Anyway, the sparemint website would > benefit from an update. Using a wiki and having a team of editors > would make the web-site much more dynamic and easily maintained. > Well.. we had a wiki on HighWire that was never used. So, I turned it off. I used MediaWiki for that. I have no problem installing a wiki for SpareMiNT.. but who will maintain it and administer it?