Hi Lisandro, Reading through the Teams wiki on debian, this is what I gathered
* Making a commitment to answer questions and/or be available at least once a week * Teams manage internal infrastructure such as wikis, faqs, etc, and a public facing irc support channel. Being a part of a team would likely have the expectation to assist with such things. * Teams have leaders and that leader would likely ask you to do something at some point. Going back to the first point, being a part of that team means a prompt reply, beit a yes or a no. Let me know if I missed anything there, and I'd have no problem with any of that if I maintained ktouchpadenabler under the kde extras team. Working along side others could only expedite the learning process on my end :) Thanks, Daniel On Wed, Oct 3, 2012 at 3:41 PM, Daniel Skinner <dan...@dasa.cc> wrote: > Responses below: > > >> OK, a *very* minor thing: in debian/changelog we (pkg kde team) use to >> write: >> >> * Some stuff (Closes: #689080). >> >> Instead of: >> >> * Some stuff. (Closes: #689080) >> >> > No problem, will do. > > >> There is only one thing missing, and I'm the one to blame. As Sune >> (svuorela) >> suggested you to package this software which is KDE-related but optional >> for >> KDE itself: would you like to maintain it under the pkg-kde-extras team's >> umbrella? >> > > I dont really know what this means. > > >> >> Furthermore: >> >> - Do you know what teams are for inside Debian? >> > > Not even vaguely, but I wanted to build the plugins for pkg sndobj and > figured I would get with the maintainer, or as a last resort, > pkg-multimedia-maintainers team. Beyond that, not sure. > > >> - Do you know what are the consequencies of team-maintaince? >> > > No clue, maybe living up to the expectations of others? > > >> - Do you know what is the pkg-krap maintainance team? >> > > I could only guess and all my guesses sound funny :p > >
