Re: Developer Status
Hi Ganeff, Just a note to register my endorsement that I believe you have great ideas here. Cheers, Andrew McMillan On Wed, 2008-10-22 at 23:33 +0200, Joerg Jaspert wrote: Developer Status Summary of this post Discussions in the past have made it clear that the current definition of Debian Developer (AKA someone who is a member of the Debian project) should be modified and made more flexible. There have been attempts in the past to do something similar, notably Debian Maintainers (DM) [GR-DM], and to some extent debian-community.org [D-C], but these have only addressed parts of the whole issue. We plan to integrate DM more closely into the NM process/system while keeping the spirit of easing entry into Debian for newcomers. At the same time we add a separate track for less-technical contributors. If you are an existing Debian Developer or Debian Maintainer, don't be afraid, we are not going to take anything away from you. Currently becoming a Debian Developer means passing through all of the New Maintainer process. People that passed this get the @debian.org mail-forwarding, an account on all (developer-accessible) Debian machines, voting and upload rights. It is a process that requires work from prospective Developers, and depending on their available time and the effort put into it, it can take a bit of time. Some time ago a few Developers thus went and pushed forward the Debian Maintainer status. DM allows newcomers to upload their packages relatively early, without having to go through the full NM process. So far it has worked quite well for the people involved, but the way it was instantiated outside of most existing structures has always made other groups in Debian uncomfortable. The ftp-masters have to deal with the technical implementation that does not fit well with the rest of the archive, and the account and keyring managers would like to remain the authoritative source for who is in Debian. Debian is about developing a free operating system, but there's more in an operating system than just software and packages. If we want translators, documentation writers, artists, free software advocates, et al. to get endorsed by the project and feel proud for it, we need some way to acknowledge that. This is where our proposal comes in. Now let us describe the way the account status is meant to be handled in future. A new user can start out in two ways depending on their personal preference. The first is the non-technical way: Debian Contributor -- A DC is someone that has a strong relation with Debian through the work they are doing for/around Debian. Possible examples are translators and documentation writers. DC have to pass the ID check, agree to the Social Contract/DFSG and have successfully answered a set of questions[DCDMQ] similar to the ones used in the current first PP step.[TEMPL] The second way is the technical one: Debian Maintainer - A DM has the same strong relation with Debian a DC has, but additionally wants to maintain a limited set of packages without the help of a sponsor. A DM has to pass the same checks a DC has and very few questions from the TS part[DCDMQ]. A (very) small TS basically, the most important TS questions for them. They are allowed to upload their own (source) package. The allowed list of (source) packages to upload can be edited by any member of the NM committee[NMC], who will do a package check before they add new packages to the DM's list. In contrast to current DM this is based on source packages and allows uploads of new binary components, which have to pass NEW, too. While, strictly speaking, this increases the barrier to get DM compared to the current implementation of DM, we do not think it is an unreasonable or too high level. Anyone who is able to get a package put together in a lintian clean way will be able to get DM without much effort or time used. Those two classes are the initial set in which every NM will end up. After six months as DC or DM one might chose to become a Debian Member or Debian Developer. This - ensures that the interest in Debian isn't short-term. - enables them to learn more about the workings in Debian and generally helps them for the next step. - leaves everyone the option to stay DC or DM, if they do not want/need more rights. After the 6 months time in Debian Contributor/Maintainer are passed, applicants can apply to get Debian Developer status. There are now 2 different classes of DD status available, one with and one without upload rights. To not add confusion we selected to name them Debian member (no upload rights) and Debian Developer (upload rights). Both are project members, i.e. with voting and all other constitutional rights, the term classes
Re: Time servers (ntp) wanted
On Thu, 2003-01-30 at 22:56, Adrian 'Dagurashibanipal' von Bidder wrote: time.fortytwo.ch round robin DNS I just wanted to say how great the Debian community is: within three hours of the announcement here, I had 5 volounteers offering their timeservers. Any other timne servers willing to join are still welcome :^) Update: the time.fortytwo.ch will probably become the pool.ntp.org project in the near future and thus become a bit more 'official'. Yay! Mailing lists for the interested: timekeepers@fortytwo.ch and [EMAIL PROTECTED] (see http://fortytwo.ch/time) If it were possible to put a country hierarchy in there I would be happy for Catalyst to include some machines in the list for .nz : nz.pool.ntp.org for example. I think this might in general be a better way to go. Slightly more accurate timekeeping perhaps if we aren't using round-the-world pings, and I don't see that it would make the debconf quizzing for ntp setup _that_ much harder for naive users. There could also be a fallback to the top-level pool.ntp.org which all might then participate in. Cheers, Andrew. -- - Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St DDI: +64(4)916-7201 MOB: +64(21)635-694OFFICE: +64(4)499-2267 Survey for nothing with http://survey.net.nz/ -
Re: Debian as a social group and how to develop it better
On Mon, 2002-12-02 at 15:34, Xavian-Anderson Macpherson wrote: Have I said enough?? Yes, thank you. Regards, Andrew. -- - Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St DDI: +64(4)916-7201 MOB: +64(21)635-694OFFICE: +64(4)499-2267 Survey for nothing with http://survey.net.nz/ -
Re: Win modems
Chris Waters wrote: On Fri, May 11, 2001 at 01:13:43AM -0700, bast3d wrote: I wanted to inquire on if Debian is going to include Win Modem support? The question should really be: does anyone in the Debian project feel like supporting WinModems? My *personal* take on the matter is that WinModems impose too much of a performance penalty on CPUs, and I would never use one, which would make it difficult for me to support. Bottom line: a) is it free enough (or redistributable enough for our non-free archives), and b) is anyone willing to do the work required. My feeling is: Most laptops have such things built-in. This is a fact of life. I would actually prefer to be able to use the WinModem built into my laptop, unfortunately no Linux drivers exist (it's a 3COM mini-PCI ethernet + pseudo-modem) so I am SOL. My laptop has a Pentium III 850, which is CPU to burn for this particular task, I hope! Using a modem is a minor task, but sometimes I am out of the office and connecting to the internet through dial-up is very important to me. I think that the Debian project should be only too happy to support [LW]inModems if there is a Debian developer packaging such beasts. Personally, if 3COM were to release a driver for my modem (or make available sufficient information to write one) I would be only too happy to package such a beast (as well as assisting in whatever way possible in it's genesis). Regards, Andrew. -- _ Andrew McMillan, e-mail: [EMAIL PROTECTED] Catalyst IT Ltd, PO Box 10-225, Level 22, 105 The Terrace, Wellington Me: +64(21)635-694, Fax: +64(4)499-5596, Office: +64(4)499-2267xtn709
Re: Incoming
Jason Gunthorpe wrote: On Mon, 3 Apr 2000, Mark Brown wrote: Would it be possible for Incoming to be made avalible via FTP as well as HTTP? Both can have problems with firewalls and forced proxying, but I don't think so, ftp is going to remain turned off on that machine. If you can't fetch things from the web, but can via ftp I think you have some serious 'issues' ; Yes, but not ones that he (or I) are necessarily in control of. Although I can download from ftp.debian.org at around 50-100k/s I can only get around 7-10k/s via http. This is because our ISP has a 'transparent' proxy cache and have somehow misconfigured it. As a result I regularly have problems downloading files larger than around 4MB via HTTP. Sure I've complained, but does it do any good? Is there some way that ftp could remain enabled? As Mark says: some proxies have problems with one, and some have problems with the other, but it would be nice to have access to an ftp archive of incoming. If ftp is to remain off on that machine, can some 'close' machine with ftp on have a sync'd copy of incoming on it? Thanks, Andrew McMillan -- _ Andrew McMillan, e-mail: [EMAIL PROTECTED] Catalyst IT Ltd, PO Box 10-225, Level 22, 105 The Terrace, Wellington Me: +64 (21) 635 694, Fax: +64 (4) 499 5596, Office: +64 (4) 499 2267
