Re: changes and standards documents
Hi,
>>"Marcus" == Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:
Marcus> Great option. Imagine the free software would follow the same
Marcus> criterion. "If you want to publish a variant C compiler, you
Marcus> can always rewrite gcc".
*Sigh*. Again you harp on software, and insist on applying
licenses good for software to everything else, blindly. Makes me
wonder of you actually know why feredom of software is
essential. (If reuse was a major goal, than by and large it has
failed; though there are plenty of exceptions to this statement).
However, since you obviously can't tell the difference between
software and all the other types of documents (I am enlclosing a list
below), I see no point in carrying on this pointless, never ending
debate with you.
manoj
Giving up an ever making marcus see reason
--
I don't make the rules, Gil, I only play the game. Cash McCall
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
3. Types and categories of Documents considered
-----------------------------------------------
Documentation for software
Technical documentation describes the behaviour, usage, and
configuration details about a specific piece of code. It may also
be instructions about how to modify or extend the software.
(Users manuals, etc) Examples include the GIMP Users Manual, the
GCC Internals guide, any source-code written with "literate
programming" tools, etc.
A Standards document
A standard describes is a common set of standard interfaces,
formats, rules, application programming interfaces, common
practice, conventions, etc, that other people are supposed to
comply with in order to facilitate interoperability, consistancy,
or some other public goal outside of the scope of one program or
developer.. Generally, this has the fax-like law: one or two
people adopting it is not of much value, a million people
adopting it and it comes into its own.
Personal opinions
Opinions of a person, whether technical or otherwise, essays,
open letters, USENET postings (assuming proper permission for
redistributin has been obtained, of course).
Works of fiction
Books, novels, essays, short stories, etc. The project Gutenburg
has a collection of works fo fiction for whom the copyright has
expired, there are tohers that give the right of redistribution
with certain restrictions.
Poetry
Defined as imaginative language or composition, whether expressed
rhythmically or in prose. Specifically: Metrical composition;
verse; rhyme; poems collectively; as, heroic poetry; dramatic
poetry; lyric or Pindaric poetry.
Magazines and graphic novels
These are publications where the layout is as important as the
contents. Graphic novels are rapidly gaining mainstream approval,
and there are already contless web-zines and other magazines
distributed purely electronically, and already Debian has several
such mags packaged up.
Art work, paintings, Images, Photographs
Rendered, ray traced, or hand created usig the GIMP, photographs,
line drawings: these are going to become more and more common.
Technical Opinion
Documents which state the opinion of a particular person or group
in relation to a technical matter. Unlike standards, this
material is not binding in an of itself, but serves rather to
influence technical decisions or to explain why or how a
particular technical decision was made. Examples include the FYI
series or RFCs, judicial opinions, NTSB crash investigation
reports, etc.
Instructional material
Documents which are written to teachtechnical material. Unlike
software documentation, this material need not be specific to a
particular piece of software, or even of software itself.
Examples: The guided-walk-through sections of the Kernel Hacker's
Guide, physics textbooks, US Department of Defence field manuals
on the proper way to brush one's teeth, etc.
Reply to: