Organization: Difference between revisions

Line 15:

=== Role Templates ===

These roles are well documented and therefore are good to pick from. If you think a different role would be helpful or that something is missing here, please bring it up in [https://matrix.to/#/#fassag-general:chat.solarpunk.moe General]! None of these roles are intended to be exclusive to any Team!

{| class="wikitable"

* Lens

|+

Lenses help focus the Team. Lenses should encourage, motivate, and direct. Members should have an idea of how they are best motivated, but if not, Lenses should try to help them figure that out. Lenses also function as oversight, to try to catch potential problems before they happen.

!Role

* Scribe

!Description

Scribes learn and guide. Scribes are heavily encouraged to talk to other members of their team to fill in gaps in their understanding. Whether documenting a project the Development Team is working on, or writing for the R&G team, Scribes should try to write as accessibly as possible. Of course, developer guides will inherently be a bit more technical, but they should aim to not make things any more technical than it has to be.

!Current members

* Engineer

|-

Engineers focus primarily on software itself. When implementing user-facing components, aim to follow guidelines we have already written! If nothing exists however, this is something to bring up with your team! Engineers are also very useful for research, as they will be able to understand why something is the way it is, in a way that those who cannot read code will not be able to.

|[[Lens]]

* Designer

|Lenses help focus the Team. Lenses should encourage, motivate, and direct. Members should have an idea of how they are best motivated, but if not, Lenses should try to help them figure that out. Lenses also function as oversight, to try to catch potential problems before they happen.

Designers have a very important job, as they will be focusing now just on what looks nice, but also on what is safe and accessible. Designers can help with style guides for writing, icons, UIs, or whatever else really. The goal here is to be creative!

|{{Role members|Role=lens}}

* Tester

|-

Testers should try to push the limits and find bugs and edge cases with the software we are working on and studying. Testers should try to also work with disabled people, to get a better understanding of what methods they use to interact with software, to test out different software using those methods.

|[[Scribe]]

* Outreach

|Scribes learn and guide. Scribes are heavily encouraged to talk to other members of their team to fill in gaps in their understanding. Whether documenting a project the Development Team is working on, or writing for the R&G team, Scribes should try to write as accessibly as possible. Of course, developer guides will inherently be a bit more technical, but they should aim to not make things any more technical than it has to be.

This is for the bigger picture stuff. Whether it's managing social accounts, putting up posters, or whatever else, the goal is to get people involved, or at the very least, make people aware of our guides. Our goal is to help people, and we cannot help them if they do not know about us!

|{{Role members|Role=scribe}}

|-

|[[Engineer]]

|Engineers focus primarily on software itself. When implementing user-facing components, aim to follow guidelines we have already written! If nothing exists however, this is something to bring up with your team! Engineers are also very useful for research, as they will be able to understand why something is the way it is, in a way that those who cannot read code will not be able to.

|{{Role members|Role=engineer}}

|-

|[[Designer]]

|Designers have a very important job, as they will be focusing now just on what looks nice, but also on what is safe and accessible. Designers can help with style guides for writing, icons, UIs, or whatever else really. The goal here is to be creative!

|{{Role members|Role=designer}}

|-

|[[Tester]]

|Testers should try to push the limits and find bugs and edge cases with the software we are working on and studying. Testers should try to also work with disabled people, to get a better understanding of what methods they use to interact with software, to test out different software using those methods.

|{{Role members|Role=tester}}

|-

|[[Outreach]]

|This is for the bigger picture stuff. Whether it's managing social accounts, putting up posters, or whatever else, the goal is to get people involved, or at the very least, make people aware of our guides. Our goal is to help people, and we cannot help them if they do not know about us!

|{{Role members|Role=outreach}}

|}

@@ Line 15: / Line 15: @@
 === Role Templates ===
 These roles are well documented and therefore are good to pick from. If you think a different role would be helpful or that something is missing here, please bring it up in [https://matrix.to/#/#fassag-general:chat.solarpunk.moe General]! None of these roles are intended to be exclusive to any Team!
+{| class="wikitable"
-* Lens
+|+
-Lenses help focus the Team. Lenses should encourage, motivate, and direct. Members should have an idea of how they are best motivated, but if not, Lenses should try to help them figure that out. Lenses also function as oversight, to try to catch potential problems before they happen.
+!Role
-* Scribe
+!Description
-Scribes learn and guide. Scribes are heavily encouraged to talk to other members of their team to fill in gaps in their understanding. Whether documenting a project the Development Team is working on, or writing for the R&G team, Scribes should try to write as accessibly as possible. Of course, developer guides will inherently be a bit more technical, but they should aim to not make things any more technical than it has to be.
+!Current members
-* Engineer
+|-
-Engineers focus primarily on software itself. When implementing user-facing components, aim to follow guidelines we have already written! If nothing exists however, this is something to bring up with your team! Engineers are also very useful for research, as they will be able to understand why something is the way it is, in a way that those who cannot read code will not be able to.
+|[[Lens]]
-* Designer
+|Lenses help focus the Team. Lenses should encourage, motivate, and direct. Members should have an idea of how they are best motivated, but if not, Lenses should try to help them figure that out. Lenses also function as oversight, to try to catch potential problems before they happen.
-Designers have a very important job, as they will be focusing now just on what looks nice, but also on what is safe and accessible. Designers can help with style guides for writing, icons, UIs, or whatever else really. The goal here is to be creative!
+|{{Role members|Role=lens}}
-* Tester
+|-
-Testers should try to push the limits and find bugs and edge cases with the software we are working on and studying. Testers should try to also work with disabled people, to get a better understanding of what methods they use to interact with software, to test out different software using those methods.
+|[[Scribe]]
-* Outreach
+|Scribes learn and guide. Scribes are heavily encouraged to talk to other members of their team to fill in gaps in their understanding. Whether documenting a project the Development Team is working on, or writing for the R&G team, Scribes should try to write as accessibly as possible. Of course, developer guides will inherently be a bit more technical, but they should aim to not make things any more technical than it has to be.
-This is for the bigger picture stuff. Whether it's managing social accounts, putting up posters, or whatever else, the goal is to get people involved, or at the very least, make people aware of our guides. Our goal is to help people, and we cannot help them if they do not know about us!
+|{{Role members|Role=scribe}}
+|-
+|[[Engineer]]
+|Engineers focus primarily on software itself. When implementing user-facing components, aim to follow guidelines we have already written! If nothing exists however, this is something to bring up with your team! Engineers are also very useful for research, as they will be able to understand why something is the way it is, in a way that those who cannot read code will not be able to.
+|{{Role members|Role=engineer}}
+|-
+|[[Designer]]
+|Designers have a very important job, as they will be focusing now just on what looks nice, but also on what is safe and accessible. Designers can help with style guides for writing, icons, UIs, or whatever else really. The goal here is to be creative!
+|{{Role members|Role=designer}}
+|-
+|[[Tester]]
+|Testers should try to push the limits and find bugs and edge cases with the software we are working on and studying. Testers should try to also work with disabled people, to get a better understanding of what methods they use to interact with software, to test out different software using those methods.
+|{{Role members|Role=tester}}
+|-
+|[[Outreach]]
+|This is for the bigger picture stuff. Whether it's managing social accounts, putting up posters, or whatever else, the goal is to get people involved, or at the very least, make people aware of our guides. Our goal is to help people, and we cannot help them if they do not know about us!
+|{{Role members|Role=outreach}}
+|}