Next week we want to launch the updated https://savecodeshare.eu website (attached the draft how it will most likely look like). For the launch we will also need some share graphics people can use on social media and on blogs, etc.
They should be in the same format (width/lenght) as the PMPC ones: http://download.fsfe.org/campaigns/pmpc/share-general/
Attached you find a draft for the footer of those graphics. We would like to include quotes (see below) from the white paper with the logos of the organisations and create share graphics out of that.
Beside that there was the other idea to have a git output (white on black):
$ git push origin master To gitlab.com:you/dotfiles.git ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'git@gitlab.com:you/dotfiles.git' hint: Your code has been rejected because our filtering technology, mandated by Art 13 of the EU "Copyright Reform", suspected a copyright violation. In case you think that is a mistake please get in contact with your git platform provider.
on a share graphic. Other ideas were:
- Use it as template for other quotes * ex.: "git push" results in suspected copyright infringement * ex.: VLC player acts up * ex.: Screenshots out of different editors (vim, emacs, yada yada) * Graphics with git, gitlab, other services from paper.... Then "Endangered by new EU legislation. Act now https://savecodeshare.eu" * Cultural Heritage endangered by EU copyright reform? (Software Heritage) * Graphic: Command line output: "$docker pull gitea/gitea:latest - Warning: you might be liable for your users" #savethecode
Would anyone of you be able to do that until Tuesday, or latest Wednesday next week? Please tell me asap, else I need to find another solution for this. And yes, feel free to be creative about it.
Best Regards, Matthias
# Quotes from White Paper for Share graphics
“Those kind of laws (the proposal) are destructive to the open source innovation.” Jean-Baptiste Kempf: President _ VideoLAN
[1]https://upload.wikimedia.org/wikipedia/commons/thumb/e/e6/VLC_Icon.svg/680px... [2]https://images.videolan.org/images/logoBlue.png
“Nowadays almost all companies and individuals in Free and Open Source Software are using version control systems to develop, plan, coordinate, and document their work. The information in those version control systems embodies precious technical and scientific knowledge and humanity cannot afford the risk of losing it.” Roberto Di Cosmo:Founder/CEO _ Software Heritage https://upload.wikimedia.org/wikipedia/commons/7/74/Software-heritage-logo-t...
“Almost all of our development is based on a web-based version control repository, and such tools play a key role in the processes of open source development and collaboration.” Richard Brown: Chairman _ openSUSE https://raw.githubusercontent.com/openSUSE/artwork/master/Logo/official-logo...
“If the new copyright directive in any way hinders innovation for the modernization of the (...) public sector then the directive is defective and harmful.” Daniel Melin : Senior Procurement Officer ICT _ Swedish National Procurement Services http://www.inpeople.se/wp-content/uploads/2014/01/Kammarkollegiet-logo.jpg (warning: not labeled with a license for reuse & sharing).
“Mozilla’s mission includes the principle that “free and open source software promotes the development of the internet as a public resource.” Many code hosting sites, some run by volunteers, participate in and enrich this ecosystem. For these sites, existing licensing systems, including open licensing, are effective. Requiring them all to create expensive scanning mechanisms and intrusive user monitoring, and deal with the resulting false positives, would establish a prohibitive environment for the development of open source software. This unintended negative consequence underlines just how broad, disproportionate, and dangerous the proposed Article 13 is for the health and vitality of the creative and open internet, and we continue to strongly oppose it.” Raegan MacDonald : Senior EU Policy Manager _ Mozilla https://upload.wikimedia.org/wikipedia/commons/d/d2/Mozilla_logo.svg
“To what extent KDE is directly impacted by the proposed regulation fully depends on whether the above setup would make us “information society service providers storing and giving access to large amounts of works and other subject-matter uploaded by their users”. If yes, then we would probably need to move most of our infrastructure and organization outside of the EU.” Thomas Pfeiffer: Board Member _ KDE https://upload.wikimedia.org/wikipedia/commons/thumb/a/a7/KDE4_logo_preview....
“These particular types of software development service or ‘platform’ do not belong in the proposed Copyright Directive. However, as a precautionary necessity, it is important for the European Parliament and Commission to provide legal clarity and reassurance early on in the first stage of the co-regulation procedure.” James Lovegrove: EMEA Public Affairs Director _ Red Hat https://upload.wikimedia.org/wikipedia/en/thumb/6/6c/RedHat.svg/1280px-RedHa...
“Article 13 creates a high level of uncertainty for the software industry and the free and open source software community, which are drivers of economic growth, jobs, education, innovation, and the democratization of technology. The article should be struck entirely, or at least tailored to exclude software development.” Tal Niv: VP Law and Policy _ GitHub https://upload.wikimedia.org/wikipedia/commons/thumb/2/24/GitHub_logo_2013_p...
Hi Matthias,
Thanks for the email. Adding Anxhelo to cc as he will be helping with this as well. We should have this ready by Monday at latest so you have a bit of time to review and tweak if needed (to make sure we understood the requirements right). We will send you PNG exports and Inkscape SVG source files.
P.S: Have you considered opening up a designer internship position at FSFE? We would happily promote it at Open Source Design.
Cheers, Elio
---- On Fri, 29 Sep 2017 05:57:43 +0000 Matthias Kirschner <mk@fsfe.org> wrote ----
Next week we want to launch the updated https://savecodeshare.eu website
(attached the draft how it will most likely look like). For the launch
we will also need some share graphics people can use on social media and
on blogs, etc.
They should be in the same format (width/lenght) as the PMPC ones:
http://download.fsfe.org/campaigns/pmpc/share-general/
Attached you find a draft for the footer of those graphics. We would
like to include quotes (see below) from the white paper with the logos
of the organisations and create share graphics out of that.
Beside that there was the other idea to have a git output (white on
black):
$ git push origin master
To gitlab.com:you/dotfiles.git
! [rejected] master -> master (non-fast-forward)
error: failed to push some refs to 'git@gitlab.com:you/dotfiles.git'
hint: Your code has been rejected because our filtering technology,
mandated by Art 13 of the EU "Copyright Reform", suspected a copyright
violation. In case you think that is a mistake please get in contact
with your git platform provider.
on a share graphic. Other ideas were:
- Use it as template for other quotes
* ex.: "git push" results in suspected copyright infringement
* ex.: VLC player acts up
* ex.: Screenshots out of different editors (vim, emacs, yada yada)
* Graphics with git, gitlab, other services from paper.... Then
"Endangered by new EU legislation. Act now https://savecodeshare.eu"
* Cultural Heritage endangered by EU copyright reform? (Software
Heritage)
* Graphic: Command line output:
"$docker pull gitea/gitea:latest - Warning: you might be liable for
your users" #savethecode
Would anyone of you be able to do that until Tuesday, or latest
Wednesday next week? Please tell me asap, else I need to find another
solution for this. And yes, feel free to be creative about it.
Best Regards,
Matthias
# Quotes from White Paper for Share graphics
“Those kind of laws (the proposal) are destructive to the open source
innovation.”
Jean-Baptiste Kempf: President _ VideoLAN
[1]https://upload.wikimedia.org/wikipedia/commons/thumb/e/e6/VLC_Icon.svg/680px...
[2]https://images.videolan.org/images/logoBlue.png
“Nowadays almost all companies and individuals in Free and Open Source
Software are using version control systems to develop, plan, coordinate,
and document their work. The information in those version control
systems embodies precious technical and scientific knowledge and
humanity cannot afford the risk of losing it.”
Roberto Di Cosmo:Founder/CEO _ Software Heritage
https://upload.wikimedia.org/wikipedia/commons/7/74/Software-heritage-logo-t...
“Almost all of our development is based on a web-based version control
repository, and such tools play a key role in the processes of open
source development and collaboration.”
Richard Brown: Chairman _ openSUSE
https://raw.githubusercontent.com/openSUSE/artwork/master/Logo/official-logo...
“If the new copyright directive in any way hinders innovation for the
modernization of the (...) public sector then the directive is defective
and harmful.”
Daniel Melin : Senior Procurement Officer ICT _ Swedish National
Procurement Services
http://www.inpeople.se/wp-content/uploads/2014/01/Kammarkollegiet-logo.jpg
(warning: not labeled with a license for reuse & sharing).
“Mozilla’s mission includes the principle that “free and open source
software promotes the development of the internet as a public resource.”
Many code hosting sites, some run by volunteers, participate in and
enrich this ecosystem. For these sites, existing licensing systems,
including open licensing, are effective. Requiring them all to create
expensive scanning mechanisms and intrusive user monitoring, and deal
with the resulting false positives, would establish a prohibitive
environment for the development of open source software. This unintended
negative consequence underlines just how broad, disproportionate, and
dangerous the proposed Article 13 is for the health and vitality of the
creative and open internet, and we continue to strongly oppose it.”
Raegan MacDonald : Senior EU Policy Manager _ Mozilla
https://upload.wikimedia.org/wikipedia/commons/d/d2/Mozilla_logo.svg
“To what extent KDE is directly impacted by the proposed regulation
fully depends on whether the above setup would make us “information
society service providers storing and giving access to large amounts of
works and other subject-matter uploaded by their users”. If yes, then we
would probably need to move most of our infrastructure and organization
outside of the EU.”
Thomas Pfeiffer: Board Member _ KDE
https://upload.wikimedia.org/wikipedia/commons/thumb/a/a7/KDE4_logo_preview....
“These particular types of software development service or ‘platform’ do
not belong in the proposed Copyright Directive. However, as a
precautionary necessity, it is important for the European Parliament and
Commission to provide legal clarity and reassurance early on in the
first stage of the co-regulation procedure.”
James Lovegrove: EMEA Public Affairs Director _ Red Hat
https://upload.wikimedia.org/wikipedia/en/thumb/6/6c/RedHat.svg/1280px-RedHa...
“Article 13 creates a high level of uncertainty for the software
industry and the free and open source software community, which are
drivers of economic growth, jobs, education, innovation, and the
democratization of technology. The article should be struck entirely, or
at least tailored to exclude software development.”
Tal Niv: VP Law and Policy _ GitHub
https://upload.wikimedia.org/wikipedia/commons/thumb/2/24/GitHub_logo_2013_p...
Hello Matthias,
I have prepared some initial drafts for this, they are in .png format and attached. You can review them and give your feedback if any further tweaks are needed :)
Cheers, Anxhelo
On 09/29/2017 10:28 AM, Elio Qoshi wrote:
Hi Matthias,
Thanks for the email. Adding Anxhelo to cc as he will be helping with this as well. We should have this ready by Monday at latest so you have a bit of time to review and tweak if needed (to make sure we understood the requirements right). We will send you PNG exports and Inkscape SVG source files.
P.S: Have you considered opening up a designer internship position at FSFE? We would happily promote it at Open Source Design.
Cheers, Elio
---- On Fri, 29 Sep 2017 05:57:43 +0000 *Matthias Kirschner mk@fsfe.org* wrote ----
Next week we want to launch the updated https://savecodeshare.eu website (attached the draft how it will most likely look like). For the launch we will also need some share graphics people can use on social media and on blogs, etc. They should be in the same format (width/lenght) as the PMPC ones: http://download.fsfe.org/campaigns/pmpc/share-general/ Attached you find a draft for the footer of those graphics. We would like to include quotes (see below) from the white paper with the logos of the organisations and create share graphics out of that. Beside that there was the other idea to have a git output (white on black): $ git push origin master To gitlab.com:you/dotfiles.git ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'git@gitlab.com <mailto:git@gitlab.com>:you/dotfiles.git' hint: Your code has been rejected because our filtering technology, mandated by Art 13 of the EU "Copyright Reform", suspected a copyright violation. In case you think that is a mistake please get in contact with your git platform provider. on a share graphic. Other ideas were: - Use it as template for other quotes * ex.: "git push" results in suspected copyright infringement * ex.: VLC player acts up * ex.: Screenshots out of different editors (vim, emacs, yada yada) * Graphics with git, gitlab, other services from paper.... Then "Endangered by new EU legislation. Act now https://savecodeshare.eu" * Cultural Heritage endangered by EU copyright reform? (Software Heritage) * Graphic: Command line output: "$docker pull gitea/gitea:latest - Warning: you might be liable for your users" #savethecode Would anyone of you be able to do that until Tuesday, or latest Wednesday next week? Please tell me asap, else I need to find another solution for this. And yes, feel free to be creative about it. Best Regards, Matthias # Quotes from White Paper for Share graphics “Those kind of laws (the proposal) are destructive to the open source innovation.” Jean-Baptiste Kempf: President _ VideoLAN [1]https://upload.wikimedia.org/wikipedia/commons/thumb/e/e6/VLC_Icon.svg/680px-VLC_Icon.svg.png [2]https://images.videolan.org/images/logoBlue.png “Nowadays almost all companies and individuals in Free and Open Source Software are using version control systems to develop, plan, coordinate, and document their work. The information in those version control systems embodies precious technical and scientific knowledge and humanity cannot afford the risk of losing it.” Roberto Di Cosmo:Founder/CEO _ Software Heritage https://upload.wikimedia.org/wikipedia/commons/7/74/Software-heritage-logo-title.2048px.png “Almost all of our development is based on a web-based version control repository, and such tools play a key role in the processes of open source development and collaboration.” Richard Brown: Chairman _ openSUSE https://raw.githubusercontent.com/openSUSE/artwork/master/Logo/official-logo-color.png “If the new copyright directive in any way hinders innovation for the modernization of the (...) public sector then the directive is defective and harmful.” Daniel Melin : Senior Procurement Officer ICT _ Swedish National Procurement Services http://www.inpeople.se/wp-content/uploads/2014/01/Kammarkollegiet-logo.jpg (warning: not labeled with a license for reuse & sharing). “Mozilla’s mission includes the principle that “free and open source software promotes the development of the internet as a public resource.” Many code hosting sites, some run by volunteers, participate in and enrich this ecosystem. For these sites, existing licensing systems, including open licensing, are effective. Requiring them all to create expensive scanning mechanisms and intrusive user monitoring, and deal with the resulting false positives, would establish a prohibitive environment for the development of open source software. This unintended negative consequence underlines just how broad, disproportionate, and dangerous the proposed Article 13 is for the health and vitality of the creative and open internet, and we continue to strongly oppose it.” Raegan MacDonald : Senior EU Policy Manager _ Mozilla https://upload.wikimedia.org/wikipedia/commons/d/d2/Mozilla_logo.svg “To what extent KDE is directly impacted by the proposed regulation fully depends on whether the above setup would make us “information society service providers storing and giving access to large amounts of works and other subject-matter uploaded by their users”. If yes, then we would probably need to move most of our infrastructure and organization outside of the EU.” Thomas Pfeiffer: Board Member _ KDE https://upload.wikimedia.org/wikipedia/commons/thumb/a/a7/KDE4_logo_preview.svg/1024px-KDE4_logo_preview.svg.png “These particular types of software development service or ‘platform’ do not belong in the proposed Copyright Directive. However, as a precautionary necessity, it is important for the European Parliament and Commission to provide legal clarity and reassurance early on in the first stage of the co-regulation procedure.” James Lovegrove: EMEA Public Affairs Director _ Red Hat https://upload.wikimedia.org/wikipedia/en/thumb/6/6c/RedHat.svg/1280px-RedHat.svg.png “Article 13 creates a high level of uncertainty for the software industry and the free and open source software community, which are drivers of economic growth, jobs, education, innovation, and the democratization of technology. The article should be struck entirely, or at least tailored to exclude software development.” Tal Niv: VP Law and Policy _ GitHub https://upload.wikimedia.org/wikipedia/commons/thumb/2/24/GitHub_logo_2013_padded.svg/1280px-GitHub_logo_2013_padded.svg.png -- Matthias Kirschner - President - Free Software Foundation Europe Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290 Registered at Amtsgericht Hamburg, VR 17030 | (fsfe.org/join) Contact (fsfe.org/about/kirschner) - Weblog (k7r.eu/blog.html)
Hello Anxhelo,
* Anxhelo Lushka [2017-09-29 22:26 +0200]:
I have prepared some initial drafts for this, they are in .png format and attached. You can review them and give your feedback if any further tweaks are needed :)
Thank you very much. I like them!
After hellekins feedback, I would propose to change the _text_ of the git version.
@Carmen: the comment was that if we use gitlab, we should clarify it with them beforehand. I agree that it would not be good to use them without their permission, but I thought that the better option would be to use git.fsfe.org as the example. Could you have a look at the example below and make sure it is correct for git.fsfe.org? Here the new proposal:
| $ git push origin master | To git.fsfe.org:you/dotfiles.git | ! [rejected] master -> master (non-fast-forward) | error: failed to push some refs to 'git@git.fsfe.org:you/dotfiles.git' | hint: Your code has been rejected because our filtering technology, | mandated by Art 13 of the EU "Copyright Reform", suspected a copyright | violation. In case you think that is a mistake please get in contact | with your git platform provider.
All the best, Matthias
Hello,
On sab, 2017-09-30 at 04:06 +0000, Matthias Kirschner wrote:
@Carmen: the comment was that if we use gitlab, we should clarify it with them beforehand. I agree that it would not be good to use them without their permission, but I thought that the better option would be to use git.fsfe.org as the example. Could you have a look at the example below and make sure it is correct for git.fsfe.org? Here the new proposal:
$ git push origin master To git.fsfe.org:you/dotfiles.git ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'git@git.fsfe.org:you/dotfiles.git' hint: Your code has been rejected because our filtering technology, mandated by Art 13 of the EU "Copyright Reform", suspected a copyright violation. In case you think that is a mistake please get in contact with your git platform provider.
Looks good. I had to do a bit more research, though, because I wasn't sure. So I created a repository that explicitly forbids me to push, rather than trying to do a false push. To be 100% faithful to the git command line, it ought look like this:
$ git push origin master Counting objects: 1, done. Writing objects: 100% (1/1), 852 bytes | 852.00 KiB/s, done. Total 1 (delta 0), reused 0 (delta 0) remote: GitLab: You are not allowed to push code to protected branches on this project. To gitlab.com:carmenbianca/web.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'git@gitlab.com:carmenbianca/web.git'
But that looks awful (the `remote` message is lost in the middle and there's a lot of needless extra fluff), so I suggest:
$ git push origin master To git.fsfe.org:you/dotfiles.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'git@git.fsfe.org:you/project.git' remote: Your code has been rejected because our filtering technology, remote: mandated by Art 13 of the EU "Copyright Reform", suspected a remote: copyright violation. In case you think that is a mistake remote: please get in contact with your git platform provider.
If you want, for clarity, you can add an extra line like this for extra emphasis (or just make the line empty so that the `remote` lines stand out):
$ git push origin master To git.fsfe.org:you/dotfiles.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'git@git.fsfe.org:you/project.git' remote: ERROR: Suspected copyright violation remote: Your code has been rejected because our filtering technology, remote: mandated by Art 13 of the EU "Copyright Reform", suspected a remote: copyright violation. In case you think that is a mistake remote: please get in contact with your git platform provider.
I hope that helps!
Yours,
* Carmen Bianca Bakker [2017-09-30 09:01 +0200]:
But that looks awful (the `remote` message is lost in the middle and there's a lot of needless extra fluff), so I suggest:
$ git push origin master To git.fsfe.org:you/dotfiles.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'git@git.fsfe.org:you/project.git' remote: Your code has been rejected because our filtering technology, remote: mandated by Art 13 of the EU "Copyright Reform", suspected a remote: copyright violation. In case you think that is a mistake remote: please get in contact with your git platform provider.
That suggestion looks good. Anxhelo, unless you feel another solution is better, please implement this. Maybe highlight "Error" and the message in remote a bit.
Cheers, Matthias
Hello Matthias,
I have replaced the main git image with the text you provided and created many other share graphics, you will find all of them attached in .png format altogether with the main template used in Inkscape .svg format.
Cheers, Anxhelo
On 09/30/2017 11:25 AM, Matthias Kirschner wrote:
- Carmen Bianca Bakker [2017-09-30 09:01 +0200]:
But that looks awful (the `remote` message is lost in the middle and there's a lot of needless extra fluff), so I suggest:
$ git push origin master To git.fsfe.org:you/dotfiles.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'git@git.fsfe.org:you/project.git' remote: Your code has been rejected because our filtering technology, remote: mandated by Art 13 of the EU "Copyright Reform", suspected a remote: copyright violation. In case you think that is a mistake remote: please get in contact with your git platform provider.
That suggestion looks good. Anxhelo, unless you feel another solution is better, please implement this. Maybe highlight "Error" and the message in remote a bit. Cheers, Matthias
Hi Anxhelo, all,
On (some of) your graphics, the hashtag «#savethecode» is used. I believe this ought be «#savecodeshare»?
Yours sincerely,
Hi Carmen,
Yes, my mistake there. Fixed now, reattaching the files.
Cheers, Anxhelo
On 09/30/2017 03:58 PM, Carmen Bianca Bakker wrote:
Hi Anxhelo, all,
On (some of) your graphics, the hashtag «#savethecode» is used. I believe this ought be «#savecodeshare»?
Yours sincerely,
Hi Anxhelo,
Thank you so much for your great work on that! These look great!
On 01.10.2017 10:26, Anxhelo Lushka wrote:
Yes, my mistake there. Fixed now, reattaching the files.
In the file savethecode_hashtag.png it is still #savethecode instead of #savecodeshare.
Thank you very much once again!
Kind regards, Polina
Hi Polina,
My pleasure, helping FSFE on its mission is really important IMO :)
Oops, it seems it didn't get exported successfully. The new corrected file (hopefully the right one this time haha) is attached.
If you need any other image or graphic, please ping me, will help :)
Cheers, Anxhelo
On 10/02/2017 01:36 PM, Polina Malaja wrote:
Hi Anxhelo,
Thank you so much for your great work on that! These look great!
On 01.10.2017 10:26, Anxhelo Lushka wrote:
Yes, my mistake there. Fixed now, reattaching the files.
In the file savethecode_hashtag.png it is still #savethecode instead of #savecodeshare.
Thank you very much once again!
Kind regards, Polina
Anxhelo, again also thank you very much for your great help with that!
Best Regards, Matthias
* Elio Qoshi [2017-09-29 10:28 +0200]:
Thanks for the email. Adding Anxhelo to cc as he will be helping with this as well. We should have this ready by Monday at latest so you have a bit of time to review and tweak if needed (to make sure we understood the requirements right). We will send you PNG exports and Inkscape SVG source files.
Thank you already. To avoid double work, please see that there were already some proposals by hellekin.
P.S: Have you considered opening up a designer internship position at FSFE? We would happily promote it at Open Source Design.
No. Before we open a internship position we would need to clarify that there is a mentor, so the intern can actually learn from someone experienced -- else it would just be a cheap work position. If you have ideas how we could open such a position but make sure that the intern actually learns from professionals, please let me know.
Regards, Matthias
* Matthias Kirschner [2017-09-30 05:47 +0200]:
- Elio Qoshi [2017-09-29 10:28 +0200]:
Thanks for the email. Adding Anxhelo to cc as he will be helping with this as well. We should have this ready by Monday at latest so you have a bit of time to review and tweak if needed (to make sure we understood the requirements right). We will send you PNG exports and Inkscape SVG source files.
Thank you already. To avoid double work, please see that there were already some proposals by hellekin.
Sorry, please ignore this above, it was a stupid mistake on my side while using my mail client.
There are no other proposals than the ones from Anxhelo I know of.
On Fri, 29 Sep 2017 05:57:43 +0000 Matthias Kirschner mk@fsfe.org wrote:
Next week we want to launch the updated https://savecodeshare.eu website (attached the draft how it will most likely look like). For the launch we will also need some share graphics people can use on social media and on blogs, etc.
Hi Matthias,
I like the git push idea, and I think it would be good to propose it directly to Gitlab people: first, they might have issues with appearing in this position, and second, they might be able to provide the necessary graphics work themselves.
on a share graphic. Other ideas were:
- Use it as template for other quotes
Following the spirit of the git push, I would add something like:
~/work/core-system/src$ make make: *** missing dependencies. Upstream reports Art 13 copyright violation. Cannot continue.
Would anyone of you be able to do that until Tuesday, or latest Wednesday next week? Please tell me asap, else I need to find another solution for this. And yes, feel free to be creative about it.
Do you have SVG sources? I might be able to make one or two.
Jan, is there a related topic on https://discourse.opensourcedesign.net/ ?
Regards,
== hk
Hello hellekin,
* hellekin [2017-09-29 22:46 +0200]:
I like the git push idea, and I think it would be good to propose it directly to Gitlab people: first, they might have issues with appearing in this position, and second, they might be able to provide the necessary graphics work themselves.
Good point. See my other mail about it.
on a share graphic. Other ideas were:
- Use it as template for other quotes
Following the spirit of the git push, I would add something like:
~/work/core-system/src$ make make: *** missing dependencies. Upstream reports Art 13 copyright violation. Cannot continue.
Not sure, if I miss something but how is the proposal related to a compile process on your computer?
Would anyone of you be able to do that until Tuesday, or latest Wednesday next week? Please tell me asap, else I need to find another solution for this. And yes, feel free to be creative about it.
Do you have SVG sources? I might be able to make one or two.
No I don't, this was provided by OFE as an idea how it could look like.
Regards, Matthias
On Sat, 30 Sep 2017 04:09:34 +0000 Matthias Kirschner mk@fsfe.org wrote:
git push idea [...] good to propose it to Gitlab people
Good point. See my other mail about it.
Ack.
~/work/core-system/src$ make make: *** missing dependencies. Upstream reports Art 13 copyright violation. Cannot continue.
Not sure, if I miss something but how is the proposal related to a compile process on your computer?
I agree it would take a lot more lines to make sense. Probably docker, node, or go are more straightforward, since they already work with upstream sources... Actually it would make sense with guix as well... The point is that if Art. 13 is in effect, some dependencies might just vanish and cascade to break other software.
Do you have SVG sources? I might be able to make one or two.
No I don't, this was provided by OFE as an idea how it could look like.
Ack. Then an indication of which fonts are used, and the exact colors might be useful. For the latter it's easy to find but my typographic recognition is not that good.
Cheers,
== hk
