evrone / evrone_opensource

Improve READMEs of opensource projects

Home Page:https://evrone.com/cases#open-source

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Define resource models for application

achempion opened this issue · comments

Project

General queue to handle new projects in order to find improvement
opportunities.

  • repository_url
  • internal_repository_url # forked repository address
  • handled_at

ProjectImprovement

If improvement opportunity is present, we fork project to a separate repository, create a commit with improvements then we wait for review or changes.

When we get successful review, we propagate changes to the origin repository.

  • project_id
  • internal_pull_request_url
  • external_pull_request_url
  • github_author_id # defined after successful review
  • status
    • awaiting review # if project corrected
    • reviewed # after successful local review
    • published # to the origin
    • merged
    • rejected
    • awaiting author response # from us, after response to "published"

Status is managed automatically based on GitHub events and
synchronization.

@ptuchster what do you think?