diff options
| -rw-r--r-- | Distrib/DebianIntegrationDeveloper.mdwn | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/Distrib/DebianIntegrationDeveloper.mdwn b/Distrib/DebianIntegrationDeveloper.mdwn new file mode 100644 index 00000000..85ac97c8 --- /dev/null +++ b/Distrib/DebianIntegrationDeveloper.mdwn @@ -0,0 +1,15 @@ +Currently, the [Debian](http://www.debian.org) Project consists of two distinct classes of people - Users and Developers. There is a [Quality Assurance](http://qa.debian.org) group that exists to try to help bridge this gap, however it is not as strong as some people would like it to be. In many ways, a DID is another name for what Debian currently classifies as QA. + +A Debian Integration Developer (DID) is a middle-person, someone to assist users and developers. From a \[[]\[user]] perspective they answer, categorize and enhance bug reports with patches or Policy suggestions. From a [developer](http://www.debian.org/devel/) perspective they update Debian specific package defaults and configuration systems. + +Besides these two perspectives, there is also a range of tasks that fall into the domain of other "Quality Assurance." Tasks necessary to perform on a range of individual packages such as Policy compliance checking, debconf use, /etc/alternatives and similar debian configuration mechanisms that integrate. The Work Needed and Prospective Packages system is an important function. Questions are sometimes raised regarding the diligence or MIA status of developers, in a way, ensuring the overall quality of the debian operational infrastructure. Gathering feedback from users and developers regarding enhancements and changes to these systems. Helping to Integrate the various infrastructure groups when responding to the environment in which Debian resides in is raising the quality of the organization. + +The more I write and think about this area, the more clearly the concept of idealistic leadership is brought to mind. Yet keys to the success of Debian can be directly attributed to the lack of a centralized organizational structure and a strong set of negotiated policies. + +Software dependencies can be very complex. There is often a need for a semi-knowledgable developer (DID or QA) to understand how things work best in a coordinated manner, how best to Integrate. + +I believe there is currently a sizable sub-set of the Developer community that already provides this function but is not recognized for the significant of their contribution. + +Perhaps a little bit of this resides in all members of the Debian community and is an important ingredient to the project's overall success. This may be because the developers are in fact, also the users. This can be extremely demanding for new users to come up to speed with what Debian is about [who participates](http://www.debian.org/intro/organization) to keep it running as it does. The [pseudo-package list](http://www.debian.org/Bugs/pseudo-packages) may give great insight into some critical areas of debian and how responsibility is divided up. + +-- [[Main/GrantBow]] - 25 Feb 2004 |