Maintainer Rules

Community
1

Lets us use GitHub features as much as we can.

Atleast one review per PR

  1. Someone to independently test the PR
  2. No direct pushes
  3. Lets also start tagging issues based on the stage
  • PR Needs a review
  • Feature request needs a design
  • Maybe add the “watchlist” label so we can plan it for the next milestone
  • Needs volunteers
  1. Start using BountySource.com if someone wants to add a bounty to an issue (@IAGAdmin)
  2. If you are reviewing a pull request, just assign it yourself.

Forum leaders will keep editing this post as per the discussion.

Please Tag the maintainers here
@rmehta @Ben_Cornwell_Mott @Eric_Delisle @Felipe_Orellana @Chude_Osiegbu @IAGAdmin @vjFaLk

2017-05-19:

Contribution Guidelines

2 Likes
3

@revant_one thanks for getting the started!

Lets us GitHub features as much as we can.

  1. Atleast one review per PR
  2. Maybe someone to independently test the PR?
  3. No direct pushes (esp me ;))
  4. Lets also start tagging issues based on the stage
  • PR Needs a review
  • Feature request needs a design
  • Maybe add the “watchlist” label so we can plan it for the next milestone
  • Needs volunteers
  1. Start using BountySource.com if someone wants to add a bounty to an issue (@IAGAdmin)
4 Likes
4

Only if it’s been approved by a team member, I’d say. Or if it’s something minor.

I think a simple fix shouldn’t require more than a single review, but it should still be approved by a team member.

Again, depends. If it’s something like a typo / silly programming mistake, sure. If it’s something more complex, get approval first.

:knife: :knife: NO :knife: :knife:

6 Likes
5

:laughing:

2 Likes
6

We are trying this [Community Development] Barcode camera scanner and integration

2 Likes
7

If you are reviewing a pull request, just assign it yourself.