Call for Community Maintainers #571

Open
opened 4 months ago by fnetX · 26 comments
fnetX commented 4 months ago
Collaborator

Dear Codeberg users and fans,

as you know, Codeberg is a collaborative effort and relies on community maintenance. To scale our human power to the increasing demand for diverse tiny tasks, I am now calling for more community maintainers for 2022.

Among other, you could help out by:

  • providing user support in various channels, e.g. the Community Issue Tracker, Matrix and IRC channels and / or Social Media
  • moderating issues in some Codeberg/* repos (labelling, sorting)
  • confirming bugs and forwarding bugs + feature requests upstream to Gitea, if they need to be addressed in the software itself
  • maintaining the Codeberg Documentation and Blog (reviewing pull requests, fixing urgent issues), and optionally contributing to them
  • planning Social Media campaigns and events
  • helping in development of various software and tools, next to Gitea we might need a helping hand with Codeberg Pages and the very-WIP moderation toolbox.

If you are interested in any of the above, and are willing to invest a somewhat steady amount of time into the project for a few weeks or months (it does not have to be much, maybe starting a few hours per month), we warmly welcome you to our journey.

Are you interested? Just comment here or drop us an email, and write a few sentences about yourself.

Thank you very much! 💙

Dear Codeberg users and fans, as you know, Codeberg is a collaborative effort and relies on community maintenance. To scale our human power to the increasing demand for diverse tiny tasks, I am now calling for more community maintainers for 2022. Among other, you could help out by: - providing user support in various channels, e.g. the Community Issue Tracker, [Matrix and IRC channels](https://docs.codeberg.org/contact/#questions-and-issues) and / or Social Media - moderating issues in some Codeberg/* repos (labelling, sorting) - confirming bugs and forwarding bugs + feature requests upstream to Gitea, if they need to be addressed in the software itself - maintaining the Codeberg Documentation and Blog (reviewing pull requests, fixing urgent issues), and optionally contributing to them - planning Social Media campaigns and events - helping in development of various software and tools, next to Gitea we might need a helping hand with [Codeberg Pages](https://codeberg.org/Codeberg/pages-server) and the very-WIP [moderation toolbox](https://codeberg.org/Codeberg/moderation). If you are interested in any of the above, and are willing to invest a somewhat steady amount of time into the project for a few weeks or months (it does not have to be much, maybe starting a few hours per month), we warmly welcome you to our journey. Are you interested? Just comment here or drop us an email, and write a few sentences about yourself. Thank you very much! 💙
fnetX added the
contribution welcome
label 4 months ago

I don't have much time to spare, but I'd be willing to help out at Codeberg Documentation (again 😉). Do you need technical maintainers or content maintainers there? Because I could help with technical maintenance, like fixing bugs, or some light development of new features. I could also help out with issue moderation for the docs repo. But I don't have enough time at the moment to write articles or review content PRs. Let me know, if that would help :-)

I don't have much time to spare, but I'd be willing to help out at Codeberg Documentation (again 😉). Do you need technical maintainers or content maintainers there? Because I could help with technical maintenance, like fixing bugs, or some light development of new features. I could also help out with issue moderation for the docs repo. But I don't have enough time at the moment to write articles or review content PRs. Let me know, if that would help :-)
Poster
Collaborator

Hey, and thank you. I added you to the team. There are some Part: Generator labels in the Documentation issues, maybe one of them appeals to you.

We need both technical maintainers and content maintainers, but it should be fine if you stick to one of them if you don't have the time to invest into both roles.

Hey, and thank you. I added you to the team. There are some [Part: Generator labels](https://codeberg.org/Codeberg/Documentation/issues?q=&type=all&state=open&labels=5660&milestone=0&assignee=0) in the Documentation issues, maybe one of them appeals to you. We need both technical maintainers and content maintainers, but it should be fine if you stick to one of them if you don't have the time to invest into both roles.
Collaborator

I would love being apart of the Codeberg team. I have experience managing various communities on different platforms. I wouldn't mind doing any thing on that list. I would also good on the developer side of things. My website is avaliable at https://ycws.vercel.app

I would love being apart of the Codeberg team. I have experience managing various communities on different platforms. I wouldn't mind doing any thing on that list. I would also good on the developer side of things. My website is avaliable at https://ycws.vercel.app
Poster
Collaborator

@youngchief Thank you very much. Feel free to ask questions here, if there are any. In this issue tracker, everything that is labelled gitea, but does not either carry the upstream or codeberg (specific) label, should be forwarded to Gitea. Maybe you can start checking some of the issues and if they exist upstream. In the end, everything should have an upstream report, and the Codeberg issue should carry the upstream label and provide the link there (if the issue is worth forwarding and not related to Codeberg).

If you are ready to help out developing, maybe you want to check out Codeberg/moderation, too. It's a new proof-of-concept moderation system in Go. Next to all of the frontend development based on Codeberg/Design, one of the next steps would be to implement an OAuth login with Codeberg that checks if the user is part of an organization and grants permissions based on which team she/he is in. I'll try to update the roadmap so it's easier to contribute, if you are interested.

You'll receive write-access to the necessary projects soon. Are you using the Matrix messenger, by chance?

@youngchief Thank you very much. Feel free to ask questions here, if there are any. In this issue tracker, everything that is labelled `gitea`, but does not either carry the `upstream` or `codeberg` (specific) label, should be forwarded to Gitea. Maybe you can start checking some of the issues and if they exist upstream. In the end, everything should have an upstream report, and the Codeberg issue should carry the upstream label and provide the link there (if the issue is worth forwarding and not related to Codeberg). If you are ready to help out developing, maybe you want to check out Codeberg/moderation, too. It's a new proof-of-concept moderation system in Go. Next to all of the frontend development based on Codeberg/Design, one of the next steps would be to implement an OAuth login with Codeberg that checks if the user is part of an organization and grants permissions based on which team she/he is in. I'll try to update the roadmap so it's easier to contribute, if you are interested. You'll receive write-access to the necessary projects soon. Are you using the Matrix messenger, by chance?
Collaborator

@fnetX Hi! Thanks for the quick response.
Yeah the OAuth project seems interesting.
Forwarding the appropriate issues is something I can do for sure.
Also yes, I am using [matrix]. My MXID is @youngchief:tchncs.de
Feel free to reach me at any time for any reason.

@fnetX Hi! Thanks for the quick response. Yeah the OAuth project seems interesting. Forwarding the appropriate issues is something I can do for sure. Also yes, I am using [matrix]. My MXID is `@youngchief:tchncs.de` Feel free to reach me at any time for any reason.
Collaborator

Hey there, I would love supporting the FLOSS movement and since everyone needs to host their project somewhere, it would be a pleasure for me to actively help improving codeberg.

I started coding in 2017 at school and this year I will graduate from the higher technical colleague Mössingerstraße - See: HTL.

Hey there, I would love supporting the FLOSS movement and since everyone needs to host their project somewhere, it would be a pleasure for me to actively help improving codeberg. I started coding in 2017 at school and this year I will graduate from the higher technical colleague Mössingerstraße - See: [HTL](https://de.wikipedia.org/wiki/H%C3%B6here_Technische_Lehranstalt).
Poster
Collaborator

Thank you. Same as written above also applies to you. Feel free to reach out to us if you have any questions.

I added both of you to a Matrix group, if something is unclear (e.g. how to proceed with an issue or PR), this can be discussed there.

Thank you. Same as written above also applies to you. Feel free to reach out to us if you have any questions. I added both of you to a Matrix group, if something is unclear (e.g. how to proceed with an issue or PR), this can be discussed there.
Collaborator

Hi there,

I like the idea. I would like to see what is available for a simple guy who likes to fiddle and try out things. I can do most of the things from the list if there is no need to create yet another account. Ideally, all tasks could be here on this platform so i can just stay in one place.

I am a release management guy focusing on infosec, which I am learning right now, and general system admin things. I have been using linux environment for the last 15+ years (like a regular user, admin, movie watcher, gamer... everything). I can fill many shoes relatively quickly and spend some time helping out as long as there is no pressure and programming (sh guy here obviously)

Not exciting but it is what it is : )

Hi there, I like the idea. I would like to see what is available for a simple guy who likes to fiddle and try out things. I can do most of the things from the list if there is no need to create yet another account. Ideally, all tasks could be here on this platform so i can just stay in one place. I am a release management guy focusing on infosec, which I am learning right now, and general system admin things. I have been using linux environment for the last 15+ years (like a regular user, admin, movie watcher, gamer... everything). I can fill many shoes relatively quickly and spend some time helping out as long as there is no pressure and programming (sh guy here obviously) Not exciting but it is what it is : )
Poster
Collaborator

@blagablongo are you interested in anything specific I listed above? I currently see high demand at the Documentation content and bug forwarding, tbh. If you are interested in sysadmin stuff, maybe you are interested in helping out with our infrastructure, stack consisting mostly from Debian, LXC, Ansible and Filesystem (ZFS + Ceph) stuff. Also, I will think of you when reworking some shellscripts we are using, shouldn't be to much programming :)

@blagablongo are you interested in anything specific I listed above? I currently see high demand at the Documentation content and bug forwarding, tbh. If you are interested in sysadmin stuff, maybe you are interested in helping out with our infrastructure, stack consisting mostly from Debian, LXC, Ansible and Filesystem (ZFS + Ceph) stuff. Also, I will think of you when reworking some shellscripts we are using, shouldn't be to much programming :)
Collaborator

@blagablongo are you interested in anything specific I listed above? I currently see high demand at the Documentation content and bug forwarding, tbh. If you are interested in sysadmin stuff, maybe you are interested in helping out with our infrastructure, stack consisting mostly from Debian, LXC, Ansible and Filesystem (ZFS + Ceph) stuff. Also, I will think of you when reworking some shellscripts we are using, shouldn't be to much programming :)

Hi,

I can start with simpler tasks so i can build up momentum and avoid giving any empty promises of course. From your lit, labeling issues sounds like fun. Drop me some details whenever you can or just point me in some direction so I can bootstrap myself a bit myself, review the pace, current discussions and/or work.

I am here to help!

> @blagablongo are you interested in anything specific I listed above? I currently see high demand at the Documentation content and bug forwarding, tbh. If you are interested in sysadmin stuff, maybe you are interested in helping out with our infrastructure, stack consisting mostly from Debian, LXC, Ansible and Filesystem (ZFS + Ceph) stuff. Also, I will think of you when reworking some shellscripts we are using, shouldn't be to much programming :) Hi, I can start with simpler tasks so i can build up momentum and avoid giving any empty promises of course. From your lit, labeling issues sounds like fun. Drop me some details whenever you can or just point me in some direction so I can bootstrap myself a bit myself, review the pace, current discussions and/or work. I am here to help!
Collaborator

I'm willing to help, but have no prior experience in this regard. thank you.

I'm willing to help, but have no prior experience in this regard. thank you.

I just noticed that I seemingly was signed up as a watcher for numerous Codeberg repositories other than Codeberg Documentation, so I want to clarify at this point that I'm only interested in helping a little bit for Documentation, not for Codeberg in general.

I just noticed that I seemingly was signed up as a watcher for numerous Codeberg repositories other than Codeberg Documentation, so I want to clarify at this point that I'm only interested in helping a little bit for Documentation, not for Codeberg in general.
Poster
Collaborator

@lhinderberger: We are using teams to manage permission. You are automatically subscribed to all repositories this team is in. Managing permissions for single use-cases would be some additional hazzle, but I wasn't aware the watching was a default setting.

@shrios Experience is not necessary. Being available to issues and tracking them, forwarding to upstream etc is a good start, with more tasks being available later.

We are having a matrix channel under the Codeberg space, if you want, you can join in there. Otherwise, this issue can be used for questions and discussion.

@lhinderberger: We are using teams to manage permission. You are automatically subscribed to all repositories this team is in. Managing permissions for single use-cases would be some additional hazzle, but I wasn't aware the watching was a default setting. @shrios Experience is not necessary. Being available to issues and tracking them, forwarding to upstream etc is a good start, with more tasks being available later. We are having a matrix channel under the Codeberg space, if you want, you can join in there. Otherwise, this issue can be used for questions and discussion.
Collaborator

ok, i think, i'd give it a try. thank you.

ok, i think, i'd give it a try. thank you.
Poster
Collaborator

@shrios @athepony I added both of you to the team. Next to labelling community issues and forwarding upstream, it would also be nice to see more work on the end-user documentation, see Codeberg/Documentation. Docs are basically non existent for Gitea, and it would be nice to contribute content back to upstream when possible, another project we'd need to coordinate.

There is a lot of content on Matrix, see https://docs.codeberg.org/contact/ for links. There are groups in Matrix for this community contributors, as well as the specifically the documentation.

@shrios @athepony I added both of you to the team. Next to labelling community issues and forwarding upstream, it would also be nice to see more work on the end-user documentation, see Codeberg/Documentation. Docs are basically non existent for Gitea, and it would be nice to contribute content back to upstream when possible, another project we'd need to coordinate. There is a lot of content on Matrix, see https://docs.codeberg.org/contact/ for links. There are groups in Matrix for this community contributors, as well as the specifically the documentation.

I need to put food on the table so I can't offer my time for free. God bless those who can. But if you're looking for help and can offer a modest wage I'm in the +8 timezone and have been using Gitea for 3 years both with Docker Compose and in Kubernetes. Contact info available from my Codeberg page. 🙏

I need to put food on the table so I can't offer my time for free. God bless those who can. But if you're looking for help and can offer a modest wage I'm in the +8 timezone and have been using Gitea for 3 years both with Docker Compose and in Kubernetes. Contact info available [from my Codeberg page](https://vhs.codeberg.page/contact/). 🙏
Poster
Collaborator

Thank you for the offer; we'll keep you in mind. Sadly, we are having much more people we'd like to hire than actual money for anyone. Currently, Codeberg runs because of volunteers and while we'll surely start paying people soon, most of the work being done here will probably stay volunteer work for long time.

Thank you for the offer; we'll keep you in mind. Sadly, we are having much more people we'd like to hire than actual money for anyone. Currently, Codeberg runs because of volunteers and while we'll surely start paying people soon, most of the work being done here will probably stay volunteer work for long time.
Collaborator

I'm willing to help also...
no experience yet

I'm willing to help also... no experience yet
Collaborator

Hi, i would love to help out to support social media. I build my first webportal for a crew of friends back in nienties and later been mod, admin & webdev in some forums. And lately I became a professional webdev exploring all the new possibilities these days...

🧐 https://stackshare.io/codeberg

Hi, i would love to help out to support social media. I build my first webportal for a crew of friends back in nienties and later been mod, admin & webdev in some forums. And lately I became a professional webdev exploring all the new possibilities these days... 🧐 https://stackshare.io/codeberg
Collaborator

Hey, I'm Daniel a front-end developer based in Spain. I have a lot of experience moderating communities (open source, discord, twitch...) and I have a lot of free time. I love this project and would like to do my bit.

Hey, I'm Daniel a front-end developer based in Spain. I have a lot of experience moderating communities (open source, discord, twitch...) and I have a lot of free time. I love this project and would like to do my bit.
Poster
Collaborator

@zenobit @redwerkz @Daniellop Thank you, all three. Do you have anything special in mind? I mentioned some of the tasks in the conversation (and I'll try to update the first message with another overview). You can also just start playing around and doing stuff as you like.

You'll receive advanced access ASAP.

@zenobit @redwerkz @Daniellop Thank you, all three. Do you have anything special in mind? I mentioned some of the tasks in the conversation (and I'll try to update the first message with another overview). You can also just start playing around and doing stuff as you like. You'll receive advanced access ASAP.
Collaborator

@zenobit @redwerkz @Daniellop Thank you, all three. Do you have anything special in mind? I mentioned some of the tasks in the conversation (and I'll try to update the first message with another overview). You can also just start playing around and doing stuff as you like.

You'll receive advanced access ASAP.

Well... I am available for anything, I can translate (I speak Spanish, English, French and Chinese), I can program anything and publish blog articles, I also have experience in technical support. Thank you for this opportunity. I'm at your disposal.

> @zenobit @redwerkz @Daniellop Thank you, all three. Do you have anything special in mind? I mentioned some of the tasks in the conversation (and I'll try to update the first message with another overview). You can also just start playing around and doing stuff as you like. > > You'll receive advanced access ASAP. Well... I am available for anything, I can translate (I speak Spanish, English, French and Chinese), I can program anything and publish blog articles, I also have experience in technical support. Thank you for this opportunity. I'm at your disposal.

Hello,

I have some development experience and I'd like to help with the following tasks mentioned that were listed:

  • confirming bugs and forwarding bugs + feature requests upstream to Gitea, if they need to be addressed in the software itself
  • maintaining the Codeberg Documentation and Blog (reviewing pull requests, fixing urgent issues), and optionally contributing to them
  • helping in development of various software and tools, next to Gitea we might need a helping hand with Codeberg Pages and the very-WIP moderation toolbox.
Hello, I have some development experience and I'd like to help with the following tasks mentioned that were listed: - confirming bugs and forwarding bugs + feature requests upstream to Gitea, if they need to be addressed in the software itself - maintaining the Codeberg Documentation and Blog (reviewing pull requests, fixing urgent issues), and optionally contributing to them - helping in development of various software and tools, next to Gitea we might need a helping hand with Codeberg Pages and the very-WIP moderation toolbox.

I will stop watching the Documentation tracker now, since I have lots of other stuff on my hands and there seem to be no technical issues coming up, but lots of content issues.

I will stop watching the Documentation tracker now, since I have lots of other stuff on my hands and there seem to be no technical issues coming up, but lots of content issues.
Poster
Collaborator

@lhinderberger Okay. I suppose we can always ping you if we need help? There is the label Part: Generator or something which contains technical issues, but they are not urgent IIRC.

@lhinderberger Okay. I suppose we can always ping you if we need help? There is the label Part: Generator or something which contains technical issues, but they are not urgent IIRC.

Sure, if there are technical questions, feel free to send me an email :-)

Sure, if there are technical questions, feel free to send me an email :-)
Sign in to join this conversation.
No Milestone
No Assignees
11 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.