Re: Survey on Bug Tracking Tools

* Dominik George: > However, I (for one) am not so comfortable with your proceedings. > > 1. Your e-mail doesn't even carry a real name (and originates at > Google Mail, in combination making it look a lot like spam). > Why not send it from a university address with a readable name, >

Re: Repository Link are NOT https://

* tom: > I have discovered that non of the repository links is https:// . Is it > not safer to use only https:// connections. https:// is meaningless for package downloads because anyone can run a mirror and see the requests directly, even if they are transport-encrypted with HTTPS. APT uses Gnu

Re: DNS Qname minimisation

* Henrique de Moraes Holschuh: > On the CDN side, Akamai were warned that their authoritative servers > were broken and would interfere with Qname minimization in February > 2015[1], and it is still not fixed. It is the same bad behavior that > happened to ECN It is similar to ECN indeed. In bo

Re: Publicly-readable list for only DDs and DMs to post to

* Ian Jackson: > tl;dr: > pls can we create debian-members@l.d.o with posting acceptance rules > copied from debian-devel-announce[1] and subscriber list maintained in > sync with debian-private. I think the only half-successful setups for such discussion lists provide web-only read access.

Re: Debian infrastructure in the EU / copyright challenges

* Daniel Pocock: > There has been some discussion about the potential impact of the latest > copyright legislation[1] on sites/services that share source code or > facilitate collaborative development services. Do you have a link to the text of the proposal? The EFF probably misrepresents its co

Re: Debian infrastructure in the EU / copyright challenges

* gregor herrmann: > Question 2: What about the "uploads by their users"? Since Debian > doesn't allow random people to upload random stuff to its servers > which Debian then promotes, I think this also doesn't apply. Correct, and Debian provides training to DDs to recognize potential copyright i

Re: Bitcoin donations

* Adam Borowski: > I consider Bitcoin to still be far less repulsive than both the mainstream > banking system and para-banks like Paypal. Many countries have a long tradition of banking cooperatives, which could provide a third option.

Re: Article 13 of the EU copyright review

* Chris Lamb: > Would there any strong objections to the Project aligning itself > against the new EU copyright review? For more background, here's a > recent Linux Journal article about this reform attempt: > > > https://www.linuxjournal.com/content/how-eus-copyright-reform-threatens-open-sour

Do we need embargoes for GPL compliance issues?

Do you think Debian should welcome embargoes for GPL compliance issues? Security embargoes are a huge pain, but one would hope that GPL violations by Linux distributions are much rarer events. I'm asking because even with the GPLv3 or the Common Cure , the 30-day p

Re: Do we need embargoes for GPL compliance issues?

* Jonathan Carter: > Having said all of that, I don't know of any case where Debian has > specifically named and shamed anyone regarding such a violation, but I > also don't see a reason why Debian should explicitly try to keep those > secret for no good reason. The main advantage for Debian woul

Re: Do we need embargoes for GPL compliance issues?

* Russ Allbery: > Florian Weimer writes: > >> Do you think Debian should welcome embargoes for GPL compliance issues? >> Security embargoes are a huge pain, but one would hope that GPL >> violations by Linux distributions are much rarer events. > > I'm so

Re: Do we need embargoes for GPL compliance issues?

* Russ Allbery: > Florian Weimer writes: >> * Russ Allbery: >>> Florian Weimer writes: > >>>> Do you think Debian should welcome embargoes for GPL compliance >>>> issues? Security embargoes are a huge pain, but one would hope that >>>

Re: Debian's Code of Conduct, and our technical excellence

* Matthew Vernon: > There have a few posts in recent discussions by people suggesting (or, > at least, appearing to suggest) that there is a conflict between > technical excellence and our Code of Conduct (or aiming to increase the > diversity of our membership, or similar). > > I think there i

Re: Binary compatibility policy for security updates and point releases

* Jakob Leben: > Well, there are use cases that are not so simple. For example: I might > deploy Debian 9.1 on an embedded machine sold to a client on the other side > of the world. I have a system for updating my own software which is also > deployed on that machine, but not the rest of the Debia

Re: metaphors and feminism

