Hi, That was meant to be a new paragraph, I just didn't demonstrate it well.
On Thu, Aug 5, 2010 at 11:46 AM, Osamu Aoki <os...@debian.org> wrote: > Hi, > > In order to minimize translation breakage, it is best done by adding a > new paragraph. > > On Thu, Aug 05, 2010 at 10:33:38AM -0400, Nick Gnat wrote: > > Here's a quick stab at shortening the wording: > > Thanks. > > > "If you are interested in packaging a particular type of software (e.g. > > games, perl modules, or KDE apps), it may be beneficial to join one of > > Debian's <a>packaging teams</a>. They'll be able to provide specific help > > for any packaging problems you may have, and will be far more likely than > > other developers to sponsor your package." > > Example of team is good idea. > > I see you are thinking mentoring by other team member... this is one > aspect. I was expecting shared VCS where new people can work part of > project etc. I think we should not make people expect too much help. > Volunteer project is mostly about selfleaning. > Well, I was thinking that too, I was just trying to phrase it in a way that had more appeal to new developers, and keep it short. To add that aspect, perhaps: <p>If you are interested in packaging a particular type of software (e.g. games, perl modules, or KDE apps), it may be beneficial to join one of Debian's <a>packaging teams</a>. Within them, you'll be able to collaboratively develop and maintain packages (through a shared VCS) alongside more experienced developers who share a common interest. This provides the team with more manpower, and provides you with both an excellent learning experience and an opportunity to contribute without possessing the full scope of knowledge required to maintain a package by yourself. Furthermore, if you contribute, experienced developers in the team will be much more likely to sponsor your packages." A little longer, but I think it puts more emphasis on collaboration, while lowering expectations on getting help. > I would put it in 1.4 "Where to ask for help," so that it seems more > > neutral, and something that could really benefit a new maintainer, but > not > > something they should feel obligated to do. > > "Where to ask for help" is for people needeing help. Your text fits > better there but I was thinking a bit different tone. > Yeah, with the revised text, maybe somewhere else fits better > > > Sorry for the unsolicited opinion, but I've been reading the New > > Maintainer's guide lately. For what it's worth, I'm always happy to help > > with phrasing, since I'm a native English speaker, and have a lot of > editing > > experience. > > Please send me typo fixes when ever you find them. > What is the best form for you to receive them in? Patches against the svn sgml? Would you like revisions that (in my estimation) increase the clarity of the text, or just typo corrections? > > > On Thu, Aug 5, 2010 at 8:55 AM, Osamu Aoki <os...@debian.org> wrote: > ... > > > On Thu, Aug 05, 2010 at 07:45:41AM +0900, Ansgar Burchardt wrote: > > > > Ansgar Burchardt <ans...@2008.43-1.org> writes: > ... > > > > > Please include a link to [1] and suggest to ask joining a packaging > > > team > > > > > somewhere. Maybe in "1.3 Official Debian Developer" and "1.4 Where > to > > > > > ask for help" or even add an extra section in the first chapter. > > I should have read this carefully. "add an extra section"! between 1.3 > and 1.4 seems better idea. Something like a new "1.4 packaging team". > > > > > Debian has various <a>packaging teams</a>. Please consider joining > > > > those related to your work. > > Do not they usually have common VCS where you can work together? > > > > > Doing so will make it easier for you to > > > > find sponsors to upload your packages to Debian and having people > > > > maintaining similar software to ask for help. Working on other > > > > packages maintained by the team will also be appreciated. > > This proposal have more positive attitude toward contribution. > I think the last part is most important and along what has been added to > 2.1. Anyway ... I am thinking ... > > <section>Packaging teams > > Debian has various <url id="http://wiki.debian.org/Teams#Packagingteams"; > name="packaging teams">. > If you are interested in packaging a particular type of software (e.g. > games, perl modules, GNOME apps, or KDE apps), it may be beneficial to > join one meant for them. > > They usually have common VCS for packages. Contributing to packages on > such VCS gives you opportunity to contribute without having full > scope of knowledge needed to be a maintainer. This is good learning > experience and will build your credibility among people with the same > kind of interest on packages and makes it more likely to find sponsors > of your package when you need them. > > > > > In my opinion having teams also helps to get faster responses in > general > > > > and distribute the workload to more people; a single maintainer might > be > > > > busy with other work, resultfing in longer delays. Maybe this could > be > > > > included somehow as well? I really think most packages should be > > > > maintained by a team :-) > > I now realize that this part was not meant for inclusion to NM guide. > So the proposed text was neutral. > > Good night > Good night (except it's just noon here), > > Osamu > Nick -- Blog: coderschi.wordpress.com Twitter: twitter.com/nickgnat Facebook: facebook.com/nickgnat
