Browse --- Chat --- Wekan

Skip to content

Allowing contributors

Review the best way to allow contributors to a repository.
User creation is disabled, so users cannot create issues, comments, or forks. This is mainly to prevent malicious users/bots from exploiting possible holes in security I don't wish to worry about for the time being (very early stage someone attempted to create a git user).
On a similar note, nobody wants to create an account on some random website/blog/hosted git repository.

What tools could be implemented that allow a user to supply a method of identification they feel comfortable providing.

  • How does diskus work where users comment on posts on relatively unknown websites/blog.

Scenario -

  • Random Randy has cloned a repo he found and likes and wants support for a feature and wants to contribute his code.
    • How can he do this from an open-trusted method

I think the best method would be figuring out how to support pull requests from GitHub.

  • We mirror our open source repositories on github
  • Users then allowed to fork, commit, then create a PR

How do we facilitate this as seamless as possible.

  • Can we create webhooks on github to create pull requests from GH as merge requests on gitlab
    • We then have to worry about PRs on github and how they interact with runners
  • Can we create webhooks on github to create issues on gitlab from github
  • Review webhook page

How do we automate this templated way of mirroring our repositories on GH and creating webhooks.

  • Can we do this for each and every project
  • Can we do this for projects in a specific group

Once we open a few more repositories and start stabilizing the development cycle/code we can circle back to this.

First step is creating a single, easily accessible location for people to provide any type of feedback for anything hosted on the codeopensrc.com domain.

Edited by kc