* Mike Hommey: > That's the primary structural distinction as an effect, but OTOH, the NM > process is a rather extensive vetting process. Not all Debian Developers went through the NM process. Account creation was handled differently in the beginning. (I wasn't around and don't know the detail

Re: GR proposal: mandating VcsGit and VcsBrowser for all packages, using the "gbp patches unapplied" layout, and maybe also mandating hosted on Salsa

* Bastian Blank: > On Wed, Jul 24, 2019 at 01:46:36AM +0200, Thomas Goirand wrote: >> On 7/23/19 11:59 PM, Adam Borowski wrote: >> > Big fat enormous NO! gbp is a workaround for the biggest evil in our >> > packaging: quilt. Watching pro-git-only talks on the Debconf, I got the >> > impression t

Re: anti-tarball clause and GPL

* Adam Borowski: > In the light of the currently discussed GR proposal, I wonder if the > following license clause would be considered DFSG-free and GPL-compatible: > > ## > I do not consider a flat tarball to be a preferred form for modification. > Thus, like any non-source form,

Re: GR proposal: mandating VcsGit and VcsBrowser for all packages, using the "gbp patches unapplied" layout, and maybe also mandating hosted on Salsa

* Vincent Bernat: > Because without uniformity, we make it harder for people to contribute. > I have already mentioned Fedora that provides everything in git with CI > enabled, ability to contribute with pull requests, but that's far the > only proponent. Fedora still uses VCS-in-VCS, so it's not

Re: Using Debian funds to support a gcc development task

* John Paul Adrian Glaubitz: > But I think the list on the page archive criteria is a bit dishonest as > well when it asks "Are machines available to buy for the general public?" > while I don't think an IBM Z mainframe is available to buy for the general > public. At last for upstream, the diffe

Re: Debian and Non-Free Services

* Ole Streicher: > You may guess that people using github accept pull requests, but you > even can't see whether they actually like them -- there are many reasons > why people use github, and PRs may not necessarily the specific reason > for the repository. And you can't disable this Github featu

Re: Ihr Artikel über Check_MK

* Jan Leptien: > Sehr geehrte Damen und Herren, > > mein Name ist Jan und ich arbeite für tribe29, dem Team hinter Check_MK. > Ich melde mich bei Ihnen, weil ich einen Artikel zu Check_MK gefunden > habe, den Sie geschrieben haben: http://www.debian.org/consultants/ Please follow the procedure ou

Re: Some thoughts about Diversity and the CoC

* Dato Simó: >> If it turns out that […] what I think […] is unacceptable >> rather than the way I express it, I will not post any more. > > Well, that’s the crux of the problem, isn’t it? > > On one hand, there is a clear consensus in the community that > misgendering someone is something we —Deb

Re: Testing Discourse for Debian - Moderation concepts

* Ansgar: > I'm not concerned about marking messages read after some time and > keeping the view time in ephermal storage for that. But that's not > what Discourse does: as described elsewhere it stores all read times > persistently on the server; that would not be neccessary for marking > posts

Re: Keysigning in times of COVID-19

