|
| 1 | +--- |
| 2 | +collaborating_projects: |
| 3 | + - gsoc-prep-tasks |
| 4 | +desc: "List open issues and pull request from various issue tracker of a specified organization." |
| 5 | +difficulty: medium |
| 6 | +initiatives: |
| 7 | + - GSoC |
| 8 | +issues: |
| 9 | + - https://github.com/coala/coala/issues/4080 |
| 10 | +markdown: git_task_list.md |
| 11 | +mentors: |
| 12 | + - blazeu |
| 13 | + - yukiisbored |
| 14 | + - yashovardhanagrawal |
| 15 | +name: "Git Task List" |
| 16 | +requirements: |
| 17 | + - "The applicant should have at least one patch merged to any of the coala repositories." |
| 18 | + - "Familiarity with Git, GitHub API, Phabricator API, and GitLab API" |
| 19 | + - "Familiarity with EmberJS and GitHub Pages" |
| 20 | +status: in_progress |
| 21 | +tags: |
| 22 | + - community |
| 23 | + - web |
| 24 | +--- |
| 25 | +The basic idea is an extended version of [GSOC Task List](http://github.com/summerofcode/gsoc-prep-tasks). |
| 26 | + |
| 27 | +In this project, tasks means open issues and unmerged pull request coming from |
| 28 | +GSOC open source projects. |
| 29 | + |
| 30 | +[GSOC prep task](http://summerofcode.github.io/gsoc-prep-tasks) is an issue |
| 31 | +finding tools that is (currently) integrated only with GitHub. It helps filter |
| 32 | +out the GitHub issues and only show the issues that are newcomer friendly and |
| 33 | +coming from limited GSoC organization. It limits the organization because |
| 34 | +different organization use different kind of issue tracking such as Phabricator |
| 35 | +and GitLab. |
| 36 | + |
| 37 | +**Git Task List** is conceptually the same as [GSOC prep task](http://summerofcode.github.io/gsoc-prep-tasks). |
| 38 | +Git Task List target a broader task type which include pull request review as |
| 39 | +the task. The goal of this project is to help developer to keep contributing to |
| 40 | +open source project by providing a sets of tasks that has been filtered using |
| 41 | +predefined keywords. |
| 42 | + |
| 43 | +In coala, this project will help sharing the tasks of reviewing a pull request |
| 44 | +on a project accross GitHub and GitLab. It will help fix the problem where |
| 45 | +developer spend too much time finding PR that haven’t been reviewed. This |
| 46 | +projects aims to getting more developer doing reviews works and sharing reviews |
| 47 | +workload, by providing an easy way to find issues that has not been reviewed |
| 48 | +both on http://github.com/coala and http://gitlab.com/coala. |
| 49 | + |
| 50 | +This will also help engage the developer to keep contributing to a project where |
| 51 | +they can’t find any issue that they can fix or keep the newcomer issue for new |
| 52 | +comer as learning path and developer with more experience can contribute by |
| 53 | +reviewing newcomer’s work PR. |
| 54 | + |
| 55 | +The goal of this projects is a static-site web page where the user |
| 56 | +can find Issues and Pull Request that haven’t been reviewed. User can select |
| 57 | +projects in Open Source hosting services like GitHub or GitLab. They also have |
| 58 | +the ability to select prefered programming language, tags, owner of the pull |
| 59 | +requests, and other metadata that is provided by the web services |
| 60 | +(GitHub/GitLab). |
| 61 | + |
| 62 | +Because the concept of this project, is the same as [GSOC prep task](http://summerofcode.github.io/gsoc-prep-tasks), it can be used as the starting point of this project. |
| 63 | + |
| 64 | +#### Known Issue Tracker Usage In GSOC Organization |
| 65 | + |
| 66 | +Issue Tracker | Usage |
| 67 | +--- | --- |
| 68 | +GitHub | 16 |
| 69 | +Trac | 7 |
| 70 | +Atlassian Jira | 7 |
| 71 | +GitLab | 4 |
| 72 | +phabricator | 4 |
| 73 | +BugZilla | 4 |
| 74 | +Usabilla | 2 |
| 75 | +Redmine | 2 |
| 76 | + |
| 77 | +Because of the difficulty to support all of the known issue tracker in the range |
| 78 | +of GSOC timeline. This project will provide support for GitHub, GitLab, and |
| 79 | +Phabricator. |
| 80 | + |
| 81 | +#### Identifying Task Of A Specific Organization |
| 82 | + |
| 83 | +For a hosted issue tracker (like GitHub.com & GitLab.com) it is already |
| 84 | +documented and we can confidently know what resource are posible and what is not |
| 85 | +. The process of adding support for a new organization is posible using an |
| 86 | +external data source such as [Wikidata](http://wikidata.org). The app can fetch |
| 87 | +for list of organization that use GitHub / GitLab via [Qikidata Query API](https://query.wikidata.org/) |
| 88 | + |
| 89 | +The case is different for a self hosted Organization. The accessibility is |
| 90 | +different. For organization that use Phabricator as issue tracker, the process |
| 91 | +of adding support to it will be manually for each organization to make sure that |
| 92 | +the API is accessible. |
| 93 | + |
| 94 | +#### Milestone |
| 95 | + |
| 96 | +##### Phase 1 |
| 97 | +- Use GraphQL (GitHub). |
| 98 | +- Add support to all GSOC 2018 organizations that are using GitHub as an issue |
| 99 | + tracker. |
| 100 | +- Add GitLab.com support. |
| 101 | + - Search issues from a specified project. |
| 102 | + |
| 103 | +##### Phase 2 |
| 104 | +- GitHub & GitLab. |
| 105 | + - Search open MR/PR. |
| 106 | + - Browse MR/PR by authors. |
| 107 | +- Add support to list Issues and MR from http://gitlab.com/coala. |
| 108 | +- Add support to all GSOC 2018 organizations that are using GitLab.com as an issue |
| 109 | + tracker. |
| 110 | + |
| 111 | +##### Phase 3 |
| 112 | +- Browse PR by authors. ([issues/20](https://github.com/summerofcode/gsoc-prep-tasks/issues/20)) |
| 113 | +- Add support GitLab CE. |
| 114 | +- Add Phabricator support. |
| 115 | +- Add support to some GSOC 2018 organizations that are using Phabricator and opened |
| 116 | + their api for public use. |
0 commit comments