You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we have a message for you, well two messages actually :-)
Join the members chat
The project runs a zulip chat for project members and people that like to be more involved with the project in general. If you would like to join please send a private message to me via the Beets Discourse forum (since we can't do that via GitHub and we don't want you to post email adresses in here)
Currently in the chat, we are running a poll with existing Beetbox project members to find out what the interests of our members are in the project, what areas they have good knowledge of the codebase/the docs, and in general in what parts of the project "they feel at home".
Providing your information there should be published in the Beets contribution docs. Its main purpose is to help future beets contributors and users to get to know who they can ask questions or who would be best to ask for a code-review.
Please don't feel forced that joining to this internal project chat would require you to participate in that poll. If you feel uncomfortable to show up on a public list as described, you certainly don't have to. Nevertheless your opinion on discussions in this chat will add value and we'd like you to join anyway!
Also at this point it probably it is a good idea to shout out to anyone who ever felt they would like to get more active in the Beets community. If you think you can add value to the project, no matter if organizational-wise or as a programmer, a PR reviewer or a user-supporter, please let us know!
We realised that this is an "opt-in" setting and most members probably didn't even know that they could adapt this setting. That's why we are reaching out:
If you'd like to show publicly as a member of the Beetbox project (in Issues comments, PR comments and so on) please set this to "public", if you'd rather like to keep this to "private" because you don't want others to know that you are part of the project, that is certainly perfectly fine as well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear members of the GitHub Beetbox organization,
we have a message for you, well two messages actually :-)
Join the members chat
The project runs a zulip chat for project members and people that like to be more involved with the project in general. If you would like to join please send a private message to me via the Beets Discourse forum (since we can't do that via GitHub and we don't want you to post email adresses in here)
Currently in the chat, we are running a poll with existing Beetbox project members to find out what the interests of our members are in the project, what areas they have good knowledge of the codebase/the docs, and in general in what parts of the project "they feel at home".
Providing your information there should be published in the Beets contribution docs. Its main purpose is to help future beets contributors and users to get to know who they can ask questions or who would be best to ask for a code-review.
Please don't feel forced that joining to this internal project chat would require you to participate in that poll. If you feel uncomfortable to show up on a public list as described, you certainly don't have to. Nevertheless your opinion on discussions in this chat will add value and we'd like you to join anyway!
Also at this point it probably it is a good idea to shout out to anyone who ever felt they would like to get more active in the Beets community. If you think you can add value to the project, no matter if organizational-wise or as a programmer, a PR reviewer or a user-supporter, please let us know!
Adapt your member public/private setting
In the list of members pointed out above, only project members that have this setting set to "public" will be shown to other GitHub users as such.
We realised that this is an "opt-in" setting and most members probably didn't even know that they could adapt this setting. That's why we are reaching out:
If you'd like to show publicly as a member of the Beetbox project (in Issues comments, PR comments and so on) please set this to "public", if you'd rather like to keep this to "private" because you don't want others to know that you are part of the project, that is certainly perfectly fine as well.
So long,
Jojo, on behalf of the Beets project.
Beta Was this translation helpful? Give feedback.
All reactions