* Philip Hands: > If I were a sociopath contemplating sabotage in the Free Software > sphere, going to the effort of becoming a DD, even for the first time, > would be nowhere near the top of my list. Even if you got a peer-reviewed research paper out of it? (If I recall correctly, academics alr

Re: Debian accepting Social Micropayment?

* Russ Allbery: > So far, these systems look like a great way for the micropayment broker to > make money and rather iffy for everyone else involved. For them, it's not about payment, but about clickstreams and related data. -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org w

No general political content on Planet

Could we please make and enforce a rule that no general political content is published on planet.debian.org and similar sites? I understand that people have different political views, and I generally appreciate that. We have developers from countries who are not on the most amicable terms, and co

Re: No general political content on Planet

* Russ Allbery: > Meeting one's fellow developer in person also (at least for me) helped a > lot in turning random political content I strongly disagree with from > something that pissed me off into something that just makes me roll my > eyes and remember the good conversation we had. :) This ce

Using corporate accounts when posting to Debian mailing lists

This is mostly an etiquette question, and I'm not sure if this is the right mailing list to post to. I've noticed that compared to, say, ten years ago, relatively few mailing list posters use corporate accounts (or accounts readily attributable to some larger organization). This phenomenon is not

Re: Using corporate accounts when posting to Debian mailing lists

* Craig Small: > On Wed, May 11, 2011 at 11:10:49PM +0200, Florian Weimer wrote: >> I wonder if this is the result of corporate pressure, or if this is >> somehow encouraged by the de-facto list policy. > You'll never find me using a corporate address. The IP and surve

Re: Using corporate accounts when posting to Debian mailing lists

* MJ Ray: > At least as I understand it (IANAL), English business emails should > contain a signature with extended contact information (thanks to the > Business Names Act, Companies Act, Distance Selling Regs and some > other stuff that covers the gaps). That stems from a European directive on b

Re: revenue sharing agreement with DuckDuckGo

* Mike Hommey: > With my iceweasel maintainer hat on, I won't start to consider ddg as a > default until it at least matches the user experience the current > default engine provides, including search suggestions and localized > results (the latter requires some manual work ; the former lacks > se

Re: revenue sharing agreement with DuckDuckGo

* Stefano Zacchiroli: > - The main risk I see in similar agreements is influencing our technical > choices by the revenues. By making clear --- to them and to us --- > that maintainers should be free to make technical decisions no matter > the agreements, I'm relatively confident this risk i

Re: Revising the Code of Conduct

* MJ Ray: > I think "mailing list" is still usually two words, so I'd change that > throughout. And "list servers". I think we should also mention that mailing lists are public (very public at that, indexed by search engines and mirrored widely) if the document is targeted a newcomers. The disc

Re: KickStarter for Debian packages - crowdfunding/donations for development

* Manu Sporny: > As an aside, PaySwarm is currency agnostic. The commercial > implementation of it (Meritora) deals with USD today, has plans for Euro > (and a few other national currencies) within a year, and Bitcoin shortly > after that. For the Euro, we already have the SEPA system, which is v

Re: Possibly moving Debian services to a CDN

* Simon Paillard: > * My own experience is different, http.d.n redirects to ftp2.fr, which i got > 10,2Mo/s, while cloudfront.d.n (Amazon) gives 5Mo/s. This matches my experience. One of the CDNs we use at work does not seem to pre-replicate content world-wide (which is not too surprising, I sus

Re: Should mailing list bans be published?

* Joey Hess: > Simply obfuscating the name on the list of banned users (or not posting > any names at all, only links to the posts that led to the ban) would > eliminate most reputational damage. Ie, random searches for that > person would not turn up a high pagerank debian.org page listing their

Re: Updates in stable releases

* Kurt Roeckx: > I want to start by giving some examples of things that got updated > in stable point releases that I know about: > - linux was 3.2.41-2 in 7.0, 3.2.51-1 in 7.3, 3.2.53-2 in > proposed-updates > - iceweasel was 10.0.12esr-1 in 7.0, is now 17.0.10esr-1~deb7u1 > - postgresql-9.1 wa

Re: Updates in stable releases

* Kurt Roeckx: >> If upstream has long-term stable versions with really limited changes >> (your linux and postgresql-9.1 examples), we may use them instead of >> rolling our own releases, based on the assumption that the released >> version has seen some testing upstream and elsewhere, more than

Re: Plan of action for Secure Boot support

* Ben Hutchings: > However, there is now a blog post from Microsoft that supports what > Matthew Garrett has been saying for a while - they may revoke the > signature on a boot loader if signature verification is not extended to > the kernel, including any mechanism to chain-load another kernel: >

Re: Plan of action for Secure Boot support

* Ben Hutchings: >> The Terms & Conditions of existing EV code-signing CAs do not permit a >> code-signing end-entity certificate to be used for signing another >> certificate, so we'd directly have to embed the end-entity certificate >> used to sign GRUB and the kernel into the shim—or we'd have

Re: Possibly moving Debian services to a CDN

* Tollef Fog Heen: > There's not really anything to be fixed, since you shouldn't be using > HTTPS for that host yet. Can't they serve it off an IP address that doesn't answer on 443/TCP, to avoid confusion? -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of

Re: Why discussions don't move from debian-private

* Brian Gupta: > Could this be addressed by a moderated "public" list, that only allows > DDs to post? Unless we provide just a public web archive (which isn't really desirable for a mailing list, with restricted posting or not), people blocked from posting will respond with their mail clients, C

Re: Plan of action for Secure Boot support

* Colin Watson: > On Wed, Jan 08, 2014 at 08:31:11AM +0100, Florian Weimer wrote: >> Furthermore, we need to store the keys for all EV certificates (both >> the certificate used for submission, and the certificate embedded in >> the shim) in devices that meet at least FI

Re: Patent clauses in licenses

* Thomas Hood: > The point of promoting free software is to allow people to > use/study/modify/redistribute software in freedom. People can't do these > things in freedom if they are subjected to unreasonable restrictions in > the licenses attached to the software. We already accept various trad

Re: Patent clauses in licenses

* Thomas Hood: > It is fine that you think that people who sue for patent infringement are > naughty, but it is also irrelevant. Debian is not in the business of > imposing ethical behavior on its users. Of course we are. Debian tries were hard to serve as a guide what is free software and what

Re: Patent clauses in licenses

* MJ Ray: > I have not expressed this view to debian-project or planet debian: > patent licences which terminate on related patent action may be free. > I do not see how copyright licences which terminate on patent action > can be free. This strongly favors patent owners over copyright owners.

Re: Patent clauses in licenses

* Wouter Verhelst: > Unlike in the software business, there are some domains (such as > pharmaceutics) where patents really are crucial to innovation It's not clear which role patents play in pharmaceutics. You can easily loose them, see:

Re: Patent clauses in licenses

* Andrew Suffield: >> We now have a (lower) German court ruling that this isn't the case, >> i.e. that the termination clause is effective and you can't just get >> another copy of the same work. It's rather surprising because it >> conflicts with our equivalent of the first-sale doctrine > > Yes,

Re: http://www.debian.org/consultants/ policy

* Noèl Köthe: > The first step I want to discuss with you is that right now there is no > real policy about who will be added to this page. In my opinion these > minimal policy should be enough: When will you delist a consultant? Only if these criteria are no longer met? You should probably doc

Re: Google ads on debian.org

* Martin Michlmayr: > Normally, I reply to advertising requests on debian.org with a polite > "no". However, given that google ads are widely considered different > to normal ads, and might even enhance a web site, I thought I'd ask on > -project to see what other people think. It's an incredibl

Re: Google ads on debian.org

* Michelle Konzack: > If I go to there was many times I have > found one of the adds after my search results are very useful and it > was a 100% hit ! If I search for "Debian Linux" on Google, a Microsoft ad is displayed next to the results. Maybe this is useful, bu

Re: Google ads on debian.org

* Henrique de Moraes Holschuh: > On Mon, 13 Dec 2004, Florian Weimer wrote: >> If I search for "Debian Linux" on Google, a Microsoft ad is displayed >> next to the results. Maybe this is useful, but I don't think we want > > Not here. Google is doing geogra

Re: Google ads on debian.org

* martin f. krafft: > also sprach Florian Weimer <[EMAIL PROTECTED]> [2004.12.13.2101 +0100]: >> If I search for "Debian Linux" on Google, a Microsoft ad is displayed >> next to the results. Maybe this is useful, but I don't think we want >> that on Deb

Re: Google ads on debian.org

* Stephen Frost: > I disagree. There are ads on postgresql.org and I certainly don't think > they make it look like Postgresql is commercial. I think it's disappointing. If this development continues, the only ad-free space on the web will be Microsoft's web site, a few obscure government sites

Re: Rewriting GFDL docs - where to start from?

* John Hasler: >> What is this license? Where can it be found? Is it also problematic with >> respect to GPL-compatibility? > > On my Woody system I have an Emacs manual that contains this: > >This is the thirteenth edition of the `GNU Emacs Manual', updated for >Emacs version 20.7. >.

Re: Debian Free Documentation Guidelines was: License of old GNU Emacs manual

* Henrique de Moraes Holschuh: >2. The freedom to study how the text is written, and adapt it to your > needs. Access to the text in the preferred form for modification is a > precondition for this. This includes the ability to modify the work to fit > in low memory situations, reference cards

Re: Debian Free Documentation Guidelines was: License of old GNU Emacs manual

* Matthew Garrett: > Perhaps an easier way to do this would be to look at the DFSG and work > out what changes need to be made. We have a set of freedoms that we > believe software should provide - rather than providing an entirely > different set of freedoms for documentation, we should try to ju

Re: documentation x executable code

* Craig Sanders: > and, as you pointed out yourself, this freedom (to patch) exists > even when it is not explicitly granted by the license. Without permission from the author, you may not redistribute patches in many jurisdictions. (DJB's analysis clearly does not apply to the situation in Germ

Re: Debian Free Documentation Guidelines was: License of old GNU Emacsmanual

* Gunnar Wolf: > Well... Remember the GPL does not require you to provide the sources > _together_ with the binary/printout/whatever - It requires you to > provide means to get the sources. So if you print a book that [...] > has the URL for the place you can refer to in order to get the > source,

Re: Debian Free Documentation Guidelines was: License of old GNUEmacsmanual

* Gunnar Wolf: > Florian Weimer dijo [Wed, Jan 05, 2005 at 07:14:55PM +0100]: >> > Well... Remember the GPL does not require you to provide the sources >> > _together_ with the binary/printout/whatever - It requires you to >> > provide means to get the source

Re: Debian Free Documentation Guidelines was: License of oldGNUEmacsmanual

* Gunnar Wolf: >> No, Debian distributes source and binaries on the same (virtual) >> medium. This is different from handing over a physical object with >> the "binary" and providing a URL for some resource on the Internet. > > So... If I hand over a Debian CD to someone, will I be breaching the

Re: License of old GNU Emacs manual

* Glenn Maynard: > It's not clear whether a work which is affected by a "strict" trademark > license is DFSG-free. Really? TeX is affected by such a license and the DFSG were written so that TeX would still be considered free software.

Re: A new banner for Sarge

* René van Bevern: > The "apt-get into it" is hard to read because the space between each > letter is almost as much as the space between each word. It's also a bit unfortunate because we recommend to use aptitude.

Re: A new banner for Sarge

* René van Bevern: > On 15.07.05, Florian Weimer wrote: >> * René van Bevern: >> > The "apt-get into it" is hard to read because the space between each >> > letter is almost as much as the space between each word. >> It's also a bit unfortunate

"Debian" Core Consortium

How is Debian related to the "Debian Core Consortium"? Why are they using the name "Debian"? In principle, I don't have anything against Debian spinoffs, but they shouldn't use confusing names that suggest they are more Debian than Debian itself (or something like that). Or is this something Deb

Re: "Debian" Core Consortium

* Lars Wirzenius: > su, 2005-07-24 kello 10:13 +0200, Florian Weimer kirjoitti: >> How is Debian related to the "Debian Core Consortium"? Why are they >> using the name "Debian"? > > I'm not sure I have ever heard of "Debian Core Consortiu

Re: "Debian" Core Consortium

* Alexander Wirt: > Florian Weimer schrieb am Sonntag, den 24. Juli 2005: > >> How is Debian related to the "Debian Core Consortium"? Why are they >> using the name "Debian"? > Maybe you sould wait until its been more than a plan to do something before

Re: "Debian" Core Consortium

* Ian Murdock: > The Debian Core Consortium (it's not going be called that, but that's > what the media has been calling us) is simply a group of companies and > nonprofits that build Debian derivatives banding together with a few > central goals: Fair enough. But somehow nobody who is involved

Re: "Debian" Core Consortium

* John Hasler: > Ian writes: >> "My response" has to do more with how that trademark policy appears to be >> inconsistent with Debian's founding goals. > > I suspect that any effective trademark policy is going to be > inconsistent with Debian's founding goals. In general, we don't have to addres

Re: "Debian" Core Consortium

* Andreas Barth: >> No, there is an *idea* for this, but the project doesn't have a name >> yet. If you think that's not true - please show me an official statement >> of the named companies using "Debian Core Consortium". > > > | A spokesperso

Re: Non-DDs as official Debian package maintainers

* Jonas Smedegaard: > Packages with noone explicitly nursing them is a bad thing. that's why > we have the routine of "oh - someone seems to be MIA - let's check what > packages is hurt by this". This is not (easily) trackable with > sponsored packages. Exactly. The sponsorship relation is usual

Re: Non-DDs as official Debian package maintainers

* Jonas Smedegaard: > In a comment to a thread in d-private that I am not allowed to publish, > I wrote regarding packages with non-DDs in the maintainer field: > >> I wholeheartedly want help also from non-DDs, I just see a problem >> relying on someone that we by definition do not (yet) trust.

Re: DPL-team issue page

* Andreas Schuldei: > http://wiki.debian.org/DPLTeamCurrentIssues Is this list really exhaustive? Or do you consider it done once it's been delegated to someone? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Resignation as Debian Release Manager

* Branden Robinson: > On Fri, Sep 23, 2005 at 12:10:00AM +0100, Colin Watson wrote: >> I hereby tender my resignation as Debian Release Manager. > > Thanks for your outstanding service, Colin. Reinventing the team > mid-release was not easy, but you and Steve didn't flinch from it and did a > gre

Re: DCC (Debian Confusion Core) trademark negotiation status

* Philip Hands: > Also, I was under the impression that recursive acronyms needed to be > witty, or at least close to being a pronounceable word, to count. > > I suppose one could try pronouncing DCC as "Dick" to make it qualify ;-) But it is, maybe unintentionally. "DCC Alliance" sounds like a

Re: DCC (Debian Confusion Core) trademark negotiation status

* Anthony Towns: >> Look at the www.dccalliance.org website: > > You missed "The initial release of the Debian Common Core, expected > in the September time frame, will be based on Debian 3.1 ("Sarge") > and certified to LSB." from the rather prominent "Press" link. Unfortunately, It's still ther

GPL v3 process

Do Debian or SPI participate in the GPL v3 process? I think Debian should, to make sure that license compatibility does not decrease substantially, and that things like the purported anti-DRM clauses remain practical. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe"

Re: GPL v3 process

* Nathanael Nerode: > Florian Weimer wrote: > >> Do Debian or SPI participate in the GPL v3 process? >> >> I think Debian should, to make sure that license compatibility does >> not decrease substantially, and that things like the purported >> anti-DRM clause

Re: DPL-team issue page

* Andreas Schuldei: > No, the list is not exhaustive. I just added the "security team" > to the issue list (but should have done so some time ago already, > once the meeting was sure to happen). > > there are other issues which are not on the list, since we > believe that it would not do much good

Re: How Delegation Works, in 10 Easy Steps

* Branden Robinson: > Let me know if you feel this is an accurate characterization of the > Constitution; I've done my best, but I'm not infallible. Also, I'd > like to hear your thoughts on whether you think delegation is a tool > that I should use more. I appreciate your comments. You missed

GNU FDL status

What is the status of the GNU FDL conflict resolution efforts? A public statement by a delegate was promised some time ago, but I can't find it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Complaint about #debian operator

* David Nusinow: > Martin, I'd like for you to come in to #debian. Not for an hour or a few > hours, but for a few weeks to see what it's like. We have consistently > refused to support non-Debian distros for years, including knoppix and > ubuntu. AFAICT, the question which sparked this thread wa

Re: Stable security support

* Anthony Towns: > As people following planet will already know, I've been working updating > dak (aka katie, the Debian archive kit, and dinstall) to support splitting > the queue of not-yet-released security updates into "unembargoed" > and "embargoed" sections, primarily so that folks from the

Re: Induction of new members to the technical committee

* Martin Zobel-Helas: > actually, i would like to know how this persons have been > appointed/selected? Will this work like any other vote, so anyone can be > recommented? Or does the CTTE need to assign this person by it's own? No, the DPL and the Technical Committee handle this by themselves. S

Re: Information abount packages.d.o and experimental

* Noèl Köthe: > is it possible to get information about the problem with packages.d.o > and the experimental problem? Isn't experimental being pulled from the archive or something like that?

Re: Information abount packages.d.o and experimental

* Adam D. Barratt: > On Sat, 2006-01-07 at 11:20 +0100, Florian Weimer wrote: >> * Noèl Köthe: >> >> > is it possible to get information about the problem with packages.d.o >> > and the experimental problem? >> >> Isn't experimental being

Re: Debian derivatives and the Maintainer: field (again)

* Matt Zimmerman: > It is important, in particular, to account for the fact that Ubuntu is not > the only Debian derivative, and that proposals like yours would amount to > Debian derivatives being obliged to fork *every source package in Debian* > for the sake of changing a few lines of text. Su

Re: Anfrage für Clan Sponsoring! www.quando-gaming.de

[He's asking if we might sponsor his computer gaming site.] > Ich wollte Sie fragen ob Sie gerne unseren Clan Sponsern würden? Nein, Debian hat völlig andere Schwerpunkte. Tut mir leid.

LWN subscription

Has Debian still got that blanket LWN subscription for all developers? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: LWN subscription

* Isaac Clerencia: > On Friday 10 March 2006 12:44, Steve Kemp wrote: >> http://lists.debian.org/debian-devel-announce/2002/10/msg00018.html > IIRC I did that Me too, and IIRC the message is even stored in the corresponding mailbox on master. Is anybody still processing requests? -- To UN

Re: Oracle has a Debian repository now

* Michael Kallas: > It would be a step into the right direction if Oracle would release it as > Free Software (according to DFSG). Until then, I'm not sure how this is > connected to the Debian project. Debian officially supports non-free software, see the Social Contract and

Re: irc.debian.org

* Paul Johnson: > Why not move it to Jabber? More people use and know what Jabber is > these days than IRC. Really? jabber.debian.net does not seem to accept new users. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [SUMMARY] About terminology for stable/testing/unstable and related issues

* Christian Perrier: > Most concerns have been raised about my proposed use of "branch" for > talking about stable/testing/unstable. "Suite" seems better...suited, > indeed. Suite has already been used informally. For completeness, you should also mention "section" (main, contrib, non-free) in y

Re: [SUMMARY] About terminology for stable/testing/unstable and related issues

* Adam D. Barratt: > On Tuesday, May 09, 2006 6:26 AM, Florian Weimer <[EMAIL PROTECTED]> wrote: > >> * Christian Perrier: >> >>> Most concerns have been raised about my proposed use of "branch" for >>> talking about stable/testing/unstable. &q

Re: Donations

* MJ Ray: > any donations to debian must be given to SPI; or Why do you think this is so? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Donations

* Manoj Srivastava: > On 11 Jun 2006, Martin Wuertele stated: > > ]Since Debian has no authority to hold money or property, any > ]donations for the Debian Project must be made to any > ]one of a set of organizations designated by the Project leader > } or a delegate to be aut

Re: Donations

* Manoj Srivastava: > > 4. The Developers by way of General Resolution or election >4.1. Powers > Together, the Developers may: > +6. Together with the Project Leader make decisions about > + property held

Re: RE : Re: RE : Re: Linux Magazin Germany, affecting Debian's image?!

* Radu-Cristian FOTESCU: >> Please provide legal references for the "responsibilities" that you >> persist in claiming someone has. To whom do you think those >> "responsibilities" are owed? > > If you don't care about your brand, you'll lose the respect of your > partners. Well, you don't gain t

Re: RE : Re: RE : Re: Linux Magazin Germany, affecting Debian's image?!

* Andreas Barth: > Does that sound like a wrong thing only to me? No, this whole thread is rather bizarre. It would be very sad if someone reading it got the impression that this is the way the Debian project interacts with other organizations, especially commercial entities. -- To UNSUBSCRIB

Re: Hardware

* Pat Tadgerson: > I am not a real hardware person, but I would like a server with 2 > hard drives with about 160 gigs of storage, with a raid 0 > configuration. RAID 0 is usually a very bad idea because you lose all your data if just one disk fails. By the way, you should use a more suitable ma

  1   2   >