Skip to content

Latest commit

 

History

History
120 lines (93 loc) · 5.6 KB

CONTRIBUTING.md

File metadata and controls

120 lines (93 loc) · 5.6 KB

Contributing Guidelines

Thank you for your interest in contributing to the wwcode-legacygroups repository! We are looking for additional community groups to add to our expanding list of legacy Women Who Code communities.

Before submitting a new name, please check the README to see whether your suggestion already exists.

How to contribute

You can edit this file using GitHub's web interface, or fork the repository and work locally in your code editor.

Please add new names in alphabetical order by last name, under the appropriate category and country.

Edit the README on GitHub

  1. Navigate to the README file in the repository and click the pencil icon to "edit file", or navigate to the URL to edit this file directly.
  2. Scroll down to the appropriate location in the file to add your suggestion. Suggestions are organized first by Technical Tracks, and then by first letter of previous group's local chapter name alphabetically.
  3. Use the format provided as a template for adding your suggestion to the document. You can toggle from "Edit" mode into "Preview" mode at the top of the file editor to view your changes as they will appear.
  4. After you make your changes, click the "Commit changes..." button in the upper right of the screen. You will be prompted to enter a commit message that will be used to describe the changes you have made. You may wish to edit this to convey more specific information to the repository maintainers (e.g. "Added a new speaker to README.md"), but this is not required. An extended description is not necessary.
  5. Click the "Propose changes" button when you are happy with your submission. This will automatically create a fork of the repository in your GitHub account with the changes you have made.
  6. Once you have committed your edits to your fork, follow the prompts to create a pull request (PR) which proposes changes to this repository.
  7. The maintainers will review your PR and either request changes or approve it.

Edit the repository locally

  1. Fork the repository. Here are the GitHub instructions for forking a repository.
  2. In the command line, clone the repository by typing git clone https://github.com/YOUR-GITHUB-USERNAME/wwcode-legacygroups.git
  3. Then type cd legacygroups to go into the project's directory.
  4. Create a branch and switch to that new branch by using the following command: git checkout -b new-branch-name
  5. Update the README.md with your new suggestion.
    • Scroll down to the appropriate location in the file to add your suggestion. Suggestions are organized first by Technical Tracks, and then by first letter of previous local chapter's name alphabetically.
    • Use the format provided as a template for adding your suggestion to the document.
  6. In the command line, stage your changes by using the git add . command.
  7. Commit your changes by using the git commit -m "commit message" command.
  8. Push up your changes to the remote branch on GitHub by using the git push -u origin branch_name command.
  9. Open a PR directed to our master branch.
  10. The maintainers will review your PR and either request changes or approve it.

Formatting

Please add yourself alphabetically per local chapter/network and be sure to add yourself alphabetically by the first letter of your community group's name.

Technical Track

## Technical Track
Previously: Old Technical Track Name
### New Community Group Name

- Community Organizer Full Name (First, Last)
- [Personal Website: Example.com](http://www.examplewebsitelink.com)
- Description - 
- [Slack](http://slack.com)
- [Discord](http://discord.com)
- [Github](http://github.com)
- [@TwitterHandle](http://twitter.com)
- [@Instagram](http://instagram.com)
- [Linkedin Group/Page](http://linkedin.com)
- [Meetup](http://meetup.com)

Network City Chapter

## City Name
Previously: Women Who Code City / Network Chapter Name
### New Community Group Name

- Community Organizer Full Name (First, Last)
- [Personal Website: Example.com](http://www.examplewebsitelink.com)
- Description - 
- [Slack](http://slack.com)
- [Discord](http://discord.com)
- [Github](http://github.com)
- [@TwitterHandle](http://twitter.com)
- [@Instagram](http://instagram.com)
- [Linkedin Group/Page](http://linkedin.com)
- [Meetup](http://meetup.com)

Spin-off Communities

#### New Community Group Name

- Community Organizer Full Name (First, Last)
- [Personal Website: Example.com](http://www.examplewebsitelink.com)
- Description - 
- [Slack](http://slack.com)
- [Discord](http://discord.com)
- [Github](http://github.com)
- [@TwitterHandle](http://twitter.com)
- [@Instagram](http://instagram.com)
- [Linkedin Group/Page](http://linkedin.com)
- [Meetup](http://meetup.com)

Getting Started

#### New Community Group Name

- Community Organizer Full Name (First, Last)
- [Personal Website: Example.com](http://www.examplewebsitelink.com)
- Description -
- [Slack](http://slack.com)
- [Discord](http://discord.com)
- [Github](http://github.com)
- [@TwitterHandle](http://twitter.com)
- [@Instagram](http://instagram.com)
- [Linkedin Group/Page](http://linkedin.com)
- [Meetup](http://meetup.com)

Beginner Friendly Resources for using Git and GitHub

Attribution

This Contribution guideline / Instructions document is adapted from fempire / women-tech-speakers-organizers.