Weekly Community Check-In Ideas

[RuthNjeri]

Hi everybody! 👏

We usually have Weekly Community Check-ins every week. This is an opportunity for the contributors, to say hi, ask questions, vent, give feedback and see how everyone is doing. Find the latest Check-in here #9600

Sometimes, you need some inspiration on the kind of topic you would like to introduce in the weekly check-in, below is a list of ideas you could borrow. They are collected from past Check-ins and suggestions from the community.

If you would like to add a topic or two, please share it in the comments or feel free to add it to this list.

Pro-tip: Whenever there is a major event happening in the community, such as Outreachy and GSOC applications, it is usually best to come up with an idea that relates to those events.

Weekly Community Check-in Ideas

1. Create First Timer Issues

To encourage the community to add more FTOs in case they are over and newcomers cannot find any to work on

2. Ask For Help

This can be split into two or one issues. Where a mentor for example for GSOC(Google Summer of Code) or Outreachy can reach out to other mentors requesting them to reach out for help. It can also be created by any community member urging other contributors to ask for help.

3. Everybody Struggles

Encourage the community to share the struggles they face during coding. This will encourage newcomers and everyone else who occasionally struggles to know they are not alone.

4. Push Your Limits

This could be thought of in various ways. Encouraging contributors to pick up new issues that are beyond FTOs, and ones labelled high-priority, bug. It could also be a topic to inquire from the community how they push their limits individually in order to grow as a developer and a contributor or maybe even in life generally.

5. Documentation

This issue could be a way of reaching out to contributors and asking them to share their ideas on what they would like documented within the Public Lab code, which will help in the contribution process. It could also be a way of encouraging First Time Contributors to write a blog about their experience and sharing it with the community.

6. Modifying Expectations

It could be a question towards Outreachy or GSOC Interns and maybe even the community, on finding out what they have been working on and what they plan to work in within that week. You could also talk about the benefit of communicating when you are no longer able to work on an issue you picked up.

7. Keep Reinventing

Re-inventing(build something successful out of the existing). You can encourage the community to share something they have re-invented. A new or existing feature that has been improved.

8. Teamwork

Encourage the community to talk about how they have worked alongside other contributors and the benefits of that.

9. Bash Alias

They provide a way to write a shortcut to a code you use often, for example, I use gco to mean git checkout as a bash alias. Ask the community about the bash aliases they use.

10. Favourite IDE

Ask the community to share their favourite IDE and what about it makes their coding experience better.

11. Learning How To Learn

What methods are effective to you in learning a new language or a new codebase or learning in general?

12. Imposter Syndrome

Have you ever felt like you do not belong in tech? How did you overcome that?

I will keep updating this list with time...TODO..create FTO to add this issue to the Weekly Check-in Template

[cesswairimu]

we can create a checkin on the topics we all proposed to learn as discussed in the meeting.
Refer to this comment - #9797 (comment)

Originally posted by @17sushmita in #9866 (comment)

[iamcynthiamamah]

This is amazing. thanks