Hello!
The next Standard for Public Code community call will be held on Thursday,
3 February, 14.00 (UTC).
Video call-in link: https://meet.publiccode.net/StandardforPublicCode
<https://meet.publiccode.net/StandardforPublicCode>
Continuing on our last community call
<https://blog.publiccode.net/community%20call/2022/01/11/notes-from-commun...>
we want to dig further into how existing policies, laws, regulations and
strategies, applicable to and made by a public organization, make demands
on codebases developed by them.
In this call, we would want to hear more from you on how you find about
such demands today and how you handle them. If you have ideas on what could
make the development easier and clearer, it would be most welcome. Would
you like to be using some kind of checklist, or would you rather see other
kind of structure or linking?
Making progress on this will inform us on how we can make the criterion
“Bundle policy and code” easier to apply to a codebase.
As always, the purpose of the community call is to make room for you, your
questions and your opinions - so if there is anything else on your mind,
feel free to bring it up. Also, if you cannot participate in this specific
call but have thoughts on this topic, feel free to reply to this email.
Preliminary agenda. <https://hackmd.io/-OegeqvoThCbAsw3c3gIjw>
We look forward to seeing you on the call!
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
Hello!The next Standard for Public Code community call will be held on
Thursday, 6 January, 14.00 (UTC).
Video call-in link: https://meet.publiccode.net/StandardforPublicCode
<https://meet.publiccode.net/StandardforPublicCode>
The Standard for Public Code is written to be broadly applicable and aimed
at the process of developing public code codebases. It does not enumerate
specific policies to apply to codebases. From the perspective of most
public organizations, there are however some key policies that are really
important that any development adhere to, for example around privacy or
accessibility. These perspectives are not really at odds with each other,
but also not synergistic right now.
How can we make it more clear that a codebase that aims to meet the
requirements of the Standard for Public Code also needs to meet the policy
requirements of the public organizations that contribute to and reuse the
codebase? This is what we would like to have a conversation about in this
community call.
As always, the purpose of the community call is to make room for you, your
questions and your opinions - so if there is anything else on your mind,
feel free to bring it up. Also, if you cannot participate in this specific
call but have thoughts on this topic, feel free to reply to this email.
Preliminary agenda. <https://hackmd.io/-OegeqvoThCbAsw3c3gIjw>
We look forward to seeing you on the call!
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
