Bug#905674: Citation notice FAQ
Hi Kurt Fitzner You question whether software should be cited and if so how? These links suggest: Yes, you should cite software, and if the author suggests a way of citing use that. * https://blog.apastyle.org/apastyle/2015/01/how-to-cite-software-in-apa-style.html * https://libguides.mit.edu/c.php?g=551454=3900280 * https://www.software.ac.uk/how-cite-software * https://aut.ac.nz.libguides.com/APA6th/software * https://libguides.rgu.ac.uk/c.php?g=380081=2983956 * https://journals.aas.org/policy-statement-on-software/ * https://guides.lib.monash.edu/c.php?g=219786=1454293 * https://www.maxqda.com/how-to-cite-maxqda If you feel the benefit from using GNU Parallel is too small to warrant a citation, then prove that by simply using another tool. Here are other examples of software showing how to cite. Some of these refer to peer-reviewed articles - others do not: * https://www.scipy.org/citing.html * https://octave.org/doc/interpreter/Citing-Octave-in-Publications.html (Octave has citation for individual packages, too) * https://stat.ethz.ch/pipermail/r-help/2008-May/161481.html * https://stat.ethz.ch/R-manual/R-devel/library/utils/html/citation.html (R has citation for individual packages, too) * http://www.partek.com/citing-partek-software-in-a-publication/ * http://www.fluortools.com/misc/cite * https://www.maxqda.com/how-to-cite-maxqda * https://www.open-mpi.org/papers/ * https://www.tensorflow.org/about/bib * http://www.fon.hum.uva.nl/paul/praat.html I would think that most people, who appreciate GNU Parallel, would be happy to help funding the development even if it is simply by making a citation. So what really puzzles me is: If you feel very strongly against helping to fund future development of GNU Parallel, why not use an alternative tool? No one forces you to use GNU Parallel. Here is a list of alternatives to help you choose: https://www.gnu.org/software/parallel/parallel_alternatives.html You also pose it might be bad if more software asked for citations. Let us make one thing abundantly clear: The reason for the citing notice in GNU Parallel is _funding_ - not prestige of being cited in an academic journal, as you hint. It has never been a secret and has been explained from the start: https://lists.gnu.org/archive/html/parallel/2013-11/msg6.html If you find another way to pay my salary, so I can continue to devote time to develop GNU Parallel, then I will have no objections to removing the notice. So please help solve that problem. Not only will it please me, but if you find a general solution, many other free software developers will thank you for it. Focusing on how we can get more free software funded is constructive. Focusing on how we can remove funding for existing free software is not. It is unclear to me why you think that funding through citations suddenly will be the prevailing way of funding, if Debian affirms GNU Parallel's version of an 'OK. Do not show this again'-message (just like the GUI-messages this message can be silenced in less than 10 seconds, and if you do not save more than 10 seconds by using GNU Parallel, maybe you should not be using it anyway). First of all, I think that is unrealistic that this sudden change will happen (most other software is financed in different ways). But even if it _did_ happen, then you would be free to use different tools (or develop your own), if you prefer not to cite. To me your email could be summarized as: "I do not want to help fund the development, but I want to reap all the benefits - even if that means killing the long term development." To me it seems it is you whom Nadia Eghbal addresses in https://www.slideshare.net/NadiaEghbal/consider-the-maintainer: "Is it alright to compromise, or even deliberately ignore, the happiness of maintainers so we that can enjoy free and open source software?" == Citation notice FAQ == > Why does GNU Parallel show a citation notice? GNU Parallel is indirectly funded through citations. It is therefore important for the long term survival of GNU Parallel that it is cited. The citation notice makes users aware of this. See also: https://lists.gnu.org/archive/html/parallel/2013-11/msg6.html > Is the citation notice compatible with GPLv3? Yes. The wording has been cleared by Richard M. Stallman to be compatible with GPLv3. This is because the citation notice is not part of the license, but part of academic tradition. Therefore the notice is not adding a term that would require citation as mentioned on: https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation > Do automated scripts break if the notice is not silenced? No. Not a single time has that happened. This is due to the notice only being printed, if the output is to the screen - not if the output is to a file or a pipe. > How do I silence the citation notice? Run this once: parallel --citation It takes less than 10 seconds to do and is thus comparable to an 'OK. Do not show this again'-dialog
Bug#905674: GNU Parallel patch
Dear Didier Thanks for help organizing the BSP in Bern. I have noticed that you have submitted a patch and closed this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905674#77 I am sure you are trying to do what is best for free software. But what looks like a good idea in the short run, may be a bad idea in the long run. The long term survival of Debian depends on others building free software that can be packaged, so destroying these people's livelihood is a bad long term strategy. In the reasoning for the patch you state: > Quoting the gpl-faq: [... https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation ...] > Therefore, removing this to make parallel GPL-compliant. I think this is due to a misunderstanding. Maybe you not aware that Richard M. Stallman together with the GNU leaders have cleared the wording and the use of the citation notice, and that he sees it as complying fully with GPLv3? And thus not in conflict with https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation The reasoning why there is no conflict is because citing is a matter of honor - not law. Thus it does not restrict anyone from making use of the program in a specific field of endeavor, but simply conveys that you will be taking away future funding for development if you do not cite. The mail from RMS is included below. Your patch therefore does not change the GPLv3-compliancy: The code was already compliant. But what your patch *does* do, is to make it harder to earn a living from developing GNU Parallel and will make it much harder for me to justify spending time maintaining GNU Parallel. Please help building more free software instead of attacking the developer's livelihood. Not everyone is so lucky that they are hired in a company where you get paid to develop free software. As Nadia Eghbal puts it in https://www.slideshare.net/NadiaEghbal/consider-the-maintainer: "Is it alright to compromise, or even deliberately ignore, the happiness of maintainers so we that can enjoy free and open source software?" This describes very well what you are doing with the patch, and I refuse to think that was your goal. So if you want to help other developers make a living and thereby get more free software made, I encourage you to revert the patch and instead upgrade to 20180922: Maybe you simply were not aware that the latest stable version (20180922) is *already* GPLv3 compliant. Thanks for your work on free software. It is appreciated. /Ole On Wed, Oct 17, 2018 at 9:07 AM Richard Stallman wrote: > > [[[ To any NSA and FBI agents reading my email: please consider]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > GNU leaders studied looked at the current version of GNU Parallel. > Based on their report, I've concluded there is no problem in it. : > -- > Dr Richard Stallman > President, Free Software Foundation (https://gnu.org, https://fsf.org) > Internet Hall-of-Famer (https://internethalloffame.org)
Bug#905674: Ready for closing?
Upgrading from 20141022 to 20180922 seems to address all issues. Can we close this ticket? #884793 was due to user error, thus not breaking scripts. I still have not seen a single situation in which the current behaviour (version 20180922) breaks scripts when used correctly. Make a Minimal, Complete, Verifiable Example to change my mind. --citation was never designed to be used with any other parameter, but only to be run on its own: parallel --citation : > will cite After running this the citation notice is silenced for future runs. In other words: It is optional and takes literally less than 10 seconds to do; thus it is comparable to clicking 'OK, do not show this message again' in a GUI tool. The current (version 20280922) wording of the citation notice has been cleared by Richard M. Stallman and is deemed not in conflict with https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation because citing is a matter of honor - not law. Thus it does not restrict anyone from making use of the program in a specific field of endeavor, but simply conveys that you will be taking away future funding for development if you do not cite. As Nadia Eghbal puts it in https://www.slideshare.net/NadiaEghbal/consider-the-maintainer: "Is it alright to compromise, or even deliberately ignore, the happiness of maintainers so we that can enjoy free and open source software?" /Ole
Bug#905674: Funding free software
Funding a free software project is hard. GNU Parallel is no exception.
On top of that it seems the less visible a project is, the harder it
is to get funding. And the nature of GNU Parallel is that it will
never be seen by "the guy with the checkbook", but only by the people
doing the actual work.
This problem has been covered by others - though no solution has been
found: https://www.slideshare.net/NadiaEghbal/consider-the-maintainer
https://www.numfocus.org/blog/why-is-numpy-only-now-getting-funded/
"Is it alright to compromise or even deliberately ignore the happiness
of the maintainers so that we can enjoy free and open source
software?"
(Slide 8 from: https://www.slideshare.net/NadiaEghbal/consider-the-maintainer)
Before implementing the citation notice it was discussed with the
users: https://lists.gnu.org/archive/html/parallel/2013-11/msg6.html
There is no doubt that this is not an ideal solution, but no one has
so far come up with an ideal solution - neither for funding GNU
Parallel nor other free software.
If you believe you have the perfect solution, you should try it out,
and if it works, you should post it on the email list. Ideas that will
cost work and which have not been tested are, however, unlikely to be
prioritized.
The notice in question:
"""
Academic tradition requires you to cite works you base your article on.
If you use programs that use GNU Parallel to process data for an article in a
scientific publication, please cite:
@book{tange_ole_2018_1146014,
author = {Tange, Ole},
title= {GNU Parallel 2018},
publisher= {Ole Tange},
month= Mar,
year = 2018,
ISBN = {9781387509881},
doi = {10.5281/zenodo.1146014},
url = {https://doi.org/10.5281/zenodo.1146014}
}
(Feel free to use \nocite{tange_ole_2018_1146014})
This helps funding further development; AND IT WON'T COST YOU A CENT.
If you pay 1 EUR you should feel free to use GNU Parallel without
citing.
More about funding GNU Parallel and the citation notice:
https://www.gnu.org/software/parallel/parallel_design.html#Citation-notice
If you send a copy of your published article to ta...@gnu.org, it will
be
mentioned in the release notes of next version of GNU Parallel.
"""
As you can see the citation notice is carefully worded so that it is
not a legal requirement. It was revised in collaboration with RMS to
make sure it was compatible with GPLv3. The notice does not deny users
the ability to use the software as they wish, for whatever purpose
they wish, without payment. It does, however, make it clear what the
wishes of the author are.
There have been rumours that the citation notice broke scripts, but
these rumours have never been backed up by evidence - so an actual
MCVE has never been shown.
As long as we have not found the perfect way of earning a living from
free software, we should try out as many methods as possible. Some
will try one method, and others will try another. If we find a way to
pay my salary I will be happy to remove the notice. And if we manage
to find a general way to fund development of free software, a lot more
developers will be happy, and we will be able to put Nadia Eghbal's
quote in the past:
"Is it alright to compromise or even deliberately ignore the happiness
of the maintainers so that we can enjoy free and open source
software?"
/Ole
On Fri, Aug 10, 2018 at 4:52 AM, Rogério Brito wrote:
> Dear Ole (and others potentially interested in having GNU Parallel in
> Debian's and derivatives' repositories),
>
> I don't know if you have been following the emails on the Debian BTS
> regarding GNU Parallel having restrictions regardings its distribution etc.
>
> Since this issue has surfaced itself once again, but now in a more intense
> manner, I believe that, if you have not yet been informed, you may want to
> give your opinion (and I will decide how I should follow my maintainership
> within the constraints of your software and the contraints of Debian).
>
> Thanks,
>
> Rogério Brito...
>
> On Aug 08 2018, Adam Borowski wrote:
>> Actually, it seems to me it's not even distributable.
>>
>> The wording sounds like a requirement rather than something non-mandatory --
>> reinforced by providing the alternative of paying €1. Yet the license
>> is GPL3+, which expressly forbids additional fees. This is even described
>> in FSF's GPL FAQ:
>> https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation
>>
>> Thus, the copyright holder can distribute this software, but no one else
>> can.
>>
>> As the requirement is not a part of the license, we could just remove the
>> demand nagware from the code. But alas, the upstream (Ole Tange) threatened
>> legal action if you do so without renaming
Bug#480775: xserver-xorg-video-intel: ver 2:2.2.1-2 breaks Virtual 2048
Package: xserver-xorg-video-intel Version: 2:2.2.1-2 Severity: grave Justification: renders package unusable xserver-xorg-video-intel version 2:2.2.1-2 crashes if Virtual is 2048. This problem seems to be fixed in 2:2.3.0-1. I suggest either downgrading xserver-xorg-video-intel to 2:2.1.0-2 or upgrading to 2:2.3.0-1. /Ole -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2007-06-28 16:53 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1674940 2008-04-29 20:37 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 6874 2008-05-12 01:33 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # Run this before: #915resolution 58 1400 1050 32 # # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc ## Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout dk EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons true EndSection Section InputDevice Driverwacom Identifierstylus OptionDevice/dev/ttyS0 OptionType stylus OptionForceDevice ISDV4 OptionTilt on Option PressCurve 50,0,100,50 EndSection Section InputDevice Driverwacom Identifiereraser OptionDevice/dev/ttyS0 OptionType eraser OptionForceDevice ISDV4 OptionTilt on EndSection Section InputDevice Driverwacom Identifiercursor OptionDevice/dev/ttyS0 OptionType cursor OptionForceDevice ISDV4 OptionTilt on EndSection Section InputDevice Identifier Synaptics Touchpad Driver synaptics Option SendCoreEventstrue # Option Device/dev/psaux Option Device/dev/input/mouse0 Option Protocol auto-dev Option HorizScrollDelta 0 Option MinSpeed 0.09 Option MaxSpeed 0.78 Option AccelFactor 0.015 Option MaxTapTime180 Option MaxTapMove220 Endsection Section InputDevice Driver synaptics Identifier Synaptics Touchpad2 Option Device/dev/psaux # Option Device/dev/input/mouse0 # Option Protocol auto-dev Option LeftEdge 1700 Option RightEdge
