calebjpicker / tgame Goto Github PK

• 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

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

1. We can use the wikis on this

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

Identify a list of games that are friendly to newcomers.

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

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

Add deadlines where necessary or feasible.

Logo
Facilitation meetings

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).

Fill out RSO Application and then file it.

Use this website to convert:

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

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

• 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.

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.

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.

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

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.

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

• 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

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

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

June 28, 2019 at 4pm

Agenda

Constitution/Bylaws
Advisor role
Kevin's Recommendations

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

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

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

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.

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

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

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.

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

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.

Select 3 actively enrolled students to hold officer positions.

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

June 24, 2019

Write detailed descriptions for each project.

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 up meeting between Sal, Rudy, and me and then use questions to ask Sal document to gain information about becoming an RSO.

Write detailed descriptions for each milestone.

Article IV Section II and Section III

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.

Becoming an RSO requires 5 actively enrolled UNLV students.

From Sal:

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

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)