cEP-0020: Newcomer metrics and Gamification system #131

sks444 · 2018-05-09T16:04:45Z

No description provided.

gitmate-bot · 2018-05-09T16:05:03Z

cEP-0020.md

+    - Creating and merging a PR for that issue
+    - Reviewing at least one difficulty/low issue
+
+- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. 


Line contains following spacing inconsistencies:

Trailing whitespaces.

Origin: SpaceConsistencyBear, Section: spacing.

The issue can be fixed by applying the following patch:

--- a/tmp/tmp2e3alytw/cEP-0020.md +++ b/tmp/tmp2e3alytw/cEP-0020.md @@ -55,7 +55,7 @@ - Creating and merging a PR for that issue - Reviewing at least one difficulty/low issue -- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. +- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. - **Badges** enable newcomers to follow their performance and compare to other newcomers.**After completing the level three successfully the newcomer will be a developer**. And he will be awarded a badge based on their performance in each level and the total number of points.

gitmate-bot · 2018-05-09T16:05:04Z

cEP-0020.md

@@ -0,0 +1,169 @@
+Newcomer metrics and Gamification


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmp2e3alytw/cEP-0020.md +++ b/tmp/tmp2e3alytw/cEP-0020.md @@ -1,17 +1,15 @@ -Newcomer metrics and Gamification -================================= +# Newcomer metrics and Gamification -|Metadata| | -|--------|-----------------------------------------------| -|cEP |20 | -|Version |1.0 | -|Title |Newcomer metrics and Gamification system | -|Authors |Shrikrishna Singh <[email protected]>| -|Status |Proposed | -|Type |Process | +| Metadata | | +| -------- | ------------------------------------------------------ | +| cEP | 20 | +| Version | 1.0 | +| Title | Newcomer metrics and Gamification system | +| Authors | Shrikrishna Singh <mailto:[email protected]> | +| Status | Proposed | +| Type | Process | -Abstract --------- +## Abstract This cEP describe how a newcomer at coala will become a developer on the basis of their activities in the community.

gitmate-bot · 2018-05-09T16:05:05Z

cEP-0020.md

+
+## Background
+
+###  Newcomer Experience


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmp2e3alytw/cEP-0020.md +++ b/tmp/tmp2e3alytw/cEP-0020.md @@ -21,7 +21,7 @@ ## Background -### Newcomer Experience +### Newcomer Experience - How to attract more newcomers - How to cope with the increasing amounts of newcomers

gitmate-bot · 2018-05-09T16:05:06Z

cEP-0020.md

+###  Newcomer Experience
+
+- How to attract more newcomers
+   - How to cope with the increasing amounts of newcomers


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmp2e3alytw/cEP-0020.md +++ b/tmp/tmp2e3alytw/cEP-0020.md @@ -24,9 +24,9 @@ ### Newcomer Experience - How to attract more newcomers - - How to cope with the increasing amounts of newcomers + - How to cope with the increasing amounts of newcomers - How to teach and help newcomers scalable so we can keep working on coala. - - Talk to Docs team + - Talk to Docs team - How to improve newcomer -> dev/maintainer ratio - How to increase amount of feedback we get - How to use feedback to improve coala and processes

gitmate-bot · 2018-05-09T16:05:07Z

cEP-0020.md

+   - Talk to Docs team
+- How to improve newcomer -> dev/maintainer ratio
+- How to increase amount of feedback we get
+   - How to use feedback to improve coala and processes


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmp2e3alytw/cEP-0020.md +++ b/tmp/tmp2e3alytw/cEP-0020.md @@ -29,7 +29,7 @@ - Talk to Docs team - How to improve newcomer -> dev/maintainer ratio - How to increase amount of feedback we get - - How to use feedback to improve coala and processes + - How to use feedback to improve coala and processes ## Why Gamification?

gitmate-bot · 2018-05-09T16:05:08Z

cEP-0020.md

+
+After we have the data, we need to track some important activities of newcomers like:
+
+* Created Issues


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmp2e3alytw/cEP-0020.md +++ b/tmp/tmp2e3alytw/cEP-0020.md @@ -79,15 +79,15 @@ After we have the data, we need to track some important activities of newcomers like: -* Created Issues -* Created Pull Requests -* Number of Gitmate errors on the PR -* CI status -* Review Comments -* Issue Comments -* Number of PRs Reviewed -* Activities on Gitter channles -* Introduce `.coafile` in other projects +- Created Issues +- Created Pull Requests +- Number of Gitmate errors on the PR +- CI status +- Review Comments +- Issue Comments +- Number of PRs Reviewed +- Activities on Gitter channles +- Introduce `.coafile` in other projects Which will help us in showing useful metrics for newcomers on a dashboard.

gitmate-bot · 2018-05-09T16:15:21Z

cEP-0020.md

+    - Creating and merging a PR for that issue
+    - Reviewing at least one difficulty/low issue
+
+- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. 


Line contains following spacing inconsistencies:

Trailing whitespaces.

Origin: SpaceConsistencyBear, Section: spacing.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpqhe2wf1y/cEP-0020.md +++ b/tmp/tmpqhe2wf1y/cEP-0020.md @@ -54,7 +54,7 @@ - Creating and merging a PR for that issue - Reviewing at least one difficulty/low issue -- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. +- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. - **Badges** enable newcomers to follow their performance and compare to other newcomers.**After completing the level three successfully the newcomer will be a developer**. And he will be awarded a badge based on their performance in each level and the total number of points.

gitmate-bot · 2018-05-09T16:15:22Z

cEP-0020.md

@@ -0,0 +1,168 @@
+# Newcomer metrics and Gamification
+
+


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpqhe2wf1y/cEP-0020.md +++ b/tmp/tmpqhe2wf1y/cEP-0020.md @@ -1,14 +1,13 @@ # Newcomer metrics and Gamification - -| Metadata | | -| -------- | ---------------------------------------------- | -| cEP | 20 | -| Version | 1.0 | -| Title | Newcomer metrics and Gamification system | -| Authors | Shrikrishna Singh <[email protected]>| -| Status | Proposed | -| Type | Process | +| Metadata | | +| -------- | ------------------------------------------------------ | +| cEP | 20 | +| Version | 1.0 | +| Title | Newcomer metrics and Gamification system | +| Authors | Shrikrishna Singh <mailto:[email protected]> | +| Status | Proposed | +| Type | Process | ## Abstract

gitmate-bot · 2018-05-09T16:17:48Z

cEP-0020.md

