Revision [621]

Last edited on 2011-05-21 21:35:35 by BenoitAudouard [revert]
Additions:
The legal issue is important for a new distribution, there are several aspects to be covered
~- organization: association or foundation
~- who's responsible for what: president, treasurer
~- licensing according to free software http://www.gnu.org/philosophy/free-sw.html & http://opensource.org (OSI) & http://faq.tuxfamily.org/License/En (see DFSG to be complete)
~- responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users, magazines distributing CD/DVD, sites selling CD/DVD
~- for packaging-specific issues, see Blog20101013MageiaLegallyGreyPackages

===Legal management of licenses for Mageia===
Well let's focus on what's distributed, mainly libre-software though copyright is not the only thing to take into account (software patents are still illegal in many countries for those trying to prevent fair-sharing and getting selfish-temporary "rights" in some countries, trademarks too have drawbacks unless they are used appropriately).
{{image class="center" alt="Mageia legal context (draft)" title="Mageia legal context (draft)" url="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png" link="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png"}}
Source is available at [[http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal.xmind Mageia legal xmind]] (of course WikiLicense applies) see CompileXMind to edit it
ToDo:
~- add user involvement
~- identify relations on graphic
~- communicate about smallest common multiple (SCM) vs greatest common denominator (GCD): empower users to contribute what they are authorized to, in their respective country, to provide as much as possible (SCM) in the distribution rather than as few as is possible everywhere (GCD), hence adding as much as possible for as many people as possible
~- add cease & desist risk (DMCA)
~- precise DIY: "Do It Yourself" as a movement empowering people to just do it, related to free software in many ways





===Examples for managing those illegal (in many countries) software patents ===

~- plf
~- example with mp3
~~- encoding with Frauhnaufer
~~- reading ? (check references)
~~- users
~~- distribution
~~- who can be concerned? packager, mirror-admin, distribution on sold CD, distribution by magazines, other Mageia-based distributions (work to be re-done or additionnal work)

===What's the use of a fair trademark?===
some examples:
~- http://www.debian.org/logos/index.en.html
~- OIN ?
~- Fedora vs Red Hat?
~- Linux Foundation for use of Linux (appropriate for any GNU/Linux distribution iirc)
~~- http://www.linuxfoundation.org/about/linux-foundation-trademark-usage-guidelines how to write it
~~- http://www.linuxfoundation.org/programs/legal/trademark/attribution everyone and sublicensees
~~- http://www.linuxfoundation.org/collaborate/workgroups/lsb example of logo
~- http://www.mozilla.org/foundation/trademarks/
~- http://foundation.gnome.org/licensing/index.html (find out KDE trademark too :D)

===Copyright attribution, or not?===
See this discussion about Open Core http://ebb.org/bkuhn/blog/2010/10/17/shuttleworth-admits-it.html interesting with Qt and Gtk examples
Another answer by MS at http://www.itwire.com/opinion-and-analysis/open-sauce/36379-canonical-copyright-assignment-policy-same-as-others?start=1 (see all 3 pages)

===Medium for those interested to follow===
Implementation should provide two means of contact, depending on the subject:
~- private: (mageia-issues?) because some things have to be discussed without public knowing, between trusted people
~- standard support: licensing, official position, explanations, like is debian-legal for example

TODO: Discuss -legal only or any need for a -licensing ML ? (IMHO, -legal is sufficient even though it would be public, private contact being possible, only requires proper explanation of what subjects can be addressed and which should not)

===Some references in French===
http://framalang.org/wiki/FRAMALANG:_10_m%C3%A9prises_courantes_sur_la_GPL
http://faq.tuxfamily.org/Licence/Fr
check [[http://cookerspot.tuxfamily.org/wikka.php?wakka=CategoryLibreAdvocacy CategoryLibreAdvocacy]], particularly [[http://cookerspot.tuxfamily.org/wikka.php?wakka=ContributionLibre ContributionLibre]] (in french)

===Implementation in Mageia===
Those legal issues can be treated in the continuity of existing practices :
~- libre software with identified libre licensing and no legal issue :
~~- mageia managed and promoted, work in common with local initiative, take into account contributions whenever possible and promote commiters (packager or maintainer or user workgroup integration)
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...) :
~~- identify clearly which derived works by communities is possible (e.g. nvidia, flash, other?)
~- libre-software with illegal-in-europe patents or trademark issue,
~~- check http://plf.zarb.org/faq.php and http://plf.zarb.org/about.php to provide end-user with easiest way to benefit from what is available, keeping in mind responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users
~~- well, just distribute through plf - as usual - no change :)
~~- room for improvement: see below

===what are the risks?===
~- cease & desist (from DMCA): should it concern the whole distribution or a single repository (which side-effects? one package would be better, from mirror-admin point of view, should be one directory, keeping the rest available)
~~- is it necessary to have patents / not_relevant_patents / DMCA / crypto / DADVSI|LOPPSI or a single directory? may be in the src.rpm description? to be pragmatic, just check how many packages are concerned at the moment
~~~- 86 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/non-free/source/
~~~- 184 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/free/source/
~~~- for >13000 packages in the distribution? well, who can take descriptions from plf (well documented to tag it and give advice about what should be included in mageia as a "must have"? see [[http://en.wikipedia.org/wiki/MoSCoW_Method MoSCoW]] )
~- the current plan is to keep those packages in a dedicated repository at the choice of the admin-mirror
~- what are the risks for our users? none identified at the moment, for example nobody has been sued for using libdvdcss (counter-example?)
~- Mageia keeps on responsibly managing these kinds of risks, based on experience of its members understanding globalcontext & shortcuts
https://www.mageia.org/pipermail/mageia-dev/20101012/001084.html

===upstream impacts of legal approach===
==vlc==
http://www.videolan.org/press/2010-1.html AOL requires to suppress shoutcast functionality
no problem with codecs, even if patented, as it's illegall in Europe to patent this kind of thing

=== RDA mail on Mageia ML ===
https://www.mageia.org/pipermail/mageia-discuss/20101004/002134.html

===Other references (for association structure mainly)===
http://www.gnomefr.org/association/statuts/
http://www.gnomefr.org/association/reglement/

=== Laws applicable to Mageia ===
~- Mageia.org registred in France, French Laws applies
~- Mirrors of Mageia are under local laws, responsability of maintainer of mirror to comply with local laws
~~- can mirrors delete on part of repos if needed by local laws → should be yes
----
CategoryBlogMageia CategoryMageiaDev
Deletions:
<a href="http://www.yourpillsonline.net/">levitra 10 mg order</a> :OOO <a href="http://www.yourstealightfully.com/nexium.html">nexium</a> %-]]]

Revision [620]

