calebjpicker/tgame

Tabletop Gaming: Assorted and Malleable Experiences (TGAME) Official Repository

TGAME

Tabletop Gaming: Assorted and Malleable Experiences Official Repository

Contact: [email protected]

Why organize?

Players are at the very core of tabletop games. At a minimum, playing tabletop games requires finding space and time to play and ensuring that players have something to do. This ensures that players can interact with each other in a comfortable setting, whether that means interacting with new people, discussing new board game ideas, or just having a comfortable space to meet with old friends. Meeting these essential functions on an ongoing basis requires establishing an organizational structure and a way to gather necessary resources.

As more and more players gather to play, the social interactions also provide unique opportunities for players to collaborate, to teach and learn from each other, to create their own experiences, and to design and test new board games. Up until now, there has been no effective way to house, support, and develop player’s various interests. Establishing an organization is therefore necessary to meet ongoing essential functions of playing tabletop games together as well as support those who want to collaborate and turn their ideas into something more tangible. Whatever the reason, establishing an organization provides a way to support each player’s various interests.

Why GitHub?

The purpose of this GitHub repository is to host all the files required for establishing, maintaining, and working on the organization. GitHub is a collaborative tool that allows multiple users to interact with, share, discuss, and modify files, important documents, and ideas.

Typically, GitHub is used to host complex computer code projects that have many moving parts and people.

GitHub is the most transparent way to track all moving parts, with all considerations from all users and to best integrate them into the documentation.

Getting Started on Providing Feedback (and Choosing Your Level of Involvement)

You have two options to get started:

Suggestion Box

You can submit a response in the suggestion box. Anyone may use the suggestion box anonymously, so please provide your sincere feedback!

After submission, we will make an issue with the request so that the issue can be tracked publicly.

Suggestion Box

Submitting Issues

Issues are the primary way that requests, concerns, enhancements, and suggestions are handled.

To get started, create an account and open an issue in this repository. To open an issue:

1. Click the ’Issues’ tab.
2. Click the green button labeled ‘New Issue’.
3. Type a detailed title.
4. Type a detailed description.
5. Click ‘Submit new issue’.

Either you or we will add additional labels to categorize the issue. Then anyone can comment and discuss the issue, and the entire discussion thread is publicly visible.

Doing More

Forks and Pull Requests

If you want to directly contribute to documentation, you can ‘fork’ this repository. A fork refers to copying this repository to your account. You make a copy, then you are free to make any changes you want. Eventually you can make a ‘pull request’ so that those changes can be reviewed. Like issues, anyone can comment and discuss the pull request and finalize it.

To fork the repository:

1. On the repository page, click the button in the upper-right hand corner that says, ‘fork’. GitHub will copy the repo to your account.
2. Create or edit files as you’d like.
3. Make a pull request by clicking ‘New pull request’.
4. Fill out the title and description, like issues.
5. Click ‘Create pull request’.

The community will then review and discuss.

Projects

Projects are used as a way to organize and implement large functions of the organization. Tasks, issues, and pull requests are organized within projects.

If you would like to get involved and manage one or more projects, please contact Rudy or Caleb.

tgame's Issues

Create list of games for newcomers

Identify a list of games that are friendly to newcomers.

Convert .docx of Constitution to LateX

Use this website to convert:

https://www.docx2latex.com/docx2latex_free/

Fill in missing sections of Bylaws

There are many missing Bylaw sections that we need to fill in.

Do we want to make this repo public

Decide whether we want to make this a public repo.
Pro:

1. We can use the wikis on this

Possible directions

Becoming a non-profit as an RSO:

Open a US Bank account as a UNLV student organization: https://www.unlv.edu/sia/student-orgs/finances-insurance/opening-bank

IRS information for applying for non-profit exemption (likely under the social club status): https://www.irs.gov/charities-non-profits/application-for-recognition-of-exemption

Set a meeting time with Kevin to establish an RSO

Send Kevin an e-mail or message asking for his availability to meet with Caleb and Rudy.

We will have to systematically go through the constitution. We should not edit sections until the previous section gets checked off.

• Preamble

• Article I

• Article II

• Article III

• Section I

• Section II

• Article IV

• Section I

• Section II

• Section III

• Article V

• Section I

• Section II

• Article VI

• Section I

• Section II

Action Items and Meeting Minutes for June 24 2019

June 24, 2019

Define 5 actively enrolled students and then confirm

Becoming an RSO requires 5 actively enrolled UNLV students.

Create issues to achieve each milestone and label them accordingly

Add deadlines where necessary or feasible.

Meet with Kevin and go over the Agenda

June 28, 2019 at 4pm

Agenda

Constitution/Bylaws
Advisor role
Kevin's Recommendations

I think we should somehow involve the group in the process.

Ian and Ed told me the group doesn't necessarily want to deal with data analysis, but they are interested in designing board games and having discussions about that.

I think we can actually create a parallel structure with the new Clark County School District standards for Engineering Design in Next Generation Science Standards to accomplish both of these goals.

https://drive.google.com/drive/folders/1vRdUr3iWercVJ-JkyFpTdTkXefG9iiuw

Create a survey to get people's feedback:

• what do board games mean to you?
• why do you come to the board game group?
• what do you want this club to be about?
• what do you get out of the club?
• how important is it to you to add new people to the club?

core concepts to probe:

• thoughts about change/adding new people

Define officer positions and assign actively enrolled students to those position

Select 3 actively enrolled students to hold officer positions.

Consider github repo websites

