Beste allemaal,
Hier is alvast een sneak peek preview van de documentatie die we samen
online verder gaan ontwikkelen:
https://docs.signalen.org/
Dit systeem maakt het eenvoudig om samen online aan documentatie te werken.
Het geheel wordt ook automatisch gesynchroniseerd met
https://github.com/Signalen/documentation.
Ik heb een begin gemaakt met de gebruikershandleiding van Signalen die
gebaseerd is op de handleiding die binnen Amsterdam gebruikt wordt. Deze
kun je hier vinden: https://docs.signalen.org/inleiding
Ik zal in ons volgende product steering overleg hier meer uitleg over
geven. In dit overleg zullen we dan ook de eerste opzet voor de
implementatie gids laten zien.
Hartelijke groeten,
Felix
--
Felix Faassen, Codebase steward
Foundation for Public Code | https://publiccode.netgithub.com/publiccodenet | github.com/felixfaassen
felix(a)publiccode.net | +31 624633278
Beste Allemaal,
Wellicht interessant voor een aantal van jullie die af en toe op GitHub te
vinden zijn maar het nog een beetje lastig te begrijpen of gebruiken vinden.
CodeForNL organiseert 2 februari om 16:00 een Introductie Workshop GitHub -
"hoe doe je een pull request?"
Mocht je daar interesse in hebben meld je dan hier aan:
https://www.meetup.com/Code-For-NL/events/276025550/
Groeten,
Felix
--
Felix Faassen, Codebase steward
Foundation for Public Code | https://publiccode.netgithub.com/publiccodenet | github.com/felixfaassen
felix(a)publiccode.net | +31 624633278
Hi Everyone,
As we had a steering call last week I would like to cancel this meeting and
pick up our normal monthly rhythm in february
Jacco and I are busy setting up a documentation repo with a nice
documentation system which allows everyone to add documentation without
Github knowledge. I will demo it in our upcoming product steering meeting.
Kind regards,
Felix
--
Felix Faassen, Codebase steward
Foundation for Public Code | https://publiccode.netgithub.com/publiccodenet | github.com/felixfaassen
felix(a)publiccode.net | +31 624633278
Signalen Product Steering Meeting 14th of January, 2021, 11:00 to 12:00
Chair: Felix
Video Chat using Jitsi: https://meet.publiccode.net/SignalenProductSteering
This note: https://hackmd.io/1JdTA5uBTvy1QOVt-bpWng
Shared Product backlog: https://github.com/orgs/Signals/projects/2 (draft)
Product steering and feature requests documentation:
https://github.com/Signalen/product-steering
Create feature request:
https://github.com/Signalen/product-steering/issues/new?assignees=&labels=e…
Slack Channel:
https://join.slack.com/share/zt-heae6d92-sqH1xvJvJQ_RMpAAMnHLKQ
Mailing list:
https://lists.publiccode.net/mailman/postorius/lists/signalen-discuss.lists…
(Check
spam)
Board: https://miro.com/app/board/o9J_kkwkuBE=/
<https://hackmd.io/1JdTA5uBTvy1QOVt-bpWng?both#Agenda>Agenda:
Started a discussion about everyone’s expectations about the Signalen in
their municipality, the challenges and what you want to get out of the
product steering meeting. Last but not least I would like to make a short
action list on steps we need to take to get a draft roadmap 2021 ready by
the end of January beginning of February.
Round question:
- What is your expectation?
- What do you need?
- What can we do now?
<https://hackmd.io/1JdTA5uBTvy1QOVt-bpWng?both#Purpose-and-goal-product-stee…>Purpose
and goal product steering meeting
Astrid is searching. She is interested in a common vision for the product
and wants to know where we are going to work together. Jacco mentions that
this is something we need together. Arjo and Astrid acknowledge it but it
is also hard as everyone is in a different adoption stage and has different
needs.
Felix mentions that it is important we meet and work on things we all
commonly need. Felix and Jacco mentioned the idea of creating an
Implementation Guide. A living collaborative document where we put our
learnings from a process and organizational perspective. Not only will help
such a document with the further adoption of Signalen but also as a vehicle
for knowledge sharing in the product steering group. In doing the work we
will also learn what is commonly needed, what is missing ultimately
informing the roadmap and our future work as product steering group.
<https://hackmd.io/1JdTA5uBTvy1QOVt-bpWng?both#Implementation-Guide>Implementation
Guide
We will start to create an implementation guide where we will re-use as
much information and documentation currently available about Signalen used
by Amsterdam and created by Arvid and his co-workers. We will make it more
generic applicable to other municipalities and will enrich the guide with
our own experience and learnings.
Jacco, Felix and Arvid will have a meeting about this. Felix will set up a
new repository for the implementation guide. Jacco, Felix and Arvid will
make an initial table of contents including references to existing
documentation. Next meeting we will discuss as a group what will need to be
changed and added and we will distribute workload and jointly develop this
document further.
<https://hackmd.io/1JdTA5uBTvy1QOVt-bpWng?both#Joint-mission--Vision>Joint
mission / Vision
We also briefly discussed working on a joint mission and vision. Here is a
work-in-progress example the mission and vision for OpenZaak
https://github.com/open-zaak/open-zaak/blob/17d32ea48bd69238776410f8a737568…
Reason why describing this is important is outlined in the standard for
public code:
https://standard.publiccode.net/criteria/document-objectives.html
<https://hackmd.io/1JdTA5uBTvy1QOVt-bpWng?both#User-testing-in-Utrecht-ampam…>User
testing in Utrecht && presentation UX team Utrecht
Astrid mentions her project where Utrecht will be conducting user
experience research. She asked if anyone is interested in certain research
questions to be included that she is most welcome to receive them.
There was also interest from the group to have the UX team researching this
to give a small presentation in a separate meeting. She will organize
something in the coming weeks.
<https://hackmd.io/1JdTA5uBTvy1QOVt-bpWng?both#Agenda-next-meeting>Agenda
next meeting
- Present draft implementation Guide with table of contents on Github
including references to existing material
- Feedback session on table of contents
- If time assign writing tasks to group
<https://hackmd.io/1JdTA5uBTvy1QOVt-bpWng?both#Action-points>Action points
Next chair: ???
ActionResponsibleDue date
Make table of contents and repo for Signalen Implementation Guide Jacco,
Felix with input from Arvid 10-12-2020
Write down short vision/mission Signalen
Hi everyone,
First of all the best wishes for 2021. Today we had scheduled a product
steering meeting today at 11:00. You may have missed it or where caught up
in important business.
Because there were no attendees today I took the liberty to reschedule our
product steering meeting to the next week Thursday at 11:00.
I hope to see you there.
Kind regards,
Felix
--
Felix Faassen, Codebase steward
Foundation for Public Code | https://publiccode.netgithub.com/publiccodenet | github.com/felixfaassen
felix(a)publiccode.net | +31 624633278
Happy new year Signalen devs!
My partner sent me a paper on making machine learning models transparent
and I expect those of you who tinker with training the ML models will also
find it good food for thought:
http://vanderschaar-lab.com/papers/NIPS2019_DBM.pdf
Jump ahead to section 5.2 "Predicting prognosis for breast cancer" to get
an idea about what they're doing.
This could be a very useful tool for combining machine learning with public
policy.
Pragmatically, it might allow Signalen to publish a transparent and
re-usable model without having to publish any sensitive data required for
generating a model.
At a glance, it seems there's more work on building models that model
models -- what a sentence! -- and "Explainable AI" seems to be a good
keyword to look up ... but I am very novice in this subject.
Cheers,
-Eric
--
Eric Herman, Lead codebase steward for quality
Foundation for Public Code | https://publiccode.netgithub.com/publiccodenet | github.com/ericherman
eric(a)publiccode.net | +31 620719662 | @Eric_Herman
------------------------------
*From:* Medlock, S.K. <s.k.medlock(a)amsterdamumc.nl>
*Sent:* Wednesday, January 15, 2020 14:32
*Subject:* interesting work from Mihaela van der Schaar
Just heard a talk from one of the machine learning people in the UK. She
had a number of interesting topics, but this is the one that caught my
attention:
http://vanderschaar-lab.com/papers/NIPS2019_DBM.pdf
Figured it might interest you too.
Stephanie "Ace" Medlock
Assistant Professor | Amsterdam UMC - Location AMC
Department of Medical Informatics | Meibergdreef 15, 1105AZ Amsterdam
www.amsterdamumc.nl
______________________________________________________
VUmc disclaimer : www.vumc.nl/disclaimer
AMC disclaimer : www.amc.nl/disclaimer
Hi Everyone,
As we discussed the product steering will move to another time slot which
suits everyone better. I sent around a datumprikker. I got 4 responses
based on the fact that it showed that Thursday's at 11:00-12:00 are the
best option.
I rescheduled our first product steering meeting to *Thursday 7th of
january 2020 at 11:00*.
I also propose to change the meeting frequency from every two weeks to once
a month. I reschedule the meeting now to occur every third Thursday of the
month at 11:00.
For the upcoming meeting on the 7th of January I would like to propose a
discussion about everyone's expectations about the Signalen in their
municipality, the challenges and what you want to get out of the product
steering meeting. Last but not least I would like to make a short action
list on steps we need to take to get a draft roadmap 2021 ready by the end
of January beginning of February.
I have also taken the liberty to use one of our product steering meetings
to get a bit more aligned on the product development of Signalen so we can
all work together more effectively and make it easier to discuss, refine
and prioritize features. As I notice some of you find it challenging to
understand the proposed features or the thinking behind a certain feature.
More about this later.
For now I want to thank you all this year for your support and hope to see
you all on the 7th in good spirits and health.
Kind regards,
Felix
--
Felix Faassen, Codebase steward
Foundation for Public Code | https://publiccode.netgithub.com/publiccodenet | github.com/felixfaassen
felix(a)publiccode.net | +31 624633278
Hoi allen,
Tijdens het vorige product steering overleg hebben we het gehad over een uitgebreid overleg om een feature request met zijn allen door te nemen: dubbele meldingen koppelen/aan de voorkant afvangen. Volgens mij hadden we bepaald om hier aankomende woensdag van 9:00 tot 11:00 uur aan te werken. Staat dit bij iedereen scherp op het netvlies? Volgens mij zijn er geen vergaderverzoeken rond gestuurd.
Ik heb het erg druk met werkzaamheden rondom de livegang van Signalen in Den Bosch en red het niet om aan te sluiten. Voor Bram en Amy vanuit onze kant geldt hetzelfde. Ons verzoek is om dit overleg uit te stellen tot wij in wat rustiger vaarwater zitten: februari 2021.
Hoor graag wat jullie van dit voorstel vinden.
Met vriendelijke groet,
Erik Veerman
Projectleider | Sector Informatiemanagement SO/SB │ gemeente 's-Hertogenbosch │
e.veerman(a)s-Hertogenbosch.nl<mailto:e.veerman@s-Hertogenbosch.nl> │06 24 53 09 61 │ Postbus 12345 │ 5200 GZ 's-Hertogenbosch │ www.s-hertogenbosch.nl<http://www.s-hertogenbosch.nl/> │
Werkdagen: ma - di - wo - do │
[cid:image001.png@01D3D2A2.08E77DC0]twitter.com/shertogenbosch<https://twitter.com/shertogenbosch>
[cid:image002.png@01D3D2A2.08E77DC0] facebook.com/Gemeente.shertogenbosch<https://www.facebook.com/Gemeente.shertogenbosch/?fref=ts>
[cid:image003.png@01D3D2A2.08E77DC0]Gemeente 's-Hertogenbosch op LinkedIn<https://www.linkedin.com/company/44432?trk=tyah&trkInfo=clickedVertical%3Ac…'s-h>
________________________________
Dit bericht is alleen voor de geadresseerde. Hebt u dit bericht onterecht ontvangen? Laat u dit dan weten aan de afzender. Verwijdert u het bericht dan ook uit uw postbus. De gemeente 's-Hertogenbosch is zo zorgvuldig mogelijk bij het voorkomen van virussen. U dient zelf te controleren of er geen virussen in de bijlage(n) zitten.
Gemeente 's-Hertogenbosch https://www.s-hertogenbosch.nl
________________________________
Beste Allemaal,
Zoals afgesproken in ons product steering overleg afgelopen Donderdag
willen we kijken naar een nieuwe datum die beter in jullie schema past.
Ik heb een datumprikker aangemaakt waar je je beschikbaarheid kunt opgeven:
https://datumprikker.nl/pdxtfyu3shw74rzz
Omdat ik bij datumprikker niet kan kiezen voor "iedere 2e dinsdag van de
maand, of dinsdag iedere weken" heb ik ervoor gekozen om de hele maand
januari alle dagen in de week in de prikker te zetten.
Lees de beschikbare opties als " iedere maandag in die week van de maand op
dat tijdslot ben ik meestal beschikbaar" Als we deze zo invullen komen we
tot de beste opties.
Fijn weekend alvast.
Groeten,
Felix
---
As agreed in our product steering meeting last Thursday, we want to look at
a new date that better fits your schedule.
I have created a date picker where you can indicate your availability:
https:// Datumprikker.nl/pdxtfyu3shw74rzz
Because I cannot choose "every 2nd Tuesday of the month, or Tuesday every X
weeks" with the date picker, I have chosen to use every day of the week
for the entire month of January.
Read the available options as "every Monday in that week of the month on
that time slot I am usually available".
Have a nice weekend.
--
Felix Faassen, Codebase steward
Foundation for Public Code | https://publiccode.netgithub.com/publiccodenet | github.com/felixfaassen
felix(a)publiccode.net | +31 624633278
Signalen Product Steering Meeting 26th of November, 2020, 14:00 to 15:00
This note: https://hackmd.io/dHk92p2TT8GU3uEqlmLfSQ
Shared Product backlog: https://github.com/orgs/Signals/projects/2 (draft)
Product steering and feature requests documentation:
https://github.com/Signalen/product-steering
Create feature request:
https://github.com/Signalen/product-steering/issues/new?assignees=&labels=e…
Slack Channel:
https://join.slack.com/share/zt-heae6d92-sqH1xvJvJQ_RMpAAMnHLKQ
Mailing list:
https://lists.publiccode.net/mailman/postorius/lists/signalen-discuss.lists…
(Check
spam)
Chair: Felix
Board: https://miro.com/app/board/o9J_kkwkuBE=/
<https://hackmd.io/dHk92p2TT8GU3uEqlmLfSQ#Agenda>Agenda:
- Announcements Felix: Meeting availability and mailing list
- Update Erik on action point : Backlog Grooming and invite to go over
these
- Discussion about refinement of
https://github.com/Signalen/product-steering/issues/30
<https://hackmd.io/dHk92p2TT8GU3uEqlmLfSQ#Announcements>Announcements
- Felix: Last meeting availability for participation meetings (see
action points)
- Jacco: Stresses importance attendance of all municipalities
<https://hackmd.io/dHk92p2TT8GU3uEqlmLfSQ#Update-on-product-backlog>Update
on product backlog
Erik briefly discussed the work Bram, Amy, Erik and Felix have done. It is
important that we keep grooming the product backlog so only relevant
features are listed and prioritized and at the same time be able to refine
and detail feature requests so we learn how the process from idea to
implementation works.
<https://hackmd.io/dHk92p2TT8GU3uEqlmLfSQ#General-discussion-about-collabora…>General
discussion about collaboration and feature requests
Bram proposed to take 1 feature and discuss this further. Arvid noticed
that a lot of thinking and designing went into how to avoid duplicate
reporting, linking reports. He will give a demo in our next project
steering meeting and share this knowledge with the group.
Also notes that designing and enhancing features takes a lot of time as it
relates closely to process. Bram suggested to plan in
The group also mentioned it is important to have regular longer sessions in
the next year, sit behind a whiteboard together to have a joint
collaborative view on the products goals, roadmap and feature requests.
Bram proposed a meeting on the 9th of december to briefly go over the
backlog again and focus working on one issue:
https://github.com/Signalen/product-steering/issues/30
Arvid pointed out that Amsterdam has set its development budget for
Signalen 2021 and would like to include other features from this group as
well which are beneficial to all.
Astrid added a “Slim melden” user test is underway in Utrecht with citizens
using Signalen.
Arjo mentioned he finds it challenging to add comments to existing features
as he is missing context. Felix adds this is normal in the beginning and
that we are working as a group to more collective knowledge. Also it is not
required to add something. Being part of the conversation around this is
the most important.
In general, Felix adds it is important to focus on our shared product
backlog. Grooming it, refining it so we get a better overview on what
features are important and which can be archived. Bram acknowledges and
adds that in addition he would also gradually want to detail and specify
feature requests. Astrid also agrees but thinks it is important to have an
overview and basic high-level idea as this will inform you on which feature
request you should spend time on for further refinement.
<https://hackmd.io/dHk92p2TT8GU3uEqlmLfSQ#Product-steering-schedule>Product
steering schedule
A number of participants indicated Thursdays at 14:00 is not working for
them. The 10th of december almost none of us are able to make it.
Felix suggests to send out a datumprikker so everyone can indicate what
works the best for them and then reschedule the meeting. If we are able to
pick a new slot before the 10th of december we can already reschedule the
10th of December to another date which works for more people.
<https://hackmd.io/dHk92p2TT8GU3uEqlmLfSQ#Agenda-next-meeting>Agenda next
meeting
- Demo from Arvid about handling and linking reports
<https://hackmd.io/dHk92p2TT8GU3uEqlmLfSQ#Action-points>Action points
Next chair: ???
ActionResponsibleDue date
Send out datumprikker to accommodate new date for product steering Felix
10-12-2020
Working session on Backlog and feature request 9th december 09:00 - 11:00
--
Felix Faassen, Codebase steward
Foundation for Public Code | https://publiccode.netgithub.com/publiccodenet | github.com/felixfaassen
felix(a)publiccode.net | +31 624633278