[PHP-DOC] Re: Russian translation

[Alexey Shein]

2010/10/5 Simion Onea :
> Greetings, Alexey!
> Yes, it's definitely ok to contact Antony Dovgal directly. But he
> should have seen your message sent to the mailing list. Maybe he is
> away for the moment.
> If you still don't receive any replies from other translators, you can
> start working on the translation (update the obsolete files) and when
> you have 2-3 files ready, present them to this mailing list
> (phpdoc@lists.php.net) and one of the SVN administrators (Philip or
> Hannes or somebody else) will grant you commit rights to the Russian
> translation.
> I did this procedure when I started working on the Romanian translation.

I think it would be better for me to continue translation so somebody
will appear eventually.

> I suggest to start with "language-defs.ent", "language-snippets.ent"
> and other files in the base directory since they are most important.

My thoughts were the same, so I've already done with language-defs.ent
and currently work on language-snippets.ent, I'll post my work here
when I'll be done if nobody answers on the doc-ru list.

--
Regards,
Shein Alexey

Re: [PHP-DOC] Russian translation

[Simion Onea]

2010/10/4 Alexey Shein :
> Hello again!
> Thanks for answering, Simion. You were right, ru/translation.xml
> contains exactly this address (doc...@lists.php.net). I wrote there 4
> days ago, but still nobody answers. Should I contact directly the
> maintainer, Antony Dovgal?
> Another problem is that russian manual doesn't compile at all. It
> seems to be very obsoleted, and some errors refer to english version
> (when I run with --enable-xml-details) which is very strange to me,
> because english version compiles just fine when taken standalone.

Greetings, Alexey!
Yes, it's definitely ok to contact Antony Dovgal directly. But he
should have seen your message sent to the mailing list. Maybe he is
away for the moment.
If you still don't receive any replies from other translators, you can
start working on the translation (update the obsolete files) and when
you have 2-3 files ready, present them to this mailing list
(phpdoc@lists.php.net) and one of the SVN administrators (Philip or
Hannes or somebody else) will grant you commit rights to the Russian
translation.
I did this procedure when I started working on the Romanian translation.

I suggest to start with "language-defs.ent", "language-snippets.ent"
and other files in the base directory since they are most important.

Regards,
Simion.

Re: [PHP-DOC] License for code examples in the PHP manual?

[Robinson Tryon]

On Mon, Oct 4, 2010 at 3:03 PM, Daniel Brown  wrote:
>    I'm of the opinion that we should license all
> machine-interpretable examples (i.e. - "code snippets") in both the
> official documentation usage examples and user-submitted examples
> alike - including those from the mailing lists and archives - under
> either the MIT or New BSD license, so it was good to see someone else
> mention those two explicitly.  A simple ratification to the license
> information pages would suffice.  Exempli gratia:
>
>        "The PHP manual text and user-submitted comments are released
> under the Creative Commons Attribution 3.0 License, Copyright (C) the
> PHP Documentation Group, with the exception of machine code regions
> (AKA - "code snippets") in the documentation or freely submitted by
> the public, which is licensed under [MIT/NBSD]."

As suggested in the DFSG FAQ, I think that a dual-licensing scheme
would provide the most clarity and flexibility for the code embedded
in the documentation. (I'd also suggest putting the copyright notice
before the license name, otherwise it's unclear whether it is the
manual or the CC license that is copyright by the PHP Doc Group!)

To riff off of your example:

"The PHP manual is Copyright (C) the PHP Documentation Group, and is
released under the Creative Commons Attribution 3.0 License. The
machine code regions (AKA - "code snippets") in the documentation or
freely submitted by the public, are also licensed under the
[MIT/NBSD]."

I'm sure that there's a good way to tighten up the language about the
"example code"/"code snippets" a bit. I'm sure we could find a lawyer
or two to review the text, if it would be helpful.

>    That said, in all technicality, anything presently in existence on
> the site is licensed under the CC-BY license, plain and simple.  It
> would not be difficult to prove it in court, as there are literally
> thousands of third-party points of reference as to what code was
> present during the Attribution licensing.  It's not an interpretable,
> subjective case - it's black-and-white reality.  Exhibit A existed at
> Date-And-Time B, whereby it was legally restricted under License C.