@@ -0,0 +1,168 @@
+# Newcomer metrics and Gamification
+
+


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpcx1vqkf5/cEP-0020.md +++ b/tmp/tmpcx1vqkf5/cEP-0020.md @@ -1,14 +1,13 @@ # Newcomer metrics and Gamification - -| Metadata | | -| -------- | ---------------------------------------------- | -| cEP | 20 | -| Version | 1.0 | -| Title | Newcomer metrics and Gamification system | -| Authors | Shrikrishna Singh <[email protected]>| -| Status | Proposed | -| Type | Process | +| Metadata | | +| -------- | ------------------------------------------------------ | +| cEP | 20 | +| Version | 1.0 | +| Title | Newcomer metrics and Gamification system | +| Authors | Shrikrishna Singh <mailto:[email protected]> | +| Status | Proposed | +| Type | Process | ## Abstract

gitmate-bot · 2018-05-09T16:19:35Z

cEP-0020.md

+    - Creating and merging a PR for that issue
+    - Reviewing at least one difficulty/low issue
+
+- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. 


Line contains following spacing inconsistencies:

Trailing whitespaces.

Origin: SpaceConsistencyBear, Section: spacing.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpqhe2wf1y/cEP-0020.md +++ b/tmp/tmpqhe2wf1y/cEP-0020.md @@ -54,7 +54,7 @@ - Creating and merging a PR for that issue - Reviewing at least one difficulty/low issue -- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. +- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. - **Badges** enable newcomers to follow their performance and compare to other newcomers.**After completing the level three successfully the newcomer will be a developer**. And he will be awarded a badge based on their performance in each level and the total number of points.

gitmate-bot · 2018-05-09T16:19:36Z

cEP-0020.md

@@ -0,0 +1,168 @@
+# Newcomer metrics and Gamification
+
+


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpqhe2wf1y/cEP-0020.md +++ b/tmp/tmpqhe2wf1y/cEP-0020.md @@ -1,14 +1,13 @@ # Newcomer metrics and Gamification - -| Metadata | | -| -------- | ---------------------------------------------- | -| cEP | 20 | -| Version | 1.0 | -| Title | Newcomer metrics and Gamification system | -| Authors | Shrikrishna Singh <[email protected]>| -| Status | Proposed | -| Type | Process | +| Metadata | | +| -------- | ------------------------------------------------------ | +| cEP | 20 | +| Version | 1.0 | +| Title | Newcomer metrics and Gamification system | +| Authors | Shrikrishna Singh <mailto:[email protected]> | +| Status | Proposed | +| Type | Process | ## Abstract

gitmate-bot · 2018-05-09T16:24:18Z

cEP-0020.md

@@ -0,0 +1,167 @@
+# Newcomer metrics and Gamification
+
+| Metadata |                                                 |


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpet_nzsjr/cEP-0020.md +++ b/tmp/tmpet_nzsjr/cEP-0020.md @@ -1,13 +1,13 @@ # Newcomer metrics and Gamification -| Metadata | | -| -------- | ----------------------------------------------- | -| cEP | 20 | -| Version | 1.0 | -| Title | Newcomer metrics and Gamification system | -| Authors | Shrikrishna Singh <[email protected]> | -| Status | Proposed | -| Type | Process | +| Metadata | | +| -------- | ------------------------------------------------------ | +| cEP | 20 | +| Version | 1.0 | +| Title | Newcomer metrics and Gamification system | +| Authors | Shrikrishna Singh <mailto:[email protected]> | +| Status | Proposed | +| Type | Process | ## Abstract

gitmate-bot · 2018-05-09T16:28:03Z

cEP-0020.md

+    - Creating and merging a PR for that issue
+    - Reviewing at least one difficulty/low issue
+
+- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. 


Line contains following spacing inconsistencies:

Trailing whitespaces.

Origin: SpaceConsistencyBear, Section: spacing.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpqhe2wf1y/cEP-0020.md +++ b/tmp/tmpqhe2wf1y/cEP-0020.md @@ -54,7 +54,7 @@ - Creating and merging a PR for that issue - Reviewing at least one difficulty/low issue -- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. +- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points. - **Badges** enable newcomers to follow their performance and compare to other newcomers.**After completing the level three successfully the newcomer will be a developer**. And he will be awarded a badge based on their performance in each level and the total number of points.

gitmate-bot · 2018-05-09T16:28:03Z

cEP-0020.md

@@ -0,0 +1,168 @@
+# Newcomer metrics and Gamification
+
+


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpqhe2wf1y/cEP-0020.md +++ b/tmp/tmpqhe2wf1y/cEP-0020.md @@ -1,14 +1,13 @@ # Newcomer metrics and Gamification - -| Metadata | | -| -------- | ---------------------------------------------- | -| cEP | 20 | -| Version | 1.0 | -| Title | Newcomer metrics and Gamification system | -| Authors | Shrikrishna Singh <[email protected]>| -| Status | Proposed | -| Type | Process | +| Metadata | | +| -------- | ------------------------------------------------------ | +| cEP | 20 | +| Version | 1.0 | +| Title | Newcomer metrics and Gamification system | +| Authors | Shrikrishna Singh <mailto:[email protected]> | +| Status | Proposed | +| Type | Process | ## Abstract

ishanSrt · 2018-05-09T16:47:09Z

cEP-0020.md

+
+- How to attract more newcomers
+  - How to cope with the increasing amounts of newcomers
+- How to teach and help newcomers scalable so we can keep working on coala.


help newcomers scalable

sentence doesn't make sense to me

Maybe help newcomers to learn and grow faster which can help the community in getting more new contributors?

Actually, I copied the background section from here

ishanSrt · 2018-05-09T16:47:36Z

cEP-0020.md

+
+## Why Gamification?
+
+As coala tries to be welcoming organization for newcomers, giving them clear pathways and as much direct assistance as possible. However, it is already known that newcomers face many barriers while attempting to contribute to the open source community for the first time. Some barriers they face include orientation issues that can potentially demotivate newcomers from placing their first contribution. On the other hand, gamification is widely used to engage and motivate people to accomplish task and improve their performance.Therefore, the goal of this project is to use gamification to orient and motivate newcomers to overcome onboarding barriers to contribute and engage with coala and its community.


don't understand what is meant by orientation issues

Problems someone face while trying to learn something for the first time?

ishanSrt · 2018-05-09T16:48:08Z

cEP-0020.md

