<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body><div style="font-family:Helvetica,Arial;font-size:13px">Hello all, </div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px">Thanks for attending our last meeting online. We were able to discuss key elements of work that can improve our process in the future and communicate this clearly to incoming and current developers in our visual design community.</div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px">In general traces, we are of the agreement that our group should:</div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px">1. Approve merge requests within a reasonable amount of time for the community to examine and review such merge requests. Some suggested waiting, at least, 24 hours before approving a merge request.</div><div style="font-family:Helvetica,Arial;font-size:13px"><span class="Apple-tab-span" style="white-space:pre"> </span>- This should prevent merge requests from being accepted without proper review by the community</div><div style="font-family:Helvetica,Arial;font-size:13px"><span class="Apple-tab-span" style="white-space:pre"> </span>- This should curve perceptions that some developers receive easy approvals while others do not</div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px">2. Approving merge requests should be done by, at least, 3 areas of our groups</div><div style="font-family:Helvetica,Arial;font-size:13px"><span class="Apple-tab-span" style="white-space:pre"> </span>- Quality assurance, code review</div><div style="font-family:Helvetica,Arial;font-size:13px"><span class="Apple-tab-span" style="white-space:pre"> </span>- Visual designers, UI reviewers</div><div style="font-family:Helvetica,Arial;font-size:13px"><span class="Apple-tab-span" style="white-space:pre"> </span>- User experience designers, UX reviewers</div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px">* Given that many of us wear many hats in our community, our approval comments in a merge request “should” include what approval hat you are wearing. For example “+1 for visuals, or user experience, or code review”.</div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px">3. Merge requests should have a sponsor person that can help that developer navigate the process of getting their request approved. We ask that every member in our community, who is able, to take on this responsibility and guide where it’s needed.</div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px">If there are any suggestions to these 3 guidelines, please let us know. We hope to place these guidelines in our documents to make this more clear to the public.</div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px">With that said, here is the recording of our last meeting! :D</div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px"><a href="https://meet.kde.org/playback/presentation/2.0/playback.html?meetingId=13c9edf5ab7dc3a850feebda14fe5ed07fbe3577-1611327239540">https://meet.kde.org/playback/presentation/2.0/playback.html?meetingId=13c9edf5ab7dc3a850feebda14fe5ed07fbe3577-1611327239540</a></div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px">Thank you all for being there!</div><div style="font-family:Helvetica,Arial;font-size:13px"><br></div><div style="font-family:Helvetica,Arial;font-size:13px">Andy (anditosan)</div></body></html>