Guenter, I agree 100% on the "false bug reports" issue you point out. I happen to have a nice one in the jpeg core page which says "your thing is not working at all"... Not to mention some bug reports in other cores which are plain publicity completely off-topic . I emailed Damjan about it some time ago and he told me there is no utility to directly delete bug reports (it should be done straight into the MySQL database). Anybody fed up with prank bug reports who can add to this subject? Regards, Victor ----Mensaje original---- De: dannoritzer at web.de Fecha: 06/03/2007 21:48 Para: "Discussion list about free open source IP cores"cores at opencores.org> Asunto: Re: [oc] plz give me the verilog code of USART Victor, I agree with what you are saying. However, there had been a discussion here some time ago about switching the mailing list to a managed one, so that people have to review each post before it reaches the mailing list. If I remember right, it never came to the point that anybody volunteered to do that. There is another issue about what you are talking about. Once in a while I look into what projects got updated recently. For example, now the AVR project is in that list at the opencores front page. If you try to figure out what got updated, you will find that it is the bug tracker and someone filed a bug report that there is no source code in CVS. I even found "plz send code" entries in bug trackers that requested code for a total different project. Talking about improvements to opencores, I have another one. I would suggest some policy when dead projects get deleted. Now I understand that if there is some source code available that it might be good to just keep that. But there are projects that are 5 years and older and after creation they never got updated or never left the stage of the initial project template. Take the so often [*] project: http://www.opencores.org/projects.cgi/web/mp3decoder/overview Created, updated the next day and that was it. Ok, that one is not over 5 years old, but even here it could probably fall under the deletion policy. Just some thoughts. Cheers, Guenter [*] I tried to avoid the name to avoid "plz send the code" emails :) _______________________________________________ http://www.opencores.org/mailman/listinfo/cores -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.opencores.org/forums.cgi/cores/attachments/20070307/05e914a4/attachment.htm

Víctor López wrote:
Now, I don't know the exact work flow for a ticket on opencores, but usually with ticket systems there is an option to reject a ticket. Which should at least make it not show up by default anymore. Another issue has to do with project maintenance: http://www.opencores.org/faq.cgi/section/6/6.6#6.6 Every project has a bug tracker, even though it might not be maintained anymore. No one who leaves really says I don't want to maintain my project anymore. People just leave without saying goodbye. So what happens is the bug tracker is there, even open for public submission, but no one cares about those bug reports. But they affect the overall site, because they suggest there was an updated to the project. One idea would be to have some verification going on, that disables the bug tracker for a project and maybe even switches it to the status un-maintained. It could go like this. If the project maintainer has not signed in to opencores for more than a year, an automatic email verifies whether the email address still works. The project maintainer needs to reply on that email and the status is still kept. If not, the bug tracker will be disabled and the project status changes to un-maintained. Cheers, Guenter

Sounds like a good idea. Does anyone see a problem with this scheme? A simpler thing to implement would be that a maintainer can delete an entry. regards Damjan Another issue has to do with project maintenance: http://www.opencores.org/faq.cgi/section/6/6.6#6.6 Every project has a bug tracker, even though it might not be maintained anymore. No one who leaves really says I don't want to maintain my project anymore. People just leave without saying goodbye. So what happens is the bug tracker is there, even open for public submission, but no one cares about those bug reports. But they affect the overall site, because they suggest there was an updated to the project. One idea would be to have some verification going on, that disables the bug tracker for a project and maybe even switches it to the status un-maintained. It could go like this. If the project maintainer has not signed in to opencores for more than a year, an automatic email verifies whether the email address still works. The project maintainer needs to reply on that email and the status is still kept. If not, the bug tracker will be disabled and the project status changes to un-maintained. Cheers, Guenter _______________________________________________ http://www.opencores.org/mailman/listinfo/cores

Do you mean 'real' login to keep it in status maintained or is CVS upload also considered login. I myself use the CVS, but do not login - at the moment no reason to do it. Martin ----- Original Message ----- From: "Damjan Lampret" damjanl at opencores.org> To: "Discussion list about free open source IP cores" cores at opencores.org> Sent: Wednesday, March 07, 2007 11:45 AM Subject: Re: [oc] False bug reports on cores

Maybe: assign active = web_login || cvs_login; regards Damjan ----- Original Message ----- From: "Martin Schoeberl" martin at jopdesign.com> To: "Discussion list about free open source IP cores" cores at opencores.org> Sent: Wednesday, March 07, 2007 12:09 PM Subject: Re: [oc] False bug reports on cores

Damjan Lampret wrote:


That is good idea. And a final email would still allow for someone not
logging in frequent to keep up its status.

Concerning old dead and empty projects, I would volunteer to compile a
list of links and post it here, if there is interest in deleting or
discussing about deleting them.

Cheers,

Guenter

----- Original Message ----- From: "Günter Dannoritzer" dannoritzer at web.de> To: "Discussion list about free open source IP cores" cores at opencores.org> Sent: Wednesday, March 07, 2007 1:49 PM Subject: Re: [oc] False bug reports on cores

Sounds good :)

regards
Damjan

I vote on this one. Damjan, is there a way we can contribute to better the site in our spare time? Regards, Victor ----Mensaje original---- De: damjanl at opencores.org Fecha: 07/03/2007 11:45 Para: "Discussion list about free open source IP cores" Asunto: Re: [oc] False bug reports on cores Sounds like a good idea. Does anyone see a problem with this scheme? A simpler thing to implement would be that a maintainer can delete an entry. regards Damjan Another issue has to do with project maintenance: http://www.opencores.org/faq.cgi/section/6/6.6#6.6 Every project has a bug tracker, even though it might not be maintained anymore. No one who leaves really says I don't want to maintain my project anymore. People just leave without saying goodbye. So what happens is the bug tracker is there, even open for public submission, but no one cares about those bug reports. But they affect the overall site, because they suggest there was an updated to the project. One idea would be to have some verification going on, that disables the bug tracker for a project and maybe even switches it to the status un-maintained. It could go like this. If the project maintainer has not signed in to opencores for more than a year, an automatic email verifies whether the email address still works. The project maintainer needs to reply on that email and the status is still kept. If not, the bug tracker will be disabled and the project status changes to un-maintained. Cheers, Guenter _______________________________________________ http://www.opencores.org/mailman/listinfo/cores _______________________________________________ http://www.opencores.org/mailman/listinfo/cores -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.opencores.org/forums.cgi/cores/attachments/20070307/f24dd9c6/attachment.htm