publiccodenet / blog

Home to the Blog for Public Code, where blog posts are planned and collectively written.

Blog for Public Code

This is the Blog for Public Code by the Foundation for Public Code.

How to contribute to the blog

Follow our contributing guide to learn how you can contribute.

Building the site

This site builds with Jekyll, as is the default of GitHub pages and uses the Foundation for Public Code Jekyll Theme.

Installing locally

1. To build the site locally make sure you have Ruby and Bundlr installed.
2. Install the dependencies of this repo with

bundle install

Serving Locally

1. Run the Jekyll server with

bundle exec jekyll serve

1. You can now view the website locally on http://localhost:4000

The server will rebuild the site every time a file changes, with the exception of _config.yml.

Statistics

We use Plausible for statistics, and they can be viewed at plausible.io/blog.publiccode.net.

License

© 2020 Foundation for Public Code. All content licensed under Creative Commons Zero v1.0 Universal, unless otherwise noted.

blog's Issues

Broken links

The links in our christmas post to the bios have been broken due to a change in the naming conventions of team bios.

Blog post on episode 1 of the podcast

To summarize the livestream, give all the links where you can find it and also reiterate that there is an audio version together with the links on where you can find it.

January 2021 Foundation for Public Code community call

This call will take place on 21 Jan 2021 at 14.00 UTC. The topic is About issue #762: how do we manage contributions to our open work in practice?

Tasks to complete the call:

• draft agenda
• send invitations and tweet about it
• set up notes document
• have call and take notes
• write up notes as a blogpost
• share draft blogpost with call attendees for review
• publish blogpost!

Markdown linting check exceptions could be narrowed

Label for blog posts

Should we add a separate label for blog posts? That would make easier to distinguish from other sorts of improvements to the blog.

Open finance of the foundation

As an open foundation, embracing working fully open, it might be wise to open up regarding the finance position of the foundation. For example: yearly figures (balance sheet), therefore the community can see the financial building blocks of the foundation apart from all the technical and service products.
One shot further: by opening up on this subject it might trigger new opportunities, involvements, such as contributions for certain projects and so forth.
This might be a subject for a future community call?

Blog post on September 3 community call

Write a blog post summarizing the Standard for Public Code community call on translations.

Essay version of the core deck

Make a blog post for the May 12 backlog pruning

It turned out that the last blog post was really handy today. So we want to keep publish them, mostly for ur one sake, but also so that the community can see what we do. Raw notes to turn into a blog post: https://hackmd.io/LfnU7iu-QqWyL8gVE2iSTw

Switch to open license

Is there any reason for the blog not to be CC 0 as well?

Add a license file

This came up in a discussion with @angelplasma about what licence is appropriate for publishing photos of real people, all of whom gave /us/ permission to use their photos in our marketing - but may not have intended to give the whole internet permission for everything forever.

November Foundation for Public Code community call

This call will take place on 19 November 2020 at 14.00 UTC.

We still need to pick a topic - please vote on the suggestions below, or add your own!

February 2021 Foundation for Public Code Community call

This call will take place on 18 Feb 2021. The proposed topic is a public demo of the new publicode.net website and wireframes, led by @angelplasma and @ElenaFdR.

October 2020 Foundation for Public Code community call

This call took place on 15 October 2020 at 14.00 UTC.

Tasks to complete the call:

• draft agenda
• send invitations and tweet about it
• set up notes document
• have call and take notes
• write up notes as a blogpost
• share draft blogpost with call attendees for review
• publish blogpost!

Make a blog post about Signalen going to incubation

August 2020 Foundation for Public Code community call

This call took place on 20 August 2020.

Tasks to complete the call:

• draft agenda
• send invitations and tweet about it
• set up notes document
• have call and take notes
• write up notes as a blogpost
• share draft blogpost with call attendees for review
• publish blogpost!

Enable MarkDown linter on blog

In the transition to GH-Actions @ericherman and @felixfaassen noticed Markdown linter is not running our blog.
Before enabling MarkDown linter we first need to address these linting errors. After that, we can enable MarkDown linter on our log just as it is enabled on about and standard repositories.

Below is a list of the MarkDown lint errors:

