Our project has established a Royalty Pool, a dedicated fund to financially compensate contributors. This pool is sustained through various sources:
- 🎁 Donations: Received from individuals or organizations.
- 🏆 Grants: Acquired from entities supporting open-source initiatives.
- 💼 Revenue: Generated from services related to our project.
- 🤝 Sponsorships: Obtained from companies or individuals benefiting from our project.
Compensation is based on a fair and transparent Royalty Points System:
- 💻 Contribution Evaluation: Contributions (coding, documentation, etc.) are assigned points based on their impact and complexity.
- 💵 Monetary Value: Points have a set monetary value, periodically adjusted to reflect the pool's status.
Payments are distributed following a regular schedule:
- 🔄 Frequency: Payments are made annually.
- 💳 Methods: We offer various payment methods, including bank transfer, PayPal, and cryptocurrencies.
We are committed to transparency:
- 📝 Reporting: Regular reports detail fund inflows, outflows, and distribution.
- 🔍 Public Records: A ledger records points earned by each contributor.
- 📢 Feedback: Contributors can provide feedback or raise concerns regarding the distribution process.
Before contributing, make sure your fork is up-to-date with the original repository to avoid merge conflicts.
- Add the original repository as a remote (if not already done). This remote is typically named
upstream
:git remote add upstream https://github.com/apipulse/brbhr-frontend
- Fetch the latest changes from the original repository:
git fetch upstream
- Switch to your main branch (assuming it's named
main
ormaster
):git checkout main
- Merge the changes from the original repository's main branch into your fork:
git merge upstream/main
- Push the updates to your fork:
git push origin main
It's a good practice to create a new branch for each set of changes you plan to contribute.
- Create and switch to a new branch (name it according to the feature or fix you're working on):
git checkout -b feature-branch-name
Implement your changes, enhancements, or fixes in this branch, then add and commit your changes:
- Add your changes:
git add .
- Commit your changes:
git commit -m "Detailed commit message"
- Push the feature branch to your fork:
git push origin feature-branch-name
After pushing your changes, create a pull request in the original repository:
- Go to the original repository on GitHub.
- Click "New pull request".
- Set the base repository to the original repository and the base branch (usually
main
). - Set the head repository as your fork and the compare branch as your feature branch.
- Fill in the pull request details and submit.
Be responsive to feedback after submitting your pull request:
- Make additional changes if requested.
- Engage in discussions and answer any questions.
After your pull request is merged:
- Switch to your main branch:
git checkout main
- Delete the feature branch locally:
git branch -d feature-branch-name
- Delete the feature branch from your fork:
git push origin --delete feature-branch-name
Note: These steps are general guidelines. Always check the project's specific guidelines if available.