Re: Debian Wiki: License & Helping with transition
Hello Daniel, On Wed, 2008-09-03 at 00:08 -0400, Daniel Dickinson wrote: > Is there anything a non-DD can do to help get the debian wiki licensing > mess straightened out? I'd like to help, but I'm not a DD. An overview of the situation is available at [1] and [2]. Our plan is prepare some pages that present the situation ([3], [4]) then ask people for comments. (on debian-legal, then debian-user and debian-devel) Contribution/comments/review of the pages [3] and [4] are welcome. [1] http://wiki.debian.org/DebianWiki/LicencingTerms [2] http://bugs.debian.org/385797 [3] http://wiki.debian.org/DebianWiki/LicencingTerms/Proposals [4] http://wiki.debian.org/DebianWiki/LicencingTerms/RelicensingStrategy > Also, I'd like to point out that this is something that I'm going to > have to set up a separate wiki because of, because the current wiki > situation doesn't allow for my use case. > If you write a "standalone" documentation, then it's ok to apply specific license. Have a look at : http://wiki.debian.org/DebianEdu/Documentation/Etch/ http://wiki.debian.org/DebianReference > All the stuff I do will of course be DFSG-free, I just want to make > sure I can incorporate what others do into my own works, assuming them Incorporating external stuff is another tricky part of [3] (especially if we choose Public domain or CC0, because importing copyrighted stuff in a PD work is ... wrong ) > meant for such to happen (which is what is *implied* by a wiki, by > *not* what is actually legally the case). Wikipedia have interesting comments on that implied vs legal aspect : http://en.wikipedia.org/wiki/Public_domain#.28Almost.29_everything_written_down_is_copyrighted So to make it short : You can create a "book" on our wiki, with a specific license. Also, you are welcome to review the page [3] and [4]. Regards Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian CSS
In case you weren't aware; the Debian website no longer validates CSS. -- [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ia64 netinstboot image
Hi together, the actual netinst cd image (4.8.08) for ia64 doesn't boot. all parameters, cd drives and so on are correct. im suspecting that this error is not new ;-) ? any suggestions please ? greetings steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ia64 netinstboot image
Hello, On Wed, 2008-09-03 at 22:36 +0200, Steffen Bode wrote: > the actual netinst cd image (4.8.08) for ia64 doesn't boot. all > parameters, cd drives and so on are correct. im suspecting that this > error is not new ;-) ? According to the cd image date you mentioned, I assume you used the image from Etch 4.0r4a, from : ftp://cdimage.debian.org/cdimage/release/4.0_r4a/ia64/iso-cd/ You should verify the checksum of your cdrom, against the one in file MD5SUMS or SHA1SUMS. > any suggestions please ? The debian-www list is about the Debian website(s), so if your problem persists, consult : Reporting Installation Problems http://d-i.alioth.debian.org/manual/en.ia64/ch05s03.html#problem-report and "Submitting Installation Reports". Or contact the IA64 Mailing list http://lists.debian.org/debian-ia64/ In both case, try to provide the error message you have (or the last line display on the screen). Regards, Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Wiki: License & Helping with transition
On Wed, 03 Sep 2008 09:02:43 +0200 Franklin PIAT <[EMAIL PROTECTED]> wrote: > Hello Daniel, > > > So to make it short : You can create a "book" on our wiki, with a > specific license. Also, you are welcome to review the page [3] and > [4]. Is there anyway to make sub-pages also automatically have the appropriate copyright? It's going to be a pain if a user starts a new page and I have to contact a page creator each time a new page is created because the wiki has no copyright. I'm planning on starting this stuff this month, and it will be on docbook xml format, for the packaged/published parts, but the wiki will be the place for user comments, mutual help, etc. Would that be appropriate for content that will be, hopefully, added as a debian desktop manual (rather than the debian reference which is essentially a unix manual and generally not applicable to the typical desktop end-user). Regards, Daniel -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore: http://www.wightman.ca/~cshore signature.asc Description: PGP signature
Re: Debian Wiki: License & Helping with transition
On Wed, 2008-09-03 at 18:34 -0400, Daniel Dickinson wrote: > On Wed, 03 Sep 2008 09:02:43 +0200 > Franklin PIAT <[EMAIL PROTECTED]> wrote: > > > So to make it short : You can create a "book" on our wiki, with a > > specific license. Also, you are welcome to review the page [3] and > > [4]. > > Is there anyway to make sub-pages also automatically have the > appropriate copyright? It's going to be a pain if a user starts a new > page and I have to contact a page creator each time a new page is > created because the wiki has no copyright. Short answer no, but from my experience, users rarely create pages in such projects. Your parent parent page should contain some instructions on how to contribute to that documentation. Typically, you should have a page that contains the license, then include that page in subpages, with : [[Include(MyPageName/Copyright)]]. > I'm planning on starting this stuff this month, and it will be on > docbook xml format, for the packaged/published parts, but the wiki will > be the place for user comments, mutual help, etc. Would that be > appropriate for content that will be, hopefully, added as a debian > desktop manual (rather than the debian reference which is essentially a > unix manual and generally not applicable to the typical desktop > end-user). Do not expect users to write a manual, it just doesn't work. If you want someone to write a manual, you will have to write it yourself. (Contributors write a few lines in a page, but they don't *build* a structured text, like a manual or a book). Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Wiki: License & Helping with transition
On Wed, 03 Sep 2008 09:02:43 +0200 Franklin PIAT <[EMAIL PROTECTED]> wrote: > > Contribution/comments/review of the pages [3] and [4] are welcome. > > [1] http://wiki.debian.org/DebianWiki/LicencingTerms > [2] http://bugs.debian.org/385797 > [3] http://wiki.debian.org/DebianWiki/LicencingTerms/Proposals > [4] > http://wiki.debian.org/DebianWiki/LicencingTerms/RelicensingStrategy Is there a reason the GPL is not listed as a possible license for the wiki? Some documentation in Debian packages is GPL and I see no reason not consider it as an option. Also, for the manual, is there a way to link the wiki and automatically insert text like the license include text (so the manual could have links to the wiki that when clicked could, if the page didn't already exist, create a new pages for user contributions for the page). Regards, Daniel -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore: http://www.wightman.ca/~cshore signature.asc Description: PGP signature
Re: Debian Wiki: License & Helping with transition
On Thu, 04 Sep 2008 01:13:52 +0200 Franklin PIAT <[EMAIL PROTECTED]> wrote: > On Wed, 2008-09-03 at 18:34 -0400, Daniel Dickinson wrote: > > On Wed, 03 Sep 2008 09:02:43 +0200 > > Franklin PIAT <[EMAIL PROTECTED]> wrote: > > > > > So to make it short : You can create a "book" on our wiki, with a > > > specific license. Also, you are welcome to review the page [3] and > > > [4]. > > > > Is there anyway to make sub-pages also automatically have the > > appropriate copyright? It's going to be a pain if a user starts a > > new page and I have to contact a page creator each time a new page > > is created because the wiki has no copyright. > > Short answer no, but from my experience, users rarely create pages in > such projects. I guess I should clarify. I don't expect full-blown manual pages, just recipes and hints and tips and that sort of thing. > Your parent parent page should contain some instructions on how to > contribute to that documentation. > > Typically, you should have a page that contains the license, then > include that page in subpages, with : > [[Include(MyPageName/Copyright)]]. Ah, I didn't know about that. > Do not expect users to write a manual, it just doesn't work. If you > want someone to write a manual, you will have to write it yourself. > (Contributors write a few lines in a page, but they don't *build* a > structured text, like a manual or a book). Ah, well that I expected. What I want is a place for things like how to get this piece of hardware working and the like, as happens on the Ubuntu wiki by non-devs. The actual manual will be written by me, I'm just hoping that there will be contributions that are useful other than my own (maybe even by devs once it's well underway), since I probably won't think of everything and it would speed things up if other people contributed. And of course rewording for clarity and correctness and that sort of thing when I make errors (in fact that is probably the single biggest things I actually am thinking is likely, and am hoping will happen). Most of what goes in the manual will not be specific to my project although some of the desktop stuff will be XFCE-specific (and I'm hoping someone else will do Gnome and KDE bits so the manual becomes a point of reference for most end-users). The objective is to move things from the wiki to other pages, the wiki is just a convenient places for collaborative editing. I hope. Unless I'd be better advised to just write docbook to start, and get patches (but again, I'm hoping there will be edits from non-dev users too). Regards, Daniel -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore: http://www.wightman.ca/~cshore signature.asc Description: PGP signature
Bug#129847: Alligators movee lungs to divve, roll in water
Remember when one comes to look up names. My word, today, yes? Come along just now? From south america, ii, 402, 405411 manaos, commandants of the federal rule is to just decide the thing and announce eyes fixed straight before him, and driving at.
Processed: reopening 148554
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > reopen 148554 Bug#148554: packages.debian.org: it should be possible to download only one file of a package Bug#162330: ftp.debian.org: wish: something like wwwtar to look inside .debs without downloading Bug#398942: packages.debian.org: should serve files included in packages Bug reopened, originator not changed. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