Right, that's the starting point.

I assume that the PHP Doc Group has copyright to all of the
non-user-submitted code examples, so changing those over would just
involve a (hopefully not too arduous) internal process.

As for user-submitted code, I assume that the submission form does (or
could easily) include a note about licensing or assigning copyright.
If the Doc Group already has a sufficiently broad license to the
existing content, as has been suggested in other emails, then
relicensing these components should be pretty straightforward.

>    One argument could exist, though, in the case that a user submits
> a code snippet also licensed under the CC-BY license.  This could
> create a legal paradox

This is a good reason to put a clearly-worded notice on the submission
page. Here's the text that Wikipedia puts on their edit pages:

"Content that violates any copyrights will be deleted...You
irrevocably agree to release your contributions under the CC-BY-SA 3.0
License and the GFDL. You agree that a hyperlink or URL is sufficient
attribution under the Creative Commons license. See the Terms of Use
for details."

Basically you have to trust your contributors to actually hold
copyright to their submissions, or to have knowledge that they are
under a sufficiently permissive license (i.e. one that's CC-BY and
NBSD/MIT -compatible)

> It is for this reason I remove any
> and all notes mentioning licensure in any form.  Further, because all
> Copyright is transferred by agreement from the submitter - of his/her
> own free accord - during the submission process, any claims to
> Copyright of any submission or portion thereof is also removed
> immediately upon discovery.

Based on this it looks like the PHP Doc group holds the copyright to
all of the material, so there's no barrier on that front to
dual-licensing.

--R

Re: [PHP-DOC] License for code examples in the PHP manual?

[Daniel Brown]

On Mon, Oct 4, 2010 at 13:35, Robinson Tryon  wrote:
>
> If The PHP Doc Group believes that the CC-BY provides a framework
> under which a simple attribution line like that is sufficient, then I
> suggest they grease the wheels and calm the lawyers by clarifying it
> with an explicit, very permissive license like the New BSD or MIT.

I'm of the opinion that we should license all
machine-interpretable examples (i.e. - "code snippets") in both the
official documentation usage examples and user-submitted examples
alike - including those from the mailing lists and archives - under
either the MIT or New BSD license, so it was good to see someone else
mention those two explicitly.  A simple ratification to the license
information pages would suffice.  Exempli gratia:

"The PHP manual text and user-submitted comments are released
under the Creative Commons Attribution 3.0 License, Copyright (C) the
PHP Documentation Group, with the exception of machine code regions
(AKA - "code snippets") in the documentation or freely submitted by
the public, which is licensed under [MIT/NBSD]."

That said, in all technicality, anything presently in existence on
the site is licensed under the CC-BY license, plain and simple.  It
would not be difficult to prove it in court, as there are literally
thousands of third-party points of reference as to what code was
present during the Attribution licensing.  It's not an interpretable,
subjective case - it's black-and-white reality.  Exhibit A existed at
Date-And-Time B, whereby it was legally restricted under License C.

One argument could exist, though, in the case that a user submits
a code snippet also licensed under the CC-BY license.  This could
create a legal paradox: the code submission would be licensed under
the CC-BY attributed to the Docs Group, with dual required attribution
to the submitter.  Only under this case, however, could it be true.  A
user claiming release under a less-restrictive license would then be
overruled by the agreement during submission that it becomes the
property of the Docs Group, with the current license taking immediate
effect.  Conversely, a more-restrictive license than any currently in
place would effectively nullify the validity of the submission (which
should force its removal), because any license of greater restriction
would explicitly disallow re-licensing by any party other than the
Intellectual Property (IP) holder.  It is for this reason I remove any
and all notes mentioning licensure in any form.  Further, because all
Copyright is transferred by agreement from the submitter - of his/her
own free accord - during the submission process, any claims to
Copyright of any submission or portion thereof is also removed
immediately upon discovery.

-- 

Network Infrastructure Manager
Documentation, Webmaster Teams
http://www.php.net/

Re: [PHP-DOC] Russian translation

