Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
#2: Post edited
by
trichoplax
·
2022-09-16T12:50:25Z (over 2 years ago)
Typos
Contributor Spotlight: sau226, sysadmin
- This is the second of an ongoing series of blog posts highlighting individual contributors to the Codidact Project, as a way of drawing attention to the hard work that people are putting in and saying thank you. In this edition, we're putting the spotlight on [sau266](https://meta.codidact.com/users/53492), one of our more behind-the-scenes contributors.
- sau266 stumbled across the project one day and decided to get involved, first through public contributions such as here on Meta, and then later on through more internal methods. sau's contributions are in a blend of the community and code areas, with a specific focus on internal tooling - e.g. setting up and maintaining our support portal, internal documentation, and more. You can read the blog post on [setting up the Atlassian stack that we use](https://meta.codidact.com/posts/286650) here in our blog category, which just so happens to be written by sau266.
- After extensive research and using sophisticated surveillance systems, we were able to determine that sau resides in the Terran Solar System. If, however, you deliver a properly signed, legally binding warrant, obtained through honest means and for proper use, you will be informed that this elusive user can actually be found in the location known as Planet Earth.
- sau works to translate between communities and code and ensure that some of Codidact's side systems keep ticking along. This involves dealing with running servers, handling community-submitted requests, performing some outreach efforts, and occasionally dipping some toes in the codebase. In terms of future plans, sau's goal is to move Codidact's systems to infrastructure that crashes less often (which is what our [Great Migration](https://meta.codidact.com/posts/286582) project is working on right now), and is involved in moving that along.
- When asked about a favorite aspect of the project, sau expressed an appreciation for the sense of community that Codidact provides, as well the opportunity to give back for the next generation of inquisitive students through code and outreach.
I'd also like to take this opportunity to shout out sau's consistency in taking the intiative. Often I'll log onto Discord or Atlassian and see that sau has identified something that we were missing or could be improved and has already taken steps to address it. That quality is not an espcially common one, and it's be appreciated when you've found it, such as we have in the form of sau266.- ---
On behalf of the Codidact Team, I'd like to thank you sincerely for the effort you put it to help the network. Even if your contributions are often more behind-the-scenes and not publicly visible, they're still appreciated by the Team and everyone involved. Thank you, and we hope to see you poking around behind the scenes for quite a while longer.
- This is the second of an ongoing series of blog posts highlighting individual contributors to the Codidact Project, as a way of drawing attention to the hard work that people are putting in and saying thank you. In this edition, we're putting the spotlight on [sau266](https://meta.codidact.com/users/53492), one of our more behind-the-scenes contributors.
- sau266 stumbled across the project one day and decided to get involved, first through public contributions such as here on Meta, and then later on through more internal methods. sau's contributions are in a blend of the community and code areas, with a specific focus on internal tooling - e.g. setting up and maintaining our support portal, internal documentation, and more. You can read the blog post on [setting up the Atlassian stack that we use](https://meta.codidact.com/posts/286650) here in our blog category, which just so happens to be written by sau266.
- After extensive research and using sophisticated surveillance systems, we were able to determine that sau resides in the Terran Solar System. If, however, you deliver a properly signed, legally binding warrant, obtained through honest means and for proper use, you will be informed that this elusive user can actually be found in the location known as Planet Earth.
- sau works to translate between communities and code and ensure that some of Codidact's side systems keep ticking along. This involves dealing with running servers, handling community-submitted requests, performing some outreach efforts, and occasionally dipping some toes in the codebase. In terms of future plans, sau's goal is to move Codidact's systems to infrastructure that crashes less often (which is what our [Great Migration](https://meta.codidact.com/posts/286582) project is working on right now), and is involved in moving that along.
- When asked about a favorite aspect of the project, sau expressed an appreciation for the sense of community that Codidact provides, as well the opportunity to give back for the next generation of inquisitive students through code and outreach.
- I'd also like to take this opportunity to shout out sau's consistency in taking the initiative. Often I'll log onto Discord or Atlassian and see that sau has identified something that we were missing or could be improved and has already taken steps to address it. That quality is not an especially common one, and it's to be appreciated when you've found it, such as we have in the form of sau266.
- ---
- On behalf of the Codidact Team, I'd like to thank you sincerely for the effort you put in to help the network. Even if your contributions are often more behind-the-scenes and not publicly visible, they're still appreciated by the Team and everyone involved. Thank you, and we hope to see you poking around behind the scenes for quite a while longer.
#1: Initial revision
by
Mithical
·
2022-08-15T20:23:12Z (over 2 years ago)
Contributor Spotlight: sau226, sysadmin
This is the second of an ongoing series of blog posts highlighting individual contributors to the Codidact Project, as a way of drawing attention to the hard work that people are putting in and saying thank you. In this edition, we're putting the spotlight on [sau266](https://meta.codidact.com/users/53492), one of our more behind-the-scenes contributors. sau266 stumbled across the project one day and decided to get involved, first through public contributions such as here on Meta, and then later on through more internal methods. sau's contributions are in a blend of the community and code areas, with a specific focus on internal tooling - e.g. setting up and maintaining our support portal, internal documentation, and more. You can read the blog post on [setting up the Atlassian stack that we use](https://meta.codidact.com/posts/286650) here in our blog category, which just so happens to be written by sau266. After extensive research and using sophisticated surveillance systems, we were able to determine that sau resides in the Terran Solar System. If, however, you deliver a properly signed, legally binding warrant, obtained through honest means and for proper use, you will be informed that this elusive user can actually be found in the location known as Planet Earth. sau works to translate between communities and code and ensure that some of Codidact's side systems keep ticking along. This involves dealing with running servers, handling community-submitted requests, performing some outreach efforts, and occasionally dipping some toes in the codebase. In terms of future plans, sau's goal is to move Codidact's systems to infrastructure that crashes less often (which is what our [Great Migration](https://meta.codidact.com/posts/286582) project is working on right now), and is involved in moving that along. When asked about a favorite aspect of the project, sau expressed an appreciation for the sense of community that Codidact provides, as well the opportunity to give back for the next generation of inquisitive students through code and outreach. I'd also like to take this opportunity to shout out sau's consistency in taking the intiative. Often I'll log onto Discord or Atlassian and see that sau has identified something that we were missing or could be improved and has already taken steps to address it. That quality is not an espcially common one, and it's be appreciated when you've found it, such as we have in the form of sau266. --- On behalf of the Codidact Team, I'd like to thank you sincerely for the effort you put it to help the network. Even if your contributions are often more behind-the-scenes and not publicly visible, they're still appreciated by the Team and everyone involved. Thank you, and we hope to see you poking around behind the scenes for quite a while longer.