Live data from Hacker News

Source for theguardian.com

github.com

21–30 of 104 posts

Re: Source for theguardian.com

#21
post #7

IANAL, but this seems to collide with their EULA with Commercial Type [1], since third party hosting of the font files is "strictly prohibited" and the font files are in fact all available in the repo, which certainly doesn't sound like "reasonable effort to prevent access/use by unlicensed parties". [1] https://github.com/guardian/frontend/blob/88cfa609c73545085c...

Though I'll not make any judgement towards "prevent access", the main license file[0] does state: > All fonts are the property of Schwartzco, Inc., t/a Commercial Type ( https://commercialtype.com/ ), and may not be reproduced without permission. As a side tangent, it constantly surprises me how deep the creative industries manage to sink their claws into IP and licensing. I don't understand how artistic commissions…

A font family with the weights and other options a newspaper needs is a major undertaking. It's maybe 5 to 10 person-years of rather specialised work. For a publication constantly fighting to even break even, the costs aren't trivial.

So, the answer obviously is: the Guardian got the font far cheaper by allowing it to be sold to other customers, and (relevant here) not paying for a license that allows sub-licensing (which would be completely useless to them, anyway).

I wouldn't be surprised if it was actually a deal where no money changed hands, with the foundry getting the Guardian name for PR, and constant feedback during the design process.

As to web design: unless otherwise specified, web design is covered by the same copyright rules as fonts (or movies, or books,...). The correct analogy actually is a customer selling your design to some third party, something that probably would upset quite a few designers.

As for the customer changing a design: that's an infringement of the creator's so-called "moral rights". Its legality varies between jurisdictions, I believe.

Re: Source for theguardian.com

#22
post #8

The docs include a recipe for Breton crêpes. :) [1] https://github.com/guardian/frontend/blob/master/docs/99-arc...

Hilarious! What the heck is it doing here?

Looks like an employee on their way out was asked for their crepes recipe. Probably made it regularly for his team.

Re: Source for theguardian.com

#23
post #10

One more reason to support them. Even if you don't always agree with their opinions, it's nice to move away from commercial journalism and keep things as open and transparent as possible.

It's nice to move away from commercial journalism, I agree. But the Guardian is very much commercial journalism. See http://expressiveegg.org/2017/02/07/guardian-bothering/ and https://www.jonathan-cook.net/blog/2015-03-03/hsbc-and-the-s...

Re: Source for theguardian.com

#24

So is the the guardian considered a monolithic app? Does this source include CMS components?

The frontend repository above is only for the user-facing front-end website (aka the guardian.com). Other back-end components such as the content API and the content creation tool (Composer) are separate projects in their own private repos (not open source). That said the Guardian has many other open source projects on their GitHub org [1], including their image management tool for instance [2].

[1] https://github.com/guardian [2] https://github.com/guardian/grid

Re: Source for theguardian.com

#25
post #8

The docs include a recipe for Breton crêpes. :) [1] https://github.com/guardian/frontend/blob/master/docs/99-arc...

This is not even close to bretonne crêpes.

Either you use buckwheat floor and water, in which case you are making Galettes. Either you use plain white wheat floor, in which case it's crêpes you are doing.

Under no circumstances you can put sugar in it, it's only added at the end. And of course, it's missing the most important ingredient: butter. #notevenclose

Re: Source for theguardian.com

#26
post #9

Earlier quoted context omitted.

> I can't see more commercially-oriented paper/website open-sourcing any of their code, even if it's a (good imho) recruitment ploy. https://github.com/nytimes https://github.com/BostonGlobe https://github.com/npr & https://github.com/nprapps https://github.com/theatlantic https://github.com/wsj ... I really wish people wouldn't always assume the worst of the media. Especially when it takes about two seconds to verif…

I would recommend to double check those links to the github orgs, I’m sorry to say they are small projects. Can’t compare with publishing the whole frontend, their image managing library and their text editor.

The NYT has 65 projects, most of which have a few hundred stars, and many in the thousands.

It's lower for some of the others. But it still seems to me that these publishers default to publishing their code.

BUT: most publishers probably do not run an entirely home-grown system. Indeed, you will find many Wordpress plugins or rails gems among those published projects. And for the homespun solutions, it's likely that they are too specific to a publisher to be usefully open-sourced without a major investment of resources, like the Guardian's undertaking.

Re: Source for theguardian.com

#27
post #25
post #8

The docs include a recipe for Breton crêpes. :) [1] https://github.com/guardian/frontend/blob/master/docs/99-arc...

This is not even close to bretonne crêpes. Either you use buckwheat floor and water, in which case you are making Galettes. Either you use plain white wheat floor, in which case it's crêpes you are doing. Under no circumstances you can put sugar in it, it's only added at the end. And of course, it's missing the most important ingredient: butter. #notevenclose

[deleted]

Re: Source for theguardian.com

#28
post #13

Earlier quoted context omitted.

I can't see more commercially-oriented paper/website open-sourcing any of their code, even if it's a (good imho) recruitment ploy. There's very little cost to opening it up, and a huge benefit (recruitment as you say, openness, community engagement, maybe even bug fixes..). Why not open up the code?

opening up publishes all your vulnerabilities, bugs, hacks and swearwords in the code as well. Thats plenty of reasons to not go open source

Security by obscurity really isn’t a great place to stay on long term. There is also an entire backend to this. I can only see great positives long term here, even if it means someone nefarious finds a bug in the short term.

Re: Source for theguardian.com

#29
post #7

IANAL, but this seems to collide with their EULA with Commercial Type [1], since third party hosting of the font files is "strictly prohibited" and the font files are in fact all available in the repo, which certainly doesn't sound like "reasonable effort to prevent access/use by unlicensed parties". [1] https://github.com/guardian/frontend/blob/88cfa609c73545085c...

Though I'll not make any judgement towards "prevent access", the main license file[0] does state: > All fonts are the property of Schwartzco, Inc., t/a Commercial Type ( https://commercialtype.com/ ), and may not be reproduced without permission. As a side tangent, it constantly surprises me how deep the creative industries manage to sink their claws into IP and licensing. I don't understand how artistic commissions…

The Guardian font seems to not be exclusive to Guardian: https://commercialtype.com/catalog/guardian
Post reply on HN