diff options
| -rw-r--r-- | Distrib/DebianIntegrationDeveloper.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Distrib/DebianIntegrationDeveloper.mdwn b/Distrib/DebianIntegrationDeveloper.mdwn index 0c3b1c72..8b34cb7b 100644 --- a/Distrib/DebianIntegrationDeveloper.mdwn +++ b/Distrib/DebianIntegrationDeveloper.mdwn @@ -8,7 +8,7 @@ The more I write and think about this area, the more clearly the concept of idea 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. This is also a natural path from which to recruit new package maintainers if assistance is provided along the way. Another separate group that subscribe to a [mail list](http://lists.debian.org) and perform this extremely valuable service is [Debian-Mentors](http://lists.debian.org/debian-mentors/). -Recognition for the significance of contribution is one reason to give this group of helpful people more courage and identity in helping the Debian project in a clearly defined and less daunting a way. The [devel](http://www.debian.org/devel) page has a link to a page describing [how you can help](http://www.debian.org/devel/join/). However this page is primarily positioned and recognized as a stepping stone into the [new maintainer process](http://www.debian.org/devel/join/). +Recognition for the significance of contribution is one reason to give this group of helpful people more courage and identity in helping the Debian project in a clearly defined and less daunting a way. The [devel](http://www.debian.org/devel) page has relevant links. There is a page describing [how you can help](http://www.debian.org/devel/join/), but (indicating the mentality) it's simply a link to the same page as the first step in the [new maintainer process](http://www.debian.org/devel/join/). Behind this first page is the real [new maintainer page](http://www.debian.org/devel/join/newmaint). There's also a [TODO list](http://www.debian.org/devel/todo/) but it's very very broad. 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 of Debian. It does take time 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 and what processes exist. The Bug Tracking System's [pseudo-package list](http://www.debian.org/Bugs/pseudo-packages) may give great insight into some processes. |