Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Talk to Sal about becoming an RSO #1

Open
calebjpicker opened this issue May 29, 2019 · 4 comments
Open

Talk to Sal about becoming an RSO #1

calebjpicker opened this issue May 29, 2019 · 4 comments
Assignees
Labels
important Needed to achieve milestones TODO Tasks to get completed
Milestone

Comments

@calebjpicker
Copy link
Owner

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

@calebjpicker calebjpicker self-assigned this May 29, 2019
@calebjpicker calebjpicker added this to the Become an RSO milestone Jun 3, 2019
@calebjpicker calebjpicker added this to Needs orgnaization in RSO administration Jun 4, 2019
@calebjpicker
Copy link
Owner Author

calebjpicker commented Jun 4, 2019

Caleb: So what advice do you have for being successful in establishing an RSO?

Sal: Hey Caleb. Sorry for the late reply.

So first off, what is the purpose of your guys organization? Also, do you guys have an advisor?

Caleb: Hey Sal, no worries.

We are called TODA, which stands for Tabletop Organization for data Analysis. The primary purpose of TODA is to play tabletop games and maintain and generate interest in tabletop games. The secondary purpose will be to collect data on gameplay and present that to members with the idea of generating interest in and teaching about data analysis.

We do not have an advisor yet and we are looking for advice about how to get one. I think Kevin is your advisor right? Do you think he would be willing to be our Advisor too?

Sal: Interesting combination for a group. I like it!!🙂🙂

As for the advisor, I'm sure Kevin would be interested but you'll need to ask him about that.

Overall though, you guys are on a good track. Let's get things started overall though. The first steps in creating your new RSO will be the following:

-1. You will need to create a constitution for your organization that meets the requirements of a RSO.

  • You will need 5 registered student to meet the required total amount to get started.
    -TODA will also need a minimal of 3 positions(President, VP, & Treasurer) along with 2 reservation coordinators(can be done by any student you choose for it that includes the President and so on).
    -You will need an advisor

These are some of the starting things you'll need to do. A lot of this can be found at the involvement unlv website

@calebjpicker calebjpicker moved this from Needs Organization to High priority in RSO administration Jun 4, 2019
@calebjpicker calebjpicker moved this from High priority to Low priority in RSO administration Jun 4, 2019
@calebjpicker calebjpicker added the TODO Tasks to get completed label Jun 4, 2019
@calebjpicker
Copy link
Owner Author

Caleb

Hey Sal, thank you for the helpful information!

We reached out to Kevin and he seems interested in becoming an advisor. We will meet up with him in a couple of weeks to discuss more.

We have found the UNLV Involvement Website, and we are in the process of finalizing all those things you mentioned. Thanks again!
👍1
We also want to get your thoughts about your experiences in running Mario Party Wars. What factors do you think contribute to the success of Mario Party Wars?

Sal

Sounds like a plan. In terms of the success with Mario Party Wars at unlv. I'd be glad to give some insight.🙂🙂

So overall, the keys that I found to success as an RSO were the following:

-1. Your objectives: What is TODA's short and long term goals? This will be important specifically for communicating with students and your members why it's great to join the org and the benefits for getting involved. This will also play a role for any CSUN funds you try to acquire as you'll need to be able to present the benefits of what you ask back to what you do as TODA.

  1. Marketing: This is essential for success due to many factors that makes RSO success difficult at unlv. Whether it's informational(flyers, events, and so on), promotional(giveaways and such), or anything else, marketing plays a big role. This leads into a factor that coincides with this.

  2. Communication: One of the most essential factors for RSO's, communication is important not only to getting the word out around campus but also to your members. Many orgs at unlv that fail don't take this seriously so it's important you guys learn how you'll communicate as an RSO.

  3. Being active: As simple as this sounds, getting involved not as simple as it seems. In order to succeed as an RSO, you'll need to be engaged with your members and get involved outside of that. Whether it's events, seminars, or anything else, being involved is very important. This includes collaborative efforts. Unlv is pretty bad at getting orgs together but it benefits everyone. Not only does it help spread the word about your org but it can also provide new opportunities and help UNLV in the process.

These are the factors I recommend for success. There are others but most of the rest will be based on the direction you guys take with TODA.🙂🙂

You guys will also have our back during our final year at unlv. If you guys ever want to work with us or even get involved with some of our events, please feel free to reach to us.🙂🙂

@calebjpicker
Copy link
Owner Author

@MElemental Should we ask the other questions?

@calebjpicker
Copy link
Owner Author

calebjpicker commented Jun 6, 2019

Also, we should convert each of those bullet points to a separate issue and put them in the Becoming an RSO project.

!RemindMe tomorrow

@calebjpicker calebjpicker added the important Needed to achieve milestones label Jun 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
important Needed to achieve milestones TODO Tasks to get completed
Projects
RSO administration
  
Low priority
Development

No branches or pull requests

1 participant