[Alexey Shein]

Hello again!
Thanks for answering, Simion. You were right, ru/translation.xml
contains exactly this address (doc...@lists.php.net). I wrote there 4
days ago, but still nobody answers. Should I contact directly the
maintainer, Antony Dovgal?
Another problem is that russian manual doesn't compile at all. It
seems to be very obsoleted, and some errors refer to english version
(when I run with --enable-xml-details) which is very strange to me,
because english version compiles just fine when taken standalone.

2010/9/29 Simion Onea :
> 2010/9/29 Alexey Shein :
>> Hello, Simion!
>
> Hello, Alexey!
>
>> Thank you for answering. It seems ru version contains is a lot of
>> files without revision numbers.
>
> That's most unfortunate! Maybe you can use the modification date of
> files to find out approximately what is the revision of the file. But
> that will not be very accurate. The only solution is to to check every
> file from top to bottom, update the translation and put the necessary
> EN-Revision number (the last revision of the English file). Later you
> will be able to compare the revisions and see the differences.
>
>> BTW revcheck.php script produces a lot of notices, I had to manually
>> set error_reporting level like this
>> $ php -d error_reporting=30711 doc-base/scripts/revcheck.php ru > 
>> revcheck.html
>> I attached the resulting html to this letter.
>
> Indeed it produces a lot of notices. I agree here.
>
>> Could you clarify for me ru-doc team lists address, is that
>> doc...@lists.php.net? It would be better for me to write there.
>
> Yes, that's the address of the mailing list. Also check the file
> "ru/translation.xml".
>
> Regards,
> Simion.
>

-- 
Regards,
Shein Alexey

Re: [PHP-DOC] License for code examples in the PHP manual?

[Robinson Tryon]

On Mon, Oct 4, 2010 at 9:59 AM, Brandon Savage
 wrote:
>
> The CC-BY license states [...some things...]
> ...
> This is the provision from which I derived that fair use avoids infringement
> even if credit is not given.

(IANAL) but it's entirely possible that a Fair Use defense would be
successful against claims of copyright infringement...

>
> That being said, if it is the opinion of the group that the CC-BY combined
> with the provisions of fair use do not protect someone who uses the
> snippets, then they simply need to give credit.

...that being said, I'm not sure that even the group's opinion is
strong enough to provide sufficient legal protection for "snippets,"
(and how long is a snippet, anyhow?).

What I mean is, even if The PHP Documentation Group makes a formal
statement that in their opinion the CC-BY license on the manual allows
people to make use of example code as long as they just provide
attribution, that formal statement might not hold up in court.

> FWIW I don't see a significant problem here with giving credit. A line in a
> README file that says "Some snippets adapted from documentation provided by
> The PHP Documentation Group" would solve the issue entirely. The specific
> names of the individuals that constitute the PHP Documentation Group are
> irrelevant; the license says "The PHP Documentation Group" is who owns the
> copyright, so that's who gets the credit.

That level of attribution sounds compatible with just about every
license out there.

If The PHP Doc Group believes that the CC-BY provides a framework
under which a simple attribution line like that is sufficient, then I
suggest they grease the wheels and calm the lawyers by clarifying it
with an explicit, very permissive license like the New BSD or MIT.

> I still don't see a significant issue or a reason to change our licensing.
> Furthermore, I don't see why we should change our license to help out the
> GPL folks, especially when they've shown considerable disregard for the
> rights of others in the software community, most recently in the fight over
> Wordpress themes. So PHP should help out the GPL community, but the GPL
> community screws the PHP community? I think not.

I think that the "PHP community" and "GPL community" share a number of
important goals, such as the promotion of FOSS, the empowerment of
users with powerful tools that they can modify and run themselves, and
a drive to write the best software available.

If one of the primary goals of the PHP community is to promote the use
of PHP, then I would suggest that the leaders make it as easy as
possible for people to start programming in the language, even if
means giving people the flexibility to write new code and re-use
example code under the GPL or a proprietary license.

--R

Re: [PHP-DOC] License for code examples in the PHP manual?

[Hannes Magnusson]

