aboutsummaryrefslogtreecommitdiffstats
path: root/markdown
Commit message (Collapse)AuthorAgeFilesLines
* Finally sign the petition to support NLnet.Denis 'GNUtoo' Carikli2025-06-151-0/+297
| | | | | | | | | | | | | | | | | | | | | | | | I took the occasion of adding our views on NLnet funding as this is probably something that not a lot of people see from the outside. In order to increase the impact of signing the petition, I also wanted to add some background about the strategic importance of the work NLnet is doing and put that in a broader historic context, whose impact go beyond the free software movement. However it took some time as I had some difficulties writing the end of the text in a way that didn't require too much political knowledge, that was not tied to a specific set of countries (even in the European Union, some of the member countries have very different histories) and that also worked accross a wide set of political affiliations. In addition due to various issues from all the people involved (me included), the back and forth between reviews and new versions of the text also took some time. Thanks a lot to to Joonas Kylmälä for the review of the markdown file. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Use first_online_replicant_meeting from Wordpress.Denis 'GNUtoo' Carikli2025-06-151-460/+454
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* markdown: first_online_replicant_meeting: Fix CEST link.Denis 'GNUtoo' Carikli2025-06-151-1/+1
| | | | | | Thanks a lot to the person who spoted the mistake. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* markdown: Add blog post about the first online Replicant meeting.Denis 'GNUtoo' Carikli2025-06-151-0/+77
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* 37c3/FOSDEM 2024: Add Wordpress link, move CommonMark file.Denis 'GNUtoo' Carikli2025-06-151-0/+0
| | | | | | | | | | | | The existing CommonMark file was moved in the place where the html would be converted to CommonMark. When running 'make markdown', this avoids silently having two similar files under different names in the markdown directory. Instead any modifications of the file would show up in git and could be caught by humans more easily. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* convert.py: licensing: Also add in Joonas's permission.Denis 'GNUtoo' Carikli2025-06-151-0/+1
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* convert.py, markdown: Add in new licenses.Denis 'GNUtoo' Carikli2025-06-1555-0/+55
| | | | | | We now have a valid license for each of the articles. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* markdown: 37C3/FOSDEM 2024 report: Add authorship information.Denis 'GNUtoo' Carikli2025-06-151-0/+1
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* markdown: 37C3/FOSDEM 2024 report: Add License.Denis 'GNUtoo' Carikli2025-06-151-0/+1
| | | | | | The two authors (dllud and GNUtoo) already agreed to use this license. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* convert.py, markdown: use UTF-8.Denis 'GNUtoo' Carikli2025-06-1511-50/+50
| | | | | | | | | | | | | | | | | Guile use ISO-8859-1 by default for ports. Since the markdown contain some UTF-8 characters, the resulting HTML ended up with unknown characters replaced by some '??'. Converting some dashes or quotes to ASCII equivalent was done in previous commits and was not a big issue, but some files also have characters with accents, so keeping most of the UTF-8 characters as-is and moving directly to UTF-8 is a better solution. Some characters still don't work, and end up in some haunt build errors (which is better than silent faillures like before). They all have valid equivalents so they were replaced by their equivalents. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* convert.py, markdown: fix quotes.Denis 'GNUtoo' Carikli2025-06-156-37/+37
| | | | | | | | | Without this fix, site/new-replicant-60-0004-release-and-replicant-11-status.html has: "As for the details on what constitute a ???replaceable battery???, [...]". Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* markdown: regenerate after tags/licenses changes.Denis 'GNUtoo' Carikli2025-06-1571-86/+86
| | | | | | | For some reasons tags and licenses are moved in the metadata header, so we need to add-in the changes to the generated markdown files. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* convert.py, markdown: fix some broken links.Denis 'GNUtoo' Carikli2025-06-1529-138/+69
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* convert.py, markdown: Fix em dash.Denis 'GNUtoo' Carikli2025-06-152-2/+2
| | | | | | | | | Some generated markdown have em dashes, such as 2010_11_fdroid-a-free-software-alternative-to-google-market.md so like with the commit e8885a941d90661a7bf45996a0ffcc1e4262d090 ("convert.py, markdown: Fix en dash.") we also needs to convert them to minuses. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* convert.py, markdown: Fix en dash.Denis 'GNUtoo' Carikli2025-06-152-9/+9
| | | | | | | | | | | | Some generated markdown have en dashes, and without this fix, it ends up being displayed as '???' in the generated HTML files. As an example with site/replicant--37c3.html we have: Introduction to Replicant ??? December 28 10:00, Saal D Converting the en dashes into minus fixed it. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Revert "convert.py, markdown: Fix trailing whitespaces."Denis 'GNUtoo' Carikli2025-06-1523-62/+62
| | | | | | | | | | | | | This reverts commit 4ff9d384f766cee1d8e322b9f6b747161f55f85e ("convert.py, markdown: Fix trailing whitespaces."). Without this revert, in site/replicant--37c3.html we see 'Location: G5, Hall 3, Level 0 DECT: 8652' instead of: Location: G5, Hall 3, Level 0 DECT: 8652 Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* convert.py, markdown: Fix trailing whitespaces.Denis 'GNUtoo' Carikli2025-06-1523-62/+62
| | | | | | | | | Many lines have 2 spaces at the end. An example is the 'Location: [G5, Hall 3, Level 0][4] ' line inside the markdown/2023_12_replicant-37c3.md file. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* convert.py, markdown: Fix right single quotation mark.Denis 'GNUtoo' Carikli2025-06-1560-369/+369
| | | | | | | | | | | | | | | Some generated markdown have right single quotation marks, and without this fix, it ends up being displayed as '???' in the generated HTML files. As an example with site/new-replicant-test-images-available.html we have: We are please to remind you that, as usual, Replicant is fully free software and doesn???t include any proprietary firmwares. Converting the right single quotation marks to apostrophes fixed it. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Sync markdown files with 'make markdown'.Denis 'GNUtoo' Carikli2025-06-1571-0/+86
| | | | | | | | The files were verified to work fine with 'make build', and the generated website seems to be the same than before (including with the same conversion issues). Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* 37C3/FOSDEM 2024 report: Use publication date from WordPress.Denis 'GNUtoo' Carikli2025-06-151-1/+1
| | | | | | | | | | | The mardown was converted to HTML with 'make build' and then published on WordPress by copy-pasting the content generated with haunthtml2wordpress.py. The publication created a date in the WordPress HTML file that I re-imported into the markdown. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* 37C3/FOSDEM 2024 report: Import latest modifications from WordPress.dllud2025-06-151-2/+3
| | | | | | | | The modifications were written by dllud from suggestion made by Tiberiu. GNUtoo: commit message. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Add 37C3 and FOSDEM reports.Denis 'GNUtoo' Carikli2025-06-151-0/+472
| | | | | | | | | | | | | | Since me and dllud planned to work together on this report, it was easier to do it in markdown in a git repository than finding a way to do that through Wordpress directly. The method to integrate that markdown document back in wordpress has been described in the Replicant infrastructure wiki here: https://redmine.replicant.us/projects/replicant-infrastructure/wiki/Wordpress Co-developed-by: dllud <dllud@riseup.net> Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Remove fix-dates.sh manual process.Denis 'GNUtoo' Carikli2025-06-1571-71/+71
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Regenerate markdown files.Denis 'GNUtoo' Carikli2024-02-282-6/+25
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Add generated markdown files.Denis 'GNUtoo' Carikli2023-12-3170-0/+5331
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
generated by cgit v1.2.3 (git 2.25.1) at 2026-06-23 19:52:16 +0000