README.md:13: MD031 Fenced code blocks should be surrounded by blank lines
README.md:20: MD031 Fenced code blocks should be surrounded by blank lines
README.md:22: MD031 Fenced code blocks should be surrounded by blank lines
_posts/2019-12-13-notes-from-community-call-5-december-2019.md:12: MD022 Headers should be surrounded by blank lines
_posts/2020-02-07-video-decidimfest-ben-cerveny.md:15: MD009 Trailing spaces
_posts/2020-02-07-video-decidimfest-ben-cerveny.md:14: MD012 Multiple consecutive blank lines
_posts/2020-02-17-learned-at-fosdem.md:21: MD033 Inline HTML
_posts/2020-02-17-learned-at-fosdem.md:22: MD033 Inline HTML
_posts/2020-02-17-learned-at-fosdem.md:23: MD033 Inline HTML
_posts/2020-02-21-notes-from-community-call-20-february-2020.md:25: MD004 Unordered list style
_posts/2020-02-21-notes-from-community-call-20-february-2020.md:26: MD004 Unordered list style
_posts/2020-02-21-notes-from-community-call-20-february-2020.md:36: MD004 Unordered list style
_posts/2020-02-21-notes-from-community-call-20-february-2020.md:37: MD004 Unordered list style
_posts/2020-03-20-notes-from-community-call-5-march-2020.md:22: MD004 Unordered list style
_posts/2020-03-20-notes-from-community-call-5-march-2020.md:23: MD004 Unordered list style
_posts/2020-03-20-notes-from-community-call-5-march-2020.md:24: MD004 Unordered list style
_posts/2020-03-23-notes-from-community-call-19-march-2020.md:38: MD004 Unordered list style
_posts/2020-03-23-notes-from-community-call-19-march-2020.md:39: MD004 Unordered list style
_posts/2020-03-23-notes-from-community-call-19-march-2020.md:40: MD004 Unordered list style
_posts/2020-03-23-notes-from-community-call-19-march-2020.md:12: MD022 Headers should be surrounded by blank lines
_posts/2020-06-03-notes-from-community-call-7-may-2020.md:34: MD009 Trailing spaces
_posts/2020-06-22-notes-from-community-call-3-june-2020.md:31: MD009 Trailing spaces
_posts/2020-06-26-notes-from-community-call-18-june-2020.md:19: MD004 Unordered list style
_posts/2020-06-26-notes-from-community-call-18-june-2020.md:20: MD004 Unordered list style
_posts/2020-06-26-notes-from-community-call-18-june-2020.md:21: MD004 Unordered list style
_posts/2020-06-26-notes-from-community-call-18-june-2020.md:22: MD004 Unordered list style
_posts/2020-06-26-notes-from-community-call-18-june-2020.md:15: MD009 Trailing spaces
_posts/2020-06-26-notes-from-community-call-18-june-2020.md:34: MD039 Spaces inside link text
_posts/2020-08-11-overdue-socially-distant-socializing.md:17: MD009 Trailing spaces
_posts/2020-08-11-overdue-socially-distant-socializing.md:19: MD033 Inline HTML
_posts/2020-08-24-notes-from-community-call-6-august-2020.md:52: MD009 Trailing spaces
_posts/2020-09-23-episode-one-of-lets-talk-about-public-code.md:26: MD009 Trailing spaces
_posts/2020-10-12-notes-from-community-call-1-october-2020.md:45: MD005 Inconsistent indentation for list items at the same level
_posts/2020-10-12-notes-from-community-call-1-october-2020.md:46: MD005 Inconsistent indentation for list items at the same level
_posts/2020-10-12-notes-from-community-call-1-october-2020.md:45: MD006 Consider starting bulleted lists at the beginning of the line
index.md:12: MD009 Trailing spaces
index.md:13: MD009 Trailing spaces
index.md:13: MD012 Multiple consecutive blank lines
index.md:14: MD022 Headers should be surrounded by blank lines
index.md:4: MD033 Inline HTML
index.md:6: MD033 Inline HTML
index.md:7: MD033 Inline HTML
index.md:7: MD033 Inline HTML
index.md:8: MD033 Inline HTML

Blog post for episode 3 of the podcast

• Link to the podcast episode on podbean
• Youtube link
• Facebook link
• Periscope link
• Screenshot image

Blog post on our connection to the Sustainable Development Goals

Make a blogpost that summarize our thought related to publiccodenet/about#755 and the talk @nebster gave last week.

Should we number our newsletters?

This seems to be very common among newsletters I'm subscribed to.

Our newsletters have always been identified with a season and date range, so I'm not sure what extra clarity/value individual sequential numbering will provide.

Perhaps this makes it easier to identify milestone newsletters? (Our 50th or 100th?)

Thoughts welcome!

Document November standard community call

Write a short blog post documenting the chat last Thursday.

Add missing functionality to blog

Missing

