Wednesday, 2014-11-12
*** wolftune has quit IRC | 00:37 | |
*** wolftune has joined #copyleft | 00:38 | |
*** Tichodroma has joined #copyleft | 02:33 | |
*** wolftune has quit IRC | 03:35 | |
*** clacke has joined #copyleft | 04:44 | |
*** Rastus_Vernon has quit IRC | 05:07 | |
*** bkuhnIdle is now known as bkuhn | 06:14 | |
*** mindspillage has quit IRC | 07:43 | |
*** bkuhn is now known as bkuhnIdle | 07:55 | |
*** Pessimist has joined #copyleft | 07:56 | |
*** clacke has quit IRC | 07:58 | |
*** clacke has joined #copyleft | 07:59 | |
*** bkuhnIdle is now known as bkuhn | 08:38 | |
*** clacke has quit IRC | 08:45 | |
*** clacke has joined #copyleft | 08:47 | |
*** mindspillage has joined #copyleft | 09:19 | |
*** mindspillage has joined #copyleft | 09:20 | |
*** mindspillage has quit IRC | 09:50 | |
*** clacke has quit IRC | 10:10 | |
*** dbs has joined #copyleft | 10:39 | |
*** cmhobbs has joined #copyleft | 10:41 | |
*** cmhobbs has joined #copyleft | 10:41 | |
dbs | Again, first person can work and be an effective approach if, say, there's a given chapter that focuses on the experience of a C&CSC investigation and the intro makes it clear that it was Denver and bkhuhn | 10:42 |
---|---|---|
dbs | But if it's sprinkled throughout the entire text, maybe not so much. | 10:42 |
bkuhn | (BTW, the "new phrase" is CCS. I dropped the & back in the late 2000s when aaronw pointed out that the words 'complete' and 'corresponding' are actually never connected with "and" anywhere in the text of GPLv2 nor GPLv3.) | 10:44 |
bkuhn | (I also never used the 'C' at the end, I guess because I thought sourcecode was one word, and also because GPL calls it "source code" and "source" interchangeably) | 10:45 |
bkuhn | dbs: As pehjota was saying elsewhere, I think first person is a mistake for the Guide, in part because there are so many authors anyway. | 10:45 |
bkuhn | I'm using now a mix of second person for instructive material and and third person when communicating policy motivations and opinions (ala "most copyleft advocates argue") | 10:46 |
*** wolftune has joined #copyleft | 10:57 | |
*** jpgepetto has joined #copyleft | 10:58 | |
*** mindspillage has joined #copyleft | 11:26 | |
*** yrk has joined #copyleft | 11:27 | |
*** yrk has joined #copyleft | 11:27 | |
*** Tichodroma has quit IRC | 11:32 | |
*** Rastus_Vernon has joined #copyleft | 11:34 | |
pehjota | I'd agree that in text written by a small number of authors working closely together the first person is best for describing actions and experiences of the authors. But in text where there are many authors and it's not clear who wrote what, the first person can be confusing and problematic. | 11:50 |
bkuhn | Agreed. | 11:50 |
pehjota | The book Open Advice handles this by having one author write each chapter and listing each chapter's author. I think it works well there, but I'm not sure if that's best for this guide. | 11:51 |
pehjota | Of course, the first person could still be used to include the authors and the audience, e.g. "We can see that …" or "This shows us that …". This is common in some textbooks. | 11:52 |
paul | Or just try avoid first/third person constructs. | 11:56 |
*** yrk has quit IRC | 11:57 | |
bkuhn | Yeah, I think I'm convinced to eradicate first-person-ism in the Guide.... I'd actually already been doing that anyway. | 11:58 |
bkuhn | I still use third person a lot where appropriate, but I'm open-minded if people think it's causing trouble. | 11:58 |
paul | "We can see from how the foo is constructed what polarity of the bar should be." → "The construction of the foo determines the polarity of the bar". | 11:59 |
bkuhn | agreed. | 12:00 |
paul | unless it /matters/ to whom the opinion being given should be attributed to, 1st/3rd person just leads to clutter. | 12:00 |
* pehjota wonders if the academic "we" is somehow derived from the royal "we". | 12:00 | |
bkuhn | But I still need to be able to say: "copyleft advocates generally agree..." for things that aren't facts. | 12:00 |
bkuhn | Particularly for points where this "almost consensus" | 12:01 |
dbs | Academics write "One" rather than "We" | 12:01 |
bkuhn | Oh geez, I hate the "one" thing. | 12:01 |
*** Rixius has joined #copyleft | 12:01 | |
dbs | So do I | 12:01 |
bkuhn | One finds it annoying to read one's own text, no longer written in one's own style, but in a style that pointlessly use the word "one" as if it is the word "man" in German. | 12:02 |
* paul prefers "one" to "we" ;) | 12:02 | |
paul | (least in some cases) | 12:02 |
paul | bkuhn: yeah, when precision matters about who thinks what, "the authors believe", etc. | 12:02 |
paul | but that doesn't mean everything has to be cast in 3rd person :) | 12:03 |
paul | bkuhn: oh definitely, needless use of either just leads to cluttered, flowery text. | 12:03 |
bkuhn | Meanwhile and unrelated, I think an interesting thing is happening organically as I work on the Guide. Specifically, the commit logs are becoming effectively a "commentary" on the work and why it's constructed. I suppose that's what VCS logs are supposed to do, but I hadn't really considered what that meant for a tutorial text (as oppose to software). | 12:21 |
bkuhn | https://gitorious.org/copyleft-org/tutorial/commit/8a3a8434ddc4759c7c2188dc1dc75ca6437e267d is an interesting example of what I'm talking about. | 12:21 |
dbs | good commit log entry! | 12:29 |
dbs | kfogel has pretty expressive entries too | 12:30 |
*** yrk has joined #copyleft | 12:30 | |
*** yrk has joined #copyleft | 12:30 | |
bkuhn | Thanks. :) | 12:39 |
pehjota | The commit message is longer than the change is. :) | 13:50 |
bkuhn | pehjota: as it should be, I think. :) | 13:53 |
pehjota | I've had that happen a few times in software repositories. I'm starting to think though that maybe some such commentary should go directly in the work, as comments or footnotes, unless the information is sufficiently specific and generally unimportant to require deep repository investigation to find. | 13:58 |
*** bkuhn is now known as bkuhnIdle | 14:11 | |
warp | pehjota: I think the repository as a whole should be considered the work. | 14:13 |
warp | pehjota: to me, the "preferred form of modification" is the dvcs repository with full history. | 14:13 |
*** Peuc2 has joined #copyleft | 14:23 | |
*** Peuc has quit IRC | 14:26 | |
*** Peuc2 is now known as Peuc | 14:26 | |
*** Peuc2 has joined #copyleft | 14:30 | |
*** Peuc has quit IRC | 14:34 | |
*** Peuc2 is now known as Peuc | 14:34 | |
*** karen has joined #copyleft | 14:39 | |
*** karen has joined #copyleft | 14:40 | |
yrk | warp: that would be hard to distribute on a t-shirt | 14:42 |
pehjota | warp: You know, you could extend that to say that the mailing list(s) on which changes are posted and discussed before merging should be included with the work too. And the bug tracker. :) | 15:00 |
pehjota | warp: But yeah, having (D)VCS commit logs for reference is often useful when modifying a work. | 15:01 |
pehjota | (As would be a snapshot of the developer's thoughts when writing some parts of some code, heh.) | 15:01 |
*** karen has quit IRC | 15:20 | |
bcotton | i’ve considered taking fontana’s commit history from copyleft-next and turning it into a short book about the history of the gpl. | 15:25 |
*** bkuhnIdle is now known as bkuhn | 15:26 | |
bkuhn | bcotton: ??? I'm confused, is there really *that* much history of GPL in copyleft-next's Git repository? I haven't read every commit message, but that honestly seems unlikely. | 15:27 |
*** karen has joined #copyleft | 15:28 | |
bkuhn | bcotton: .... but, if you want to write a material about the history of the GPL, I suggest you improve the sections in gpl-lgpl.tex in this project; there's a brief history of GPL already there. | 15:28 |
bkuhn | (and you could incorporate Fontana's work from copyleft-next's DVCS logs, since that's CC0) | 15:28 |
bcotton | bkuhn: i might be exaggerating a bit. when the project first started there were a lot of multi-paragraph commits. for someone who didn’t previously know the history, it was a great primer (though undoubtedly incomplete and in some cases disputed) | 15:29 |
bcotton | bkuhn: i definitely intend to do just that once i learn how to not oversubscribe myself quite so much. completing my thesis should free up a little bit of time here soon | 15:29 |
bkuhn | Yeah, so I'd appreciate if you'd take a look at what's in the tutorial repository now, and offer merge requests to add what you learned from copyleft-next repository. | 15:30 |
bcotton | will do. i just won’t make any promises about a timeline :-) | 15:31 |
bkuhn | No problem. This is a marathon, not a sprint, anyway. | 15:31 |
bkuhn | (Even though I've been sprinting on it for two weeks straight almost, as I did back in Feb. 2014, but I'm going to have to stop that soon and go back to marathon mode. ;) | 15:32 |
*** karen has quit IRC | 15:33 | |
*** mlinksva_ is now known as mlinksva | 16:51 | |
*** jpgepetto has quit IRC | 18:01 | |
*** cmhobbs has quit IRC | 18:15 | |
*** Peuc2 has joined #copyleft | 18:59 | |
*** Peuc has quit IRC | 19:02 | |
*** Peuc2 is now known as Peuc | 19:02 | |
*** Peuc2 has joined #copyleft | 19:05 | |
*** Peuc has quit IRC | 19:06 | |
*** Peuc2 is now known as Peuc | 19:06 | |
*** Peuc2 has joined #copyleft | 19:11 | |
*** Peuc has quit IRC | 19:12 | |
*** Peuc2 is now known as Peuc | 19:12 | |
*** Peuc has quit IRC | 19:25 | |
*** Peuc2 has joined #copyleft | 19:26 | |
*** Peuc2 is now known as Peuc | 19:26 | |
*** bkuhn is now known as bkuhnIdle | 19:32 | |
*** karen_ has joined #copyleft | 19:39 | |
*** mindspillage has quit IRC | 20:30 | |
*** yrk has quit IRC | 20:54 | |
*** Rastus_Vernon has quit IRC | 21:17 | |
*** botCopyleftLog has joined #copyleft | 23:05 | |
*** Pessimist_ has joined #copyleft | 23:07 | |
*** warp_ has joined #copyleft | 23:10 | |
*** Pessimist has quit IRC | 23:12 | |
*** warp has quit IRC | 23:12 | |
*** warp_ is now known as warp | 23:12 | |
*** karen_ has quit IRC | 23:30 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!