On Mon, Oct 4, 2010 at 16:06, Jesus M. Castagnetto
 wrote:
> Pardon this old doc dinosaur for meddling in this thread, just a couple of
> comments:
> - IIRC there was never a "notes group" as such. It was mainly a mailing
> list, some code we hacked and some rules of thumb, and whoever had the time
> will chip in ad do some notes housekeeping once in a while. Ergo, the notes,
> code and text should formally be responsability of the doc group (which is a
> changing entity over the years).
>
> - Not sure as pointed out by Brandon, that theres is a need for licensing
> code snippets separately, they usually are exemplars of concepts and
> techniques, small and simple, and not significant enough to warrant all that
> work (being that there is a provision for "fair use"). I would suggest the
> current doc maintainers to use Occam's razor in this respect :-)

its quite scary to apply Occam's razor on legal matters.. :)

Robinson point is that the GPL license is incompatible with the
current license of all examples and user contributed codes in the
manual.
Be it edgecase incompatibility or what, we need to take a conscious
decision of either ignore it or fix it.. :)

-Hannes

Re: [PHP-DOC] License for code examples in the PHP manual?

[Brandon Savage]

On Mon, Oct 4, 2010 at 7:24 AM, Hannes Magnusson  wrote:

> On Mon, Oct 4, 2010 at 12:08, Robinson Tryon 
> wrote:
> > It shouldn't take too long to fix this -- I'd just add a note in the
> > documentation section of the PHP license page along the lines of "All
> > example code in the PHP manual, including user notes, are additionally
> > available under the terms of the New BSD License," and then link to a
> > local copy of the New (i.e. the 3-clause) BSD License.
>
>
> The fix is easy, but it has many legal implications :)
>
> We also would have to update several other pages describing the manual
> pages, such as the add-notes page, and the license document in the
> manual itself.
>
> Also, who exactly is "The Documentation Group"? When we changed the
> manual license it was relatively obvious that we had to contact the
> authors listed on the frontpage, but who is in the group for the user
> notes and manual code examples? :(
>
> -Hannes
>

All,

I'm not 100% sure I believe we actually have an issue here.

The manual as a whole is licensed under the CC-BY 3.0 license; that is, were
someone to duplicate a considerable amount of the manual verbatim, they
would be obligated to credit The Documentation Group as the
authors/maintainers of the documentation.

However, use of small parts of the manual, or even whole code snippets,
would not rise to the level of copyright infringement if the author refused
to attribute those snippets to The Documentation Group. In fact, I would
argue that this use would fall under the Fair Use doctrine in many cases.

The fact that authors of notes are made explicitly aware of the fact that
their notes become available as a part of the PHP manual, and that they
intentionally surrender their intellectual property rights as a part of
their submission, says to me that the practical effect of the license and
enforcement thereof becomes our responsibility.

All of this has been a long route to saying the following: anyone who uses a
small piece of a code snippet, changing it or not for their own needs, does
not necessarily rise to the level of infringing upon the copyright of the
snippet's owner(s) simply by doing so, and thus doesn't necessarily obligate
them to credit the author under the Creative Commons license. While
wholesale duplication of the manual and its contents without attribution
would be a clear violation, minor, inconsequential use does not necessarily
qualify.

Now, the two caveats here are this: first, I'm not a lawyer by trade, but a
software developer. And second, this interpretation may not be compatible
with certain licenses (the GPL in particular seems to think it can rewrite
copyright law and limit fair use and define how derivative works are
handled, both of which are it's problem). That all being said, I'm still not
sure we have any obligation to change the license at all.

Brandon

Re: [PHP-DOC] License for code examples in the PHP manual?

[Jesus M. Castagnetto]

Pardon this old doc dinosaur for meddling in this thread, just a couple of
comments:

- IIRC there was never a "notes group" as such. It was mainly a mailing
list, some code we hacked and some rules of thumb, and whoever had the time
will chip in ad do some notes housekeeping once in a while. Ergo, the notes,
code and text should formally be responsability of the doc group (which is a
changing entity over the years).

- Not sure as pointed out by Brandon, that theres is a need for licensing
code snippets separately, they usually are exemplars of concepts and
techniques, small and simple, and not significant enough to warrant all that
work (being that there is a provision for "fair use"). I would suggest the
current doc maintainers to use Occam's razor in this respect :-)

Now, I am not a lawyer, and don't even play one in RPGs, just a crusty old
chemist/code mangler.

Keep up the good work.

Cheers

--
Jesus M. Castagnetto 
Web: http://www.castagnetto.com/


On Mon, Oct 4, 2010 at 08:59, Brandon Savage wrote:

>  The "snippet's owner(s)" is the PHP Documentation Group.
>> The CC-BY license has this explicit notice (in human readable terms):
>> "Attribution — You must attribute the work in the manner specified by
>> the author or licensor (but not in any way that suggests that they
>> endorse you or your use of the work)"
>>
>> It doesn't say "if you use significant amount" or anything along those
>> lines. Whenever, whatever, you copy, distribute, share, or adapt
>> anything from the manual or its notes you have to attribute that work.
>> As for the manual text itself, that attribution note was intentional
>> choice by us when we changed the license couple of hours ago.
>> As for the side affect it had on the user contributed code snippets
>> and examples in the manual, that point was never realized until now
>> (at least not on my part).
>>
>>
> Hannes,
>
> The CC-BY license states, in addition to what you pointed out, the
> following:
>
>
>- *Other Rights* — In no way are any of the following rights affected
>by the license:
>   - Your fair dealing or fair 
> userights,
>  or other applicable copyright exceptions and limitations;
>   - The author's 
> moralrights;
>   - Rights other persons may have either in the work itself or in how
>   the work is used, such as 
> publicityor
>  privacy rights.
>
> This is the provision from which I derived that fair use avoids
> infringement even if credit is not given.
>
> That being said, if it is the opinion of the group that the CC-BY combined
> with the provisions of fair use do not protect someone who uses the
> snippets, then they simply need to give credit.
>
> FWIW I don't see a significant problem here with giving credit. A line in a
> README file that says "Some snippets adapted from documentation provided by
> The PHP Documentation Group" would solve the issue entirely. The specific
> names of the individuals that constitute the PHP Documentation Group are
> irrelevant; the license says "The PHP Documentation Group" is who owns the
> copyright, so that's who gets the credit.
>
> I still don't see a significant issue or a reason to change our licensing.
> Furthermore, I don't see why we should change our license to help out the
> GPL folks, especially when they've shown considerable disregard for the
> rights of others in the software community, most recently in the fight over
> Wordpress themes. So PHP should help out the GPL community, but the GPL
> community screws the PHP community? I think not.
>
> For the above stated reasons I'm not in favor of a license change at this
> point.
>
> Brandon
>

Re: [PHP-DOC] License for code examples in the PHP manual?

[Brandon Savage]

>
> The "snippet's owner(s)" is the PHP Documentation Group.
> The CC-BY license has this explicit notice (in human readable terms):
> "Attribution — You must attribute the work in the manner specified by
> the author or licensor (but not in any way that suggests that they
> endorse you or your use of the work)"
>
> It doesn't say "if you use significant amount" or anything along those
> lines. Whenever, whatever, you copy, distribute, share, or adapt
> anything from the manual or its notes you have to attribute that work.
> As for the manual text itself, that attribution note was intentional
> choice by us when we changed the license couple of hours ago.
> As for the side affect it had on the user contributed code snippets
> and examples in the manual, that point was never realized until now
> (at least not on my part).
>
>
Hannes,

The CC-BY license states, in addition to what you pointed out, the
following:


   - *Other Rights* — In no way are any of the following rights affected by
   the license:
  - Your fair dealing or fair
userights,
or other applicable copyright exceptions and limitations;
  - The author's
moralrights;
  - Rights other persons may have either in the work itself or in how
  the work is used, such as
publicityor
privacy rights.

This is the provision from which I derived that fair use avoids infringement
even if credit is not given.

That being said, if it is the opinion of the group that the CC-BY combined
with the provisions of fair use do not protect someone who uses the
snippets, then they simply need to give credit.

FWIW I don't see a significant problem here with giving credit. A line in a
README file that says "Some snippets adapted from documentation provided by
The PHP Documentation Group" would solve the issue entirely. The specific
names of the individuals that constitute the PHP Documentation Group are
irrelevant; the license says "The PHP Documentation Group" is who owns the
copyright, so that's who gets the credit.

I still don't see a significant issue or a reason to change our licensing.
Furthermore, I don't see why we should change our license to help out the
GPL folks, especially when they've shown considerable disregard for the
rights of others in the software community, most recently in the fight over
Wordpress themes. So PHP should help out the GPL community, but the GPL
community screws the PHP community? I think not.

For the above stated reasons I'm not in favor of a license change at this
point.

Brandon

Re: [PHP-DOC] License for code examples in the PHP manual?

[Robinson Tryon]

On Mon, Oct 4, 2010 at 4:40 AM, Hannes Magnusson
 wrote:
>
> Actually, when adding a use contributor note the note becomes
> 'property of the PHP Documentation Group'
>
> See http://no.php.net/manual/add-note.php
> "This means that any note submitted here becomes the property of the
> PHP Documentation Group and will be available under the same license
> as the documentation."

Ah, that's good to know!

> We did recently changed the manual license to CC-BY, and I must admit
> I didn't consider the consequences that had on the code snippets.
>
> I'm also unsure how we can fix that. Add a note "all code examples are
> BSD licensed" clause somewhere?

There's a DFSG (draft) FAQ that provides some good insight on the topic:


http://people.debian.org/~bap/dfsg-faq.html#docs

Q: I'm writing documentation to accompany a free program. What license
should I use for this documentation?

A: We strongly suggest you use the same license as used for the
program. Then it will be possible to take code and put it into the
documentation, and vice versa.

If you would like to grant some extra freedoms for the documentation
not granted for the remainder of the software package (eg freedom to
distribute as a paper manual without corresponding document source) we
recommend you use a dual license: one of which grants these extra
freedoms, and the other the same license as the program.


Given that the PHP License isn't compatible with the GPL, then yes, I
think choosing a permissive license like the New BSD License is an
appropriate choice.

It shouldn't take too long to fix this -- I'd just add a note in the
documentation section of the PHP license page along the lines of "All
example code in the PHP manual, including user notes, are additionally
available under the terms of the New BSD License," and then link to a
local copy of the New (i.e. the 3-clause) BSD License.

I'm sure that people will re-use code from the manual with or without
an explicit license to it, but it makes a lot of sense to formalize
the whole thing, keeping our codebases and licenses all nice and tidy.

Cheers,
--R

Re: [PHP-DOC] License for code examples in the PHP manual?

[Hannes Magnusson]

On Mon, Oct 4, 2010 at 03:56, Adam Harvey  wrote:
> On 3 October 2010 08:43, Robinson Tryon  wrote:
>> Is there
>> any chance that the code examples in the manual are also available
>> under a different license as well?
>
> As you've seen on the licensing page, the manual — including the code
> examples — is only available under the CC-BY licence. Given the number
> of contributors over the years, I think it's unlikely that we'd be
> able to relicense (or dual license) to anything else at this point.


Actually, when adding a use contributor note the note becomes
'property of the PHP Documentation Group'

See http://no.php.net/manual/add-note.php
"This means that any note submitted here becomes the property of the
PHP Documentation Group and will be available under the same license
as the documentation."

We did recently changed the manual license to CC-BY, and I must admit
I didn't consider the consequences that had on the code snippets.

I'm also unsure how we can fix that. Add a note "all code examples are
BSD licensed" clause somewhere?

-Hannes

Re: [PHP-DOC] License for code examples in the PHP manual?

[Hannes Magnusson]

On Mon, Oct 4, 2010 at 12:08, Robinson Tryon  wrote:
> It shouldn't take too long to fix this -- I'd just add a note in the
> documentation section of the PHP license page along the lines of "All
> example code in the PHP manual, including user notes, are additionally
> available under the terms of the New BSD License," and then link to a
> local copy of the New (i.e. the 3-clause) BSD License.


The fix is easy, but it has many legal implications :)

We also would have to update several other pages describing the manual
pages, such as the add-notes page, and the license document in the
manual itself.

Also, who exactly is "The Documentation Group"? When we changed the
manual license it was relatively obvious that we had to contact the
authors listed on the frontpage, but who is in the group for the user
notes and manual code examples? :(

-Hannes

Re: [PHP-DOC] License for code examples in the PHP manual?

[Hannes Magnusson]

On Mon, Oct 4, 2010 at 15:43, Hannes Magnusson
 wrote:
> As for the manual text itself, that attribution note was intentional
> choice by us when we changed the license couple of hours ago.

s/hours/years :P

-Hannes

Re: [PHP-DOC] License for code examples in the PHP manual?

[Hannes Magnusson]

On Mon, Oct 4, 2010 at 14:15, Brandon Savage  wrote:
> On Mon, Oct 4, 2010 at 7:24 AM, Hannes Magnusson
>  wrote:
>>
>> On Mon, Oct 4, 2010 at 12:08, Robinson Tryon 
>> wrote:
>> > It shouldn't take too long to fix this -- I'd just add a note in the
>> > documentation section of the PHP license page along the lines of "All
>> > example code in the PHP manual, including user notes, are additionally
>> > available under the terms of the New BSD License," and then link to a
>> > local copy of the New (i.e. the 3-clause) BSD License.
>>
>>
>> The fix is easy, but it has many legal implications :)
>>
>> We also would have to update several other pages describing the manual
>> pages, such as the add-notes page, and the license document in the
>> manual itself.
>>
>> Also, who exactly is "The Documentation Group"? When we changed the
>> manual license it was relatively obvious that we had to contact the
>> authors listed on the frontpage, but who is in the group for the user
>> notes and manual code examples? :(
>>
>> -Hannes
>
> All,
>
> I'm not 100% sure I believe we actually have an issue here.
>
> The manual as a whole is licensed under the CC-BY 3.0 license; that is, were
> someone to duplicate a considerable amount of the manual verbatim, they
> would be obligated to credit The Documentation Group as the
> authors/maintainers of the documentation.
>
> However, use of small parts of the manual, or even whole code snippets,
> would not rise to the level of copyright infringement if the author refused
> to attribute those snippets to The Documentation Group. In fact, I would
> argue that this use would fall under the Fair Use doctrine in many cases.
>
> The fact that authors of notes are made explicitly aware of the fact that
> their notes become available as a part of the PHP manual, and that they
> intentionally surrender their intellectual property rights as a part of
> their submission, says to me that the practical effect of the license and
> enforcement thereof becomes our responsibility.
>
> All of this has been a long route to saying the following: anyone who uses a
> small piece of a code snippet, changing it or not for their own needs, does
> not necessarily rise to the level of infringing upon the copyright of the
> snippet's owner(s) simply by doing so, and thus doesn't necessarily obligate
> them to credit the author under the Creative Commons license. While
> wholesale duplication of the manual and its contents without attribution
> would be a clear violation, minor, inconsequential use does not necessarily
> qualify.
>

The "snippet's owner(s)" is the PHP Documentation Group.
The CC-BY license has this explicit notice (in human readable terms):
"Attribution — You must attribute the work in the manner specified by
the author or licensor (but not in any way that suggests that they
endorse you or your use of the work)"

It doesn't say "if you use significant amount" or anything along those
lines. Whenever, whatever, you copy, distribute, share, or adapt
anything from the manual or its notes you have to attribute that work.
As for the manual text itself, that attribution note was intentional
choice by us when we changed the license couple of hours ago.
As for the side affect it had on the user contributed code snippets
and examples in the manual, that point was never realized until now
(at least not on my part).

I personal have no problem with sticking to that clause when copying
snippets from that manual, and have done so in the past (just because
thats something I always do), but if CC-BY is incompatible with GPL..
then those hillbillies have a problem using the examples.

The question then becomes: Should we ignore the GPL weirdos, or should
we help them out by dual licensing code snippets and examples under
BSD?
If yes, who actually is the authority here? The listed manual authors?

-Hannes