-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
11 changed files
with
1,642 additions
and
89 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
node_modules | ||
dist |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
{ | ||
"root": true, | ||
"parser": "@typescript-eslint/parser", | ||
"plugins": [ | ||
"@typescript-eslint" | ||
], | ||
"extends": [ | ||
"eslint:recommended", | ||
"plugin:@typescript-eslint/eslint-recommended", | ||
"plugin:@typescript-eslint/recommended" | ||
] | ||
} |
Validating CODEOWNERS rules …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
# This is an example of a code owners file | ||
# lines starting with a `#` will be ignored. | ||
# https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners | ||
|
||
# We can specify a default global match using wildcards: | ||
* @RentDynamics/qa | ||
|
||
# Code Owners section: | ||
# changes to redux | ||
store/ @chase2981 | ||
reducers/ @chase2981 | ||
|
||
# changes to deploy | ||
deploy/ @levicus @chase2981 | ||
.circleci/ @levicus @chase2981 | ||
|
||
# changes to actual codeowners file | ||
CODEOWNERS @chase2981 @RentDynamics/qa @levicus |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,175 @@ | ||
https://github.com/chase2981/angular-styleguide/tree/master/a2 | ||
|
||
|
||
Constitution of Google@Berkeley | ||
Student Organization Name: Google@Berkeley | ||
Date Prepared: August 30, 2015 | ||
Date Amended: | ||
Date Approved (LEAD Center staff): | ||
Approved by (LEAD Center staff): | ||
|
||
|
||
Article I - Name | ||
The name of this student organization shall be Google@Berkeley. | ||
|
||
|
||
Article II - Purpose | ||
The purpose of this organization shall be: | ||
• To unite students who are passionate about technology, leadership, and innovation on | ||
UC Berkeley campus | ||
|
||
|
||
• To promote and organizes activities to educate the students and staff about technology, | ||
innovation and Google products | ||
|
||
|
||
• To provide personal and professional development for its members | ||
|
||
|
||
Article III - Membership | ||
|
||
|
||
Membership is open to any student, faculty, or staff who are interested in technology and/or | ||
Google. Only currently registered students, faculty, and staff may be active members in a | ||
registered student organization. Only active members may vote or hold office. | ||
|
||
|
||
|
||
|
||
Article IV - Officers & Elections | ||
|
||
|
||
Google@Berkeley Executive Board shall consist of the President and the Vice President. | ||
|
||
|
||
The Executive(s) may create committees and positions within committees if deemed necessary. All committees will be appointed by the President. A member may be appointed to more than one committee. Each Chair will call meetings of their own committee meetings as necessary, and report to the rest of the Executive Board. | ||
|
||
|
||
General Responsibilities | ||
|
||
|
||
• Promote and raise awareness about Google – the company, the culture, the products, | ||
the service | ||
|
||
|
||
• Attend all executive board meetings unless under special circumstances (must clear | ||
within 24 hours in advance) | ||
|
||
|
||
• Table and chalk as needed | ||
|
||
|
||
• Attend and assist with large-scale and small scale activities and educational events | ||
|
||
|
||
• Assist other board members during times of need | ||
|
||
|
||
The President | ||
• Act as the primary spokesman, the chief executive, and the primary signatory of | ||
Google@Berkeley | ||
|
||
|
||
• Provide the overall vision and sense of direction for the organization | ||
|
||
|
||
• Call, organize, and preside over general club meetings, club elections, and Executive | ||
Board meetings | ||
|
||
|
||
• Supervise/oversee the work of the other officers and ensures that they function | ||
together as an effective team | ||
|
||
|
||
• Act as a parliamentarian in the event of constitutional questions, in accordance with | ||
Robert’s Rules of Order | ||
|
||
|
||
The Vice President of External Affairs | ||
• Serve as the primary ASUC liaison for Google@Berkeley | ||
|
||
|
||
• Collaborate with the President to attain approval for club events and meetings | ||
|
||
|
||
• Promote the Google@Berkeley organization to campus, including overseeing tabling on | ||
Sproul and chalking when necessary | ||
|
||
|
||
• Assist in marketing the large-scale events, activities, and educational workshops | ||
|
||
|
||
• Collaborate with the Vice President of Internal Affairs to designate a budget for events | ||
The Vice President of Internal Affairs | ||
|
||
|
||
• Coordinate the work between the different committees to ensure the overall | ||
organization functions smoothly | ||
|
||
|
||
• Take notes during meetings and write the monthly newsletter | ||
|
||
|
||
• Maintain the organization’s online presence via Facebook, Google Plus, and other | ||
Channels | ||
|
||
|
||
• Collaborate with the Vice President of External Affairs to designate a budget for events | ||
The Hack-a-thon/Large-Scale Event Chair | ||
|
||
|
||
• Host a large-scale event each semester | ||
|
||
|
||
• Appoint a committee of individuals that will assist in planning said large-scale event | ||
|
||
|
||
• Look for supplemental funding and donations for said large-scale event | ||
|
||
|
||
• Work with the Activities Chair to ensure that Google@Berkeley will not have conflicting | ||
Events | ||
|
||
|
||
|
||
|
||
The application process shall begin in early September. The President shall appoint all other | ||
members of the executive board. | ||
The term of office shall be from August 1 to July 31 of next year. Elected officers and committee | ||
chairs or assistants may be impeached and removed from office for failure to perform their | ||
constitutional duties such as failure to comply with the regulations of the University of | ||
California at Berkeley. | ||
|
||
|
||
Article V - Meetings | ||
General meetings are to be held at a reasonable time and location once per year. Officer | ||
meetings are to be held at reasonable times and locations twice per year. The President is | ||
responsible for calling meetings. | ||
|
||
|
||
At least fifty percent quorum is needed to establish laws. | ||
|
||
|
||
Two-thirds vote is required to amend them. | ||
|
||
|
||
Article VI - Constitutional Amendments | ||
|
||
|
||
Any voting member can propose an amendment. Amendments to the Constitution require a | ||
fifty per cent quorum and a 2/3 vote to be passed. Nevertheless, the president reserves the | ||
ability to veto any approved amendments. | ||
Google@Berkeley can establish by-laws. At least fifty per cent quorum is needed to establish by | ||
laws. Two-thirds vote is required to amend them. Any changes in either the Constitution or the | ||
by-laws will be reported to {CompanyName} CTO by the President. | ||
|
||
|
||
All amendments, additions or deletions to this document must be filed with the LEAD Center in | ||
102 Hearst Gym. | ||
|
||
|
||
Article VII - Dissolution | ||
|
||
|
||
Dissolution will be decided if 90% of the group members vote to dissolve. Dissolution will also | ||
take place in case of low membership or merging with another more powerful organization. |
Oops, something went wrong.