draft text from bullet points on community

content/blog/2024-04-10-writing-retreat-community.md

@@ -29,51 +29,15 @@ The "monday morning hello" was mentioned as one way of feeling engaged with and
 
 Apart from "not enough time" to follow the chat, also its unorganized nature was mentioned as a reason not to engage.
 This can partly be solved by using the chat differently, following/unfollowing topics that are of interest to oneself and marking topics as "resolved".
+We have since been discussing a chat cleanup and reorganization/renaming strategy (to be implemented in early summer '24) and sharing tips on how to use Zulip efficiently as blog, event or video. In addition to that, admins will try to be more active in managing the chat.
+After the reorganization and the addition of an eventes channel will also try to share more events of interest to the community via chat and our [calendars](https://coderefinery.org/calendars/) where appropriate. 
+We already implemented a "CodeRefinery for busy people" weekly chat summary, which anyone can sign up to here:  [https://postit.csc.fi/sympa/subscribe/coderefinery-team](https://postit.csc.fi/sympa/subscribe/coderefinery-team). In addition to that, we will also continue the less frequent (~one email every one/two months) [newsletter](https://postit.csc.fi/sympa/subscribe/coderefinery).
 
-Improvement suggestions for the CodeRefinery community: 
-- More event news sharing
-- Community calls
-- Newsletters
-- Adjust default channels for new members and update their descriptions
-- Dedicated admins
-- More work sharing
+One big ask from the community was to share the work/tasks more open and completely. We used to have a large list of tasks sorted by amount of time a community member has to spare. While this was considered a good idea, the tasks often lacked description, and so were not taken over by the community. We have therefore started to move the tasks back to the github organization, where all open tasks are assigned to repositories and described in enough detail that anyone in the community could pick up the task. The tasks are also labelled by the time it approximately takes to fulfill the task and urgency. You can find the board under the Coderefinery GitHub organization under Projects.
 
-We also collected some feedback on how we could activate more helpers and instructors for our workshops; answers:
-- stream format and site of the workshop
-- no train the trainer training offered lately+4
-- What we have now has worked so far: thus we don't ask around enough for more people as much as we could.
-- Simplify workshop complexity
-- Ask peopel directly "do you want to be an instructor?  I'll mentor you."
-- when organising the training event, directly ask who will get onboard to be instructors for xxx session.
-    - when close to the workshop, ask who will be active helpers for specific sessions (if you ask me about this 3 months before the workshop, it is difficult for me to decide as i may have other activities that I have to be there).
-- What do I get in return ?
+In addition community calls were mentioned. We will have some more in the future and try to have them also more regularly. These community calls can have a specific topic and/or serve as Q&A and discussion sessions for the community. We also invite the community to shape these calls, by suggesting topics or take over the organization of a call. In order to attract people to the community calls, the topics and dates should be set as early as possible.
 
-Community engagement suggestions:
-- community calls
-  - They were not so popular were they?
-  - Could it be a zoom/chat session?
-- clear calls for "please do this" (not just teaching)
-  - Maybe the GH board would function as such?
-- recognizing different levels
-  - levels of what?
-- Telling people what to do?  Can be hard to step up but maybe people want to do more but don't know what, someone specifically asking you helps.
-- microtasking
-- regular Q/A sessions to provide support
+We also brainstormed ideas for attracting more people to be instructors/helpers/organizers of the CodeRefinery workshop. Since we upscaled the workshop from ~20 people in person workshop to ~200 online participants, things have gotten more complex. It is less engaging to teach to the stream. Our co-teaching model ensures that the instructor is never alone and the collaborative document is used to influence the teaching, but that does not replace a room full of learners. The current workshop format also seems very complex for newcomers and we have not been offering a train-the-trainer program lately (planned for fall 2024 now! - stay tuned). Due to the sometimes a little bit chaotic planning phase and usually enough team members signing up for the workshop we have not done much active outreach. For this to work it might be required to contact possible instructors more directly and offer f2f mentoring. We should also make sure to not misuse our dear volunteers by not overburdening and burning them out. There needs to be something to get in return. 
 
-Community call suggestions: 
-- topical +1
-- engagement possibility
-  - I think this is not enough as such -> a random person needs a reason to engage with someone. What would these reasons be? A need of help at least.
-- anyone new that comes can leave with something to do (if they want)
-- interesting topics to learn from and not a place to get more tasks to do
-- user stories
-- sharing experiences about conference/meeting, and other onsite/online activities that are relevant to CodeRefinery trainings
-- They also need to know about all the good possibilities beforehand
-
-Other thoughts on community: 
-## Any other thought about communities you may have 
-
-- BYOC (bring your own code) sessions could be made a thing? -> "coderefinery garage"
-- Connection to RSE can bring people on
-- networking with research community ->sessions where we address a particular research community
-- presence in events and event organize own events 
+In order to engage with the community a few other ideas were discussed as well: 
+We could approach different domain communities by visiting their events and presenting CodeRefinery. In addition, we could organize our own info events, targeting different groups to engage more directly. Here, also our close connection to the RSE community could be used more. Another idea was to offer further BYOC (bring your own code) sessions to provide the possibility of interacting with CodeRefinery instructors and asking for support.