Bug#796969: ITP: hamradio-maintguide -- Debian Hamradio Maintainers Guide

2015-08-26 Thread Iain R. Learmonth
Package: wnpp Severity: wishlist Owner: "Iain R. Learmonth" * Package name: hamradio-maintguide Version : 0.1 Upstream Author : Iain R. Learmonth * License : BSD-2-clause maybe Programming Lang: Sphinx Description : Debian Hamradio Maintainers Guide

Re: How to cope with patches sanely --> Debian New Maintainers' Guide

2008-02-06 Thread Patrick Schoenfeld
Hi Pierre, On Tue, Feb 05, 2008 at 09:17:12PM +0100, Pierre Habouzit wrote: > Again, the discussion isn't (for me) about a tool, but an exchange > format. We are discussing having patches served in a quilt series, and okay, this approach is similar but different. So you want a quilt series, but

Re: How to cope with patches sanely --> Debian New Maintainers' Guide

2008-02-05 Thread Pierre Habouzit
On Tue, Feb 05, 2008 at 06:24:38PM +, Patrick Schoenfeld wrote: > So, I would agree with those recommending quilt, if it has significant > pros besides dpatch. That would be forcing to a specific tool and so > giving up some diversity, but it would keep giving up freedom of choice > on a low le

Re: How to cope with patches sanely --> Debian New Maintainers' Guide

2008-02-05 Thread Patrick Schoenfeld
Hi, On Sat, Jan 26, 2008 at 12:40:14AM +0900, Osamu Aoki wrote: > This seems to be much cleaner than dpatch or quilt. Also with the help > of gitk, history is much more visible. I look forward to see it matured > and accepted. personally I am a fan of the diversity in the Debian project. Its re

Re: How to cope with patches sanely --> Debian New Maintainers' Guide

2008-01-25 Thread Osamu Aoki
Hmmm... On Fri, Jan 25, 2008 at 10:51:41PM +0900, Osamu Aoki wrote: > I ended up updating NM guide which only had dpatch to current one with > quilt: > > http://www.debian.org/doc/manuals/maint-guide/ch-build.en.html#s-dpatch As I read this thread back to d-project, ... interesting. It all star

Re: How to cope with patches sanely --> Debian New Maintainers' Guide

2008-01-25 Thread Osamu Aoki
Hi, On Fri, Jan 25, 2008 at 10:51:05AM +0100, Lucas Nussbaum wrote: > On 25/01/08 at 08:01 +, Steve Langasek wrote: > > As a second runner up, quilt is ok by me. :) > > I made some stats (see [1]). 7.8% of our packages use quilt, while 14.4% > use dpatch. This was discussed in debian-doc a

Re: BTS package to report bugs in "Debian New Maintainers' Guide"

2007-01-07 Thread Andreas Fester
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jari Aalto wrote: > [Please keep CC] > > Where should the bugs found in "Debian New Maintainers' Guide" be > reported? BTS package name? maint-guide? http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=maint-guide Bes

Re: BTS package to report bugs in "Debian New Maintainers' Guide"

2007-01-07 Thread Mohammed Adnène Trojette
On Sun, Jan 07, 2007, Jari Aalto wrote: > Where should the bugs found in "Debian New Maintainers' Guide" be > reported? BTS package name? maint-guide [no Cc:, I read the list] -- Mohammed Adnène Trojette -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of &

Re: BTS package to report bugs in "Debian New Maintainers' Guide"

2007-01-07 Thread Luca Capello
HellO! On Sun, 07 Jan 2007 18:02:34 +0100, Jari Aalto wrote: > Where should the bugs found in "Debian New Maintainers' Guide" be > reported? BTS package name? = [EMAIL PROTECTED]:~$ dpkg -s maint-guide | grep Description Description: Debian New Maintainers&#x

BTS package to report bugs in "Debian New Maintainers' Guide"

2007-01-07 Thread Jari Aalto
[Please keep CC] Where should the bugs found in "Debian New Maintainers' Guide" be reported? BTS package name? Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Maintainers Guide

2006-04-01 Thread John Hasler
Tollef Fog Heen writes: > Are you able to claim that source code written is not under copyright in > any way? It's less than 70 years after the author's death (even for > really old code from, say, 1950) and if it clearly is copyrightable, it > will be under copyright. If it was written by a US g

