Hello,
The next Standard for Public Code community call will be held on Thursday,
3 December, 14.00 (UTC).
Video call-in link: https://meet.publiccode.net/StandardforPublicCode
<http://odoo.publiccode.net/r/jdv/m/830>
For our last Standard for Public Code community call of the year we have
two topics to discuss.
One is in an early and more exploratory phase - how well is the standard
suited for codebases which have a rolling-release process especially where
the updates tend to involve regular content changes or evolving layout with
A/B testing? What are you missing in the Standard relating to this, or is
there something in it that you would like to change?
The second issue is related to the required feedback when reviewing. What
is enough, and do we need to adjust the requirement?
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 translations, feel free to just reply to this
email.
Preliminary agenda. <http://odoo.publiccode.net/r/zTE/m/830>
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,!
Today we released version 0.2.0. I'm pasting the changelog below for
convenience, the updated version is already live at standard.publiccode.net.
October 26th 2020: đ the sixth draft splits a requirement and adds clarity.
- Split âWelcome contributionsâ criterion into âMake contributing easyâ
and âWelcome contributorsâ.
- Rename criterion âPay attention to codebase maturityâ to âDocument
codebase maturityâ.
- Changed MUST to SHOULD for requirement of codebase in use by multiple
parties.
- Add MUST NOT requirement regarding copyright assignment.
- Clarify role of configuration in reusable code requirement.
- Glossary additions: continuous integration, policy, repository, and
version control.
- Replace references to âcitiesâ with âpublic organizationsâ.
- Clarify aspects of sensitive code by separating contributor and
reviewer requirements into separate items.
- Expand further reading, and guidance to policy makers, developers and
designers.
- Add Felix Faassen and Arnout Engelen to authors.
- Made additional minor changes to text for clarity.
A new pdf is available in the GitHub release:
https://github.com/publiccodenet/standard/releases/tag/0.2.0
--
Jan Ainali, Codebase Steward
jan(a)publiccode.net | +46762122776 | @jan_ainali
Foundation for Public Code https://publiccode.net
