Feb Foundation community call

_data/staff.csv

@@ -8,3 +8,4 @@ elena,Elena Findley-de Regt,ElenaFdR,ejfdr,Communications coordinator
 eric,Eric Herman,ericherman,Eric_Herman,Lead Codebase Steward for Quality
 jan,Jan Ainali,ainali,Jan_Ainali,Codebase Steward for Community
 laura,Laura Scheske,lscheske,thelboms,Membership developer
+ryan,Ryan Conlan,angelplasma,prahjex2501,Designer

_posts/2021-02-25-notes:-february-2021-foundation-for-public-code-community-call.md

@@ -0,0 +1,52 @@
+---
+title:  "Notes: February 2021 Foundation for Public Code community call"
+date: 2021-02-25
+author: elena, ryan 
+type: blogpost
+excerpt: Introducing the publiccode.net product requirements document
+category: community call
+---
+
+
+# Notes: February 2021 Foundation for Public Code community call
+
+In this community call, we talked through our thinking about [publiccode.net](https://publiccode.net/) as product ([pull request #169](https://github.com/publiccodenet/publiccode.net/pull/169)), and demo'd [our wireframes](https://www.figma.com/file/Mcz4evZVI4rRwv3quXtKGC/Site-Map-Wireframe-exploration-Foundation-for-Public-Code?node-id=177%3A0).
+
+## Attendees
+
+* Alba Roza
+* Ben Cerveny
+* Boris van Hoytema
+* Claus Mullie
+* Elena Findley-de Regt (chair)
+* Eric Herman
+* Felix Faassen
+* Jan Ainali
+* Laura Scheske
+* Martin Dias d'Ullois
+* Rasmus Frey
+* Ryan Conlan (guest speaker)
+
+## Short update from the Foundation for Public Code
+
+* [Signalen is in incubation](https://blog.publiccode.net/news/2021/02/04/signalen-is-in-incubation.html) to fully meet the Standard for Public Code 🎉🎉
+* Watch out for a new release of the [Standard for Public Code](https://standard.publiccode.net/) next week
+* We've given lots of conference talks recently, so we've finally [pulled them together on one page](https://projects.publiccode.net/talks-and-articles.html). We'll update this as more as videos are shared (and also tweet!)
+
+## Call summary
+
+The substance of the call started with [short presentation](https://hackmd.io/@elenafdr/H11apesZ_#/) of the product requirements document for the evolution of publiccode.net by [Ryan](http://www.angelplasma.net/work/) (designer) and [Elena](https://publiccode.net/who-we-are/team/elena-findley-de-regt.html) (communications coordinator).
+
+There was time for questions and conversation afterward.
+
+Some questions focused on specific wording in the document, such as the seemingly contradictory aims to be both "future looking" and "timeless". Others considered the broader process of contributing to the Foundation for Public Code, and whether these changes to publiccode.net made that easier or harder.
+
+People were enthusiastic about the new media center, which will showcase news and stories from our codebase communities. Martin advocated for increasing the visibility of the Standard for Public Code.
+
+Regarding the goals set out in the product requirements document, Martin suggested we focus on positioning the Foundation for Public Code to be "really, really broadly accessible".
+
+Ryan explained our intent to amplify the current site's invitations to collaborate (across publiccode.net and its subdomains).
+
+Laura wondered about how people could contribute in the future as the changes outlined in the product requirements document were implemented; Elena proposed using future community calls for regular updates and feedback as the site evolves. Ryan and Elena also have regular coworking sessions, which they offered to open to the community.
+
+Rasmus joked that instead of revamping the [OS2 website](https://os2.eu/), he would wait until we'd implemented all these changes on publiccode.net and then fork it. He noted that integrated functionality for signing up to events or newsletters was critical, and not something he'd seen covered in the presentation.