Skip to content

Commit

Permalink
feat(all): initial oss release
Browse files Browse the repository at this point in the history
  • Loading branch information
PixnBits authored and 10xLaCroixDrinker committed Nov 22, 2019
1 parent 31e956e commit 339c694
Show file tree
Hide file tree
Showing 40 changed files with 16,698 additions and 1 deletion.
9 changes: 9 additions & 0 deletions .babelrc
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
{
"presets": [
["env", {
"targets": {
"node": "4.4.1"
}
}]
]
}
18 changes: 18 additions & 0 deletions .editorconfig
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# http://editorconfig.org
root = true

[*]
charset = utf-8
indent_style = space
indent_size = 2
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true
max_line_length = 100

[*.md]
max_line_length = 0
trim_trailing_whitespace = false

[COMMIT_EDITMSG]
max_line_length = 80
13 changes: 13 additions & 0 deletions .eslintignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# node & npm
node_modules
*.log
lib

# test
test-results

# OS
.DS_Store

# IDE
.idea
1 change: 1 addition & 0 deletions .eslintrc.json
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{ "extends": "amex" }
38 changes: 38 additions & 0 deletions .github/ISSUE_TEMPLATE/bug-report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
---
name: Bug report
about: Create a bug report for amex-lumberjack
---

# 🐞 Bug Report

## Describe the bug

A clear and concise description of what the bug is.

## To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

## Expected behavior

A clear and concise description of what you expected to happen.

## Screenshots

If applicable, add screenshots to help explain your problem.

## System information

- OS: [e.g. macOS, Windows]
- Browser (if applies) [e.g. chrome, safari]
- Version of amex-lumberjack: [e.g. 5.0.0]
- Node version:[e.g 10.15.1]

## Additional context

Add any other context about the problem here.
26 changes: 26 additions & 0 deletions .github/ISSUE_TEMPLATE/feature-request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
name: Feature request
about: Create a feature request for amex-lumberjack
---

# 💡 Feature request

## Is your feature request related to a problem? Please describe

A clear and concise description of what you want and what your use case is.

## Example

Please include a basic code example of the new feature. Skip this section if not applicable.

## Describe the solution you'd like

A clear and concise description of what you want to happen.

## Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

## Additional context

Add any other context or screenshots about the feature request here.💡
10 changes: 10 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
# node & npm
/node_modules
npm-debug.log

# build
/lib

# test
.jest-cache
test-results
10 changes: 10 additions & 0 deletions .npmignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
# test
__tests__
.jest-cache
test-results

# src
.babelrc
.editorconfig
.eslintrc.json
.npmignore
1 change: 1 addition & 0 deletions .npmrc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
registry=https://registry.npmjs.org
15 changes: 15 additions & 0 deletions .travis.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
language: node_js
jobs:
include:
# Define the release stage that runs semantic-release
- stage: release
node_js:
- 10
- 12
deploy:
on:
branch: master
provider: script
skip_cleanup: true
script:
- npx semantic-release
Empty file added CHANGELOG.md
Empty file.
3 changes: 3 additions & 0 deletions CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
# https://help.github.com/en/articles/about-code-owners

* @americanexpress/one
131 changes: 131 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,131 @@
### American Express Open Source Community Guidelines

#### Last Modified: January 29, 2016

Welcome to the American Express Open Source Community on GitHub! These American Express Community
Guidelines outline our expectations for Github participating members within the American Express
community, as well as steps for reporting unacceptable behavior. We are committed to providing a
welcoming and inspiring community for all and expect our community Guidelines to be honored.

**IMPORTANT REMINDER:**

When you visit American Express on any third party sites such as GitHub your activity there is
subject to that site’s then current terms of use., along with their privacy and data security
practices and policies. The Github platform is not affiliated with us and may have practices and
policies that are different than are our own.

Please note, American Express is not responsible for, and does not control, the GitHub site’s terms
of use, privacy and data security practices and policies. You should, therefore, always exercise
caution when posting, sharing or otherwise taking any action on that site and, of course, on the
Internet in general.

