Purism issueshttps://source.puri.sm/groups/Purism/-/issues2022-09-05T08:26:35Zhttps://source.puri.sm/Purism/librem5-policy/-/issues/2Developers certificate of origin2022-09-05T08:26:35ZEvangelos Ribeiro TzarasDevelopers certificate of originhttps://source.puri.sm/Librem5/librem5-policy/-/blob/master/source/software.rst?plain=1#L21-22
mentions:
> The projects should use a [Developer Certificate of Origin](https://developercertificate.org/) (DCO).
What does this mean in pr...https://source.puri.sm/Librem5/librem5-policy/-/blob/master/source/software.rst?plain=1#L21-22
mentions:
> The projects should use a [Developer Certificate of Origin](https://developercertificate.org/) (DCO).
What does this mean in practice? Include a link to that in project READMEs? Usage of `Signed-of` tags in commits?
Does/SHOULD this apply to all projects? If not, what kind of projects are exempt?https://source.puri.sm/Purism/librem5-policy/-/issues/1Document where source repositories go2021-04-28T12:27:24ZGuido GuntherDocument where source repositories gofrom a recent discussion:
it's:
* purism upstream **/Librem5** (hence usually debian native)
* core apps (part of the default install set that use proper packaging and hence can also go into byzantium) **/Librem5/debs**
* sloppy build...from a recent discussion:
it's:
* purism upstream **/Librem5** (hence usually debian native)
* core apps (part of the default install set that use proper packaging and hence can also go into byzantium) **/Librem5/debs**
* sloppy builds: **/Librem5** (these will fade out)
* optional 3rd party apps **/Librem5-apps** (reason being to allow for a different permission model)https://source.puri.sm/Purism/pureos-static/-/issues/2Download page should provide digital signatures for images2019-09-27T22:23:02ZBenedikt WildenhainDownload page should provide digital signatures for imagesCurrently the Download page only offers hashsums to check whether the download wasn't accidently corrupted during download. To check the integrity of the image it would be useful to have a OpenPGP signature file to validate that the imag...Currently the Download page only offers hashsums to check whether the download wasn't accidently corrupted during download. To check the integrity of the image it would be useful to have a OpenPGP signature file to validate that the image file hasn't been changed on the way from the build system to the web server by some attacker.https://source.puri.sm/Purism/flossy-gnu/-/issues/2flossy gnu needs build instructions2019-06-05T11:35:23ZJeremiah Fosterflossy gnu needs build instructionsUnderstanding how to build the game is the first step in packaging. If that information were placed in the README or in a separate file that would allow contribution.Understanding how to build the game is the first step in packaging. If that information were placed in the README or in a separate file that would allow contribution.https://source.puri.sm/Purism/pureos-static/-/issues/1PureOS.net video renders off when viewing with GNOME Web (Epiphany)2018-10-14T13:19:33ZTodd WeaverPureOS.net video renders off when viewing with GNOME Web (Epiphany)![pureos-net-epiphany-display-issue](/uploads/2d1e2dcf575b75418749a57752e99d70/pureos-net-epiphany-display-issue.png)![pureos-net-epiphany-display-issue](/uploads/2d1e2dcf575b75418749a57752e99d70/pureos-net-epiphany-display-issue.png)Eugen RochkoEugen Rochko