-
Es scheint gar nicht so einfach zu sein, einen Patch in den Linux Kernel zu bekommen
Autor: Vertex 10.06.15 - 20:22
Hier hat das mal jemand versucht und berichtet: http://dirkriehle.com/uploads/byhand/theses/2012/holger_macht_studienarbeit.pdf
As a whole, the feature submission failed, because it was not possible to include all
the required changes in all target projects in time. The failure has two main reasons:
First, it is caused by technical problems which could occur in every software project, and thus not related to open source processes in particular. Second, and more relevant for this research, delays occurred due to common obstacles one has to face in the individual open source development processes. Individuals cannot put as much pressure as they like on the projects and are kind of at their mercy.
As an overall outcome, trying to include a new feature in different open source projects depending on each other is possible, however, unpredictable to a certain extent. The open source community has its own rules and processes, companies or other contributors cannot rely on being able to influence in whatever way they want.
The advancements heavily depend on the relevant community and project members and thus the process involved.
Conclusion: When submitting patches, always expect another iteration. -
Re: Es scheint gar nicht so einfach zu sein, einen Patch in den Linux Kernel zu bekommen
Autor: Nugget32 11.06.15 - 08:33
Vertex schrieb:
--------------------------------------------------------------------------------
> Hier hat das mal jemand versucht und berichtet: dirkriehle.com
>
> As a whole, the feature submission failed, because it was not possible to
> include all
> the required changes in all target projects in time. The failure has two
> main reasons:
> First, it is caused by technical problems which could occur in every
> software project, and thus not related to open source processes in
> particular. Second, and more relevant for this research, delays occurred
> due to common obstacles one has to face in the individual open source
> development processes. Individuals cannot put as much pressure as they
> like on the projects and are kind of at their mercy.
> As an overall outcome, trying to include a new feature in different open
> source projects depending on each other is possible, however,
> unpredictable to a certain extent. The open source community has its own
> rules and processes, companies or other contributors cannot rely on being
> able to influence in whatever way they want.
> The advancements heavily depend on the relevant community and project
> members and thus the process involved.
> Conclusion: When submitting patches, always expect another iteration.
Das Zeigt auch das viele Hersteller versuchen eigene Wege zu gehen ,aber das ist generell zum scheitern Verurteilt wenn man die Regeln und Richtlinien die jetzt schon estehen , Ignoriert.
Man kann die Mehrheit nicht zu etwas zwingen was Sie nicht will. Entweder halten sich die Hersteller an die Regeln oder Sie lassen es ,müssen Einbußen im Umsatz Hinehmen und anderen den vorlauf lassen. Oder Sie akzeptieren es ,Entwickeln mit den vorgaben und können sich am Umsatz erfreuen wenn Leute dann ihre Hardware kaufen. Für welchen Weg sich die entwickler in den jeweilligen Firmen sich entcheiden ist jedem selbst Überlassen.



