guide Changelog

git guide

Changelog @ 85bbbf1ec649 - showing 100 out of 849 revisions

Go to tip of repository Branch filter:

bkuhn	85bbbf1ec649	13 months ago	Gitorious Apocalypse: even more gitorious URLS I believe these are the last few Gitorious URLs master
bkuhn	eb51d8327cf8	13 months ago	Gitorious Apocalypse: remove gitorious more URLs The Gitorious URLs are now dead. A few Gitorious URLs continued to appear in the front matter of the Guide itself. This fixes those links to with k.copyleft.org equivalents.
bkuhn	56ec3c68ee58	2 years ago	This clearly should have been \ref all along.
bkuhn	0b3b7ecffd3a	2 years ago	Notice in Contributing section about individuals. Individuals act on their own behalf in this project, regardless of who sponsors it. 2
bkuhn	4dcf54510828	2 years ago	Gitorious Apocalypse: recovery existing clone These instructions are simple and I've tested them.
bkuhn	0a5d6db00372	2 years ago	Gitorious Apocalypse: remove all gitorious URLs The Gitorious URLs will disappear in the next few hours. The canonical hosting location of this project is now on copyleft.org. Specific gitorious URLs are generally replaced with k.copyleft.org, which is copyleft.org's self-hosted Kallithea instance.
bkuhn	26def8538a10	2 years ago	FIXME note about restoring UCITA reference.
bkuhn	a8d58d6b65d3	2 years ago	Remove stray open parenthesis.
bkuhn	d3ce0a8a2fff	2 years ago	Correct spelling of acronym.
bkuhn	73a7028469b8	2 years ago	More words that don't appear in some dictionaries. Add to the LocalWords list for Emacs spell checker.
bkuhn	3b357f274733	2 years ago	Update bkuhn & tony copyright notices for 2015 After last commit, there has been new copyrightable material copyrighted by these two individuals added in 2015.
bkuhn	4067c5f9915f	2 years ago	Clarify & expound on issue of warranty disclaimer The existing paragraph on this issue was inadequate, since it punted entirely to GPLv2§11 for dealing with critics' claims of unenforceability. That left a mistaken impression of validity of such claims. The commit herein adds reference to CIGS, which likely permits GPL's sort of warranty disclaimer in most jurisdictions, and also bolsters the reference to the UCC earlier in the section. However, given academic debate about the applicability of CIGS to software licenses, this commit includes a footnote referencing the two sides of that debate. Tony Sebro and I co-drafted these changes together. Signed-Off-By: Tony Sebro <tony@sfconservancy.org> Signed-Off-By: Bradley M. Kuhn <bkuhn@ebb.org>
bkuhn	e62b08eb9cb5	2 years ago	Note that most USA states/commonwealths adopt UCC. While most USA lawyers will know this as simple fact, the tutorial wants to welcome an international audience and non-lawyers too. As such, this dependent clause is worth adding.
bkuhn	40fa2e6685f8	2 years ago	Clarify who "most people" meant, drop UCITA ref. The intent of this text was to point out that most users don't actually believe they get warranties, which is still surely correct, given that GPL disclaims warranties in the same manner nearly every software license -- proprietary or free -- does anyway. Also, the forward-reference to the later section's discussion of UCC should be hinted at here. There is no explicit reference to UCC made here, but it is encompassed in "many local laws", since the later section mentions the specific section of UCC involved. Meanwhile, the reference to UCITA is dropped, but perhaps it should be reintroduced in other text in the main warranty section. UCITA has had much less policy impact than was expected when the original version of this text was written. It might be useful to ask policy folks and attorneys from Maryland and Virginia who might be able to help explain what impact UCITA has had being on the books only there.
bkuhn	555a72beb114	2 years ago	Suggestions for in depth discussion of GPLv2§2(a) GPLv2§2(a) is mentioned quite cursorily. Olly Betts suggests more coverage here might useful on IRC. I noted some ideas after he suggested it.
bkuhn	ec2abce02114	2 years ago	Rework text to introduce definition of CCS. CCS ultimately wasn't mentioned until much later in the GPLv3 sections, where, ironically, we have to point out that GPLv3 defined the term as "Corresponding Source" [0], not CCS, and explain why GPL enforcement wonks still say CCS. This rework now introduces the acronym at the natural moment: while describing GPLv2§3's use of the words "complete" and "corresponding". Adding that made the section even more disjoint than it already was. I put in some \subsection's to make it slightly less so, and did some wordsmith work on surrounding text. [0] I wish some GPLv3 drafter had asked me what to call the defined term so that I could point out what fit standard parlance. :)
bkuhn	15ae6f3a175c	2 years ago	Wordsmith this tortured text.
bkuhn	dca1aa011573	2 years ago	"by definition" is clearer here than "by default" There's probably another phrase we could use that's even better.
bkuhn	f22e9b7209f5	2 years ago	Make this item FIXME-URGENT. I've set this to FIXME-URGENT as I will merge this into a public branch after this commit, and I want it clear that we cannot merge into next or master until this is resolved. merge-request-027-working-solution
bkuhn	076f7b7cd8e3	2 years ago	Preservation of implied patent license is unique. This footnote, co-drafted by me and Richard Fontana, explains the apparent uniqueness GPLv3's preservation clause for GPLv2's original implied patent license. Fontana pointed out this distinction with commercial patent licensing. I noticed as a further point that even some copyleft licenses, let alone non-copyleft Free Software licenses, fail to include any clauses preserving implicit patent license grants. Such is certainly of concern for those licenses that contain explicit patent licensing provisions. Fontana notes that during GPLv3 process, he was concerned that an explicit patent license in GPLv3 might provide a basis for some to later argue an implied patent license was no longer present. GPLv3§11's final paragraph assures its safety.
bkuhn	1f6399f54ece	2 years ago	Rework & expand discussion: express patent license Upon consultation with Richard Fontana, we drafted together this rewrite of the original paragraph discussing this issue. The original paragraph was tersely written and indeed accurate. However, it was likely comprehensible only to those already familiar with patent licensing regimes and systems. As such, it fit poorly in the tutorial, which is designed for all policy makers who care about copyleft, who may in fact be new to patent policy and licensing. Please note: Richard Fontana <fontana@sharpeleven.org> dictated to me some of this text, and therefore he is likely a copyright and "creator" (per CC-BY-SA 4.0) of some of this text. In fact, since we wrote it collaboratively, I suspect Fontana and I are co-copyright holders and co-creators of this commit.
bkuhn	5eb476183bbc	2 years ago	Punctuation fix: Add missing period.
bkuhn	dc0714a3ef85	2 years ago	Formatting change: use itemize here instead.
fontana	59dda6ad9091	2 years ago	Uncommented material on implied patent licenses and GPLv3 sec. 11 definition of "patent license", with added sentence noting final paragraph of sec. 11.
bkuhn	2a42c6fb7e48	2 years ago	FIXME describing what introduction should say. We need an introduction, particularly if we merge the CC-BY-SA material that @mlinksva provided.
bkuhn	0adba8392352	2 years ago	FIXME re: "dynamic linking delayed" to runtime. The existing text of the Guide hints at this point but doesn't discuss it directly. This FIXME is merely a reminder note to investigate this issue in further detail and perhaps add text here on the question.
bkuhn	eab5efb42b23	2 years ago	Null character needed at end of a LaTeX sentence.
bkuhn	0e49270eb14e	2 years ago	Contributing text from third-party works. Integration of text from third-party works is complicated, since the text must be incorporated to flow properly with the rest of the Guide. Also, historical archiving commits are particularly useful in such situations. This tutorial explains how to contribute such additions for this project.
bkuhn	04a38b87ecf6	2 years ago	Order matters in \usepackage{hyperref}. The problem exhibited only in PDF files, wherein \ref{} links to appendix chapters referred instead to regular chapters. http://tex.stackexchange.com/questions/77886/fncychap-and-hyperref-messes-up-page-references suggest that loading hyperref second fixes the problem. This indeed worked.
mlinksva	27739cd92ee0	2 years ago	copyleft.org tutorial, not conservancy policies
mlinksva	ce1c96a1a1a0	2 years ago	Make attributions consistent. Also, fix a few spurious characters.
mlinksva	f4fd426471cd	2 years ago	consistent capitalization of verbs, no reason to copy capitalization within CC-BY-SA or any other license
bkuhn	79c5b890eb8e	2 years ago	Consolidate copyright notices into single place. Historically, this project used (more-or-less) a file-by-file copyright inventory. This commit ends that practice. The project now has a single toplevel copyright inventory, stored exclusively in comprehensive-gpl-guide.tex (so that it appears also in compiled versions of the Guide as well). The side-effect of this commit is that the parts may no longer be easily publishable separably without (at least) the additional work of copyright notice reconstruction. This may in particular create a challenge for the FSF, who has historically selectively published sections of this Guide as materials for its CLE classes. However, without this change, this Guide will eventually suffer from the inherent problems in maintaining file-by-file copyright inventory. Circumstances simply dictate a single, top-level copyright and license notice for the entire Guide. In addition to consolidation of copyright notices, I've also herein updated my historical copyright notices to properly credit me for my own work done in 2003 through 2005. I've also updated the license notice to reflect the changes made by the previous commit and related issues.
bkuhn	ce9168a9af5b	2 years ago	Citations of third-party works in appendix only. As alluded to in 2ea19b71d4a917babb29024f06acabfe73309f40 's commit message on 2014-12-17 19:52:15 -0500, keeping any information on a part-by-part basis is difficult and error-prone, since there exists no reliable way to auto-generate such information accurately. Therefore, citations to third-party works, in addition to remaining fully documented in the commit log as they always have been, are now placed in specifically one location in the body of the text itself: a single appendix specifically designed for that purpose. In this manner, contributors have no house-keeping work regarding citations. Contributors need only list third party works and links in one place: third-party-citations.tex. Documentation in CONTRIBUTING.md for making contributions of third-party works is left as a TODO.
bkuhn	1da1b24a1439	2 years ago	Wordsmith sentence after phrase "such software". I think Fontana's change a few commits back which s/it/such software/ in this sentence is a useful one. However, the entire sentence reads even worse because "such software Free Software" looks so strange as a string of words in the middle of the sentence. This change is the best rework I could find that resolved the problem. It's probably not the best option but is certainly an improvement.
bkuhn	c5866203ee02	2 years ago	Replace editorial commentary w/ FSF's link. My personal comment here, which I wrote on 2003-05-26 (see f05ce6c657e07a5e6c6def3f7ff8cb2b2bcf6246 ), is probably not particularly useful. I still tend to use the phrasing as original stated in the removed text herein; however, I'm admittedly the only one. I don't deny that I hope to coin some terminology usage through my work on this Guide, but this particular use of "nonfree software" to mean "noncommercially proprietary" is not so important IMO that this Guide must coin it. The FSF's page on this doesn't make that distinction, and has much more detail on this issue than this section does. Therefore, the personal statement is removed, and the organizational statement on the FSF's site is instead linked to.
fontana	628ffb60207e	2 years ago	Some editorial changes. Commenting on one: the initial-caps stylistic preference for "Free Software" (though it contradicts prevailing usage, including that of RMS and the FSF) ought to be respected, but I think it is confusing to capitalize the 'S' when referring to nonfree software as "non-Free Software". So I changed this to "non-Free software" and also implicitly acknowledged that the preference for "non-Free" over "nonfree" is the editor-in-chief's stylistic idiosyncrasy.
fontana	170f507ac67a	2 years ago	Some editorial changes.
fontana	dab88657a43a	2 years ago	"GNU project" -> "GNU Project".
fontana	ff7790d6085d	2 years ago	"business people" -> "businesspeople"
bkuhn	cd25fdd2c919	2 years ago	Document work-around for 'next' branch rebases. Upstream in the copyleft.org tutorial repository, the next branch is sometimes rebased against the master branch. (For example, this occurs when there have been quick fixes done on 'master' while new drafting occurs on 'next'.) This procedure, while convoluted, is the best way I've found to compensate for this problem. Hosting sites like Gitorious really aren't designed for rebased branches.
bkuhn	81157b31366a	2 years ago	No instructions for 'master';just note possibility Ultimately, users will probably pick either 'master' or 'next' to submit changes anyway, so just leave the instructions to refer to 'next' and note that they could replace 'next' with 'master'.
bkuhn	ea09b83e0016	2 years ago	It's useful to post merge requests on mailing list
bkuhn	c830d8b51bc8	2 years ago	Typo fixes.
bkuhn	fd2318650e15	2 years ago	Detailed merge request instructions for Gitorious. Most Gitorious users know this procedure, but it seems useful to document it in great detail here, since copyleft.org seeks contributions from those who might be knew to Git, and those who are more familiar with procedures of other collaboration sites.
bkuhn	57e8fa1cb2d7	2 years ago	Note merge request should usually target next. Some targets to master are acceptable, though.
bkuhn	e1373883c9ab	2 years ago	More about the next branch.
bkuhn	6b441fa05742	2 years ago	Note TODO list and lack of bugtracker.
bkuhn	756748a79b07	2 years ago	Wordsmith this text.
bkuhn	fd8fdee5bf32	2 years ago	Rewrite text to not sound so BDFL-ish.
bkuhn	b855c3f4ca26	2 years ago	Note that our tools are themselves copylefted.
bkuhn	d3baa07f5f20	2 years ago	CONTRIBUTING.md now canonical such information.
bkuhn	883e2078ece4	2 years ago	Logs have more than just committers.
bkuhn	8498c557d576	2 years ago	Correct title and formatting. There was a typo in the title and a stray comma.
bkuhn	71c4a749744e	2 years ago	Begin section on merge/patch workflow.
bkuhn	cacdffc1920f	2 years ago	First draft of CONTRIBUTING.md file.
Andrew Engelbrecht	daced4361072	2 years ago	move long parenthetical text out of short sentence it's easier to read this way.
Andrew Engelbrecht	5879dd334413	2 years ago	correct literal meaning of phrase GPL protected code-bases don't demand industry trust, modern industry trusts GPL protected code-bases.
Joshua Wells	07912cb5fc40	2 years ago	Fix broken link
bkuhn	1ed31baa283a	2 years ago	Gerund use was incorrect grammar here.
bkuhn	b0801a2b8a2f	2 years ago	Clarify sentence. Make this sentence a bit clearer.
bkuhn	e01c6bf303e1	2 years ago	Remove spurious line. This line was carried over as a paste from a previous version of the paragraph above it, and is now no longer needed.
bkuhn	6a0567ac6fdc	2 years ago	Make descriptions uniform. Descriptions in this list should be uniformly worded.
bkuhn	48e517cb83d3	2 years ago	Additional published work. This publish work was also referenced in the old commit logs already, but now that we have a list in the work itself, it can also be listed here.
bkuhn	bd80fd47031a	2 years ago	List missing co-author on this published work. Karen Sandler was co-author of the work herein referenced, and was accidentally left off the list of authors in an earlier commit.
bkuhn	22fe0956db83	2 years ago	Add hyperlinks to remixed published works. Now that a list of published works is part of the document proper, it is reasonably practicable to add hyperlinks to those works.
bkuhn	b75c05d7bb10	2 years ago	Provide additional href link command. Add additional command that can be used in place of href where appropriate.
bkuhn	2ea19b71d4a9	2 years ago	Remove incomplete lists of authors entirely. The lists of authors in each part has been continually out of date and incomplete. There are multiple examples, here are a few: * In September 2005, John Sullivan made improvements and was not placed on the Authors lists until I did so in a March 2014 commit. * In March 2014, Martin Michlmayr submitted many patches, but was not placed on the Authors lists until I did so in an April 2014 commit. There is no easy way to keep these Authors lists current, and they aren't necessary under CC-BY-SA-4.0 anyway, so I herein remove the Authors lists. Additionally, previous commit added "published sources" in each part, which is more static and easier to keep up to date and provides similar information.
bkuhn	3605394f30b0	2 years ago	List published works & link to Git logs. References and details regarding these published works from which some text was incorporated already appeared in the commit logs in great detail. The information, already fully available in the Guide's Git logs in full compliance with CC-BY-SA-4.0 §3(a)(1-2), now appears in summary form additionally in the compiled PDF/HTML/Postscript output.
bkuhn	19c75b012cb3	2 years ago	Link to sponsors.
bkuhn	251bcc69475e	2 years ago	Typo fix.
bkuhn	30e4942891c6	3 years ago	Reword paragraph; Include ref: "standard requests" Mostly these changes are wordsmith, but I added a note that violators should ask for the "standard requests" for compliance to be adequate.
bkuhn	b9f7a402a6a7	3 years ago	Rewrite paragraph for readability.
bkuhn	39ead95e9bea	3 years ago	Rewrite paragraph to fix better with section. This paragraph was from text brought through from another document, and as such, while this section was built "around it", the text itself was stylistically different and otherwise problematic. This change brings it into form with the rest of the document.
bkuhn	3e88116a43cd	3 years ago	Small grammar fix.
Martin Michlmayr	cbfa27466e40	3 years ago	Update references to gitorious repo
mlinksva	5ffc6153202e	3 years ago	Reword mind-reading statements. Merge requested proposed by @mlinksva has been changed slightly by @bkuhn because there were changes to the README.md file since the merge request was submitted that made some of the changes moot.
bkuhn	b920a7a4b827	3 years ago	Change links to copyleft.org site (now it exists)
mlinksva	312718cda029	3 years ago	it's is
mlinksva	a5fa6ca556b5	3 years ago	2 paras in a row start with However,
mlinksva	b35e89a8d85d	3 years ago	more powerful interests implicitly allied
mlinksva	a867743eb394	3 years ago	para prohibits anyone
mlinksva	784976f1e3f1	3 years ago	consistent singular
mlinksva	38329c1b5a4e	3 years ago	"an set"
mlinksva	126d4fc04131	3 years ago	cap The in middle of sentence
mlinksva	b8ec5dbbe92b	3 years ago	it indicates
mlinksva	5f18dfd82f24	3 years ago	add needed connecting word/punctuation
mlinksva	4b25ade52060	3 years ago	two "Furthermore..." sentences in a row
mlinksva	e52a3d32dc52	3 years ago	relate sections -> related sections
mlinksva	5084f8b60f33	3 years ago	disparate not desperate views
mlinksva	057263d799bb	3 years ago	"would sometimes allowing distributors"
mlinksva	26c0a26169b4	3 years ago	"designed as part to permit" -> "designed to permit"
mlinksva	706e29388f10	3 years ago	consistent plural examples
mlinksva	5bc731e260c9	3 years ago	"includes with particular examples" drop "with"
mlinksva	95ff20c42029	3 years ago	"rather bulk term" -> "rather bulky term"
mlinksva	9641e72df0b0	3 years ago	consistent fn follows punctuation
mlinksva	37bdf9caddc1	3 years ago	typos/extra words
mlinksva	d3f9715bce8e	3 years ago	"because GPLv2~\S2(b)" with nothing following doesn't work in discussion of that section, removed
mlinksva	fcb21b4a381e	3 years ago	"does grants such permission"
mlinksva	468946040bfc	3 years ago	"the Maryland"

< 1 2 3 4 5 .. 9 >

Login to Your Account

git guide