+
+## Why Gamification?
+
+As coala tries to be welcoming organization for newcomers, giving them clear pathways and as much direct assistance as possible. However, it is already known that newcomers face many barriers while attempting to contribute to the open source community for the first time. Some barriers they face include orientation issues that can potentially demotivate newcomers from placing their first contribution. On the other hand, gamification is widely used to engage and motivate people to accomplish task and improve their performance.Therefore, the goal of this project is to use gamification to orient and motivate newcomers to overcome onboarding barriers to contribute and engage with coala and its community.


improve their performance.Therefore,

styling issue: space after full stop

ishanSrt · 2018-05-09T16:48:50Z

cEP-0020.md

+
+## Process involved in the Gamification system
+
+As the goal of this project is to make use of metrics and gamification to motivate and support newcomers to overcome the orientation barriers to contribute to the community.


this sentence should end with a comma, the way it is framed

ishanSrt · 2018-05-09T16:50:45Z

cEP-0020.md

+As the goal of this project is to make use of metrics and gamification to motivate and support newcomers to overcome the orientation barriers to contribute to the community.
+To achieve this goal we have selected three game design elements to help newcomers: Levels, Points, and Badges. For each of these elements, we will have a set of rules to describe the operation of the gamified environment. i.e.:
+
+- **Levels** group different tasks, enabling users to unlock specific and contextualize set of actions. Levels will be applied to make newcomers focus on a given step before moving ahead on the contribution process. E.g.: We will divide our newcomer process into three levels and each level will contain three tasks:


~~contextualize~~ contextual set of actions ??

ishanSrt · 2018-05-09T16:54:57Z

cEP-0020.md

+    - Creating and merging a PR for that issue
+    - Reviewing at least one difficulty/low issue
+
+- **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance with what was expected. Points can be earned by means of performing actions to the different tasks under levels. E.g.: If a user wants to go to next level he will have to collect a certain number of points from doing the tasks under levels. But in case of Level-II and Level-III if a user is not able to acquire the required number of points after performing all the tasks, he will have to review more PRs to collect the required points.


so the threshold for leveling up will be more that what you can earn by the minimum right? so that more reviews are encouraged

ishanSrt · 2018-05-09T17:04:35Z

cEP-0020.md

+
+These all are just basic ideas, the process and tasks in the levels can be changed according to the use case and implementaion process.
+
+A similar process can also be extended and applied to developers to achieve more number of badges or something more.