• about this blog
• Populate contact page (with HTML and our info) - solved by deleting
• something that makes at least the most recent post text appear on the index
• front matter rendering for posts
• internal nav: eg breadcrumbs to get from post back to index (not needed because you can click on the word 'blog)
• external nav: link to http site (see PR #15)
• internal nav: link to the blog's about
• favicon (warns GitHub)
• RSS feed?
• social sharing
• fix rendering of blog name

Not currently relevant

• layout file for posts
• Go back to https://jekyllrb.com/docs/configuration/front-matter-defaults/ to set up default post layout after reading about layouts
• data files - can be used to organise site by author!
• collections of posts

Make blog post for episode 4 of the podcast

With all the relevant links!

Blogpost on the OpenZaak market consultation

(Creating an issue instead of a note so that we make better use of Github's project tracker.)

December 2020 Standard for Public Code community call

Draft approved by participants, ready to do a PR.

March 2021 Foundation for Public Code community call

This call will take place on Thursday, 18 March 2021 at 15.00 CET.
If you have a topic proposal, please comment below!
We'll choose the topic the week before the call date.

Make blog post for April Standard community call

Blogpost for the 16 July community call

September 2020 Foundation for Public Code community call

This call took place on 11 September 2020.

Tasks to complete the call:

• draft agenda
• send invitations and tweet about it
• set up notes document
• have call and take notes
• write up notes as a blogpost
• share draft blogpost with call attendees for review
• publish blogpost!

Write first blogpost!

Announcing our legal existence.

Blog post on 1 October 2020 Standard for Public Code community call

Blog post with Decidim video

A reminder issue for us to not forget making a blogpost with the video with the talk of @nebster embedded:

https://www.youtube.com/watch?v=cnJtnZ9Cx1o

Blog post explaining why the association is called Foundation

Based on questions @Ainali and myself got during a recent round of meetings, it might be good to have a short blog post in which we sum up our actual situation, the reasons why we are an association (verening) and not a foundation (stichting) but why the association is named the Foundation for Public Code Vereniging.

It will be important for all staff (particularly those joining after we had these discussions internally) to feel comfortable explaining this clearly and consistently. Moreover, having a link to point to always helps.

What do you think @bvhme @ElenaFdR ?

Blogpost for 2 July 2020 Standard community call

link checking could be narrowed

Temporary 50x errors and some additional link exceptions in the GH Actions can be reduced or removed

Update blog CONTRIBUTING FILE

Sparked by @attogram's PR #34, we should make clear when and how community members can contribute to this blog so that they feel welcomed and encouraged to do so.

Success criteria:

1. clear info in CONTRIBUTING on how to submit an idea for a blogpost (issue) or proposed blogpost (PR)
2. clear explanation in CONTRIBUTING for when a blogpost is in scope for this blog (suggestion: content is of strong interest to our community, and something subjective about us being the right/best forum for that information to be published - eg, someone whistleblowing at a Foundation member might be of interest, but we're not the right forum)
3. boilerplate notice text to put on community posts explaining that they're published because we think they'll be interesting to the community, not necessarily that the Foundation endorses this idea (linking back to the blog scope)
4. process agreed for updating the authors file when we publish PR (for example, the Standard invites people to open a PR to update the authors file after their PR is merged).
5. potentially update the authors file to distinguish between staff and community authors (explore if this is necessary with consistent application of point 3).

Tags for blog posts?

We should probably add something to the readme about which categories to use. So far we only have posts in the Community call category. I was thinking about writing a blog post about the governance game and are not sure what to use. News? A separate for the game is probably too granular. Having a list to choose from would be easier for the author of a post.

Mumble only voice

I'd like to report an issue in _posts/2020-03-23-notes-from-community-call-19-march-2020.md
hey guys, mumble is voice only so maybe use another example in video, e.g. Jitsi
best, deb

April 2021 Foundation community call

This call will take place on Thursday, 15 April 2021 at 15.00 CEST.

The topic for this call is our upcoming search for new members for our board of directors.
Which experience and expertise should we be looking for?
What other criteria or factors should we take into consideration?

May 2021 Foundation for Public Code community call

This call will take place on Thursday, 20 May 2021 at 15.00 CEST.
If you have a topic proposal, please comment below!
We'll choose the topic the week before the call date.

Potential call topic ideas:

• what we should do next to scale the Foundation for Public Code
• what we learned from publishing our first annual report
• how to grow/deepen our codebase stewardship practice?

Add blog post for ltapc #5

Blogpost about Dutch 'publieke belang, publieke software?' debate

@felixfaassen has a strong reaction to this debate this morning, and would like to blog about some fundamental FOSS concepts that were not very clear in the discussion.

Outstanding questions:

• which platform to publish this on (probably https://opensource.pleio.nl/)
• language? (probably Dutch)

February Standard for Public Code Community Call

Summarize notes to a blog post

Blogpost for the August 6 Standard call

Write the blog post.

May 2021 Standard for Public Code community call

Write a blog post with a summary

January 2021 Standard for Public Code community call

Blogpost for June 18 community call (our code of conduct)

Draft blogpost and call notes

Create blog post on being standard compliant from the start

We have been thinking and tinkering a bit on this and could share this with the world.

Make blog post for March Standard community call

Blog post on community calls

I would like to make a blog post on our thinking on community calls and how we use them as a way of really collaborating in the open (and not just being an entrance point for non-staff). Having this would make it easier for anyone to understand what we mean by them. I could take a stab at a first draft and then perhaps @bvhme could take a look to see if I manage to capture the spirit correctly. After this is written, perhaps our pages on about could also be improved. Does this sound like a useful idea?