Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Python Briar Wrapper
Python Briar Wrapper
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • briar
  • Python Briar WrapperPython Briar Wrapper
  • Issues
  • #3

Closed
Open
Opened Dec 14, 2019 by Nico Alt@nicoaltMaintainer

Discussion of collaborative work flow for this project

@fphemeral From previous work in free and open source projects, I really liked the way of always doing merge request when working together on a project. What do you think about doing this for briar-wrapper, too? I currently see 4 options:

  1. always do merge requests and let them merge by other contributors
  2. always do merge requests and wait for an OK by other contributors
  3. always do merge requests, but sometimes merge it yourself
  4. push directly to master

Personally, I'd prefer option 3, so that we always make merge requests to master and in general wait for an OK by other contributors, but also can merge it ourselves if it's only a little change.

What do you think about this?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: briar/python-briar-wrapper#3