Edited on 2011-05-21 03:31:47 by 168.216.31.185 [hJpaqdmefZYKNQge]
Additions:
<a href="http://www.yourpillsonline.net/">levitra 10 mg order</a> :OOO <a href="http://www.yourstealightfully.com/nexium.html">nexium</a> %-]]]
Deletions:
<a href="http://www.car-insur-online.com/">car insurance</a> 8D <a href="http://www.getcarinsur.com/">infinity auto insurance</a> 631919 <a href="http://www.carinsurersonline.net/">car insurance</a> lmpk

Revision [619]

Edited on 2011-05-21 00:54:52 by 208.64.176.157 [NghRrDycI]
Additions:
<a href="http://www.car-insur-online.com/">car insurance</a> 8D <a href="http://www.getcarinsur.com/">infinity auto insurance</a> 631919 <a href="http://www.carinsurersonline.net/">car insurance</a> lmpk
Deletions:
<a href="http://www.fastrxstore.net/">ultram</a> xyg <a href="http://www.123-drugstore.com/">aciphex altace</a> >:((( <a href="http://www.medications-for-all.net/">buying viagra online</a> xfmp

Revision [618]

Edited on 2011-05-20 06:42:00 by 134.244.77.16 [253]
Additions:
<a href="http://www.fastrxstore.net/">ultram</a> xyg <a href="http://www.123-drugstore.com/">aciphex altace</a> >:((( <a href="http://www.medications-for-all.net/">buying viagra online</a> xfmp
Deletions:
<a href="http://www.pillssearch.net/">lexapro and nexium</a> =D <a href="http://www.20sipatru.net/propecia.html">propecia</a> 253

Revision [617]

Edited on 2011-05-20 02:48:42 by 95.174.9.130 [201]
Additions:
<a href="http://www.pillssearch.net/">lexapro and nexium</a> =D <a href="http://www.20sipatru.net/propecia.html">propecia</a> 253
Deletions:
The legal issue is important for a new distribution, there are several aspects to be covered
~- organization: association or foundation
~- who's responsible for what: president, treasurer
~- licensing according to free software http://www.gnu.org/philosophy/free-sw.html & http://opensource.org (OSI) & http://faq.tuxfamily.org/License/En (see DFSG to be complete)
~- responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users, magazines distributing CD/DVD, sites selling CD/DVD
~- for packaging-specific issues, see Blog20101013MageiaLegallyGreyPackages

===Legal management of licenses for Mageia===
Well let's focus on what's distributed, mainly libre-software though copyright is not the only thing to take into account (software patents are still illegal in many countries for those trying to prevent fair-sharing and getting selfish-temporary "rights" in some countries, trademarks too have drawbacks unless they are used appropriately).
{{image class="center" alt="Mageia legal context (draft)" title="Mageia legal context (draft)" url="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png" link="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png"}}
Source is available at [[http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal.xmind Mageia legal xmind]] (of course WikiLicense applies) see CompileXMind to edit it
ToDo:
~- add user involvement
~- identify relations on graphic
~- communicate about smallest common multiple (SCM) vs greatest common denominator (GCD): empower users to contribute what they are authorized to, in their respective country, to provide as much as possible (SCM) in the distribution rather than as few as is possible everywhere (GCD), hence adding as much as possible for as many people as possible
~- add cease & desist risk (DMCA)
~- precise DIY: "Do It Yourself" as a movement empowering people to just do it, related to free software in many ways





===Examples for managing those illegal (in many countries) software patents ===

~- plf
~- example with mp3
~~- encoding with Frauhnaufer
~~- reading ? (check references)
~~- users
~~- distribution
~~- who can be concerned? packager, mirror-admin, distribution on sold CD, distribution by magazines, other Mageia-based distributions (work to be re-done or additionnal work)

===What's the use of a fair trademark?===
some examples:
~- http://www.debian.org/logos/index.en.html
~- OIN ?
~- Fedora vs Red Hat?
~- Linux Foundation for use of Linux (appropriate for any GNU/Linux distribution iirc)
~~- http://www.linuxfoundation.org/about/linux-foundation-trademark-usage-guidelines how to write it
~~- http://www.linuxfoundation.org/programs/legal/trademark/attribution everyone and sublicensees
~~- http://www.linuxfoundation.org/collaborate/workgroups/lsb example of logo
~- http://www.mozilla.org/foundation/trademarks/
~- http://foundation.gnome.org/licensing/index.html (find out KDE trademark too :D)

===Copyright attribution, or not?===
See this discussion about Open Core http://ebb.org/bkuhn/blog/2010/10/17/shuttleworth-admits-it.html interesting with Qt and Gtk examples
Another answer by MS at http://www.itwire.com/opinion-and-analysis/open-sauce/36379-canonical-copyright-assignment-policy-same-as-others?start=1 (see all 3 pages)

===Medium for those interested to follow===
Implementation should provide two means of contact, depending on the subject:
~- private: (mageia-issues?) because some things have to be discussed without public knowing, between trusted people
~- standard support: licensing, official position, explanations, like is debian-legal for example

TODO: Discuss -legal only or any need for a -licensing ML ? (IMHO, -legal is sufficient even though it would be public, private contact being possible, only requires proper explanation of what subjects can be addressed and which should not)

===Some references in French===
http://framalang.org/wiki/FRAMALANG:_10_m%C3%A9prises_courantes_sur_la_GPL
http://faq.tuxfamily.org/Licence/Fr
check [[http://cookerspot.tuxfamily.org/wikka.php?wakka=CategoryLibreAdvocacy CategoryLibreAdvocacy]], particularly [[http://cookerspot.tuxfamily.org/wikka.php?wakka=ContributionLibre ContributionLibre]] (in french)

===Implementation in Mageia===
Those legal issues can be treated in the continuity of existing practices :
~- libre software with identified libre licensing and no legal issue :
~~- mageia managed and promoted, work in common with local initiative, take into account contributions whenever possible and promote commiters (packager or maintainer or user workgroup integration)
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...) :
~~- identify clearly which derived works by communities is possible (e.g. nvidia, flash, other?)
~- libre-software with illegal-in-europe patents or trademark issue,
~~- check http://plf.zarb.org/faq.php and http://plf.zarb.org/about.php to provide end-user with easiest way to benefit from what is available, keeping in mind responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users
~~- well, just distribute through plf - as usual - no change :)
~~- room for improvement: see below

===what are the risks?===
~- cease & desist (from DMCA): should it concern the whole distribution or a single repository (which side-effects? one package would be better, from mirror-admin point of view, should be one directory, keeping the rest available)
~~- is it necessary to have patents / not_relevant_patents / DMCA / crypto / DADVSI|LOPPSI or a single directory? may be in the src.rpm description? to be pragmatic, just check how many packages are concerned at the moment
~~~- 86 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/non-free/source/
~~~- 184 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/free/source/
~~~- for >13000 packages in the distribution? well, who can take descriptions from plf (well documented to tag it and give advice about what should be included in mageia as a "must have"? see [[http://en.wikipedia.org/wiki/MoSCoW_Method MoSCoW]] )
~- the current plan is to keep those packages in a dedicated repository at the choice of the admin-mirror
~- what are the risks for our users? none identified at the moment, for example nobody has been sued for using libdvdcss (counter-example?)
~- Mageia keeps on responsibly managing these kinds of risks, based on experience of its members understanding globalcontext & shortcuts
https://www.mageia.org/pipermail/mageia-dev/20101012/001084.html

===upstream impacts of legal approach===
==vlc==
http://www.videolan.org/press/2010-1.html AOL requires to suppress shoutcast functionality
no problem with codecs, even if patented, as it's illegall in Europe to patent this kind of thing

=== RDA mail on Mageia ML ===
https://www.mageia.org/pipermail/mageia-discuss/20101004/002134.html

===Other references (for association structure mainly)===
http://www.gnomefr.org/association/statuts/
http://www.gnomefr.org/association/reglement/

=== Laws applicable to Mageia ===
~- Mageia.org registred in France, French Laws applies
~- Mirrors of Mageia are under local laws, responsability of maintainer of mirror to comply with local laws
~~- can mirrors delete on part of repos if needed by local laws → should be yes
----
CategoryBlogMageia CategoryMageiaDev

Revision [603]

Edited on 2011-05-18 23:27:21 by BenoitAudouard [revert]
Additions:
The legal issue is important for a new distribution, there are several aspects to be covered
~- organization: association or foundation
~- who's responsible for what: president, treasurer
~- licensing according to free software http://www.gnu.org/philosophy/free-sw.html & http://opensource.org (OSI) & http://faq.tuxfamily.org/License/En (see DFSG to be complete)
~- responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users, magazines distributing CD/DVD, sites selling CD/DVD
~- for packaging-specific issues, see Blog20101013MageiaLegallyGreyPackages

===Legal management of licenses for Mageia===
Well let's focus on what's distributed, mainly libre-software though copyright is not the only thing to take into account (software patents are still illegal in many countries for those trying to prevent fair-sharing and getting selfish-temporary "rights" in some countries, trademarks too have drawbacks unless they are used appropriately).
{{image class="center" alt="Mageia legal context (draft)" title="Mageia legal context (draft)" url="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png" link="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png"}}
Source is available at [[http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal.xmind Mageia legal xmind]] (of course WikiLicense applies) see CompileXMind to edit it
ToDo:
~- add user involvement
~- identify relations on graphic
~- communicate about smallest common multiple (SCM) vs greatest common denominator (GCD): empower users to contribute what they are authorized to, in their respective country, to provide as much as possible (SCM) in the distribution rather than as few as is possible everywhere (GCD), hence adding as much as possible for as many people as possible
~- add cease & desist risk (DMCA)
~- precise DIY: "Do It Yourself" as a movement empowering people to just do it, related to free software in many ways





===Examples for managing those illegal (in many countries) software patents ===

~- plf
~- example with mp3
~~- encoding with Frauhnaufer
~~- reading ? (check references)
~~- users
~~- distribution
~~- who can be concerned? packager, mirror-admin, distribution on sold CD, distribution by magazines, other Mageia-based distributions (work to be re-done or additionnal work)

===What's the use of a fair trademark?===
some examples:
~- http://www.debian.org/logos/index.en.html
~- OIN ?
~- Fedora vs Red Hat?
~- Linux Foundation for use of Linux (appropriate for any GNU/Linux distribution iirc)
~~- http://www.linuxfoundation.org/about/linux-foundation-trademark-usage-guidelines how to write it
~~- http://www.linuxfoundation.org/programs/legal/trademark/attribution everyone and sublicensees
~~- http://www.linuxfoundation.org/collaborate/workgroups/lsb example of logo
~- http://www.mozilla.org/foundation/trademarks/
~- http://foundation.gnome.org/licensing/index.html (find out KDE trademark too :D)

===Copyright attribution, or not?===
See this discussion about Open Core http://ebb.org/bkuhn/blog/2010/10/17/shuttleworth-admits-it.html interesting with Qt and Gtk examples
Another answer by MS at http://www.itwire.com/opinion-and-analysis/open-sauce/36379-canonical-copyright-assignment-policy-same-as-others?start=1 (see all 3 pages)

===Medium for those interested to follow===
Implementation should provide two means of contact, depending on the subject:
~- private: (mageia-issues?) because some things have to be discussed without public knowing, between trusted people
~- standard support: licensing, official position, explanations, like is debian-legal for example

TODO: Discuss -legal only or any need for a -licensing ML ? (IMHO, -legal is sufficient even though it would be public, private contact being possible, only requires proper explanation of what subjects can be addressed and which should not)

===Some references in French===
http://framalang.org/wiki/FRAMALANG:_10_m%C3%A9prises_courantes_sur_la_GPL
http://faq.tuxfamily.org/Licence/Fr
check [[http://cookerspot.tuxfamily.org/wikka.php?wakka=CategoryLibreAdvocacy CategoryLibreAdvocacy]], particularly [[http://cookerspot.tuxfamily.org/wikka.php?wakka=ContributionLibre ContributionLibre]] (in french)

===Implementation in Mageia===
Those legal issues can be treated in the continuity of existing practices :
~- libre software with identified libre licensing and no legal issue :
~~- mageia managed and promoted, work in common with local initiative, take into account contributions whenever possible and promote commiters (packager or maintainer or user workgroup integration)
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...) :
~~- identify clearly which derived works by communities is possible (e.g. nvidia, flash, other?)
~- libre-software with illegal-in-europe patents or trademark issue,
~~- check http://plf.zarb.org/faq.php and http://plf.zarb.org/about.php to provide end-user with easiest way to benefit from what is available, keeping in mind responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users
~~- well, just distribute through plf - as usual - no change :)
~~- room for improvement: see below

===what are the risks?===
~- cease & desist (from DMCA): should it concern the whole distribution or a single repository (which side-effects? one package would be better, from mirror-admin point of view, should be one directory, keeping the rest available)
~~- is it necessary to have patents / not_relevant_patents / DMCA / crypto / DADVSI|LOPPSI or a single directory? may be in the src.rpm description? to be pragmatic, just check how many packages are concerned at the moment
~~~- 86 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/non-free/source/
~~~- 184 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/free/source/
~~~- for >13000 packages in the distribution? well, who can take descriptions from plf (well documented to tag it and give advice about what should be included in mageia as a "must have"? see [[http://en.wikipedia.org/wiki/MoSCoW_Method MoSCoW]] )
~- the current plan is to keep those packages in a dedicated repository at the choice of the admin-mirror
~- what are the risks for our users? none identified at the moment, for example nobody has been sued for using libdvdcss (counter-example?)
~- Mageia keeps on responsibly managing these kinds of risks, based on experience of its members understanding globalcontext & shortcuts
https://www.mageia.org/pipermail/mageia-dev/20101012/001084.html

===upstream impacts of legal approach===
==vlc==
http://www.videolan.org/press/2010-1.html AOL requires to suppress shoutcast functionality
no problem with codecs, even if patented, as it's illegall in Europe to patent this kind of thing

=== RDA mail on Mageia ML ===
https://www.mageia.org/pipermail/mageia-discuss/20101004/002134.html

===Other references (for association structure mainly)===
http://www.gnomefr.org/association/statuts/
http://www.gnomefr.org/association/reglement/

=== Laws applicable to Mageia ===
~- Mageia.org registred in France, French Laws applies
~- Mirrors of Mageia are under local laws, responsability of maintainer of mirror to comply with local laws
~~- can mirrors delete on part of repos if needed by local laws → should be yes
----
CategoryBlogMageia CategoryMageiaDev
Deletions:
<a href="http://www.forever40.org/">auto insurance rates</a> qxsoo <a href="http://www.bestinsurersonline.com/">car insurance online</a> 05278 <a href="http://www.carinsurersonline.net/">car insurance</a> 87735

Revision [602]

Edited on 2011-05-15 17:41:18 by mail.pingg.com [JQZqnEafxOlkQTqW]
Additions:
<a href="http://www.forever40.org/">auto insurance rates</a> qxsoo <a href="http://www.bestinsurersonline.com/">car insurance online</a> 05278 <a href="http://www.carinsurersonline.net/">car insurance</a> 87735
Deletions:
<a href="http://www.getcarinsur.com/">cheap car insurance</a> =-OOO <a href="http://www.bestinsurersonline.com/">car insurance quotes</a> %O <a href="http://www.homeinsuronline.com/">home owners insurance quote</a> =-OO

Revision [601]

Edited on 2011-05-14 13:41:33 by 210249029162.rev.datacenter.ne.jp [UJzYCDFwBgZAtm]
Additions:
<a href="http://www.getcarinsur.com/">cheap car insurance</a> =-OOO <a href="http://www.bestinsurersonline.com/">car insurance quotes</a> %O <a href="http://www.homeinsuronline.com/">home owners insurance quote</a> =-OO
Deletions:
<a href="http://www.goodmedstoday.com/">buy accutane</a> %-[[[ <a href="http://www.medicakey.com/">ultram</a> hjjnz <a href="http://www.generalmeds.net/">buy prednisone</a> hhqss

Revision [600]

Edited on 2011-05-14 05:06:54 by bsb223.bsb-muenchen.de [1871]
Additions:
<a href="http://www.goodmedstoday.com/">buy accutane</a> %-[[[ <a href="http://www.medicakey.com/">ultram</a> hjjnz <a href="http://www.generalmeds.net/">buy prednisone</a> hhqss
Deletions:
<a href="http://www.car-insur-online.com/">car insurance</a> mwv <a href="http://www.lifeinsuroffer.com/">company life insurance</a> 278 <a href="http://www.homeinsuronline.com/">in home health care insurance</a> 1871

Revision [599]

Edited on 2011-05-13 13:47:00 by 124-247-235-162.aicte-india.org [201]
Additions:
<a href="http://www.car-insur-online.com/">car insurance</a> mwv <a href="http://www.lifeinsuroffer.com/">company life insurance</a> 278 <a href="http://www.homeinsuronline.com/">in home health care insurance</a> 1871
Deletions:
The legal issue is important for a new distribution, there are several aspects to be covered
~- organization: association or foundation
~- who's responsible for what: president, treasurer
~- licensing according to free software http://www.gnu.org/philosophy/free-sw.html & http://opensource.org (OSI) & http://faq.tuxfamily.org/License/En (see DFSG to be complete)
~- responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users, magazines distributing CD/DVD, sites selling CD/DVD
~- for packaging-specific issues, see Blog20101013MageiaLegallyGreyPackages

===Legal management of licenses for Mageia===
Well let's focus on what's distributed, mainly libre-software though copyright is not the only thing to take into account (software patents are still illegal in many countries for those trying to prevent fair-sharing and getting selfish-temporary "rights" in some countries, trademarks too have drawbacks unless they are used appropriately).
{{image class="center" alt="Mageia legal context (draft)" title="Mageia legal context (draft)" url="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png" link="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png"}}
Source is available at [[http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal.xmind Mageia legal xmind]] (of course WikiLicense applies) see CompileXMind to edit it
ToDo:
~- add user involvement
~- identify relations on graphic
~- communicate about smallest common multiple (SCM) vs greatest common denominator (GCD): empower users to contribute what they are authorized to, in their respective country, to provide as much as possible (SCM) in the distribution rather than as few as is possible everywhere (GCD), hence adding as much as possible for as many people as possible
~- add cease & desist risk (DMCA)
~- precise DIY: "Do It Yourself" as a movement empowering people to just do it, related to free software in many ways





===Examples for managing those illegal (in many countries) software patents ===

~- plf
~- example with mp3
~~- encoding with Frauhnaufer
~~- reading ? (check references)
~~- users
~~- distribution
~~- who can be concerned? packager, mirror-admin, distribution on sold CD, distribution by magazines, other Mageia-based distributions (work to be re-done or additionnal work)

===What's the use of a fair trademark?===
some examples:
~- http://www.debian.org/logos/index.en.html
~- OIN ?
~- Fedora vs Red Hat?
~- Linux Foundation for use of Linux (appropriate for any GNU/Linux distribution iirc)
~~- http://www.linuxfoundation.org/about/linux-foundation-trademark-usage-guidelines how to write it
~~- http://www.linuxfoundation.org/programs/legal/trademark/attribution everyone and sublicensees
~~- http://www.linuxfoundation.org/collaborate/workgroups/lsb example of logo
~- http://www.mozilla.org/foundation/trademarks/
~- http://foundation.gnome.org/licensing/index.html (find out KDE trademark too :D)

===Copyright attribution, or not?===
See this discussion about Open Core http://ebb.org/bkuhn/blog/2010/10/17/shuttleworth-admits-it.html interesting with Qt and Gtk examples
Another answer by MS at http://www.itwire.com/opinion-and-analysis/open-sauce/36379-canonical-copyright-assignment-policy-same-as-others?start=1 (see all 3 pages)

===Medium for those interested to follow===
Implementation should provide two means of contact, depending on the subject:
~- private: (mageia-issues?) because some things have to be discussed without public knowing, between trusted people
~- standard support: licensing, official position, explanations, like is debian-legal for example

TODO: Discuss -legal only or any need for a -licensing ML ? (IMHO, -legal is sufficient even though it would be public, private contact being possible, only requires proper explanation of what subjects can be addressed and which should not)

===Some references in French===
http://framalang.org/wiki/FRAMALANG:_10_m%C3%A9prises_courantes_sur_la_GPL
http://faq.tuxfamily.org/Licence/Fr
check [[http://cookerspot.tuxfamily.org/wikka.php?wakka=CategoryLibreAdvocacy CategoryLibreAdvocacy]], particularly [[http://cookerspot.tuxfamily.org/wikka.php?wakka=ContributionLibre ContributionLibre]] (in french)

===Implementation in Mageia===
Those legal issues can be treated in the continuity of existing practices :
~- libre software with identified libre licensing and no legal issue :
~~- mageia managed and promoted, work in common with local initiative, take into account contributions whenever possible and promote commiters (packager or maintainer or user workgroup integration)
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...) :
~~- identify clearly which derived works by communities is possible (e.g. nvidia, flash, other?)
~- libre-software with illegal-in-europe patents or trademark issue,
~~- check http://plf.zarb.org/faq.php and http://plf.zarb.org/about.php to provide end-user with easiest way to benefit from what is available, keeping in mind responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users
~~- well, just distribute through plf - as usual - no change :)
~~- room for improvement: see below

===what are the risks?===
~- cease & desist (from DMCA): should it concern the whole distribution or a single repository (which side-effects? one package would be better, from mirror-admin point of view, should be one directory, keeping the rest available)
~~- is it necessary to have patents / not_relevant_patents / DMCA / crypto / DADVSI|LOPPSI or a single directory? may be in the src.rpm description? to be pragmatic, just check how many packages are concerned at the moment
~~~- 86 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/non-free/source/
~~~- 184 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/free/source/
~~~- for >13000 packages in the distribution? well, who can take descriptions from plf (well documented to tag it and give advice about what should be included in mageia as a "must have"? see [[http://en.wikipedia.org/wiki/MoSCoW_Method MoSCoW]] )
~- the current plan is to keep those packages in a dedicated repository at the choice of the admin-mirror
~- what are the risks for our users? none identified at the moment, for example nobody has been sued for using libdvdcss (counter-example?)
~- Mageia keeps on responsibly managing these kinds of risks, based on experience of its members understanding globalcontext & shortcuts
https://www.mageia.org/pipermail/mageia-dev/20101012/001084.html

===upstream impacts of legal approach===
==vlc==
http://www.videolan.org/press/2010-1.html AOL requires to suppress shoutcast functionality
no problem with codecs, even if patented, as it's illegall in Europe to patent this kind of thing

=== RDA mail on Mageia ML ===
https://www.mageia.org/pipermail/mageia-discuss/20101004/002134.html

===Other references (for association structure mainly)===
http://www.gnomefr.org/association/statuts/
http://www.gnomefr.org/association/reglement/

=== Laws applicable to Mageia ===
~- Mageia.org registred in France, French Laws applies
~- Mirrors of Mageia are under local laws, responsability of maintainer of mirror to comply with local laws
~~- can mirrors delete on part of repos if needed by local laws → should be yes
----
CategoryBlogMageia CategoryMageiaDev

Revision [598]

Edited on 2011-05-12 01:18:11 by BenoitAudouard [revert]
Additions:
The legal issue is important for a new distribution, there are several aspects to be covered
~- organization: association or foundation
~- who's responsible for what: president, treasurer
~- licensing according to free software http://www.gnu.org/philosophy/free-sw.html & http://opensource.org (OSI) & http://faq.tuxfamily.org/License/En (see DFSG to be complete)
~- responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users, magazines distributing CD/DVD, sites selling CD/DVD
~- for packaging-specific issues, see Blog20101013MageiaLegallyGreyPackages

===Legal management of licenses for Mageia===
Well let's focus on what's distributed, mainly libre-software though copyright is not the only thing to take into account (software patents are still illegal in many countries for those trying to prevent fair-sharing and getting selfish-temporary "rights" in some countries, trademarks too have drawbacks unless they are used appropriately).
{{image class="center" alt="Mageia legal context (draft)" title="Mageia legal context (draft)" url="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png" link="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png"}}
Source is available at [[http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal.xmind Mageia legal xmind]] (of course WikiLicense applies) see CompileXMind to edit it
ToDo:
~- add user involvement
~- identify relations on graphic
~- communicate about smallest common multiple (SCM) vs greatest common denominator (GCD): empower users to contribute what they are authorized to, in their respective country, to provide as much as possible (SCM) in the distribution rather than as few as is possible everywhere (GCD), hence adding as much as possible for as many people as possible
~- add cease & desist risk (DMCA)
~- precise DIY: "Do It Yourself" as a movement empowering people to just do it, related to free software in many ways





===Examples for managing those illegal (in many countries) software patents ===

~- plf
~- example with mp3
~~- encoding with Frauhnaufer
~~- reading ? (check references)
~~- users
~~- distribution
~~- who can be concerned? packager, mirror-admin, distribution on sold CD, distribution by magazines, other Mageia-based distributions (work to be re-done or additionnal work)

===What's the use of a fair trademark?===
some examples:
~- http://www.debian.org/logos/index.en.html
~- OIN ?
~- Fedora vs Red Hat?
~- Linux Foundation for use of Linux (appropriate for any GNU/Linux distribution iirc)
~~- http://www.linuxfoundation.org/about/linux-foundation-trademark-usage-guidelines how to write it
~~- http://www.linuxfoundation.org/programs/legal/trademark/attribution everyone and sublicensees
~~- http://www.linuxfoundation.org/collaborate/workgroups/lsb example of logo
~- http://www.mozilla.org/foundation/trademarks/
~- http://foundation.gnome.org/licensing/index.html (find out KDE trademark too :D)

===Copyright attribution, or not?===
See this discussion about Open Core http://ebb.org/bkuhn/blog/2010/10/17/shuttleworth-admits-it.html interesting with Qt and Gtk examples
Another answer by MS at http://www.itwire.com/opinion-and-analysis/open-sauce/36379-canonical-copyright-assignment-policy-same-as-others?start=1 (see all 3 pages)

===Medium for those interested to follow===
Implementation should provide two means of contact, depending on the subject:
~- private: (mageia-issues?) because some things have to be discussed without public knowing, between trusted people
~- standard support: licensing, official position, explanations, like is debian-legal for example

TODO: Discuss -legal only or any need for a -licensing ML ? (IMHO, -legal is sufficient even though it would be public, private contact being possible, only requires proper explanation of what subjects can be addressed and which should not)

===Some references in French===
http://framalang.org/wiki/FRAMALANG:_10_m%C3%A9prises_courantes_sur_la_GPL
http://faq.tuxfamily.org/Licence/Fr
check [[http://cookerspot.tuxfamily.org/wikka.php?wakka=CategoryLibreAdvocacy CategoryLibreAdvocacy]], particularly [[http://cookerspot.tuxfamily.org/wikka.php?wakka=ContributionLibre ContributionLibre]] (in french)

===Implementation in Mageia===
Those legal issues can be treated in the continuity of existing practices :
~- libre software with identified libre licensing and no legal issue :
~~- mageia managed and promoted, work in common with local initiative, take into account contributions whenever possible and promote commiters (packager or maintainer or user workgroup integration)
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...) :
~~- identify clearly which derived works by communities is possible (e.g. nvidia, flash, other?)
~- libre-software with illegal-in-europe patents or trademark issue,
~~- check http://plf.zarb.org/faq.php and http://plf.zarb.org/about.php to provide end-user with easiest way to benefit from what is available, keeping in mind responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users
~~- well, just distribute through plf - as usual - no change :)
~~- room for improvement: see below

===what are the risks?===
~- cease & desist (from DMCA): should it concern the whole distribution or a single repository (which side-effects? one package would be better, from mirror-admin point of view, should be one directory, keeping the rest available)
~~- is it necessary to have patents / not_relevant_patents / DMCA / crypto / DADVSI|LOPPSI or a single directory? may be in the src.rpm description? to be pragmatic, just check how many packages are concerned at the moment
~~~- 86 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/non-free/source/
~~~- 184 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/free/source/
~~~- for >13000 packages in the distribution? well, who can take descriptions from plf (well documented to tag it and give advice about what should be included in mageia as a "must have"? see [[http://en.wikipedia.org/wiki/MoSCoW_Method MoSCoW]] )
~- the current plan is to keep those packages in a dedicated repository at the choice of the admin-mirror
~- what are the risks for our users? none identified at the moment, for example nobody has been sued for using libdvdcss (counter-example?)
~- Mageia keeps on responsibly managing these kinds of risks, based on experience of its members understanding globalcontext & shortcuts
https://www.mageia.org/pipermail/mageia-dev/20101012/001084.html

===upstream impacts of legal approach===
==vlc==
http://www.videolan.org/press/2010-1.html AOL requires to suppress shoutcast functionality
no problem with codecs, even if patented, as it's illegall in Europe to patent this kind of thing

=== RDA mail on Mageia ML ===
https://www.mageia.org/pipermail/mageia-discuss/20101004/002134.html

===Other references (for association structure mainly)===
http://www.gnomefr.org/association/statuts/
http://www.gnomefr.org/association/reglement/

=== Laws applicable to Mageia ===
~- Mageia.org registred in France, French Laws applies
~- Mirrors of Mageia are under local laws, responsability of maintainer of mirror to comply with local laws
~~- can mirrors delete on part of repos if needed by local laws → should be yes
----
CategoryBlogMageia CategoryMageiaDev
Deletions:
DrKZsd <a href="http://txqbhjepaqex.com/">txqbhjepaqex</a>

Revision [597]

Edited on 2011-05-11 06:03:42 by ec2-50-17-190-145.compute-1.amazonaws.com [hVEsmHbYtLdO]
Additions:
DrKZsd <a href="http://txqbhjepaqex.com/">txqbhjepaqex</a>
Deletions:
Such a deep awnser! GD&RVVF;

Revision [596]

Edited on 2011-05-10 16:17:41 by 207.160.242.242 [201]
Additions:
Such a deep awnser! GD&RVVF;
Deletions:
The legal issue is important for a new distribution, there are several aspects to be covered
~- organization: association or foundation
~- who's responsible for what: president, treasurer
~- licensing according to free software http://www.gnu.org/philosophy/free-sw.html & http://opensource.org (OSI) & http://faq.tuxfamily.org/License/En (see DFSG to be complete)
~- responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users, magazines distributing CD/DVD, sites selling CD/DVD
~- for packaging-specific issues, see Blog20101013MageiaLegallyGreyPackages

===Legal management of licenses for Mageia===
Well let's focus on what's distributed, mainly libre-software though copyright is not the only thing to take into account (software patents are still illegal in many countries for those trying to prevent fair-sharing and getting selfish-temporary "rights" in some countries, trademarks too have drawbacks unless they are used appropriately).
{{image class="center" alt="Mageia legal context (draft)" title="Mageia legal context (draft)" url="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png" link="http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal20101003.png"}}
Source is available at [[http://download.tuxfamily.org/cooker/mageia/doc/MageiaLegal.xmind Mageia legal xmind]] (of course WikiLicense applies) see CompileXMind to edit it
ToDo:
~- add user involvement
~- identify relations on graphic
~- communicate about smallest common multiple (SCM) vs greatest common denominator (GCD): empower users to contribute what they are authorized to, in their respective country, to provide as much as possible (SCM) in the distribution rather than as few as is possible everywhere (GCD), hence adding as much as possible for as many people as possible
~- add cease & desist risk (DMCA)
~- precise DIY: "Do It Yourself" as a movement empowering people to just do it, related to free software in many ways





===Examples for managing those illegal (in many countries) software patents ===

~- plf
~- example with mp3
~~- encoding with Frauhnaufer
~~- reading ? (check references)
~~- users
~~- distribution
~~- who can be concerned? packager, mirror-admin, distribution on sold CD, distribution by magazines, other Mageia-based distributions (work to be re-done or additionnal work)

===What's the use of a fair trademark?===
some examples:
~- http://www.debian.org/logos/index.en.html
~- OIN ?
~- Fedora vs Red Hat?
~- Linux Foundation for use of Linux (appropriate for any GNU/Linux distribution iirc)
~~- http://www.linuxfoundation.org/about/linux-foundation-trademark-usage-guidelines how to write it
~~- http://www.linuxfoundation.org/programs/legal/trademark/attribution everyone and sublicensees
~~- http://www.linuxfoundation.org/collaborate/workgroups/lsb example of logo
~- http://www.mozilla.org/foundation/trademarks/
~- http://foundation.gnome.org/licensing/index.html (find out KDE trademark too :D)

===Copyright attribution, or not?===
See this discussion about Open Core http://ebb.org/bkuhn/blog/2010/10/17/shuttleworth-admits-it.html interesting with Qt and Gtk examples
Another answer by MS at http://www.itwire.com/opinion-and-analysis/open-sauce/36379-canonical-copyright-assignment-policy-same-as-others?start=1 (see all 3 pages)

===Medium for those interested to follow===
Implementation should provide two means of contact, depending on the subject:
~- private: (mageia-issues?) because some things have to be discussed without public knowing, between trusted people
~- standard support: licensing, official position, explanations, like is debian-legal for example

TODO: Discuss -legal only or any need for a -licensing ML ? (IMHO, -legal is sufficient even though it would be public, private contact being possible, only requires proper explanation of what subjects can be addressed and which should not)

===Some references in French===
http://framalang.org/wiki/FRAMALANG:_10_m%C3%A9prises_courantes_sur_la_GPL
http://faq.tuxfamily.org/Licence/Fr
check [[http://cookerspot.tuxfamily.org/wikka.php?wakka=CategoryLibreAdvocacy CategoryLibreAdvocacy]], particularly [[http://cookerspot.tuxfamily.org/wikka.php?wakka=ContributionLibre ContributionLibre]] (in french)

===Implementation in Mageia===
Those legal issues can be treated in the continuity of existing practices :
~- libre software with identified libre licensing and no legal issue :
~~- mageia managed and promoted, work in common with local initiative, take into account contributions whenever possible and promote commiters (packager or maintainer or user workgroup integration)
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...) :
~~- identify clearly which derived works by communities is possible (e.g. nvidia, flash, other?)
~- libre-software with illegal-in-europe patents or trademark issue,
~~- check http://plf.zarb.org/faq.php and http://plf.zarb.org/about.php to provide end-user with easiest way to benefit from what is available, keeping in mind responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users
~~- well, just distribute through plf - as usual - no change :)
~~- room for improvement: see below

===what are the risks?===
~- cease & desist (from DMCA): should it concern the whole distribution or a single repository (which side-effects? one package would be better, from mirror-admin point of view, should be one directory, keeping the rest available)
~~- is it necessary to have patents / not_relevant_patents / DMCA / crypto / DADVSI|LOPPSI or a single directory? may be in the src.rpm description? to be pragmatic, just check how many packages are concerned at the moment
~~~- 86 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/non-free/source/
~~~- 184 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/free/source/
~~~- for >13000 packages in the distribution? well, who can take descriptions from plf (well documented to tag it and give advice about what should be included in mageia as a "must have"? see [[http://en.wikipedia.org/wiki/MoSCoW_Method MoSCoW]] )
~- the current plan is to keep those packages in a dedicated repository at the choice of the admin-mirror
~- what are the risks for our users? none identified at the moment, for example nobody has been sued for using libdvdcss (counter-example?)
~- Mageia keeps on responsibly managing these kinds of risks, based on experience of its members understanding globalcontext & shortcuts
https://www.mageia.org/pipermail/mageia-dev/20101012/001084.html

===upstream impacts of legal approach===
==vlc==
http://www.videolan.org/press/2010-1.html AOL requires to suppress shoutcast functionality
no problem with codecs, even if patented, as it's illegall in Europe to patent this kind of thing

=== RDA mail on Mageia ML ===
https://www.mageia.org/pipermail/mageia-discuss/20101004/002134.html

===Other references (for association structure mainly)===
http://www.gnomefr.org/association/statuts/
http://www.gnomefr.org/association/reglement/

=== Laws applicable to Mageia ===
~- Mageia.org registred in France, French Laws applies
~- Mirrors of Mageia are under local laws, responsability of maintainer of mirror to comply with local laws
~~- can mirrors delete on part of repos if needed by local laws → should be yes
----
CategoryBlogMageia CategoryMageiaDev


Revision [256]

Edited on 2010-10-29 22:54:45 by BenoitAudouard [201]
Additions:
~- precise DIY: "Do It Yourself" as a movement empowering people to just do it, related to free software in many ways

Revision [253]

Edited on 2010-10-29 22:40:16 by BenoitAudouard [201]
Additions:
ToDo:
Deletions:
TODO:

Revision [167]

Edited on 2010-10-19 14:21:38 by BenoitAudouard [201]
Additions:
Another answer by MS at http://www.itwire.com/opinion-and-analysis/open-sauce/36379-canonical-copyright-assignment-policy-same-as-others?start=1 (see all 3 pages)
===Implementation in Mageia===
Deletions:
===implementation in Mageia===

Revision [166]

Edited on 2010-10-19 13:32:04 by BenoitAudouard [add copyright attribution]
Additions:
===Examples for managing those illegal (in many countries) software patents ===
~~- who can be concerned? packager, mirror-admin, distribution on sold CD, distribution by magazines, other Mageia-based distributions (work to be re-done or additionnal work)
===Copyright attribution, or not?===
See this discussion about Open Core http://ebb.org/bkuhn/blog/2010/10/17/shuttleworth-admits-it.html interesting with Qt and Gtk examples
===Medium for those interested to follow===
Deletions:
===managing those illegal (in many countries) software patents ===
~~- who can be concerned?
===for those interested to follow===

Revision [125]

Edited on 2010-10-15 22:33:20 by BenoitAudouard [add copyright attribution]
Additions:
~- for packaging-specific issues, see Blog20101013MageiaLegallyGreyPackages
Deletions:
~- for packaging specific issues, see Blog20101013MageiaLegallyGreyPackages

Revision [124]

Edited on 2010-10-15 22:33:09 by BenoitAudouard [add copyright attribution]
Additions:
~- for packaging specific issues, see Blog20101013MageiaLegallyGreyPackages

Revision [121]

Edited on 2010-10-14 14:43:37 by GoOm [add copyright attribution]
Additions:
=== Laws applicable to Mageia ===
~- Mageia.org registred in France, French Laws applies
~- Mirrors of Mageia are under local laws, responsability of maintainer of mirror to comply with local laws
~~- can mirrors delete on part of repos if needed by local laws → should be yes

Revision [114]

Edited on 2010-10-13 22:20:41 by BenoitAudouard [add copyright attribution]
Additions:
The legal issue is important for a new distribution, there are several aspects to be covered
Deletions:
rThe legal issue is important for a new distribution, there are several aspects to be covered

Revision [113]

Edited on 2010-10-13 22:20:24 by BenoitAudouard [add copyright attribution]
Deletions:
r

Revision [112]

Edited on 2010-10-13 22:15:48 by BenoitAudouard [add copyright attribution]
Additions:
~- responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users, magazines distributing CD/DVD, sites selling CD/DVD
Deletions:
~- responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users

Revision [111]

Edited on 2010-10-13 00:46:09 by BenoitAudouard [add copyright attribution]
Additions:
rThe legal issue is important for a new distribution, there are several aspects to be covered
~~~- for >13000 packages in the distribution? well, who can take descriptions from plf (well documented to tag it and give advice about what should be included in mageia as a "must have"? see [[http://en.wikipedia.org/wiki/MoSCoW_Method MoSCoW]] )
r
Deletions:
The legal issue is important for a new distribution, there are several aspects to be covered
~~~- for >13000 packages in the distrribution? well, who can take descriptions from plf (well documented to tag it and give advice about what should be included in mageia as a "must have"? see [[http://en.wikipedia.org/wiki/MoSCoW_Method MoSCoW]] )

Revision [110]

Edited on 2010-10-13 00:44:58 by BenoitAudouard [add copyright attribution]
Additions:
~- libre-software with illegal-in-europe patents or trademark issue,
~~- check http://plf.zarb.org/faq.php and http://plf.zarb.org/about.php to provide end-user with easiest way to benefit from what is available, keeping in mind responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users
~~- well, just distribute through plf - as usual - no change :)
~~- room for improvement: see below
~- Mageia keeps on responsibly managing these kinds of risks, based on experience of its members understanding globalcontext & shortcuts
Deletions:
~- libre-software with illegal-in-europe patents or trademark issue, check http://plf.zarb.org/faq.php and http://plf.zarb.org/about.php to provide end-user with easiest way to benefit from what is available, keeping in mind responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users
~- Mageia keeps on responsibly managing these kinds of risks, based on experience of its members

Revision [109]

Edited on 2010-10-13 00:38:15 by BenoitAudouard [add copyright attribution]
Additions:
~- libre software with identified libre licensing and no legal issue :
~~- mageia managed and promoted, work in common with local initiative, take into account contributions whenever possible and promote commiters (packager or maintainer or user workgroup integration)
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...) :
~~- identify clearly which derived works by communities is possible (e.g. nvidia, flash, other?)
Deletions:
~- libre software with identified libre licensing and no legal issue : mageia managed and promoted, work in common with local initiative, take into account contributions whenever possible and promote commiters (packager or maintainer or user workgroup integration)
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...) : identify clearly which derived works by communities is possible (e.g. nvidia, flash, other?)

Revision [108]

Edited on 2010-10-13 00:37:22 by BenoitAudouard [add copyright attribution]
Additions:
~- the current plan is to keep those packages in a dedicated repository at the choice of the admin-mirror
~- what are the risks for our users? none identified at the moment, for example nobody has been sued for using libdvdcss (counter-example?)
~- Mageia keeps on responsibly managing these kinds of risks, based on experience of its members
==vlc==
http://www.videolan.org/press/2010-1.html AOL requires to suppress shoutcast functionality
no problem with codecs, even if patented, as it's illegall in Europe to patent this kind of thing
Deletions:
http://www.videolan.org/press/2010-1.html

Revision [107]

Edited on 2010-10-13 00:29:41 by BenoitAudouard [add copyright attribution]
Additions:
===what are the risks?===
~- cease & desist (from DMCA): should it concern the whole distribution or a single repository (which side-effects? one package would be better, from mirror-admin point of view, should be one directory, keeping the rest available)
~~- is it necessary to have patents / not_relevant_patents / DMCA / crypto / DADVSI|LOPPSI or a single directory? may be in the src.rpm description? to be pragmatic, just check how many packages are concerned at the moment
~~~- 86 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/non-free/source/
~~~- 184 in http://distrib-coffee.ipsl.jussieu.fr/pub/linux/plf/mandriva/cooker/free/source/
~~~- for >13000 packages in the distrribution? well, who can take descriptions from plf (well documented to tag it and give advice about what should be included in mageia as a "must have"? see [[http://en.wikipedia.org/wiki/MoSCoW_Method MoSCoW]] )

Revision [106]

Edited on 2010-10-13 00:12:50 by BenoitAudouard [add copyright attribution]
Additions:
~- libre software with identified libre licensing and no legal issue : mageia managed and promoted, work in common with local initiative, take into account contributions whenever possible and promote commiters (packager or maintainer or user workgroup integration)
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...) : identify clearly which derived works by communities is possible (e.g. nvidia, flash, other?)
~- libre-software with illegal-in-europe patents or trademark issue, check http://plf.zarb.org/faq.php and http://plf.zarb.org/about.php to provide end-user with easiest way to benefit from what is available, keeping in mind responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users
Deletions:
~- libre software with identified libre licensing and no legal issue
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...)
~- libre-software with illegal-in-europe patents or trademark issue, check

Revision [105]

Edited on 2010-10-12 23:46:42 by BenoitAudouard [add copyright attribution]
Additions:
~- responsibilities of those involved: upstream, packagers, mirror-admin, testers, developers, users
~- add cease & desist risk (DMCA)


===implementation in Mageia===
Those legal issues can be treated in the continuity of existing practices :
~- libre software with identified libre licensing and no legal issue
~- non-free software distributed with needed clauses (contract for flash, non-commercial clause...)
~- libre-software with illegal-in-europe patents or trademark issue, check
https://www.mageia.org/pipermail/mageia-dev/20101012/001084.html
===upstream impacts of legal approach===
Deletions:
~- responsibilities of those involved: packagers, mirror-admin, testers, developers, users
=== VLC and shoutcast ===

Revision [104]

Edited on 2010-10-12 23:45:05 by AOrleans-154-1-72-107.w90-20.abo.wanadoo.fr [add copyright attribution]
Additions:
=== VLC and shoutcast ===
http://www.videolan.org/press/2010-1.html

Revision [87]

Edited on 2010-10-11 02:18:04 by BenoitAudouard [add association status]
Additions:
===Other references (for association structure mainly)===
http://www.gnomefr.org/association/statuts/
http://www.gnomefr.org/association/reglement/

Revision [82]

Edited on 2010-10-10 03:30:12 by BenoitAudouard [add association status]
Additions:
check [[http://cookerspot.tuxfamily.org/wikka.php?wakka=CategoryLibreAdvocacy CategoryLibreAdvocacy]], particularly [[http://cookerspot.tuxfamily.org/wikka.php?wakka=ContributionLibre ContributionLibre]] (in french)
Deletions:
check CategoryLibreAdvocacy particularly ContributionLibre (in french)

Revision [69]

Edited on 2010-10-10 03:01:41 by BenoitAudouard [add association status]
Additions:
~- Fedora vs Red Hat?
Deletions:
~- Fedora vs RedHat?

Revision [51]

The oldest known version of this page was created on 2010-10-09 22:49:33 by BenoitAudouard [add association status]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki