├── .github
    └── ISSUE_TEMPLATE
    │   ├── 1.talk-submission.md
    │   ├── 2.talk-request.md
    │   └── 3.job-posting.md
├── CODE_OF_CONDUCT.md
└── README.md


/.github/ISSUE_TEMPLATE/1.talk-submission.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | name: 1. Volunteer your Talk
 3 | about: Talk submission and call for early feedback.
 4 | title: "<Topic Description>"
 5 | labels: talk volunteered
 6 | assignees: ''
 7 | 
 8 | ---
 9 | 
10 | ## Summary of talk
11 | 
12 | <!-- Describe you talk, and maybe how it came about -->
13 | 
14 | ## Details
15 | 
16 | **Title of the Talk**  
17 | <!-- Fill me in! I'll be used for posts on Meetup and Twitter -->
18 | 
19 | **Description of the Talk**  
20 | <!-- I'll also be used for posts on Meetup (and maybe Twitter if it can be fit) - try to make me "conversational"! -->
21 | 
22 | **My Info**  
23 | <!-- Give us your Twitter handle if you have one! -->
24 | 


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/2.talk-request.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | name: 2. Idea for a Talk
 3 | about: Not ready to present, but have an idea?
 4 | title: "<Topic Description>"
 5 | labels: talk request
 6 | assignees: ''
 7 | 
 8 | ---
 9 | 
10 | ## Summary of talk
11 | 
12 | <!-- Describe the talk, and maybe why you'd like to see it presented. -->
13 | 


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/3.job-posting.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | name: 3. Job Posting
 3 | about: Got a position open at your company?
 4 | title: "<Position> at <Company>"
 5 | labels: job offer
 6 | assignees: ''
 7 | 
 8 | ---
 9 | 
10 | <!-- Rules for posting! -->
11 | <!-- 1. We allow direct posting only! No proxying through recruitment folks. -->
12 | <!-- 2. Mention if the position is part or full time. -->
13 | <!-- 3. Put contact details in there (an email address is good). -->
14 | <!-- 4. Include a timeframe for the hiring. It's also helpful for us, because we need to tear the posting down at some point! -->
15 | 
16 | <!-- Example of a well formatted job posting: -->
17 | <!-- https://github.com/reactbris/meetup/issues/47 -->
18 | 


--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
 1 | # Code of Conduct
 2 | 
 3 | > _Last updated 7 April 2019_
 4 | 
 5 | We strive to make ReactBris a safe and welcoming environment for everyone. Our events are a reflection of the diversity found within the Brisbane tech community; it’s this diversity that makes the community so awesome.
 6 | 
 7 | To maintain this warm and friendly environment, we ask that all attendees and community members comply with our Code of Conduct.
 8 | 
 9 | ## The Code
10 | 
11 | 1. Harassment of any kind is not tolerated, either in-person at our events or on the various ReactBris social media pages. This includes:
12 |    1. Discrimination based on (but not limited to) age, sex, gender, race, disability, physical characteristics, religious or political beliefs
13 |    1. Inappropriate or unwelcome physical contact, including unwanted sexual attention
14 |    1. Disruptive or aggressive behaviour
15 | 1. Attendees are asked to drink responsibly at any ReactBris event where there is alcohol available.
16 | 1. Some ReactBris events may have an official photographer taking photos. If you are attending and don’t want to be included in any photos, please let the photographer know in-person.
17 | 
18 | ## Reporting a violation
19 | 
20 | If you are being harassed, see others being harassed, or just have some questions or feedback regarding the Code of Conduct, don’t hesitate to reach out to an organiser at any time. You can usually speak to an organiser in-person at an event, but you can also reach us online:
21 | 
22 | Thomas McCarthy - tom@reactbris.org - [@iamtommcc](https://twitter.com/iamtomcc)  
23 | Lochlan Bunn - lochlan@reactbris.org - [@loklaan](https://twitter.com/loklaan)
24 | 
25 | Reported violations are taken extremely seriously, and are followed up immediately once a report is received.
26 | 
27 | ## Enforcement
28 | 
29 | Attendees who are asked by an organiser to stop any harassing or disruptive behaviour are expected to comply immediately.
30 | 
31 | Serious or reported violations may result in attendees being asked to leave, and these attendees may be barred from attending future events.
32 | 
33 | Posts on the ReactBris Meetup page or ReactBris Github which violate the Code of Conduct may be deleted.
34 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
 1 | <p align="center">
 2 |   <img alt="reactbris logo" width="300px" src="https://raw.githack.com/reactbris/site/master/static/logo.png" />
 3 | </p>
 4 | 
 5 | <p align="center">
 6 |   <strong>Meetup Planning :calendar:</strong>
 7 | </p>
 8 | 
 9 | 
10 | <p align="center">
11 |   Want to give a talk? Or maybe you have a talk in mind that someone else could present?<br />:sparkles: Open a <a title="Create a github issue" href="https://github.com/reactbris/meetup/issues/new/choose">new github issue</a> to get started. :sparkles:
12 | </p>
13 | 
14 | ## :rainbow_flag: Community Participation
15 | 
16 | The meetup is run by folk in the community, so please feel encouraged to jump in on any talk [submissions](https://github.com/reactbris/meetup/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22talk+volunteered%22) or [requests](https://github.com/reactbris/meetup/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22talk+request%22) that you think you can add value to :pray:.
17 | 
18 | ## :mailbox_with_mail: Job Postings
19 | 
20 | We're happy to help the industry grow, so if you're from a company that has a position opening _related to React_, then feel welcome to [create a posting](https://github.com/reactbris/meetup/issues/new/choose). Organisers will highlight the posting during future meetup events.
21 | 
22 | <details>
23 |   <summary><a href="https://github.com/reactbris/meetup/labels/job%20offer">Current Job Postings</a></summary>
24 | </details>
25 | <details>
26 |   <summary><em>Guide for Job Posters</em></summary>
27 | 
28 | <br>
29 | 
30 | > ReactBris **does** accomodate **transparent job postings**. :thumbsup:  
31 | > ReactBris **doesn't** accomodate **opaque or vague recruitment**. :thumbsdown:
32 | 
33 | ## :gem: "Transparent" Job Postings
34 | 
35 | **Disclose** the organisation name behind the job.
36 | 
37 | ### Examples
38 | 
39 | #### Good :thumbsup:: Deliberate company name disclosure and job details
40 | 
41 | _These are provided as examples, they're pretty sweet, but we aren't attributed to the companies :)._
42 | 
43 | * [Front End Developer at ABC News](https://github.com/BrisJS/meetups/issues/267)
44 | * [Senior Software Engineer at Stacktrace](https://github.com/BrisJS/meetups/issues/269)
45 | 
46 | #### No good :no_entry_sign:: "Opaque" or "vague" recruitment messages
47 | 
48 | _These show a distinct disconnect from the community, which we're not about :)._
49 | 
50 | > "Hey all, I am looking for a frontend developer with react experience. Kindly check ( recruit.biz/developer-catch-all ) for more details."
51 | 
52 | > "Hey Peeps,Full Stack role available. Stack Laravel/React. Min 3 years commercial exp with PHP. email smith@recruit.biz thanks"
53 | 
54 | ## 📖 Where to post?
55 | 
56 | On our `reactbris/meetups` github repo, as new Issues!
57 | 
58 | Choose the "[Job Posting](https://github.com/reactbris/meetup/issues/new/choose)" option from our [Issue Templates](https://github.com/reactbris/meetup/issues/new/choose).
59 | 
60 | ## 😬 Expectations on Meetup.com
61 | 
62 | No job posting in the Discussions section of Meetup.com! This is a community-stuff only section.
63 | 
64 | The meetup organisers **will** take down job ads from Discussions. 👈
65 | 
66 | </details>
67 | 


--------------------------------------------------------------------------------