badges and points among developers sound cool. After a threshold developers can get the ability to atleast unack PRs, apart from the issue I already opened about it. (I think it's gonna take time for the gitmate plugins to get out, but the recent comments on that which I have failed to read may be of importance over here). unack does much much less harm than an ack. A Gitlab like feature would also be beneficial over here, requiring acks by 3 or more developers can automatically assign the PRs a tag, like approved by developers or something so that maintainers can clear them out as early as possible. ability to ack can be given at a higher threshold.

Stretch goal stuff, don't let this get in the way of you completing the project

ishanSrt · 2018-05-09T17:07:39Z

cEP-0020.md

+- Review Comments
+- Issue Comments
+- Number of PRs Reviewed
+- Activities on Gitter channles


~~channles~~ --> channels

ishanSrt · 2018-05-09T17:08:25Z

cEP-0020.md

+    name='pullrequest')
+```
+
+And then we will define defferent metics to track in each of the domain:


~~metics~~ --> metrics

ishanSrt · 2018-05-09T17:08:58Z

cEP-0020.md

+
+### Gamification
+
+As we have already discuss the game elements involed in the gamification system, we will assign some points to each of the activities we will be tracking for a newcomer and then accordingly we will unlock the levels and provide them badges. now assuming the implementation of this process with [django-gamification](https://github.com/mattjegan/django-gamification) package, we need to link our `user` model to the gamification interface:


~~involed~~ --> involved

sks444 · 2018-05-10T17:40:33Z

Thanks, @andrewda, for the suggestions! :)

manankalra · 2018-05-10T20:12:38Z

cEP-0020.md

+
+## Abstract
+
+This cEP describe how a newcomer at coala will become a developer on the


manankalra · 2018-05-10T20:18:10Z

cEP-0020.md

+This cEP describe how a newcomer at coala will become a developer on the
+basis of their activities in the community.
+
+For the implementation of this process, we will build a gamification system


~~build~~ incorporate a gamification system in which we will allow us to track ...
^I find this better, optional, anyway ;)

manankalra · 2018-05-10T20:18:20Z

cEP-0020.md

+## Abstract
+
+This cEP describe how a newcomer at coala will become a developer on the
+basis of their activities in the community.


sorry for nitpicking: coala communnity

manankalra · 2018-05-10T20:20:53Z

cEP-0020.md

+basis of their activities in the community.
+
+For the implementation of this process, we will build a gamification system
+in which we will track newcomer progress and assign some points to each of the


newcomer progress makes no sense to me
maybe replace it with a newcomer's progress or progress of new contributors

manankalra · 2018-05-10T20:24:30Z

cEP-0020.md

+  - Talk to Docs team
+- How to improve newcomer -> dev/maintainer ratio
+- How to increase amount of feedback we get
+  - How to use feedback to improve coala and processes


What is this whole Newcomer Experience section about?

John said to add the newcomer bullet points from here as a background part.

You could copy edit them to make readable prose

And decide if any are beyond the scope of your project, maybe with a section or paragraph explicitly indicating what is out of scope.

manankalra · 2018-05-10T21:47:59Z

cEP-0020.md

+
+Assuming that we are using
+[django-trackstats](https://github.com/pennersr/django-trackstats) for tracking
+the statics of newcomers, then we will make different domains of similar set of


manankalra · 2018-05-10T21:54:45Z

cEP-0020.md

+level and the total number of points.
+
+These all are just basic ideas, the process and tasks in the levels can be
+changed according to the use case and implementaion process.


https://github.com/coala/cEPs/blob/master/cEP-0000.md mentions:

After specifying features with a cEP they should be implemented as specified. Unspecified features should not be implemented.

Although, I don't know how strict this practice is.

these are cEPs for GSoC projects so imo some changes during the course of the projects are inevitable

Yeah, all the ideas I have mentioned here is most probably confirm.
I was just saying we might change a few if we face some implementations difficulty, or if we don't have the good experience with a feature in the real world.

manankalra · 2018-05-10T21:58:35Z

cEP-0020.md

+for the sake of earning points, to avoid this type of spam we will use some
+of the ideas from **Meta-review system**, i.e.: We will also check the reactions
+on the comments and if it is Thumbs Down we will not give any points to the
+newcomers.


Still, the whole thread will be spammed and will become cumbersome to follow upon.
Maybe assigning negative points can be given a thought, which again can lead to certain kind of badges, followed by demotion or removal from the community. 😆

We have discussions about negative points and we will implement it if it will not be so hard to implement.

we will use some of the ideas from Meta-review system

err, you dont need to do that. that is a separate GSoC project this year, and it will be providing data to the community data model, which your gamification system will hopefully use and/or provide the data model for. You probably want to go look at that cEP.

manankalra · 2018-05-10T21:59:07Z

cEP-0020.md

+* Bad behavior message model
+
+So, before importing Gitter messages to our models we can check in which
+category this message fall? We can do that by applying


~~this~~ the

manankalra · 2018-05-10T22:06:32Z

cEP-0020.md

+certain number of questions in a day. Then we will track both the message model
+of the newcomer and assign some points to both separately and see which model
+metric has grown fast or slow while the whole newcomer process and not promote
+them until they have learned to learn things by themselves.


This whole sentiment analysis approach needs to be revised IMO and should be clearly stated. Whatever you have mentioned is a little vague, no?
How about Can you review this? ? Begging for a review + Includes a question mark.

Yeah, that was just an idea from my side. Would be great if you could suggest me some patterns in both the category. :)

will follow along during the implementation phase of this part. ;)

gitmate-bot · 2018-05-11T05:13:21Z

cEP-0020.md

+operation of the gamified environment. I.e.:
+
+- **Levels** group different tasks, enabling users to unlock specific and
+contextualized sets of actions. Levels will be applied to make newcomers


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpbdj_g1ue/cEP-0020.md +++ b/tmp/tmpbdj_g1ue/cEP-0020.md @@ -58,10 +58,10 @@ operation of the gamified environment. I.e.: - **Levels** group different tasks, enabling users to unlock specific and -contextualized sets of actions. Levels will be applied to make newcomers -focus on a given step before moving ahead on the contribution process. -We will divide our newcomer process into three levels and each level -will contain three tasks: + contextualized sets of actions. Levels will be applied to make newcomers + focus on a given step before moving ahead on the contribution process. + We will divide our newcomer process into three levels and each level + will contain three tasks: - Level-I: - Joining our gitter channel and the community

gitmate-bot · 2018-05-11T05:13:21Z

cEP-0020.md

+    - Reviewing at least one difficulty/low issue
+
+- **Points** will be the most applied element out of three game design elements.
+Acquiring points means that the actions performed by the users are in accordance


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpbdj_g1ue/cEP-0020.md +++ b/tmp/tmpbdj_g1ue/cEP-0020.md @@ -77,13 +77,13 @@ - Reviewing at least one difficulty/low issue - **Points** will be the most applied element out of three game design elements. -Acquiring points means that the actions performed by the users are in accordance -with what was expected. Points can be earned by means of performing actions to -the different tasks under levels. If a user wants to go to next level he -will have to collect a certain number of points from doing the tasks from the -previous level. But in case of Level-II and Level-III if a user is not able to -acquire the required number of points after performing all the tasks, he will have -to review more PRs to collect the required points. + Acquiring points means that the actions performed by the users are in accordance + with what was expected. Points can be earned by means of performing actions to + the different tasks under levels. If a user wants to go to next level he + will have to collect a certain number of points from doing the tasks from the + previous level. But in case of Level-II and Level-III if a user is not able to + acquire the required number of points after performing all the tasks, he will have + to review more PRs to collect the required points. - **Badges** enable newcomers to follow their performance and compare to other newcomers. **After completing the level three successfully the newcomer will be

gitmate-bot · 2018-05-11T05:13:22Z

cEP-0020.md

+to review more PRs to collect the required points.
+
+- **Badges** enable newcomers to follow their performance and compare to other
+newcomers. **After completing the level three successfully the newcomer will be


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpbdj_g1ue/cEP-0020.md +++ b/tmp/tmpbdj_g1ue/cEP-0020.md @@ -86,9 +86,9 @@ to review more PRs to collect the required points. - **Badges** enable newcomers to follow their performance and compare to other -newcomers. **After completing the level three successfully the newcomer will be -a developer**. And he will be awarded a badge based on their performance in each -level and the total number of points. + newcomers. **After completing the level three successfully the newcomer will be + a developer**. And he will be awarded a badge based on their performance in each + level and the total number of points. These all are just basic ideas; the process and tasks in the levels can be changed according to the use case and implementaion process.

gitmate-bot · 2018-05-11T05:13:23Z

cEP-0020.md

+can apply some extra rules on Gitter messages, we will divide our message model
+into two parts:
+
+* Good behavior message model


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpbdj_g1ue/cEP-0020.md +++ b/tmp/tmpbdj_g1ue/cEP-0020.md @@ -214,8 +214,8 @@ can apply some extra rules on Gitter messages, we will divide our message model into two parts: -* Good behavior message model -* Bad behavior message model +- Good behavior message model +- Bad behavior message model So, before importing Gitter messages to our models we can check in which category the message fall? We can do that by applying

gitmate-bot · 2018-05-11T05:13:24Z

cEP-0020.md

+
+Basically, we will define two dictionaries of good and bad messages.
+In the bad one, we will keep patterns like “please review [issue link]”,
+“updated [issue link]”, “have a look [issue link]”, “[mention] [issue link]”


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpbdj_g1ue/cEP-0020.md +++ b/tmp/tmpbdj_g1ue/cEP-0020.md @@ -224,7 +224,7 @@ Basically, we will define two dictionaries of good and bad messages. In the bad one, we will keep patterns like “please review [issue link]”, -“updated [issue link]”, “have a look [issue link]”, “[mention] [issue link]” +“updated [issue link]”, “have a look [issue link]”, “[mention][issue link]” etc. So, that a newcomer doesn’t beg for review all the time. In the good one, we will have the pattern of questions so we will generally match “?” in the end. But what happens if a newcomer started asking irrelevant

gitmate-bot · 2018-05-11T05:19:27Z

cEP-0020.md

+operation of the gamified environment. I.e.:
+
+- **Levels** group different tasks, enabling users to unlock specific and
+contextualized sets of actions. Levels will be applied to make newcomers


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpbdj_g1ue/cEP-0020.md +++ b/tmp/tmpbdj_g1ue/cEP-0020.md @@ -58,10 +58,10 @@ operation of the gamified environment. I.e.: - **Levels** group different tasks, enabling users to unlock specific and -contextualized sets of actions. Levels will be applied to make newcomers -focus on a given step before moving ahead on the contribution process. -We will divide our newcomer process into three levels and each level -will contain three tasks: + contextualized sets of actions. Levels will be applied to make newcomers + focus on a given step before moving ahead on the contribution process. + We will divide our newcomer process into three levels and each level + will contain three tasks: - Level-I: - Joining our gitter channel and the community

gitmate-bot · 2018-05-11T05:19:28Z

cEP-0020.md

+    - Reviewing at least one difficulty/low issue
+
+- **Points** will be the most applied element out of three game design elements.
+Acquiring points means that the actions performed by the users are in accordance


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpbdj_g1ue/cEP-0020.md +++ b/tmp/tmpbdj_g1ue/cEP-0020.md @@ -77,13 +77,13 @@ - Reviewing at least one difficulty/low issue - **Points** will be the most applied element out of three game design elements. -Acquiring points means that the actions performed by the users are in accordance -with what was expected. Points can be earned by means of performing actions to -the different tasks under levels. If a user wants to go to next level he -will have to collect a certain number of points from doing the tasks from the -previous level. But in case of Level-II and Level-III if a user is not able to -acquire the required number of points after performing all the tasks, he will have -to review more PRs to collect the required points. + Acquiring points means that the actions performed by the users are in accordance + with what was expected. Points can be earned by means of performing actions to + the different tasks under levels. If a user wants to go to next level he + will have to collect a certain number of points from doing the tasks from the + previous level. But in case of Level-II and Level-III if a user is not able to + acquire the required number of points after performing all the tasks, he will have + to review more PRs to collect the required points. - **Badges** enable newcomers to follow their performance and compare to other newcomers. **After completing the level three successfully the newcomer will be

gitmate-bot · 2018-05-11T05:19:29Z

cEP-0020.md

+to review more PRs to collect the required points.
+
+- **Badges** enable newcomers to follow their performance and compare to other
+newcomers. **After completing the level three successfully the newcomer will be


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpbdj_g1ue/cEP-0020.md +++ b/tmp/tmpbdj_g1ue/cEP-0020.md @@ -86,9 +86,9 @@ to review more PRs to collect the required points. - **Badges** enable newcomers to follow their performance and compare to other -newcomers. **After completing the level three successfully the newcomer will be -a developer**. And he will be awarded a badge based on their performance in each -level and the total number of points. + newcomers. **After completing the level three successfully the newcomer will be + a developer**. And he will be awarded a badge based on their performance in each + level and the total number of points. These all are just basic ideas; the process and tasks in the levels can be changed according to the use case and implementaion process.

gitmate-bot · 2018-05-11T05:19:30Z

cEP-0020.md

+can apply some extra rules on Gitter messages, we will divide our message model
+into two parts:
+
+* Good behavior message model


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpbdj_g1ue/cEP-0020.md +++ b/tmp/tmpbdj_g1ue/cEP-0020.md @@ -214,8 +214,8 @@ can apply some extra rules on Gitter messages, we will divide our message model into two parts: -* Good behavior message model -* Bad behavior message model +- Good behavior message model +- Bad behavior message model So, before importing Gitter messages to our models we can check in which category the message fall? We can do that by applying

gitmate-bot · 2018-05-11T05:19:31Z

cEP-0020.md

+
+Basically, we will define two dictionaries of good and bad messages.
+In the bad one, we will keep patterns like “please review [issue link]”,
+“updated [issue link]”, “have a look [issue link]”, “[mention] [issue link]”


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpbdj_g1ue/cEP-0020.md +++ b/tmp/tmpbdj_g1ue/cEP-0020.md @@ -224,7 +224,7 @@ Basically, we will define two dictionaries of good and bad messages. In the bad one, we will keep patterns like “please review [issue link]”, -“updated [issue link]”, “have a look [issue link]”, “[mention] [issue link]” +“updated [issue link]”, “have a look [issue link]”, “[mention][issue link]” etc. So, that a newcomer doesn’t beg for review all the time. In the good one, we will have the pattern of questions so we will generally match “?” in the end. But what happens if a newcomer started asking irrelevant

gitmate-bot · 2018-05-11T08:43:41Z

cEP-0020.md

+  We will divide our newcomer process into three levels and each level
+  will contain three tasks:
+
+    - Level-I:


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpsaib1jfs/cEP-0020.md +++ b/tmp/tmpsaib1jfs/cEP-0020.md @@ -63,18 +63,18 @@ We will divide our newcomer process into three levels and each level will contain three tasks: - - Level-I: - - Joining our gitter channel and the community - - Running CI tools on your fork - - Running coala-ci on a popular github repo - - Level-II: - - Getting assigned to a difficulty/newcomer issue - - Creating and merging PR for that issue - - Reviewing at least one difficulty/newcomer issue - - Level-III: - - Getting assigned to a difficulty/low issue - - Creating and merging a PR for that issue - - Reviewing at least one difficulty/low issue + - Level-I: + - Joining our gitter channel and the community + - Running CI tools on your fork + - Running coala-ci on a popular github repo + - Level-II: + - Getting assigned to a difficulty/newcomer issue + - Creating and merging PR for that issue + - Reviewing at least one difficulty/newcomer issue + - Level-III: + - Getting assigned to a difficulty/low issue + - Creating and merging a PR for that issue + - Reviewing at least one difficulty/low issue - **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance

gitmate-bot · 2018-05-11T08:55:20Z

cEP-0020.md

+  We will divide our newcomer process into three levels and each level
+  will contain three tasks:
+
+    - Level-I:


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpsaib1jfs/cEP-0020.md +++ b/tmp/tmpsaib1jfs/cEP-0020.md @@ -63,18 +63,18 @@ We will divide our newcomer process into three levels and each level will contain three tasks: - - Level-I: - - Joining our gitter channel and the community - - Running CI tools on your fork - - Running coala-ci on a popular github repo - - Level-II: - - Getting assigned to a difficulty/newcomer issue - - Creating and merging PR for that issue - - Reviewing at least one difficulty/newcomer issue - - Level-III: - - Getting assigned to a difficulty/low issue - - Creating and merging a PR for that issue - - Reviewing at least one difficulty/low issue + - Level-I: + - Joining our gitter channel and the community + - Running CI tools on your fork + - Running coala-ci on a popular github repo + - Level-II: + - Getting assigned to a difficulty/newcomer issue + - Creating and merging PR for that issue + - Reviewing at least one difficulty/newcomer issue + - Level-III: + - Getting assigned to a difficulty/low issue + - Creating and merging a PR for that issue + - Reviewing at least one difficulty/low issue - **Points** will be the most applied element out of three game design elements. Acquiring points means that the actions performed by the users are in accordance

gitmate-bot · 2018-05-11T11:32:41Z

cEP-0020.md

+
+So, before importing Gitter messages to our models we can check in which
+category the message fall? We can do that by applying
+[basic sentiment analysis](


The text does not comply to the set style.

Origin: MarkdownBear, Section: markdown.

The issue can be fixed by applying the following patch:

--- a/tmp/tmpysgsag5f/cEP-0020.md +++ b/tmp/tmpysgsag5f/cEP-0020.md @@ -219,8 +219,7 @@ So, before importing Gitter messages to our models we can check in which category the message fall? We can do that by applying -[basic sentiment analysis]( -http://fjavieralba.com/basic-sentiment-analysis-with-python.html) +[basic sentiment analysis](http://fjavieralba.com/basic-sentiment-analysis-with-python.html) on the messages. Basically, we will define two dictionaries of good and bad messages.

jayvdb · 2018-05-11T12:55:11Z

cEP-0020.md

+contribute to the community, to achieve this goal we have selected three
+game design elements to help newcomers: Levels, Points, and Badges. For
+each of these elements, we will have a set of rules to describe the
+operation of the gamified environment. I.e.:


jayvdb · 2018-05-11T13:43:50Z

cEP-0020.md

+For getting the stats of newcomer's messages, we will use
+[Gitter API](https://developer.gitter.im/docs/messages-resource) and import
+all the messages to newcomers or by newcomers in our webservices with some
+textual analysis for avoiding spam. And then we will import the final analysis


what is the benefit of avoiding spam. we dont get much of it, and it will be associated with users who dont contribute code (are not ever going to be developers), so it will just be a tiny bit of unfindable data in the DB that is never surfaced on the website.

IMO not worth the effort of removing it.

It is easier for us to remove real spam from gitter by deleting the messages.

jayvdb · 2018-05-11T13:46:41Z

cEP-0020.md

+[Gitter API](https://developer.gitter.im/docs/messages-resource) and import
+all the messages to newcomers or by newcomers in our webservices with some
+textual analysis for avoiding spam. And then we will import the final analysis
+of the messages to our community repo for tracking and gamification process.


the analysis, and algorithms, belong in the community repo, as that is where you have the django gamification tools.

jayvdb · 2018-05-11T13:46:55Z

cEP-0020.md

+textual analysis for avoiding spam. And then we will import the final analysis
+of the messages to our community repo for tracking and gamification process.
+
+We will have different django models for each category like for GitHub/GitLab


this paragraph doesnt belong in the 'Gitter' section.

jayvdb · 2018-05-11T13:51:34Z

cEP-0020.md

+for the sake of earning points, to avoid this type of spam we will use some
+of the ideas from **Meta-review system**, i.e.: We will also check the reactions
+on the comments and if it is Thumbs Down we will not give any points to the
+newcomers.


we will use some of the ideas from Meta-review system

err, you dont need to do that. that is a separate GSoC project this year, and it will be providing data to the community data model, which your gamification system will hopefully use and/or provide the data model for. You probably want to go look at that cEP.

jayvdb · 2018-05-11T14:13:54Z

cEP-0020.md

+As the goal of this project is to make use of metrics and gamification to
+motivate and support newcomers to overcome the orientation barriers and
+contribute to the community, to achieve this goal we have selected three
+game design elements to help newcomers: Levels, Points, and Badges. For


I think we need to "Activities" here too. As I understand it, they are the raw actions.

And I am not understanding the way they are all related.

A worked example would be helpful.

What is the relationship between Activities and Points. Is each activity given a configurable number of points?

jayvdb · 2018-05-11T14:26:35Z

cEP-0020.md

+  able to acquire the required number of points after performing all the tasks,
+  he will have to review more PRs to collect the required points.
+
+- **Badges** enable newcomers to follow their performance and compare to other


We should be modeling badges based on https://openbadges.org/ , where they are a visual representation of learning outcomes achieved, and those are not necessarily coala specific.

As a result, each badge would be a predefined grouping of activities, possibly requiring the activities have been done several times.

'coala Developer' would be one coala specific badge, and we would need to version that badge, as the definition of that badge would change over time.

But most newcomers would work towards more basic badges like 'git beginner' , 'git rebaser', 'markdown editor', 'markdown reviewer', 'python coder basic', 'python reviewer', 'JS coder basic', 'JS reviewer'. Those are badges they can 'take' with them even if they have no intention of becoming a 'coala developer'.

jayvdb · 2018-05-11T14:27:26Z

cEP-0020.md

+
+- **Badges** enable newcomers to follow their performance and compare to other
+  newcomers. **After completing the level three successfully the newcomer will
+  be a developer**. And he will be awarded a badge based on their performance


I really dont get this sentence (or the previous one in bold).

based on on their performance ..

Is that automated, or are badges manually awarded?

If automated, how is performance measured?

Is performance different from points?

jayvdb · 2018-05-11T14:33:40Z

cEP-0020.md

+  be a developer**. And he will be awarded a badge based on their performance
+  in each level and the total number of points.
+
+These all are just basic ideas; the process and tasks in the levels can be


this cEP needs to describe precisely what the community will be able to do with the result of this project.

Specifically, we need an example definition of a 'coala developer' and how the newcomer gets there.

And, what alternative definitions of a 'coala developer' will be possible without new coding. i.e. how configurable will this be.

And, what are the intermediary items a newcomer can 'earn' in this system on their pathway to 'coala developer'. If the system is very configurable, the cEP may not describe every pathway as each person will travel their own different path.

jayvdb · 2018-05-11T14:35:46Z

cEP-0020.md

+These all are just basic ideas; the process and tasks in the levels can be
+changed according to the use case and implementaion process.
+
+A similar process can also be extended and applied to developers to achieve more


This sentence needs to be adjusted to indicate that post-developer is out of scope for this project, but it is right to say that this project could be used in the future to build something similar for developers.

sks444 · 2018-05-11T23:34:43Z

@jayvdb, I have revised the whole idea part from the beginning, please have a look.

prnvdixit

@sks444 This is great! Just some points from my side.

Also, these review comments don't expect any change in cEP - Just some implementation details/challenges. 😄

prnvdixit · 2018-05-12T03:34:32Z

cEP-0020.md

+newcomers to take. i.e.:
+
+- Created Issues by a Newcomer
+- Created Pull Requests by a Newcomer


Misusing by making excessive PRs (knowingly or unknowingly)?

Ya we need to track closed-not-merged PRs

" by a Newcomer" - eh ... this cEP is all about newcomers, so why mention it here and in other activities?

non-Newcomer stuff is out of scope for your project.

@prnvdixit @sks444 , yes we need to think about abuse. I've mentioned it frequently, but it isnt dealt with in detail in the cEP yet, probably as the bottom half hasnt been overhauled yet.

The problem is where do we record abusing behaviour so that this system can use it. Obtaining a feed of feedback from corobo is possible approach, but corobo is currently not storing state, and I doubt we would do that.

Meta-review provides a lot of opportunity for storing state, but it doesnt cover everything. It especially does not cover gitter/IM behaviour.
We may want to look at replies to a newcomer IM messages as a way to create a feedback loop there.

One concern with the schema design below is that the points dont seem to link to specific actions, so it wont be possible to use the data to see which actions counted and which ones didnt, which makes it harder to diagnose why a score isnt as high as it should be, which becomes especially relevant if there are rules aimed at preventing scores for potentially abuse behaviour.

One concern with the schema design below is that the points dont seem to link to specific actions, so it wont be possible to use the data to see which actions counted and which ones didnt, which makes it harder to diagnose why a score isnt as high as it should be,

This gets me to thinking - Shouldn't there be any logs being maintained for all increments/decrements of points (I'm thinking of a possibility if something goes wrong, we can just use (maybe manually) some deferred or immediate modification recovery)?

prnvdixit · 2018-05-12T03:38:47Z

cEP-0020.md

+- Created Pull Requests by a Newcomer
+- Number of Gitmate errors on the PR
+- CI status of the PR
+- Number of reviews done by a Newcomer


Spammy reviews - Things which does count as a review but isn't actually a review to be specific. Eg. Just adding a review Check coala.io/commit. would be suitable for most of newcomer PRs. Valid but insufficient review.
Adding this is not necessarily part of the goal ^^ 😅

Yeah, Spammy reviews will be covered in the meta review projcet #131 (comment)

I'll look at that cEP as well then in a day or two, travelling rn 😅

prnvdixit · 2018-05-12T03:39:45Z

cEP-0020.md

+- Number of Gitmate errors on the PR
+- CI status of the PR
+- Number of reviews done by a Newcomer
+- Number of comments in one review by a Newcomer


Some people can just review for the sake of points - As @prnvdixit said in his review......... Maybe add a system to allow PR owner to give points to the reviewer?

Yeah, I also had an idea for that is to also check the reactions on the review comments, E.g.: if its thumbs up, we will assign him the points and vice versa, But this thing is taking into consideration in the very vague way in the meta-review project and as John said here

it will be providing data to the community data model

Makes sense then 😄

prnvdixit · 2018-05-12T03:43:05Z

cEP-0020.md

+    - Review at least a difficulty/low or higher Pull Request
+
+So, for becoming a developer at coala, a newcomer must complete all the
+activities mentioned in the `coala Developer` badge. But in case


Did you accidentally omit something here? The sentence is incomplete. 😄

prnvdixit · 2018-05-12T03:47:10Z

cEP-0020.md

+In the good one, we will have the pattern of questions so we will generally
+match “?” in the end. But what happens if a newcomer started asking irrelevant
+questions? So for that, we can also define a rule like a newcomer can only ask a
+certain number of questions in a day. Then we will track both the message model


Umm... "certain" seems a bit "harsh" - No? I mean everyone does ask a lot of questions during onboarding phase. 😅

prnvdixit · 2018-05-12T03:53:24Z

Are we thinking of an easy (maybe private to repo owners) way of decrementing someone's points in case some abuse is detected? Easy, so that it's not much of a hassle for the maintainer to do so - Maybe a corobo command for maintainers/owners only.
@jayvdb - Thoughts?
(Also helpful if someone (maybe owner himself) is getting troubled (maybe on personal gitter chat) and is brought to notice of maintainers)

jayvdb · 2018-05-13T09:20:11Z

cEP-0020.md

+For the implementation of this process, we will incorporate a gamification
+system which will allow us to track newcomer's progress and assign some
+points to each of the activity they do. We will also have different levels
+and give them badges on the basis of points earned and performed activities


badges on the basis of points earned and performed activities

Im not sure about this.

badges are about skills, and points are not.

It should at least be

badges on the basis of performed activities and points given for those activities.

Or

badges on the basis of how many times they have performed an activity.

jayvdb · 2018-05-13T09:23:28Z

cEP-0020.md

+As coala tries to be a welcoming organization for newcomers, it gives them
+clear pathways and as much direct assistance as possible. However, it is
+already known that newcomers face many barriers while attempting to contribute
+to the open source community for the first time. Some barriers they face include


to the open source community for the first time.

to open source for the first time, and additional barriers while attempting to contribute to projects run by the coala organisation.

The next sentence (Some barriers) is better as a new paragraph as it moves from broad&vague to specific information

jayvdb · 2018-05-13T09:26:55Z

cEP-0020.md

+build a gamified design. The first step is to define the activities that we want
+newcomers to take. i.e.:
+
+- Created Issues by a Newcomer


In the paragraph above you talk about rules, and points, but dont define any rules, or how points are calculated.

The first real specific information here is ... these activities.

We will be recording how many issues the person creates?
If so, that is the most basic element in the design.

Create a separate section for Activities, put it before all of this points, levels, badges stuff.

jayvdb · 2018-05-13T09:27:41Z

cEP-0020.md

+newcomers to take. i.e.:
+
+- Created Issues by a Newcomer
+- Created Pull Requests by a Newcomer


" by a Newcomer" - eh ... this cEP is all about newcomers, so why mention it here and in other activities?

non-Newcomer stuff is out of scope for your project.

jayvdb · 2018-05-13T09:32:39Z

cEP-0020.md

+- Activities on Gitter channels
+- Introduce `.coafile` in other projects
+
+Then we will assign some points to each of the activity a newcomer perform.


who is "we". Remove that word everywhere. Be specific about who will do this, even if it is only 'the organisation' vs 'this project'.

i.e. does this project define these values, or will the organisation be able to configure it? Will the organisation be able to change these values any time they like?

jayvdb · 2018-05-13T09:36:32Z

cEP-0020.md

+  - Reviewing at least one difficulty/low issue
+
+But that would be hard to implement and out of the scope of this project
+as we can't automatically prevent newcomers from performing the activities


as we can't automatically prevent newcomers ...

This is not relevant to gamification. It is not expected that participants do not do all activities in order; it is expected that the gamification changes their level when they have met the pre-reqs, irrespective of what additional activities they have done which are not related to the next level they are seeking.

jayvdb · 2018-05-13T09:44:25Z

cEP-0020.md

+- Badge-III:
+  - Name: The coder
+  - Details: The one who code
+  - Activity: Merged at least 3 or more PRs


This Activity / Activities item is the important one.

To begin with, if it can include multiple, then it should always be Activities: and have sub-items underneath it.

It should use the same activity name as mentioned in the activities listed earlier, with a note that it needs to have been done three times.

jayvdb · 2018-05-13T09:47:31Z

cEP-0020.md

+- Badge-II:
+  - Name: The reviewer
+  - Details: The one who review others pull requests
+  - Activities: Reviewed at least 4 or more PRs


bad example at the moment, as reviews will rely on meta-review.

IMO replace this badge with something else, or just remove it.

jayvdb · 2018-05-13T09:50:08Z

cEP-0020.md

+  - Name: High
+  - Points_required = 300
+
+More complex designs, such as awarding levels based on consecutive activities


If levels can be achieved by doing a set of activities, how does that differ from a badge? When should we use a level vs a badge?

If level is only points based, people will expect to be able to compare the levels sanely. Two different newcomers doing different types of activities might have similar points - ensuring they are on a similar level depends on getting the points allocation correct. ouch.

If level is only points based, the proposed model is quite similar to stackoverflow with

points - reputation,

badges (customised sets of pre-reqs),

and privileges (point count thresholds)

I think most people earn badges and privileges on stackoverflow at roughly the same rate, but I guess some people might get lots of points without getting new badges.

If we are doing points only levels, we probably want to do the same as stackoverflow, allocating privileges to point thresholds, otherwise these levels are not very valuable.
This means people dont try to compare the effort by two people with similar levels -- when a person gets new privileges they usually start using them, and become more active. As the levels in stackoverflow have exponentially increasing thresholds, two people on the same level are busy trying to use those privileges to get to the next level.

If we dont allocate some value to these points thresholds, people will only aim for the badges.

What privileges could we give to them in each of the levels?

The one I could think of is to give them permission to use corobo after the completion of level one?

Also, it would be good to have some privileges after a newcomer has earned the coala Developer badge.

Another one suggested by @ishanSrt:

Give permission to ping maintainers on gitter after some points threshold.

jayvdb · 2018-05-13T10:17:58Z

cEP-0020.md

+newcomers to take. i.e.:
+
+- Created Issues by a Newcomer
+- Created Pull Requests by a Newcomer


@prnvdixit @sks444 , yes we need to think about abuse. I've mentioned it frequently, but it isnt dealt with in detail in the cEP yet, probably as the bottom half hasnt been overhauled yet.

The problem is where do we record abusing behaviour so that this system can use it. Obtaining a feed of feedback from corobo is possible approach, but corobo is currently not storing state, and I doubt we would do that.

Meta-review provides a lot of opportunity for storing state, but it doesnt cover everything. It especially does not cover gitter/IM behaviour.
We may want to look at replies to a newcomer IM messages as a way to create a feedback loop there.

One concern with the schema design below is that the points dont seem to link to specific actions, so it wont be possible to use the data to see which actions counted and which ones didnt, which makes it harder to diagnose why a score isnt as high as it should be, which becomes especially relevant if there are rules aimed at preventing scores for potentially abuse behaviour.

sks444 · 2018-05-13T20:22:53Z

Migrate to #150

gitmate-bot added process/pending review size/S labels May 9, 2018

gitmate-bot reviewed May 9, 2018

View reviewed changes

jayvdb added process/wip and removed process/pending review labels May 9, 2018

gitmate-bot added process/pending review and removed process/wip labels May 9, 2018

gitmate-bot reviewed May 9, 2018

View reviewed changes

ishanSrt reviewed May 9, 2018

View reviewed changes

manankalra suggested changes May 10, 2018

View reviewed changes

gitmate-bot reviewed May 11, 2018

View reviewed changes

jayvdb added process/wip and removed process/pending review labels May 11, 2018

gitmate-bot added process/pending review and removed process/wip labels May 11, 2018

gitmate-bot reviewed May 11, 2018

View reviewed changes

jayvdb requested changes May 11, 2018

View reviewed changes

cEP-0020: Newcomer metrics and Gamification system

0cc5775

prnvdixit reviewed May 12, 2018

View reviewed changes

jayvdb requested changes May 13, 2018

View reviewed changes

jayvdb added process/wip and removed process/pending review labels May 13, 2018

sks444 closed this May 13, 2018

sks444 mentioned this pull request May 14, 2018

cEP-0020: Newcomer metrics and Gamification system #150

Merged


		After we have the data, we need to track some important activities of newcomers like:

		* Created Issues

		@@ -0,0 +1,167 @@
		# Newcomer metrics and Gamification

		\| Metadata \| \|


		## Why Gamification?

		As coala tries to be welcoming organization for newcomers, giving them clear pathways and as much direct assistance as possible. However, it is already known that newcomers face many barriers while attempting to contribute to the open source community for the first time. Some barriers they face include orientation issues that can potentially demotivate newcomers from placing their first contribution. On the other hand, gamification is widely used to engage and motivate people to accomplish task and improve their performance.Therefore, the goal of this project is to use gamification to orient and motivate newcomers to overcome onboarding barriers to contribute and engage with coala and its community.


		## Process involved in the Gamification system

		As the goal of this project is to make use of metrics and gamification to motivate and support newcomers to overcome the orientation barriers to contribute to the community.


		These all are just basic ideas, the process and tasks in the levels can be changed according to the use case and implementaion process.

		A similar process can also be extended and applied to developers to achieve more number of badges or something more.


		### Gamification

		As we have already discuss the game elements involed in the gamification system, we will assign some points to each of the activities we will be tracking for a newcomer and then accordingly we will unlock the levels and provide them badges. now assuming the implementation of this process with [django-gamification](https://github.com/mattjegan/django-gamification) package, we need to link our `user` model to the gamification interface:


		## Abstract

		This cEP describe how a newcomer at coala will become a developer on the

cEP-0020: Newcomer metrics and Gamification system #131

cEP-0020: Newcomer metrics and Gamification system #131

Conversation

sks444 commented May 9, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sks444 commented May 10, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

manankalra May 10, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sks444 commented May 11, 2018

prnvdixit left a comment • edited Loading

manankalra May 10, 2018 •

edited

Loading

prnvdixit left a comment •

edited

Loading