Skip to content

Latest commit

 

History

History
181 lines (128 loc) · 6.14 KB

CONTRIBUTING.md

File metadata and controls

181 lines (128 loc) · 6.14 KB
Raw

Contributing

Table of Contents

Introduce

I'm really glad you're reading this, because we need volunteer developers to help this project come to fruition.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Code of Conduct

Refer to CODE_OF_CONDUCT.md.

We Develop with Github

We use github to host code, to track issues and feature requests, as well as accept pull requests.

After feedback has been given we expect responses within two weeks. After two weeks we may close the issue and pull request if it isn't showing any activity.

Environment

You can configure it as follows:

## clone repository
git clone https://github.com/black7375/Firefox-UI-Fix.git
cd ./Firefox-UI-Fix

## install dependencies
git checkout <BRANCH_NAME>

Your First Contribution

Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub

The following documents may be helpful:

Live Debugging:

Firefox Source Code:

Test for None mac users:

Contribution Targets

We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:

Promotions

  • Introduce project
    • Video (Recommend!!, We need it)
    • Blog
    • SNS
    • Reddit, Hackernews..etc
  • Sample

Docs

  • Fix typos, alignments.
  • Correct awkward sentences.
  • Improve document readability.

Issues

  • Report a bug.
  • Discussing the current state of the code.
  • Tell us about related or relevant projects and documents.
  • Help other users issue.
  • Proposing others..

Codes

  • New Features.
  • Bug fixes.
  • Improved compatibility or accessibility.
  • Refactoring.

Rules

Version

Milestone, The versioning scheme we use is SemVer. (Maintainer decides, do not pull request.)

We will release the feature as soon as it is complete, but the cycle should be 2-4 weeks. Rapid releases.

Branch

Stable: Only bugfix, Documentation.

  • master: Common bugfix, documentation.
  • photon-style: Bugfix, documentation specified in photon-style.
  • proton-sryle: Bugfix, documentation specified in proton-style.

Development: New Features.

  • dev: Common new features.
  • photon-style-dev: New features specified in photon-style.
  • proton-style-dev: New features specified in proton-style.

Issue

  • Versions:
  • Make sure you’re on the latest version.
  • Try older versions.
  • Try switching up dependency versions.
  • Search: Search the project’s issues to make sure it's not a known issue.

Coding style

  • Indent: 2 spaces for indentation rather than tabs.
  • Columns: Fit 80~100 columns as much as possible.

Commit

  • Meaningfully:: It doesn't make meaningless commits.
  • One per task: It's difficult to distinguish when various tasks are mixed.
  • Often: Codes may corrupt during large changes.

Commit Message

For intuitive recognition, I put a prefix.

  • Add: Add feature or enhanced.
  • Fix: Bug fix or change default values.
  • Clean: Refactoring.
  • Doc: Update docs.

Pull request

  • Branch: Check the Branch section and PR to the correct branch.
  • Issue: We recommend that you open the issue first to discuss the changes with the owner of this repository.

License

Any contributions you make will be under the MPL 2.0 Software License

In short, when you submit code changes, your submissions are understood to be under the same MPL 2.0 License that covers the project. Feel free to contact the maintainers if that's a concern.

Reference specification

Even if you copy the code snippet, it is recommended that you leave a link.

FAQ

If you have any questions about other licenses, please see Moailla's MPL 2.0 FAQ.

References