Main meeting times can be seen in our events channel under "Server Info".

Game Design meetings happen when, during a main meeting, the person leading the meeting tells everyone to split off into their team's respective channel.

We keep a list of active members on the Member Management Trello board (accessed through this Trello card). During a meeting, find Design Team members on this board that are not present, and tag several of them in the Work [Rules] chat when asked.
If you have not made a member card yet, do so using the template under "HOW TO USE".

Attending meetings frequently is the best way to learn about what we do here. Your interviewer can also answer your questions.

It is important for you to complete our online courses "New Volunteer Onboarding Course" and "Design Team Onboarding Course". Both are found here: https://www.p1vc.org/academy

Visit our GDD here: https://bfe5d24f-161e-423e-883c-d8c02e3b6648.mynotice.io

You can also play a build of the game by signing up for playtesting and then visiting our itch.io page.

While the \review command is recommended, it is NOT necessary for your join exam. Simply move your Trello card to "Ready for Review/Testing" under the orange "DESIGN" header, and it WILL be reviewed during the next Primary Time scrum meeting. See this video for more details.

As Trust will be important later on, you can learn more about it on this Trello card.

Contact your interviewer about your next steps and apprenticeship. If they are unresponsive, say something during the next Design Team scrum meeting (especially when asked if you have blockers).

In the meantime, the latter half of this video covers this topic. Watch it!

This card thoroughly covers the topic from the perspective of the interviewer.

To summarize:

• You may now take on any task for the Design Team.
• You must complete AT LEAST 3 tasks (any) + 1 "service" task (ONLY recruiter counts). You do NOT need all 4 tasks assigned at once. It is recommended to find one or two tasks to do at a time.
• You will track your "apprenticeship deadline" privately.
• When your deadline arrives and you have completed the 4 tasks necessary, you will stand for election. Again, ask your interviewer or an elected member for guidance, and refer to this card.

Most likely.

Generally speaking, if you have experienced someone doing that role, you may take on that role. Examples: If you have been interviewed, you may interview. If you have attended a scrum meeting, you may volunteer to be scrum master.
This is a safe place to fail and learn, so volunteer!

During a Design Team scrum meeting, everyone will be asked "the 3 questions", which are essentially: "What'd you do yesterday?", "What are you doing today?", "Any blockers?". This is when you will make clear that you need a new task assigned to you.

If you are just starting your apprenticeship, it is helpful to say that you are, and which join exam you completed.

Otherwise, ask if you can take on any tasks in the "TO DO" column.

WAIT! If you have NOT completed our Miro documentation tutorial yet, do so before accessing our Miro boards! >> https://trello.com/c/YXXSuW8T

We keep track of finalize Jelly and Biome designs here:

This location is subject to change. Notify the team to have this updated.

WAIT! If you have NOT completed our Miro documentation tutorial yet, do so before accessing our Miro boards! >> https://trello.com/c/YXXSuW8T

Jelly Abilities:

Jelly Interactions:

This location is subject to change. Notify the team to have this update.

Learn more about our systems and responsibilities here: https://585e70ef-ad87-47f0-9f4a-5bec64bcda3b.mynotice.io/

As Game Designers, our principle role is to plan out the game and guide other teams in the game's creation.

For Design Team decisions, check under "SENSITIVE ISSUES" and "RETHINKING" on our Design idea progression board

For major updates regarding our organization, check our YouTube channel P1 Academy

Using our \review bot command creates a "ticket" that can be verified by team members in our "white discord", a server that only apprentices and elected members can access. These tickets help ensure that task are reviewed properly, create a paper trail, and award trust to the verifiers.

If you use the \review command (can be done anywhere on our main server) and have white discord access, be sure to include a link to the ticket by finding it in the reviews channel, click the 3 dots on the corner of the message (similar to adding a reaction) and click "Copy Message Link", and paste the link as a comment on your Trello task card. Also consider reviewing someone else's task.

If you would like to verify a review ticket, ensure that there are no verifiers yet, that the task card is under "WALL OF FAME", AND that there is a comment on the task card from a team member stating that the work fulfills the Acceptance Criteria. Then, you may select the blue "Review" button and answer the bot's questions at the bottom of the channel.

Our current sprint's goals are kept on the Action Trello under the "SPRINT GOALS" list/column.

You can see our current milestone (long-term goal) under the "MILESTONES" column. Note: unlike other teams, our milestones involve creating the milestones, and sagas that the other teams follow.

Learn how to use our "Milestone Production Storyboards" Miro here (This video also discusses creating new Trello cards!):

Access to the Biome Asset List can be found here: https://trello.com/c/BBDivjNV