https://pages.github.com/
we could use github pages to make an accessible interface of this repository.

Fill out RSO Application

Fill out RSO Application and then file it.

Possible name change: Tabletop organization with Design, Data, and Adventure

application and design are kind of redundant. Adventure would capture a broader set of interests, and put it at the same level as Data and Design. I think it would capture the sense of excitement, learning, and story.

Present survey data in open forum

Talk to Jordan about overseeing our setting up a server on Caleb's Synology NAS.

Jordan has a lot of knowledge. It'd be good to get his expertise in setting up and maintaining a git server.

Look in TODA Outline document and create projects from headers

Open the TODA Outline document, peruse headers, and use those headers to create new Projects.

Create, organize, and tidy the folder structure within the github repo

We just uploaded our Google Drive info. Now we have to think about how to best organize it. Then organize it.

Pick 2 members to become reservation coordinators

From Sal:

along with 2 reservation coordinators(can be done by any student you choose for it that includes the President and so on).

Select a Faculty/Staff Advisor of our RSO

Find out from Sal whether Kevin can become our faculy/staff advisor. If Kevin cannot or will not, then during the filling out of Intent to Organize form, we can have the system send out a request on the "We need an Advisor!" form (or we fill out this form ourselves).

Revise and finalize Constitution

I essentially filled out the rest of these sections. I will put these changes into a pull request that you can then review. Please commit any new changes to the pull request I create.

We may also need to give the Constitution another look through to make sure we still agree with everything and to ensure that all language is consistent throughout all sections.

Originally posted by @calebjpicker in #23 (comment)

code of conduct changes 1

Photography section should be included so people ask for permission before taking pics. We will have to remove photos at the request of people.

Trimm etiquette section, so that it allows for people to create their own experiences

Structure our purpose to partially parallel NGSS Engineering and Possibly other standards.

the engineering design section of NGSS, promotes ideas like failure-laden learning and iterative design. the NGSS also have a focus on educating you students about how engineering interacts with science and society.

We can create a CONTRIBUTING file for establishing contribution standards.

We have the option of creating a CONTRIBUTING.org file.

Talk to Sal about becoming an RSO

Set up a meeting with Sal and then use the questions to ask sal document to gather information about becoming an RSO.

Write list of all ongoing and planned projects

Write detailed descriptions for each project.

Graphics

Logo
Facilitation meetings

**Standardize Projects**

have a clear column in each project, with links to relevant documentation.

Analyze Survey data

we should analyze the survey data, put it into a presentable form, and based upon the conclusions we draw, come up with solutions for problems or ways to improve and so on.

Define and create milestones for each project

Write detailed descriptions for each milestone.

Convert all documents into plain text documents so we may track changes. (preferably .org)

• Constitution
• Bylaws
• Code of Conduct
• Meeting Notes
• Templates

Review and define philosophical pillars and Preamble of TODA

Tabletop Organization for Data, Design, and Application
Purpose of TODA—philosophical pillars that can be summarized in one word

Interdisciplinary and Collaborative. Every perspective has value through different analyses. And every analysis generates new value through collaboration. -- rudy, caleb

Growth Mindset. Knowledge and skills increase through passion and perseverance. -- rudy, caleb

Engage and Adapt. Involve and develop with the changing needs of the organization and the community.

Educate and Empower. Develop, demonstrate, and parallel new knowledge and skills to increase self-confidence.

Engage. Engage the community in how science and engineering principles.
Parallel. Break up false dichotomy between being technical and creative.
Educating.

Daring. Different. Diverse.
Structure.
Slogan
Design. Test. Play.
Learn.

Import copy of UNLV RSO Constitution and Bylaws to be used as templates

Use UNLV RSO constitution and bylaws as template and identify areas that we should modify with our previous constitution and bylaws.

Meet with Sal about becoming an RSO.

Set up meeting between Sal, Rudy, and me and then use questions to ask Sal document to gain information about becoming an RSO.

Create to-do list and import into github for establishing chatting platform and standards

Define the current problem regarding chatting and social media. Then create a plan to address that problem as well as an actionable to do list to execute that plan. Convert each item into a github issue under this issue's milestone.

Fill out missing sections of the constitution:

Article IV Section II and Section III

We need to organize:

• how we make modifications
• how come up with issues
• how we assign tasks
• the interface we use for workflow
• how we assign people to milestones or modules
• how we upload files
• how often we go through github and organize it.

Ask Kevin about whether he would be our RSO advisor

Sal said Kevin might be willing to be our advisor, however, he said to ask Kevin. So that's what we will do.

Communicate with Faculty/Staff Advisor to Confirm Position

UNLV will send an e-mail to the faculty/staff advisor within 1-2 days of completing the Intent to Organize form. The faculty/staff advisor must complete registration. Mark this done when complete.

we can create issue templates

We should use these when we want to have issues stated in a formatted manner

Action Items and Meeting Minutes for June 17 2019

Scheduled Meeting

June 17, 2019 at 4:30 PM

Agenda

-[ ] Discuss how to best present results to the group.

-[ ] Discuss and finalize work on preamble.

-[ ] Plan meeting space, date and time, and structure for Open Forum. Message that to the group.

-[ ] Review outstanding issues and triage as necessary.

-[ ] Determine most important and urgent Projects. Then create milestones for those projects. Then create issues to reach those milestones.

-[ ] Determine next meeting date and time, and agenda.

-[ ] Assign or work on remaining sections of the constitution.

Please click below to view the meeting minutes:

Meeting Minutes.