Re: Maintainers Guide

2006-04-01 Thread Tollef Fog Heen
* Anthony DeRobertis | Well, isn't prohibiting the "I didn't know it is copyrighted" defence | the only legal effect of having the notice nowadays, anyway? Are you able to claim that source code written is not under copyright in any way? It's less than 70 years after the author's death (even fo

Re: Maintainers Guide

2006-03-30 Thread Joerg Sommer
Hello Anthony, Anthony DeRobertis <[EMAIL PROTECTED]> wrote: > Jeremy Stanley wrote: >>This has to include a copyright year, also. >> >> ...and following additional discussion, the resolution is: >> >>After considering the suggestion, I have decided to close this >>bug. >> > The yea

Re: Maintainers Guide

2006-03-29 Thread Henning Makholm
Scripsit Anthony DeRobertis <[EMAIL PROTECTED]> > On Tue, Mar 28, 2006 at 03:51:30PM +0200, Henning Makholm wrote: >> Only for some pretty strange values of "worthless". AFAIU the only >> legal effect of the notice requirements you cite is as defined by >> subsection (d): if a compliant notice is

Re: Maintainers Guide

2006-03-28 Thread Anthony DeRobertis
On Tue, Mar 28, 2006 at 03:51:30PM +0200, Henning Makholm wrote: > Only for some pretty strange values of "worthless". AFAIU the only > legal effect of the notice requirements you cite is as defined by > subsection (d): if a compliant notice is present, a defendant is > excluded from the defense t

Re: Maintainers Guide

2006-03-28 Thread Henning Makholm
Scripsit Anthony DeRobertis <[EMAIL PROTECTED]> > The year really should be included. At least in the US, not having a > year in the notice appears to make the notice worthless. Quoting Title > 17 USC Sec. 401(b): Only for some pretty strange values of "worthless". AFAIU the only legal effect of

Re: Maintainers Guide

2006-03-27 Thread Anthony DeRobertis
Jeremy Stanley wrote: This has to include a copyright year, also. ...and following additional discussion, the resolution is: After considering the suggestion, I have decided to close this bug. The year really should be included. At least in the US, not having a year in the notice a

Re: Maintainers Guide

2006-03-27 Thread Nico Golde
7; Palfrader wrote a nice little "How (not) to > >>> write copyright files"[1]. Please read that *now*. > >>> [1] http://lists.debian.org/debian-devel-announce/2003/12/msg7.html > >> [...] > >> Why not add this to the New Maintainers Guide inst

Re: Maintainers Guide

2006-03-26 Thread Frank Küster
copyright files"[1]. Please read that *now*. >>> [1] http://lists.debian.org/debian-devel-announce/2003/12/msg7.html >> [...] >> Why not add this to the New Maintainers Guide instead of >> forcing Applicants to search the mailing list archive for >> this? > &

Re: Maintainers Guide (was: How (not) to write copyright files - take two)

2006-03-26 Thread Yaroslav Halchenko
I just can't locate copyright statement anywhere within the package -- only license file (MPL 1.1/GPL 2.0/LGPL 2.1) is copyright assumed to belong to upstream author? what years then should be mentioned? -- .-. =-- /v\

Re: Maintainers Guide (was: How (not) to write copyright files - take two)

2006-03-26 Thread Jeremy Stanley
; > > [1] http://lists.debian.org/debian-devel-announce/2003/12/msg7.html > > [...] > Why not add this to the New Maintainers Guide instead of > forcing Applicants to search the mailing list archive for > this? Furthermore, the format given in the message is dissimilar

Re: Maintainers Guide

2006-03-26 Thread Joerg Jaspert
bian.org/debian-devel-announce/2003/12/msg00007.html > [...] > Why not add this to the New Maintainers Guide instead of > forcing Applicants to search the mailing list archive for > this? Feel free to submit patches to wherever it may get added. -- bye Joerg >Starting network manag

Maintainers Guide (was: How (not) to write copyright files - take two)

2006-03-26 Thread Nico Golde
ml [...] Why not add this to the New Maintainers Guide instead of forcing Applicants to search the mailing list archive for this? Regards Nico -- Nico Golde - JAB: [EMAIL PROTECTED] | GPG: 0x73647CFF http://www.ngolde.de | http://www.muttng.org | http://grml.org Forget about that mouse with 3/4