Skip to content

Commit 5746535

Browse files
jaskiratsingh2000gitbook-bot
authored andcommitted
GitBook: [master] 3 pages modified
1 parent 60dbde0 commit 5746535

File tree

3 files changed

+28
-22
lines changed

3 files changed

+28
-22
lines changed
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,36 @@
11
# Badge and point allotment Api
22

3-
Priority:- High
3+
### Priority:
44

5-
\*\*\*\*
5+
High
66

7-
## Summary
7+
### Description:
88

9-
In Codebadge, presently all the badge allotment computation are taking place at browser level. We require to shift all the badge related computation at backend using nodejs API. The task to be preformed under this task are:-
9+
#### Summary
10+
11+
In Codebadge, presently all the badge allotment computation are taking place at browser level. We require to shift all the badge related computation at back-end using nodejs API. The task to be preformed under this task are:-
1012

1113
* Designing a database schema to manage user points for projects and organization, storing badge templates in efficient manner, storing admin defined pattern for awarding badges and special badges.
12-
* Design a badge allotment api which shall fulfill following criterias:-
13-
* Admin can decide the count of points for alloting points.
14-
* Using Machine Learning allocating points as per past relatable issues.
14+
* Design a badge allotment API which shall fulfill following criteria's:-
15+
* Admin can decide the count of points for allotting points.
16+
* Using Machine Learning allocating points as per past relocatable issues.
1517
* Designing a special badge allotment system which can be decided by the admin while creating an account.
16-
* Designing an api system which returns renderable badges. Badges must be saved in minified format which shall be improved in quality and size on rendering time.
18+
* Designing an API system which returns render-able badges. Badges must be saved in minified format which shall be improved in quality and size on rendering time.
1719
* Creating shareable illustrator system which admin can only share with his organization contributors using email/github username.
18-
* Fetching contribution outside browser without using cron jobs approach which makes the computation speed slower.
20+
* Fetching contribution outside browser without using crone jobs approach which makes the computation speed slower.
1921

20-
**Required Skills/knowledge:**
22+
### **Required Skills/knowledge:**
2123

2224
* Good knowledge of databases
2325
* languages such as NodeJs
2426
* experience of working sockets programming and using github apis
2527
* Good Knowledge of Modules Bundling
2628

27-
#### Difficulty Level: Moderate
29+
### Difficulty Level:
30+
31+
Moderate
32+
33+
### Potential Mentors:
34+
2835

29-
#### Mentors
3036

activities/gsoc2020/gsoc2020-ideas/draft-bot-for-donut-platform.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -50,5 +50,5 @@ Hard
5050

5151
### **Potential Mentors:**
5252

53-
\*\*\*\*[**Jaskirat Singh**](https://github.com/jaskirat2000) ****and ****[**Devesh Verma**](https://github.com/devesh-verma) ****
53+
[**Devesh Verma**](https://github.com/devesh-verma) **and** [**Lakshya Khera**](https://github.com/lakshyabatman)\*\*\*\*
5454

activities/gsoc2020/gsoc2020-ideas/role-management.md

+9-9
Original file line numberDiff line numberDiff line change
@@ -11,15 +11,15 @@ High
1111
Development of configuration mechanism is one of our newest additions to our installation frameworks of Donut Platform. Currently Donut is central hosted but aims to get bundled as FOSS/OSS tool. So, the task of this major project is to develop an **Admin Management System** that will allow individuals or community admins to setup for themselves. To simplify the configuration, these predefined modules will have the most common use cases with different options for modules and settings while setting up this environment.Few have been described below which would serve essential features as a separate modules:
1212

1313
1. Development of module for Configuration screens :
14-
2. **Screen 1:** Registering Admin account with information such as Admin name, Email, Username, Password, etc. For example check [**here**](https://www.tecmint.com/wp-content/uploads/2018/05/Create-New-Discourse-Account.png)
15-
3. **Screen 2:** Include Admin Account Confirmation through email. An email send to the Admin account, On confirmation should redirect them to the page of "Activate Account" which further leads to other setup.
16-
4. **Screen 3:** Welcoming Screen, that should allow to setup Community account. For hint check [**here**](https://support.patreon.com/hc/article_attachments/360027026912/Image_2019-04-24_at_9.25.35_AM.png)
17-
5. **Screen 4:** Setting up Community profile and permissions like Community Name, Description,Welcoming Invites, Access \( Is community open to everyone or limited to invites,etc. \), Automated Invites, System Email setup, etc.
18-
6. **Screen 5:** This screen includes **View** are from User end that how the Admins want their platform to look like. This will have custom things like Theme Selection, Community Top bar \( Including Logos\), home page look, some other modules. **\(Important Part !\)**
19-
7. **Screen 6:** Includes the Thumbnail or the preview of the main page based upon the settings configured by Admin.
20-
8. Development of Admin panel :
21-
22-
This will include building of Admin panel or dashboard which will be visible to them after configuring the Donut Platform on their server.
14+
15+
* **Screen 1:** Registering Admin account with information such as Admin name, Email, Username, Password, etc. For example check [**here**](https://www.tecmint.com/wp-content/uploads/2018/05/Create-New-Discourse-Account.png)
16+
* **Screen 2:** Include Admin Account Confirmation through email. An email send to the Admin account, On confirmation should redirect them to the page of "Activate Account" which further leads to other setup.
17+
* **Screen 3:** Welcoming Screen, that should allow to setup Community account. For hint check [**here**](https://support.patreon.com/hc/article_attachments/360027026912/Image_2019-04-24_at_9.25.35_AM.png)
18+
* **Screen 4:** Setting up Community profile and permissions like Community Name, Description,Welcoming Invites, Access \( Is community open to everyone or limited to invites,etc. \), Automated Invites, System Email setup, etc.
19+
* **Screen 5:** This screen includes **View** are from User end that how the Admins want their platform to look like. This will have custom things like Theme Selection, Community Top bar \( Including Logos\), home page look, some other modules. **\(Important Part !\)**
20+
* **Screen 6:** Includes the Thumbnail or the preview of the main page based upon the settings configured by Admin.
21+
22+
2. Development of Admin panel :
2323

2424
* Admins can add members to the community through Invites, also can invite other as an Admin/moderator due which all the same rights will be shared with the other person.
2525
* Blocking users \( Giving access to block people\)

0 commit comments

Comments
 (0)