Здравствуйте, Maxim S. Shatskih, Вы писали:

СО>>Хмм... Проект Eclipse, как пример открытого ПО (как я понимаю, "для души" это то что

MSS>Это коммерческий продукт крупной компании, розданной в open source.

Тогда про Linux:
Kernel Summit 2005: Development process and quality assurance
"There are currently two problems, according to Andrew (Linux kernel maintainer Andrew Morton):

Many subsystems are waiting too long to merge their changes into the mainline, with the result that they miss many weeks of testing time. Getting those changes in sooner could help testers find some of the bugs which have been slipping through into the stable releases.

The kernel developers are simply not fixing bugs, even after they have been found. According to Andrew, we have to try harder, to be more diligent. "

Другой комментарий (можно на него найти ссылку здесь)
"Linux: 2.6.13-rc4, Improved Development Process
Posted by Jeremy on Friday, July 29, 2005 — 06:03

Back from the 2005 Linux Kernel Developers' Summit, Linus Torvalds released the 2.6.13-rc4 kernel. Linus noted that the improved development process discussed at the recent summit will begin after the upcoming release of the 2.6.13 kernel, "which is hopefully not too far away." The general idea of the new process, which improves upon last year's development model [story], is to require that all major merges happen within two weeks of a stable kernel release. All the rest of the time between releases should then be spent on fixing bugs. Linus summarized:

"So if you have a favourite kernel developer, please wake him up with a friendly kick to the head and explain this concept to him in small easy-to-understand words, and tell him that we're in the freeze process for 2.6.13 now, and that he should be gathering up the patches, and make sure they get to me _after_ 2.6.13 is out, but at that point do it in a timely manner."

И снова Линус:
Torvalds: How to Keep Linux Kernel on Course

и снова он:
"Torvalds ... is also proud of the formal tracking process he and Morton established to better manage updates and fixes to the kernel. Still, he keeps a healthy distance from the legal and business issues, says Stuart Cohen, CEO of the OSDL. "

С уважением,
Сергей

P.S. а вот если не брать ядро — может быть текущее состояние соотв. процесса разработки остальной функциональности Linux и является причиной столь часто пересекающихся фич в различных утилитах и модулях? Простой пример — почему настройка работы с раскладкой существует и на уровне XFree и на уровне десктопов? (приводящая в определенных случаях к конфликтам — например между xkb и kbd)

Здравствуйте, Gaperton, Вы писали:


G>В Москве контор, которые соответствуют CMM3 — по пальцам перечесть, а насчет СММ5 мы, наверное, единственные, да и то — мы сертификацию не проходили (хоть ключевым требованиям и удовлетворяли),


Luxoft — CMMI 5
http://www.pressroom.ru/?ID=458614&PRID=23718

к сожалению пока с PSP не знаком, но скажу спасибо за подсказку для исправления своего незнания (:

Здравствуйте, Orin.i9, Вы писали:

OI>Luxoft — CMMI 5
OI>http://www.pressroom.ru/?ID=458614&PRID=23718
Круто, молодцы они.

OI>к сожалению пока с PSP не знаком, но скажу спасибо за подсказку для исправления своего незнания (:
http://www.sei.cmu.edu/tsp/tsp.html

Здравствуйте, Orin.i9, Вы писали:

OI>к сожалению пока с PSP не знаком, но скажу спасибо за подсказку для исправления своего незнания (:
Еще:

Главная страница PSP/TSP

Отношение PSP/TSP к CMM

CMM and PSP
In the late 1980s and early 1990s the SEI developed the Capability Maturity Model (CMM) which captured organizational best practices for software development. SEI Fellow Watts Humphrey decided to apply the underlying principles of the CMM to the software development practices of a single developer. The result of this effort was the Personal Software Process (PSP), designed to be a CMM level 5 process for individual software developers.

CMM and TSP
It soon became obvious that, while excellent results were possible using the PSP, it was almost impossible to maintain the discipline required for PSP practices if the surrounding environment did not encourage and demand them. Humphrey then developed the Team Software Process (TSP) for the smallest operational unit in most organizations, the project team. TSP was designed to be a CMM level 5 process for project teams. Recent results of using the TSP to achieve world-class quality levels while meeting cost and schedule estimates are documented in an SEI technical report.