Hello. Hopefully this is the correct mailinglist for a proposal like this. And hopefully you have not already had this discussion before. In which case, I would like to apologize.
Anyways, I have a proposal, to make OpenBSD, the OS that I love, maybe a little bit cuter. # VISION I was thinking the other day, wouldn't it be great if OpenBSD had * A NICE-LOOKING SOFTWARE CATALOGUE. * Personally, I do not know how such a catalogue could look like, or how it would be implemented. However, if some people were to write a program, a website or even a book, they might need a list of URLs to download screenshots to make it more pleasing to the reader. In theory, they could generate the screenshots themselves, but this might be tedious, and also the choice might not be the one that the maintainer agrees on best representing the software. This proposal is attempting to formalize the manner in which the catalogue-programmers know which shots to use. # IMPLEMENTATION (create a pkg/SCREENSHOTS file) My first idea was to add a key/value pair like SCREENSHOT=url to the Makefile. But this falls short in many ways, and it will be negatively impacting the build process. So, in addition to the pkg/DESCR I am proposing a pkg/SCREENSHOTS file. Like the one I took the liberty of attaching to this mail. If you open it, you can see that it contains the key/value pairs URL=... . Those are pointing towards a the internet, where the screenshots can be downloaded. Afterwards, a handful of key/value pairs follow, to set properties for the URL. The rule is, that each new URL gets default properties. The ones following it in the pkg/SCREENSHOT file are overriding them. # SECURITY (add SHA256 sums) After the first URL you might notice a line with SHA256=... This is a way of automatically checking if the content matches the intention. It is meant to make sure that a malicious web site does not swap the wonderful screenshot with a picture containing breasts... It is up to the catalogue programmers to decide whether to use the picture anyways. # LEGAL (explicitly PERMIT the usage of the screenshots) Copyright law is a bitch, and it extends to pictures as well. Hence my idea of adding PERMIT_WEBSITE= and PERMIT_PRINT= keys. The default is "no". So it is up to the maintainer to explicitly allow the use of the one screenshot referenced by the last URL= key. Once again, it is up to the catalogue programmers to decide whether to use the picture anyways. What do you guys think? (And if it is the wrong mailing list to ask, please point me to the appropriate one) Thomas
# This is a comment # # The first screenshot URL=https://dettus.net/dMagnetic/sixel_mag_guild.png MIRROR=https://www.dettus.net/dMagnetic/sixel_mag_guild.png SHA256=91564ce484b0732952c2bf60cdf834beeb0f99782b7d4f924f8a2bbe5ac87923 PERMIT_WEBSITE=yes PERMIT_PRINT=yes # If maintainers are interested in more than one screenshot, then the first is # followed by a second one URL=https://dettus.net/dMagnetic/sixel_mag_wonder.png MIRROR=https://www.dettus.net/dMagnetic/sixel_mag_wonder.png SHA256=bd7b7d6c4d22d333fb723a4a61e18f4931122608e1ab0d3ffa33ad0b7bd7657b PERMIT_WEBSITE=no # This is the default PERMIT_PRINT=yes # Maintainers have to explicitly permit the use # More screenshots, but without the security measures URL=https://dettus.net/dMagnetic/thepawn_photo4.jpg URL=https://dettus.net/dMagnetic/sixel_mag_pawn.png URL=https://dettus.net/dMagnetic/sixel_mag_jinxter.png URL=https://dettus.net/dMagnetic/sixel_mag_myth.png URL=https://dettus.net/dMagnetic/sixel_mag_corruption.png PERMIT_WEBSITE=yes # This one belongs to the last URL