Our open source community strives to:
- **Be friendly and patient**.
- **Be welcoming**: We strive to be a community that welcomes and supports people of all
backgrounds and identities. This includes, but is not limited to members of any race, ethnicity,
culture, national origin, color, immigration status, social and economic class, educational level,
sex, sexual orientation, gender identity and expression, age, size, family status, political belief,
religion, and mental and physical ability.
- **Be considerate**: Your work will be used by other people, and you in turn will depend on the
work of others. Any decision you take will affect users and colleagues, and you should take those
consequences into account when making decisions. Remember that we're a world-wide community, so you
might not be communicating in someone else's primary language.
- **Be respectful**: Not all of us will agree all the time, but disagreement is no excuse for poor
behavior and poor manners. We might all experience some frustration now and then, but we cannot
allow that frustration to turn into a personal attack. It’s important to remember that a community
where people feel uncomfortable or threatened is not a productive one.
- **Be careful in the words that we choose**: We are a community of professionals, and we conduct
ourselves professionally. Be kind to others. Do not insult or put down other participants.
Harassment and other exclusionary behavior aren't acceptable.
- **Try to understand why we disagree**: Disagreements, both social and technical, happen all the
time. It is important that we resolve disagreements and differing views constructively. Remember
that we’re all different people. The strength of our community comes from its diversity, people from
a wide range of backgrounds. Different people have different perspectives on issues. Being unable to
understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is
human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve
issues and learning from mistakes.

### Definitions
Harassment includes, but is not limited to:
- Offensive comments related to gender, gender identity and expression, sexual orientation,
disability, mental illness, neuro(a)typicality, physical appearance, body size, race, age, regional
discrimination, political or religious affiliation
- Unwelcome comments regarding a person’s lifestyle choices and practices, including those related
to food, health, parenting, drugs, and employment
- Deliberate misgendering. This includes deadnaming or persistently using a pronoun that does not
correctly reflect a person's gender identity. You must address people by the name they give you when
not addressing them by their username or handle
- Physical contact and simulated physical contact (eg, textual descriptions like “hug” or “backrub”)
without consent or after a request to stop
- Threats of violence, both physical and psychological
- Incitement of violence towards any individual, including encouraging a person to commit suicide
or to engage in self-harm
- Deliberate intimidation
- Stalking or following
- Harassing photography or recording, including logging online activity for harassment purposes
- Sustained disruption of discussion
- Unwelcome sexual attention, including gratuitous or off-topic sexual images or behaviour
- Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of
intimacy with others
- Continued one-on-one communication after requests to cease
- Deliberate “outing” of any aspect of a person’s identity without their consent except as necessary
to protect others from intentional abuse
- Publication of non-harassing private communication

Our open source community prioritizes marginalized people’s safety over privileged people’s comfort.
We will not act on complaints regarding:
- ‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’
- Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not
discussing this with you”
- Refusal to explain or debate social justice concepts
- Communicating in a ‘tone’ you don’t find congenial
- Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or assumptions

### Diversity Statement
We encourage everyone to participate and are committed to building a community for all. Although we
will fail at times, we seek to treat everyone both as fairly and equally as possible. Whenever a
participant has made a mistake, we expect them to take responsibility for it. If someone has been
harmed or offended, it is our responsibility to listen carefully and respectfully, and do our best
to right the wrong.

Although this list cannot be exhaustive, we explicitly honor diversity in age, gender, gender
identity or expression, culture, ethnicity, language, national origin, political beliefs,
profession, race, religion, sexual orientation, socioeconomic status, and technical ability. We will
not tolerate discrimination based on any of the protected characteristics above, including
participants with disabilities.

### Reporting Issues
If you experience or witness unacceptable behavior—or have any other concerns—please report it by
contacting us at opensource@aexp.com. All reports will be handled with discretion. In your report
please include:
- Your contact information.
- Names (real, nicknames, or pseudonyms) of any individuals involved. If there are additional
witnesses, please include them as well. Your account of what occurred, and if you believe the
incident is ongoing. If there is a publicly available record (e.g. a mailing list archive or a
public IRC logger), please include a link.
- Any additional information that may be helpful.

After filing a report, a representative of our community will contact you personally, review the
incident, follow up with any additional questions, and make a decision as to how to respond. If the
person who is harassing you is part of the response team, they will recuse themselves from handling
your incident. If the complaint originates from a member of the response team, it will be handled by
a different member of the response team. We will respect confidentiality requests for the purpose of
protecting victims of abuse.

### Removal of Posts
We will not review every comment or post, but we reserve the right to remove any that violates these
Guidelines or that, in our sole discretion, we otherwise consider objectionable and we may ban
offenders from our community.

### Suspension/Termination/Reporting to Authority
In certain instances, we may suspend, terminate or ban certain repeat offenders and/or those
committing significant violations of these Guidelines. When appropriate, we may also, on our own or
as required by the GitHub terms of use, be required to refer and/or work with GitHub and/or the
appropriate authorities to review and/or pursue certain violations.

### Attribution & Acknowledgements
These Guidelines have been adapted from the
[Code of Conduct of the TODO group](http://todogroup.org/opencodeofconduct/). They are subject to
revision by American Express and may be revised from time to time.

Thank you for your participation!
Loading

0 comments on commit 339c694

Please sign in to comment.