forked from anitab-org/anitab-org.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "Merge branch 'master' into develop"
- Loading branch information
Showing
33 changed files
with
1,164 additions
and
147 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,23 @@ | ||
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files. | ||
|
||
# dependencies | ||
/node_modules | ||
/.pnp | ||
.pnp.js | ||
|
||
# testing | ||
/coverage | ||
|
||
# production | ||
/build | ||
|
||
# misc | ||
.DS_Store | ||
.env.local | ||
.env.development.local | ||
.env.test.local | ||
.env.production.local | ||
|
||
npm-debug.log* | ||
yarn-debug.log* | ||
yarn-error.log* |
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 @@ | ||
# anitab-org.github.io |
This file was deleted.
Oops, something went wrong.
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,83 @@ | ||
# Code of Conduct | ||
|
||
## 1. Purpose | ||
|
||
A primary goal of AnitaB.org Open Source is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof). | ||
|
||
This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior. | ||
|
||
We invite all those who participate in open source contributions to help us create safe and positive experiences for everyone. | ||
|
||
## 2. Open Source Citizenship | ||
|
||
A supplemental goal of this Code of Conduct is to increase open source citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community. | ||
|
||
Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society. | ||
|
||
If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know. | ||
|
||
## 3. Expected Behavior | ||
|
||
The following behaviors are expected and requested of all community members: | ||
|
||
* Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community. | ||
* Exercise consideration and respect in your speech and actions. | ||
* Attempt collaboration before conflict. | ||
* Refrain from demeaning, discriminatory, or harassing behavior and speech. | ||
* Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential. | ||
* Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations. | ||
|
||
## 4. Unacceptable Behavior | ||
|
||
The following behaviors are considered harassment and are unacceptable within our community: | ||
|
||
* Violence, threats of violence or violent language directed against another person. | ||
* Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language. | ||
* Posting or displaying sexually explicit or violent material. | ||
* Posting or threatening to post other people’s personally identifying information ("doxing"). | ||
* Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability. | ||
* Inappropriate photography or recording. | ||
* Inappropriate physical contact. You should have someone’s consent before touching them. | ||
* Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances. | ||
* Deliberate intimidation, stalking or following (online or in person). | ||
* Advocating for, or encouraging, any of the above behavior. | ||
* Sustained disruption of community events, including talks and presentations. | ||
|
||
## 5. Consequences of Unacceptable Behavior | ||
|
||
Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated. | ||
|
||
Anyone asked to stop unacceptable behavior is expected to comply immediately. | ||
|
||
If a community member engages in unacceptable behavior, the community admins may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event). | ||
|
||
## 6. Reporting Guidelines | ||
If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community admin as soon as possible by emailing [email protected]. Please read [Reporting Guidelines](reporting_guidelines.md) for details. | ||
|
||
|
||
|
||
Additionally, community admins are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, community admins (or event managers) will also provide escorts as desired by the person experiencing distress. | ||
|
||
## 7. Addressing Grievances | ||
|
||
Only permanent resolutions (such as bans) may be appealed. To appeal a decision of the working group, contact AnitaB.org staff at [email protected] with your appeal and we will review the case. | ||
|
||
|
||
## 8. Scope | ||
|
||
We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues–online and in-person–as well as in all one-on-one communications pertaining to community business. | ||
|
||
This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members. | ||
|
||
## 9. Contact info | ||
|
||
[email protected] | ||
|
||
## 10. License and attribution | ||
|
||
This Code of Conduct is distributed under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/). | ||
|
||
Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy). | ||
|
||
Retrieved on November 22, 2016 from [http://citizencodeofconduct.org/](http://citizencodeofconduct.org/) | ||
|
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
File renamed without changes.
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,43 @@ | ||
<!DOCTYPE html> | ||
<html lang="en"> | ||
<head> | ||
<meta charset="utf-8" /> | ||
<link rel="icon" href="%PUBLIC_URL%/favicon.ico" /> | ||
<meta name="viewport" content="width=device-width, initial-scale=1" /> | ||
<meta name="theme-color" content="#000000" /> | ||
<meta | ||
name="description" | ||
content="Web site created using create-react-app" | ||
/> | ||
<link rel="apple-touch-icon" href="%PUBLIC_URL%/logo192.png" /> | ||
<!-- | ||
manifest.json provides metadata used when your web app is installed on a | ||
user's mobile device or desktop. See https://developers.google.com/web/fundamentals/web-app-manifest/ | ||
--> | ||
<link rel="manifest" href="%PUBLIC_URL%/manifest.json" /> | ||
<!-- | ||
Notice the use of %PUBLIC_URL% in the tags above. | ||
It will be replaced with the URL of the `public` folder during the build. | ||
Only files inside the `public` folder can be referenced from the HTML. | ||
Unlike "/favicon.ico" or "favicon.ico", "%PUBLIC_URL%/favicon.ico" will | ||
work correctly both with client-side routing and a non-root public URL. | ||
Learn how to configure a non-root public URL by running `npm run build`. | ||
--> | ||
<title>React App</title> | ||
</head> | ||
<body> | ||
<noscript>You need to enable JavaScript to run this app.</noscript> | ||
<div id="root"></div> | ||
<!-- | ||
This HTML file is a template. | ||
If you open it directly in the browser, you will see an empty page. | ||
You can add webfonts, meta tags, or analytics to this file. | ||
The build step will place the bundled scripts into the <body> tag. | ||
To begin the development, run `npm start` or `yarn start`. | ||
To create a production bundle, use `npm run build` or `yarn build`. | ||
--> | ||
</body> | ||
</html> |
File renamed without changes
File renamed without changes
File renamed without changes.
File renamed without changes.
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,54 @@ | ||
# Reporting Guidelines | ||
|
||
If you believe someone is violating the code of conduct we ask that you report it to the community admins by emailing [email protected]. | ||
|
||
**All reports will be kept confidential**. In some cases we may determine that a public statement will need to be made. If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise. | ||
|
||
If you believe anyone is in physical danger, please notify appropriate emergency services first. If you are unsure what service or agency is appropriate to contact, include this in your report and we will attempt to notify them. | ||
|
||
In your report please include: | ||
|
||
* Your contact info for follow-up contact. | ||
* Names (legal, nicknames, or pseudonyms) of any individuals involved. | ||
* If there were other witnesses besides you, please try to include them as well. | ||
* When and where the incident occurred. Please be as specific as possible. | ||
* Your account of what occurred. | ||
* If there is a publicly available record (e.g. a mailing list archive or a public IRC logger) please include a link. | ||
* Any extra context you believe existed for the incident. | ||
* If you believe this incident is ongoing. | ||
* Any other information you believe we should have. | ||
|
||
|
||
|
||
## What happens after you file a report? | ||
|
||
You will receive an email from the AnitaB.org Open Source's Code of Conduct response team acknowledging receipt as soon as possible, but within 48 hours. | ||
|
||
The working group will immediately meet to review the incident and determine: | ||
|
||
* What happened. | ||
* Whether this event constitutes a code of conduct violation. | ||
* What kind of response is appropriate. | ||
|
||
If this is determined to be an ongoing incident or a threat to physical safety, the team's immediate priority will be to protect everyone involved. This means we may delay an "official" response until we believe that the situation has ended and that everyone is physically safe. | ||
|
||
Once the team has a complete account of the events they will make a decision as to how to respond. Responses may include: | ||
|
||
Nothing (if we determine no code of conduct violation occurred). | ||
* A private reprimand from the Code of Conduct response team to the individual(s) involved. | ||
* A public reprimand. | ||
* An imposed vacation (i.e. asking someone to "take a week off" from a mailing list or IRC). | ||
* A permanent or temporary ban from some or all of AnitaB.org spaces (events, meetings, mailing lists, IRC, etc.) | ||
* A request to engage in mediation and/or an accountability plan. | ||
We'll respond within one week to the person who filed the report with either a resolution or an explanation of why the situation is not yet resolved. | ||
|
||
Once we've determined our final action, we'll contact the original reporter to let them know what action (if any) we'll be taking. We'll take into account feedback from the reporter on the appropriateness of our response, but our response will be determined by what will be best for community safety. | ||
|
||
Finally, the response team will make a report on the situation to the AnitaB.org's Open Source Board. The board may choose to issue a public report of the incident or take additional actions. | ||
|
||
|
||
|
||
## Appealing the response | ||
|
||
Only permanent resolutions (such as bans) may be appealed. To appeal a decision of the working group, contact the community admins at [email protected] with your appeal and we will review the case. | ||
|
This file was deleted.
Oops, something went wrong.
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,15 @@ | ||
import React from 'react'; | ||
import { View } from 'react-native'; | ||
import Header from './Components/Header'; | ||
import Content from './Components/Content'; | ||
|
||
function App() { | ||
return ( | ||
<View style={{ flex: 1, alignItems: 'center' }}> | ||
<Header /> | ||
<Content /> | ||
</View> | ||
); | ||
} | ||
|
||
export default App; |
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,9 @@ | ||
import React from 'react'; | ||
import { render } from '@testing-library/react'; | ||
import App from './App'; | ||
|
||
test('renders learn react link', () => { | ||
const { getByText } = render(<App />); | ||
const linkElement = getByText(/learn react/i); | ||
expect(linkElement).toBeInTheDocument(); | ||
}); |
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,19 @@ | ||
import React from 'react'; | ||
import { View, Text } from 'react-native'; | ||
|
||
function Content() { | ||
return ( | ||
<View | ||
style={{ | ||
width: 800, | ||
height: 600, | ||
alignItems: 'center', | ||
paddingTop: 40, | ||
}} | ||
> | ||
<Text>UNDER CONSTRUCTION</Text> | ||
</View> | ||
); | ||
} | ||
|
||
export default Content; |
Oops, something went wrong.