Wednesday, September 17. 2008Whatever happened to Coverity?Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Coverity is dependent on the build system working; when our dependencies and/or build system change, they need to follow suit. I think the reason was that they didn't have enough people to track everything all the time.
Maybe someone needs to contact Stanford and tell them their $800,000 gift from DHS has run out?
I think that DHS stands for "U.S. Department of Homeland Security" (I found it in the wikipedia page you linked).
So I think he's telling that they spent all the money they got from the contract with the DHS.
This is the proprietary trap. They aren't profiting from you (you're just free advertising for them) so where's their incentive to put resources into ensuring continued compatibility with your build system? You could help them out by sending them patches -- oh wait, you can't do that... they're proprietary and closed!
Well at least it wasn't an SCM tool with all of your code locked up in it -- it's "merely" QA tools. Now that you realize you can't free ride forever with closed source, if there aren't any open, non-proprietary replacements on par with Coverity's offerings, find the closest thing and help make it better!
Their incentive in the first place was to get a bunch of people using their system who wouldn't have otherwise. And we have day jobs, so then we might buy it in our companies. That incentive didn't change.
Exactly my point; that was their initial incentive, that you would help spread their word.
So now they've grown (with the help of our tax dollars, no less!) where's their continued incentive? As a small project, you no longer bring them the level of market visibility they need to justify the level of support (in terms of continuous compatibility) they were devoting to you.
Just an idea, but if you're interested in receiving ongoing analysis, we'd be glad to help. Yes, we compete with Coverity. Yes, you might get different results from us than you were getting from them. Yes, we do this for other FOSS projects. No, we're not dependent on US Federal money (nor are they, to be fair).
If you'd like to take us up on this offer, please have one of the committers respond here or e-mail me directly, either works. Cheers, Gwyn Fisher CTO, Klocwork. gwyn-at-klocwork.com
Gwyn, thank you very much for your offer. In fact I've already had the pleasure to work with Klocwork on a different project, and we are looking forward to receiving an analysis for Amarok too.
We have already contacted Klocwork a few weeks ago, but your engineer apparently had problems with building Amarok 2. I will contact you soon via email.
Hi Mark,
We have been working on getting our new build servers set up. It has taken a while, but they're serving up builds now. KDE is 3rd from the top of my list of projects with build issues to get cleaned up, so you will start seeing regular builds again shortly. Re: DHS - the actual dollar figure Coverity received for the Open Source Hardening Project was a total of $300,000 for the three year effort. Despite the fact that those three years are almost at an end, we'll be continuing the program, and have acquired more hardware to run it on, and have a second full time person on the project as well - Erinn Clark from Debian. Hopefully that addresses some of Alex's concerns as well. -- David Maxwell Coverity Open Source Strategist http://scan.coverity.com/
David, thank you very much for the clarification. It's great to hear that Coverity is already working on the issue
|
Amarok LinksCalendar
QuicksearchCategoriesBlog Administration |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||