## Permissions
---
| First Header | Second Header |
| ------------- | ------------- |
| Content Cell | Content Cell |
| Content Cell | Content Cell |

<table>
 <tr>
 <td>Org Admin

View
 </td>
 <td>Team Manager (for assigned team)

View
 </td>
 <td>Org Contributor

View
 </td>
 <td>External Contributor

No access
 </td>
 </tr>
</table>



## Cycle Time

_Add a screenshot of the chart (trim dates, title)_


### Get answers to the following questions:



1. How are the activities/contributions going (trending up or down) for the organization/team? 

3. What team/contributor is below average? What is above?


### Recommended actions:



1. Discuss on retrospective or/and on 1-2-1s:
 * How to help contributors below average and with trends strongly going down. Keep in mind day-offs, vacations, etc.
 
 * The possibility to scale the actions made trends go up for specific teams/contributors.
2. Actualize the Alert thresholds for instant notifications about activity bottlenecks.


## Coding Time

_Add a screenshot of the chart (trim dates, title)_


### Get answers to the following questions:



1. What type of contribution is dominating for a specific team/contributor?
2. Do you need to rebalance the attention of contributors to other types of contributions?
3. Do you have enough team members to perform Code Review efficiently?

5. Are commits and pull requests balanced? Or do you need to correct the work chunks teams are operating?
6. Is there a known reason for someone strongly ahead or behind the rest of the team?


### Recommended actions:



1. Discuss the insights on retrospective.

3. Make sure all team members are familiar with the analytics.
4. Ask for the reasons and proposals from contributors strongly below average.
5. Use team and individual Challenge thresholds to set appropriate goals and forward attention to necessary types of contributions.
6. Make sure alert thresholds are actualized to get the instant notification and make corrections right away not at the end of the period.


## Pickup Time

_Add a screenshot of the chart (trim dates, title)_


### Get answers to the following questions:



1. What days are likely to be more/less active? 
2. What period likely was a vacation period?

4. How does the team structure impact the activity over a longer period?


### Recommended actions:



1. Consider the meetings list for the less active days of the week.

3. Plan the vacation schedule ahead.


## Review Time

_Add a screenshot of the chart (trim dates, title)_


### You may get answers to the following questions:



1. What days are likely to be more/less active? 
2. What period likely was a vacation period?

4. How does the team structure impact the activity over a longer period?


### Recommended actions:



1. Consider the meetings list for the less active days of the week.

3. Plan the vacation schedule ahead.


## Deploy Time (coming soon)

_Add a screenshot of the chart (trim dates, title)_


### You may get answers to the following questions:



1. What days are likely to be more/less active? 

3. What period likely was a vacation period?
4. How does the team structure impact the activity over a longer period?


### Recommended actions:



1. Consider the meetings list for the less active days of the week.

3. Plan the vacation schedule ahead.


## Recommendations



* Use filters by repository, and label to identify work quality metrics for specific segments of your project

* Consider challenges related to cycle time, and review time to impact metrics


## See also



* [XP (Contribution Score)](https://devactivity.com/help/contribution-score)

* [What is Cycle Time?](https://devactivity.com/help/cycle-time)
* [What is Coding Time?](https://devactivity.com/help/coding-time)
* [What is Pickup Time?](https://devactivity.com/help/pickup-time)
* [What is Review Time?](https://devactivity.com/help/review-time)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Work Quality Analytics

## Public Repositories (Open Source)


### What to expect after devActivity app installation?



1. Account created, devActivity [processes repository metadata for contributions](https://devactivity.com/help/repository-metadata).
2. Based on contributions each contributor is [rewarded with XP](https://devactivity.com/help/xp-levels).
3. Based on XP appropriate [Level](https://devactivity.com/help/xp-levels) is assigned.
4. [20+ Challenges](https://devactivity.com/help/configureChallenges) available to complete: 
 * One-time
 
 * Monthly
 * Accumulative 
5. [Public Dashboard](https://devactivity.com/help/publicDashboard) with Leaderboard and other widgets available.
6. Org Contributors get email invitations to access devActivity. [Who is an Org Contributor?](https://devactivity.com/help/roles-and-permissions)

8. Pull Requests will be [commented on by devActivity bot](https://devactivity.com/help/settings) with the following: 
 * Summary comment after merge
 
 * Completed challenges comment
8. Pull Request comments include the Sign Up link to invite participated External Contributor to track progress with devActivity. [Who is a External Contributor?](https://devactivity.com/help/roles-and-permissions)

After signing up Org Contributors get:



1. [Organization Dashboard](https://devactivity.com/help/dashboard).

3. Detailed [Contributions](https://devactivity.com/help/contributions), [Work Quality](https://devactivity.com/help/workQuality) (Cycle Time and more), [Contributors](https://devactivity.com/help/contributors), and [Discussions](https://devactivity.com/help/discussions) reports.
4. [Alerts](https://devactivity.com/help/discussions), [Active Challenges](https://devactivity.com/help/activeChallenges), [Leaderboard](https://devactivity.com/help/leaderboard), and more.

After signing up External Contributors get:



1. [Personal Dashboard](https://devactivity.com/help/dashboard) to track own progress.
2. [Monthly Report](https://devactivity.com/help/settings).

4. [Personal Embeddables](https://devactivity.com/help/embeddables).


### What to do to make even more impact?


#### Community Communication



1. Community Announcement:
 * Discussions – _sample message_
 
 * Group Chat messages (Slack, Discord, etc) – _sample message_
2. Communicate valuable inactive contributors:
 * Direct contact (email, chat) – _sample message_
 
 * Tag under their PR, issues – _sample message_
3. Useful Resources:
 * [Contribution Score and XP](https://devactivity.com/help/contribution-score)
 * [XP to Levels Table](https://devactivity.com/help/xp-levels)
 
 * [Challenges Reward Types](https://devactivity.com/help/configureChallenges)
4. Engage Feedback and Open Discussion.


#### README file improvements



1. Contributing section update (or create) – _sample message_. Add a short message about Gamification and link to CONTRIBUTING.md
2. Add a kind of shield at the top to attract – _sample message_

4. [Embed](https://devactivity.com/help/embeddables) widgets:
 * Top Contributors
 * Repo Stats
 * Cycle Time


#### CONTRIBUTING file improvements



1. Add shield – _sample message_

3. Add Gamification section – _sample message_


### How to keep the community engaged with gamification?



1. Track the trend of the contribution with [Contributors](https://devactivity.com/help/contributors) report.
2. Configure [Alerts](https://devactivity.com/help/alertsConfig) targets suitable for your project and process. Recommended to consider:
 * No activity from Contributor for X working days
 * No reviewer assigned to PR for X hours
 * More than X hours for PR's Pickup Time
 
 * More than X comments for a single PR
 * More than X comments for a single issue
3. Track the challenge's [progress](https://devactivity.com/help/activeChallenges), and [keep goals actual](https://devactivity.com/help/configureChallenges).
4. Assign [custom achievements](https://devactivity.com/help/customAchievements) for community heroes.
5. Use [custom challenges](https://devactivity.com/help/custom-challenges) for some issues with higher complexity or scope. One per week or a few per month is recommended.

7. Ask to share the ideas for new challenges/achievements.


## Private Repositories


### What to expect after devActivity app installation?



1. Account created, devActivity [processes repository metadata for contributions](https://devactivity.com/help/repository-metadata).

3. Based on contributions each contributor is [rewarded with XP](https://devactivity.com/help/xp-levels).
4. Based on XP appropriate [Level](https://devactivity.com/help/xp-levels) is assigned.
5. [20+ Challenges](https://devactivity.com/help/configureChallenges) available to complete: 
 * One-time
 * Monthly
 
 * Accumulative 
5. [Public Dashboard](https://devactivity.com/help/publicDashboard) with Leaderboard and other widgets available.

7. Org Contributors get email invitations to access devActivity. [Who is an Org Contributor?](https://devactivity.com/help/roles-and-permissions)
8. Pull Requests will be [commented on by devActivity bot](https://devactivity.com/help/settings) with the following: 
 * Summary comment after merge
 
 * Completed challenges comment


### What to do to make even more impact?



1. Community Communication / Team Announcement:
 * Email – _sample message_
 
 * Group Chat messages (Slack, Discord, etc) – _sample message_
2. Useful Resources:
 * [Contribution Score and XP](https://devactivity.com/help/contribution-score)
 * [XP to Levels Table](https://devactivity.com/help/xp-levels)
 
 * [Challenges Reward Types](https://devactivity.com/help/configureChallenges)
3. Engage Feedback and Open Discussion.


### What are additional motivations based on Contribution progress?


#### Meaningful Rewards



1. Offer rewards that are appealing and relevant to your audience. Provide both intrinsic rewards (recognition, status) and extrinsic rewards (discounts, merchandise). Here are some general ideas:
 * **Professional Development Opportunities** – reward developers with access to conferences, workshops, or online courses to enhance their skills and stay updated on industry trends.
 
 * **Flexible Work Arrangements** – offer the flexibility to work remotely, choose preferred work hours, or participate in a "hackathon" week where developers can work on innovative projects.
 * **Recognition and Visibility** – showcase top-performing developers on the company website, in newsletters, or during team meetings, providing public recognition for their achievements.
 * **Gadget or Tech Gear Allowance** – provide a budget for developers to purchase gadgets, tech gear, or software tools that contribute to their productivity and enjoyment.
 * **Extra Vacation Days** – grant additional vacation days as a reward for reaching specific XP milestones or completing challenging projects.
 * **Personalized Workspace Upgrades** – allow developers to upgrade their workstations with customized equipment, ergonomic furniture, or personalized decorations based on their preferences.
 * **Team Outings or Retreats** – organize team-building activities, outings, or retreats as a reward for achieving collective goals or milestones.
 * **Wellness Programs** – introduce wellness programs such as gym memberships, meditation sessions, or health-related workshops to support the physical and mental well-being of developers.
 * **Special Project Opportunities** – provide the opportunity to work on special projects, research initiatives, or innovation labs as a reward for reaching higher levels or demonstrating exceptional skills.
 * **Profit-Sharing or Bonuses** – implement a profit-sharing system or provide bonuses based on individual or team achievements, encouraging a sense of shared success.
2. And few ideas for merchandise:
 * **Customized Developer Swag** – design and offer exclusive swag items such as T-shirts, hoodies, or caps featuring a unique design that represents the development team or achievement levels.
 * **Stylish Laptop Stickers** – create a set of high-quality laptop stickers that developers can proudly display to showcase their achievements, levels, or special accomplishments.
 * **Tech Accessories Bundle** – bundle together useful tech accessories like mouse pads, phone stands, and cable organizers with custom branding related to the gamification elements.
 * **Customized Water Bottles or Mugs** – provide durable water bottles or coffee mugs featuring custom designs, achievement badges, or level indicators to make a functional yet personalized reward.
 
 * **Premium Quality Notebooks** – offer high-quality notebooks or journals with custom covers and pages, creating a branded space for developers to jot down ideas, notes, or project plans.
 * **Branded USB Drives** – design USB drives with the company or gamification branding, possibly pre-loaded with development resources, tools, or exclusive content as a bonus.
 * **Game-themed Desk Toys** – introduce unique desk toys or figurines related to gaming or coding, adding a playful touch to developers' workspaces.
 * **Quality Backpacks or Tech Bags** – provide durable backpacks or tech bags with custom embroidery or patches indicating different levels or achievements in the gamification system.
 * **Exclusive Developer Pins** – create a collection of collectible enamel pins that developers can proudly display on their clothing or accessories, each representing a specific achievement or milestone.
 
 * **Limited Edition Art Prints** – commission or create limited edition art prints featuring custom artwork related to the gamification elements, allowing developers to decorate their workspaces with unique pieces.
 
3. Make a real-world impact. Connect gamification achievements to real-world benefits or social causes. Tie accomplishments to tangible outcomes, such as charity donations or community projects.


### How to keep the team engaged with gamification?



1. **Personal Development Opportunities**. Integrate gamified elements that contribute to the team's professional development. Offer opportunities for skill-building and growth through the gamified system.

3. **Social Features and Events**. Facilitate social interaction through features like forums, chat, or team events. Organize occasional team-building activities or social events to strengthen connections.


## Message Examples


### Community Announcements


#### Discussions


<table>
 <tr>
 <td>example
 </td>
 </tr>
 <tr>
 <td>Subject: Exciting News: Gamification Implementation! ????

Dear Contributors,

???? We've just implemented gamification elements in our project using devActivity app. Earn XP, unlock Levels, and conquer Challenges as you contribute. Closed Pull Requests will now have summary comments with your achievements.

???? Check out our new Public Dashboard to showcase your achievements! \
 \
You’re welcome to sign up for devActivity account to track your progress using Personal Dashboard. \
 \
Your feedback is crucial as we embark on this gamified journey together. Happy coding and gaming!
 </td>
 </tr>
</table>



#### Groups (Discord/Slack)


<table>
 <tr>
 <td>example
 </td>
 </tr>
 <tr>
 <td>Contributors,

???? We've just implemented gamification elements in our project using devActivity app. Earn XP, unlock Levels, and conquer Challenges as you contribute. Closed Pull Requests will now have summary comments with your achievements.

???? Check out our new Public Dashboard to showcase your achievements! \
 \
You’re welcome to sign up for devActivity account to track your progress using Personal Dashboard \
 \
Your feedback is crucial as we embark on this gamified journey together. Happy coding and gaming!
 </td>
 </tr>
</table>



### Inactive Contributors Communication


#### Direct Contact


<table>
 <tr>
 <td>example
 </td>
 </tr>
 <tr>
 <td>[Contributor's Name],

Your contributions have been missed for ProjectName! We've added gamification, and you're already at Level 8 with 365 XP. 

Ready to jump back in?
 </td>
 </tr>
</table>



#### Contribution Comment


<table>
 <tr>
 <td>example
 </td>
 </tr>
 <tr>
 <td>Your contributions have been missed for ProjectName! We've added gamification, and you're already at Level 8 with 365 XP. 

Ready to jump back in?
 </td>
 </tr>
</table>



### README file improvements


#### Contributing section update (or create)


<table>
 <tr>
 <td>example
 </td>
 </tr>
 <tr>
 <td>Attention! Our Project is Leveled Up! Earn XP, Achieve Levels, Conquer Challenges, and Shine on the Leaderboard. [Learn more]
 </td>
 </tr>
</table>



#### Add a kind of shield at the top to attract



* ! [Gamified Contribution Odyssey Shield](https://img.shields.io/badge/Gamified%20Contribution-Odyssey%20Theme-purple)

* ! [Achieve, Game On Shield](https://img.shields.io/badge/Achieve-Game%20On-orange)
* ! [Quest for Impact Shield](https://img.shields.io/badge/Quest-For%20Impact-blue)
* ! [Contribute, Level Up Shield](https://img.shields.io/badge/Contribute-Level%20Up-green)


### CONTRIBUTING file improvements


#### Shield



* ! [Gamified Contribution Odyssey Shield](https://img.shields.io/badge/Gamified%20Contribution-Odyssey%20Theme-purple)

* ! [Achieve, Game On Shield](https://img.shields.io/badge/Achieve-Game%20On-orange)
* ! [Quest for Impact Shield](https://img.shields.io/badge/Quest-For%20Impact-blue)
* ! [Contribute, Level Up Shield](https://img.shields.io/badge/Contribute-Level%20Up-green)


#### Gamification Section



1. Sample message.

3. Additional Info:
 * [How are contributions rewarded with XP?](https://devactivity.com/help/xp-levels)
 
 * [How are Levels assigned based on earned XP?](https://devactivity.com/help/xp-levels)
 * [How are Challenges rewarded with XP?](https://devactivity.com/help/configureChallenges)


## Recommendations



* Share your gamification case with our community


## See also



* [Gamification Concept](https://docs.google.com/document/u/2/d/1POUBc4Jpz0KbSivde_bRDwfIoXfmSBWb6bQ0cq5tEzo/edit)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)
* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)

* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

How to implement gamification elements for your software engineering project with devActivity.

Gamification Implementation Guide

## Permissions


<table>
 <tr>
 <td>Org Admin

Add

Delete
 </td>
 <td>Team Manager (for assigned team)

No access
 </td>
 <td>Org Contributor

No access
 </td>
 <td>External Contributor

No access
 </td>
 </tr>
</table>


Workspace represents the Organization or Personal profile with the app installed.

Each Workspace is managed separately. It may have its own billing plan, teams/contributors, settings, etc.

A new Workspace is created after the devActivity app is installed and authorized to retrieve metadata from repositories.

Workspace may be deleted from Settings->General section. Please note, that all data, including levels progress, and achievements will be permanently deleted. This action is unrecoverable.


## See also



* [What is GitHub Repository Metadata?](https://devactivity.com/help/repository-metadata)
* [Roles and Permissions](https://devactivity.com/help/roles-and-permissions)
* [Onboarding](https://devactivity.com/help/onboarding)

* [Gamification Implementation Guide](https://devactivity.com/help/gamification-implementation)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Workspace management

## What is Cycle Time?

In software development, cycle time refers to the period it takes from the first commit of code to the final production release. It is a crucial metric that helps measure the efficiency and effectiveness of a software development team's process, as well as its ability to deliver value to the customer.

Four elements contribute to the calculation of cycle time:



* coding time
* pickup time

* review (merge) time
* deploy time

By understanding and optimizing these elements, software development teams can reduce cycle time, enhance collaboration, and deliver high-quality software efficiently. 


## Why Cycle Time is Important?

Shorter cycle times lead to increased revenue through a variety of channels. Firstly, faster time to market allows companies to meet customer demands more quickly, attracting more customers and staying ahead of competitors. This increased customer satisfaction leads to higher renewal rates, ensuring a stable and loyal customer base.

Furthermore, shorter cycle times result in a more efficient and happier development team. By reducing delays and bottlenecks in the development process, teams can work more seamlessly and effectively. This improves their morale, engagement, and productivity, leading to higher-quality software and faster delivery. It also allows team members to focus on more creative and value-added tasks, rather than getting stuck in repetitive tasks or waiting for code reviews.

On the other hand, longer cycle times have adverse effects on both the business and the development team. Delivery delays can result in disappointing customers, loss of prospects, and damage to the company's reputation. This can lead to decreased revenue and customer renewal rates. Moreover, development teams can feel frustrated and demotivated when faced with long cycle times, leading to decreased productivity and team collaboration.


## How to Improve Cycle Time?



1. To begin, utilize past performance data to provide context for identifying bottlenecks. Analyze metrics such as cycle times, code review times, and time to market. This data will help you pinpoint areas that require improvement and give you a baseline for setting realistic goals.

3. Next, set goals to improve one tier over the next 2-3 iterations. This means targeting a specific area of improvement and working towards enhancing it by one level. For example, if your average code review time is longer than industry standards, set a goal to reduce it to meet or exceed those standards within the next few iterations.
4. By setting team goals, utilizing past performance data, and developing a cadence for tracking progress, you can make targeted improvements in your software development process and overcome bottlenecks that hinder productivity.
5. Use **devActivity**'s cycle time challenges for individuals and for teams to make the process of improving as efficient as possible. 


## Recommendations



* Consider Cycle Time-related challenges to impact metrics

* Configure Alerts related to Cycle Time to get notified of delays instantly


## See also



* [What is Review Time?](https://devactivity.com/help/review-time)

* [What is Coding Time?](https://devactivity.com/help/coding-time)
* [What is Pickup Time?](https://devactivity.com/help/pickup-time)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

What is Cycle Time?

## Definition of Review Time

Review Time refers to the duration it takes for code reviews to be completed in the software development process. It measures the time elapsed between the initiation of code reviews and when a pull request (PR) is ultimately merged.


## Benefits of Monitoring Review Time

Including Review Time in the software development process offers numerous benefits to development teams.



1. Firstly, it allows teams to evaluate the efficiency and effectiveness of their code review practice. By documenting the time taken for code changes to go through the review process, teams can identify any bottlenecks or areas for improvement in their code review process.
2. Additionally, having a defined Review Time helps in setting realistic expectations for code changes, allowing for better planning and resource allocation. It also provides valuable insights into the overall quality of the codebase, as code changes that spend a substantial amount of time in review may indicate potential issues or areas of improvement.

4. Moreover, including Review Time in the software development process promotes accountability and transparency within the team, as it allows all stakeholders to track the progress of code changes and actively engage in the review process.
5. Overall, incorporating Review Time in the software development process is crucial for fostering code quality, efficiency, and continuous improvement within development teams.


## Early Detection of Issues and Defects

Early detection of issues and defects is crucial in software development as it helps prevent potential problems from escalating into major issues and delays in project timelines. Review time plays a significant role in identifying these issues early on.

Use alerts in **devActivity** to trigger the notification each time it exceeds the expected value.


## How to Improve Review Time?



1. One effective way to optimize the review process is by setting clear expectations. Establishing guidelines for code quality and ensuring developers understand them reduces ambiguity and helps reviewers focus on specific aspects.

3. Additionally, utilizing automation tools can significantly improve review time. These tools can automatically scan for common coding mistakes, code style violations, and potential bugs, allowing reviewers to concentrate on more complex issues.
4. Implementing a systematic approach to code review is another valuable technique. Creating a checklist or template that covers common code review areas such as logic, error handling, security, and performance fosters a structured and consistent review process. This approach enables reviewers to quickly identify and address specific areas of concern.
5. Use the individual and team challenges for Review Time in **devActivity** to gamify the metrics improvement.


## Recommendations



* Consider Review Time related challenges to impact these metrics

* Configure Alerts related to Review Time to get notified of delays instantly


## See also



* [What is Cycle Time?](https://devactivity.com/help/cycle-time)

* [What is Coding Time?](https://devactivity.com/help/coding-time)
* [What is Pickup Time?](https://devactivity.com/help/pickup-time)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

What is Review Time?

## Permissions

Please refer to [this table](https://docs.google.com/spreadsheets/d/1KrdKtyK-huMD4bOU7xaLQUQDD8ibC0GGPtFu5D9A1YA/edit#gid=0) for an overview of the permissions available for each role.


## Roles


#### Org Admin

The user has access to all permissions for billing, user/team management, settings management, etc. They can also access all reports for all teams. This role is assigned to users that are GitHub org admins. It could also be assigned manually by other Org Admin.


#### Team Manager

The user can access reports that are filtered by assigned teams and manage basic alert settings. They can also perform contributor reviews and peer recognition, assign custom achievements, and create custom challenges. It could be assigned by Org Admin. 


#### External Manager

Similar to Team Manager but invited by Org Admin via email. Might not have a GitHub account or access to GitHub organization at all. Used to provide access for HRs, Project Managers, and Client Representatives.


#### Org Contributor

Contributors imported from GitHub organization. The individual who can view reports related to his team, assign peer recognition awards to colleagues, and access embeddable widgets representing his contributions.


#### External Contributor

If a person contributes to a repository on GitHub but is not currently or no longer part of the organization, they have no access to reports and data for private repositories. However, in public repositories, External Contributors can sign up and review their contributions, achievements, and individual challenges. They can also access embeddable widgets that represent their contributions.


## See also



* [Workspace management](https://devactivity.com/help/workspace-management)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)
* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)

* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Roles and Permissions

## Permissions


<table>
 <tr>
 <td>Org Admin

View Dashboard
 </td>
 <td>Team Manager (for assigned team)

View Dashboard
 </td>
 <td>Org Contributor

View Dashboard
 </td>
 <td>External Contributor

View Personal Dashboard
 </td>
 </tr>
</table>


We tailored different dashboards based on the workspace billing plan:



* **Dashboard for Public Repositories (Free/Premium)** – represents key data for private repositories development teams. Main focus: contributions and work quality metrics.
* **Dashboard for Private Repo (Open Source)** – represents key data for public (open source) repositories development teams. Main focus: gamification.

* **External Contributor Personal Dashboard** – represents key data for an individual External Contributor to track his progress across the project (workspace).


## Recommendations



* Click on chart bars to drill down for more data insights

* Share the idea for additional widgets


## See also



* [Contributions Analytics](https://devactivity.com/help/contributions)

* [Work Quality Analytics](https://devactivity.com/help/workQuality)
* [Public Dashboard](https://devactivity.com/help/publicDashboard)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Dashboard

## Permissions


<table>
 <tr>
 <td>Org Admin

View
 </td>
 <td>Team Manager (for assigned team)

View
 </td>
 <td>Org Contributor

View
 </td>
 <td>External Contributor

No access
 </td>
 </tr>
</table>



## Discussions

This page represents the discussion list across all authorized repositories. This report can be enabled/disabled by Org Admin from Settings->General.


### Get answers to the following questions:



1. What discussion has more than 5 comments?

3. Who answered a couple of last discussions?


### Recommended actions



1. Ask community members for help to manage discussions if you have too much open ones.


## Recommendations



* Share an idea on what data/insight related to the discussion might be useful for you


## See also



* [Contributors Analytics](https://devactivity.com/help/contributors)

* [Work Quality Analytics](https://devactivity.com/help/workQuality)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Discussions Analytics

## Definition of Coding Time


Coding Time is the duration measured from the creation of the first commit to a branch until the eventual submission of a pull request (PR). The time spent on coding can vary based on factors such as the complexity of the task, the programming language being used, the developer's familiarity with the codebase, and other considerations. It's important to recognize that this coding time is just one component of the broader development process, which includes activities like code review, testing, debugging, and collaboration with team members. 

Modern software development practices often emphasize not only the speed of coding but also the quality, maintainability, and alignment with project requirements.


## Benefits of Monitoring Coding Time

Including Coding Time in the software development process offers numerous benefits to development teams.



1. Coding time serves as a productivity metric, allowing teams to assess individual and collective efficiency by tracking the time spent actively coding. This data aids in project planning, helping teams allocate resources effectively and set realistic deadlines.

3. Beyond productivity measurement, monitoring coding time helps identify potential bottlenecks in the development process. By analyzing the distribution of time across different stages, teams can pinpoint areas that may require attention, such as improvements in requirements gathering, design, or testing.


## Early Detection of Issues and Defects

Early detection of issues and defects is crucial in software development as it helps prevent potential problems from escalating into major issues and delays in project timelines. Review time plays a significant role in identifying these issues early on.

Use alerts in **devActivity** to trigger the notification each time it exceeds the expected value.


## How to Improve Coding Time?



1. Define clear objectives and requirements before coding.

3. Break complex tasks into smaller, manageable sub-tasks.
4. Prioritize tasks and create a plan for efficient time management.
5. Utilize code skeletons and templates for common patterns.
6. Use feature-rich Integrated Development Environments for productivity.
7. Automate routine processes to save time.
8. Engage in regular code reviews for feedback and improvement.
9. Stay updated with the latest technologies and tools.
10. Learn and use keyboard shortcuts for faster coding.
11. Minimize distractions to maintain focus.
12. Break coding sessions into focused intervals with breaks.
13. Maintain a library of commonly used code snippets.
14. Pay attention to algorithmic efficiency.
15. Use tools to track and analyze coding time for insights.


## Recommendations



* Create a new branch when you start to work on coding new features or fixing bug


## See also



* [What is Cycle Time?](https://devactivity.com/help/cycle-time)

* [What is Review Time?](https://devactivity.com/help/review-time)
* [What is Pickup Time?](https://devactivity.com/help/pickup-time)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

What is Coding Time?

## Definition of Pickup Time

Pickup Time could be understood as the duration from creating a pull request (PR) to the commencement of the review process. This timeframe encompasses the period it takes for a developer or a team to transition from the PR creation to the initiation of the review phase. Factors influencing this duration may include the developer's workload, task priorities, availability, and any dependencies on other tasks. 

It's worth noting that terminologies and practices related to development processes may vary among different teams and methodologies.


## Benefits of Monitoring Pickup Time

Monitoring pickup time in software development can offer several advantages for teams and individual developers. 



1. One key benefit is improved project planning. By understanding how quickly developers can pick up and start working on assigned tasks, teams can better estimate project timelines and allocate resources effectively. It allows for a more realistic assessment of workloads, preventing potential bottlenecks and ensuring a smoother development process.

3. Another advantage lies in the identification of workflow impediments. Monitoring pickup time can reveal delays in task initiation, prompting teams to investigate and address potential issues such as unclear requirements, dependencies on other tasks, or individual workloads. This proactive approach to identifying and resolving bottlenecks contributes to a more agile and responsive development environment.
4. Furthermore, monitoring pickup time contributes to individual and team productivity. Developers can refine their task management strategies, prioritize effectively, and reduce idle time between assignments. This not only accelerates the development lifecycle but also ensures that the team operates at optimal efficiency.

In summary, monitoring pickup time provides actionable insights for project planning, helps identify and address workflow impediments, enhances collaboration, and boosts overall productivity within software development teams.


## Early Detection of Issues and Defects

Early detection of issues and defects is crucial in software development as it helps prevent potential problems from escalating into major issues and delays in project timelines. Review time plays a significant role in identifying these issues early on.

Use alerts in **devActivity** to trigger the notification each time it exceeds the expected value.


## How to Improve Pickup Time?

Here are several strategies to improve pickup time:



1. Prioritize tasks based on urgency and importance. Sequencing tasks logically can facilitate a smoother transition between different assignments, reducing idle time. Minimize dependencies between tasks. This reduces the likelihood of delays caused by waiting for the completion of other tasks and allows for more independent task pickup.

3. Maintain comprehensive documentation for the codebase and projects. Well-documented code and project details make it easier for developers to understand and pick up tasks more quickly.
4. Implement automated testing processes. This reduces the time developers spend on manual testing and allows them to confidently pick up new tasks without fear of introducing errors.
5. Implement CI/CD pipelines to automate the integration and deployment processes. This ensures that changes can be quickly integrated and deployed, reducing the time between task completion and production.


## Recommendations



* Consider Pickup Time-related challenges to impact these metrics

* Configure Alerts related to Pickup Time to get notified of delays instantly


## See also



* [What is Cycle Time?](https://devactivity.com/help/cycle-time)

* [What is Review Time?](https://devactivity.com/help/review-time)
* [What is Coding Time?](https://devactivity.com/help/coding-time)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

What is Pickup Time?

## Permissions


<table>
 <tr>
 <td>Org Admin

View
 </td>
 <td>Team Manager (for assigned team)

View
 </td>
 <td>Org Contributor

View
 </td>
 <td>External Contributor

No access
 </td>
 </tr>
</table>


This page represents the list of Pull Requests across the authorized repositories.


## Recommendations



* Filter by period and sort by specific metric to identify operational bottlenecks

* Share an idea of what kind of data/metric related to Pull Request might be useful


## See also



* [Contributions Analytics](https://devactivity.com/help/contributions)

* [Work Quality Analytics](https://devactivity.com/help/workQuality)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Pull Requests

## Permissions


<table>
 <tr>
 <td>Org Admin

View

Create

Comment

Delete
 </td>
 <td>Team Manager (for assigned team)

View

Create

Comment

Delete
 </td>
 <td>Org Contributor

View
 </td>
 <td>External Contributor

No access
 </td>
 </tr>
</table>



## General information

devActivity Performance Review is pre-generated templates filled with data for specific Contributor for the selected period:



* Contributions
* Work Quality
* Cooperation/Feedback

* Achievements

For Premium users: compare data with previous periods and the team’s averages.

The Manager or Admin may add comments to the review, download the PDF, and send it to the appropriate person.


### Performance Review List (Archive)

_Screenshot_

The page displays all available performance reviews accessible to a user and available according to the data retention period. Upgrade to Premium to access all reviews.


### Available Review Periods



* Monthly

* Quarterly
* Half-yearly
* Yearly


### Overview of Performance Review Template

2 previous periods are displayed (1 and 2 columns) to understand the trend.

_Screenshot_

Team average displayed to compare with other team members.

_Screenshot_


### Review Export

You can download the review in PDF using the appropriate button on the detailed view page. 

_Screenshot_


## Review Sections


### Contributions



* [XP (Contribution Score)](https://devactivity.com/help/contribution-score)
* Commits
* Code Reviews

* Pull Requests
* Closed Issues 


### Work Quality



* [Cycle Time](https://devactivity.com/help/cycle-time)

* [Coding Time](https://devactivity.com/help/coding-time)
* [Pickup Time](https://devactivity.com/help/pickup-time)
* [Review Time](https://devactivity.com/help/review-time)
* Deploy Time (coming soon)


### Cooperation / Feedback



* Comments

* [Peer Recognition Awards received / submitted](https://devactivity.com/help/peerRecognition)


### Achievements



* [XP & Levels](https://devactivity.com/help/xp-levels)

* [Achievements (total received) / Last Achievements](https://devactivity.com/help/achievements)


### Manager Comments

List of the comments for Contributor's current review. Creating comments available only for Managers and Org Admins.

Good comments are not easy to find, as it may seem.


## Recommendations



* The optimal performance review period is 3 or 6 months. You may set up an appropriate alert so as not to miss the review.
* You can share the review results with HR, PM, or Client's Representative by inviting them as External Managers with the ability to create and view Reviews. External Managers don’t affect the billing for the Premium plan.

* Include the goals for the next period (e.g. metrics level to achieve).
* Try to check with AI tools how your comment may sound to the reviewer. 


## See also



* Complete Guide

* [Peer Recognition](https://devactivity.com/help/peerRecognition)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Performance Review

## What is XP?

XP (eXperience Points) are points Contributors rewarded for contributions, completing challenges, and other activities. XP is designed to reward a wider set of activities impacting the team’s life compared to the Contribution Score: 



* [Peer recognition](https://devactivity.com/help/peerRecognition) (submit and receive).

* [Challenges](https://devactivity.com/help/activeChallenges) completion, including custom challenges.
* [Custom achievements](https://devactivity.com/help/customAchievements) assigned.


### Contributions (events) and XP Reward

Represented in this [table](https://docs.google.com/spreadsheets/d/1SitbyQ6JCBkp-ZW6uz82Jq3eTgGJBqa4zJPu8o1ZHkQ/edit#gid=1436893147).


## What is Level?

Levels are similar to most game levels and represent the amount of XP earned but in a more intuitive form (at least for humans). 


## XP to Levels Relation

Represented in this [table](https://docs.google.com/spreadsheets/d/1SitbyQ6JCBkp-ZW6uz82Jq3eTgGJBqa4zJPu8o1ZHkQ/edit#gid=2071178529).


## Where to check current Level/XP?



* [Leaderboard](https://devactivity.com/help/leaderboard).

* Contributor profile dropdown.


## How to earn more XP?



1. Contribute more (commits, pull requests, completed tasks).
2. Complete challenges to earn extra XP (see [Challenges](https://devactivity.com/help/configureChallenges) for more details).

4. Get [Custom Achievement](https://devactivity.com/help/customAchievements) for a significant contribution.


## Recommendations



* Keep an eye for challenge thresholds

* Consider additional motivation for Contributor’s Level


## See also



* [Custom Challenges](https://devactivity.com/help/customChallenges)

* [Active Challenges](https://devactivity.com/help/activeChallenges)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

XP and Levels

## Permissions


<table>
 <tr>
 <td>Org Admin

View
 </td>
 <td>Team Manager (for assigned team)

View
 </td>
 <td>Org Contributor

View
 </td>
 <td>External Contributor

View his own progress
 </td>
 </tr>
</table>


This page represents the list of Contributors sorted by level with progress to achieve the next level.


## Recommendations



* Use Leaderboard to check Contributor’s progress towards the next Level 


## See also



* [Contributors Analytics](https://devactivity.com/help/contributors)

* [Custom Achievements](https://devactivity.com/help/customAchievements)
* [Custom Challenges](https://devactivity.com/help/customChallenges)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Leaderboard

## Permissions


<table>
 <tr>
 <td>Org Admin

View

Assign Reward

Configure
 </td>
 <td>Team Manager (for assigned team)

View

Assign Reward
 </td>
 <td>Org Contributor

View

Assign Reward
 </td>
 <td>External Contributor

No Access
 </td>
 </tr>
</table>


The inspiration behind the Peer Recognition Awards stemmed from the team's commitment to fostering regular peer feedback and acknowledgment.


## How it works?



1. Team members receive the weekly or monthly notification to assign a reward to the colleagues list by email or Slack.

 _Screenshot_

2. After clicking on a specific colleague, they requested a simple pre-filled confirmation form with optional comments.

Any team member may assign a Peer Recognition Award for one Contributor only once per period.

It’s also possible to submit the form from the [Peer Recognition](https://app.devactivity.com/achievements/?activeTab=peerRecognition) page.


## Configuration

Available for Org Admin only.

Use Settings->General->Peer Recognition to configure:



1. Iteration periods: 
 * weekly
 
 * monthly 
1. Or disable this feature (it might not be useful for most Open Source projects). 

_Screenshot_


## Recommendations



* Stimulate this way of feedback and discuss it on a retrospective

* Set up the Slack integration to get the requests right there
* Set a higher reward for challenges related to the number of received Recognition Awards to stimulate the usage
* Disable Peer Recognition from Settings (General -> Peer Recognition) if you don’t wish to send requests regularly or have other way to gather team feedback


## See also



* [Performance Review](https://devactivity.com/help/perfomanceReview)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Peer Recognition

This guide will help you to configure devActivity using Onboarding Wizard. 

Select the repository type you have:



* Public

* Private


## Public Repositories (Open Source)


### Step 1

Users synced from GitHub organization. It might be a single person for personally held repositories.

All Contributors that aren’t part of your organization are assigned to the “External Contributors” Team.

What to do in this step:


1. Check whatever you want to invite to devActivity for all imported contributors.

3. Decide if you wish to create any Teams. We recommend creating a separate Team for your active contributors to track the contributions for them separately from others. You can invite them as external managers. Also, this may be done later anytime.
3. Invite Active contributors as External Managers to provide access to devActivity extra reports. You need to know their email addresses to send invites.

More information:



* [Roles and Permissions](https://devactivity.com/help/roles-and-permissions)

* [Settings](https://docs.google.com/document/u/2/d/1FXmMuG9pyJUSJjojOMs75E7l5i92Yp47BdyK8_0ieUs/edit)


### Step 2

We’ve applied the alerts default configuration for public (open source) repositories but it still needs verification to your specific project’s needs.

If you have multiple teams please check the alert configuration per each.

What to do in this step:



1. Overview-enabled alerts if the condition looks ok to you. 

3. Edit alerts or disable if you believe it’s not relevant at this point. 
4. If you aren’t sure about the condition value you may set some higher value and actualize it after data is processed and reports are available.

No worries, you’ll be able to enable or edit alerts anytime later.

More information:



* [Alerts Configuration](https://devactivity.com/help/alertsConfig)

* [Alerts](https://devactivity.com/help/alerts)


### Step 3

We’ve applied the challenges default configuration for public (open source) repositories but it still needs verification to your specific project’s needs.

What to do in this step:



1. Overview the challenges if the goals look ok to you. 
2. Edit challenges if necessary: set goals and rewarded XP value. 

4. There are 2 types of XP rewards:
    * For one-time challenges, it’s simply a fixed XP value. For example, 5XP.
    
    * For monthly and accumulative challenges you can set % from Contributor’s XP earned monthly. For example, if he earned 1000 XP during a month and completed a specific challenge with a 3% reward, then he’ll get 30 XP for this challenge completion.
5. If you aren’t sure about the goal you may set some higher value and actualize it later.


More information:



* [Challenges Configuration](https://devactivity.com/help/configureChallenges)

* [Active Challenges](https://devactivity.com/help/activeChallenges)


### Step 4

Use recommendations from the [Implementation Guide](https://devactivity.com/help/gamification-implementation) to integrate gamification even more efficiently.


## Private Repositories


### Step 1

Users synced from GitHub organization. It might be a single person for personally held repositories.

All Contributors that aren’t part of your organization are assigned to the “External Contributors” Team.

What to do in this step:



1. Check whatever you want to invite to devActivity for all imported contributors.

3. Decide if you wish to create any Teams. 
We recommend creating a separate Team for your active contributors to track the contributions for them separately from others. You can invite them as external managers. Also, this may be done later anytime.
3. Invite Active contributors as External Managers to provide access to devActivity extra reports. You need to know their email addresses to send invites.

More information:



* [Roles and Permissions](https://devactivity.com/help/roles-and-permissions)

* [Settings](https://devactivity.com/help/settings)


### Step 2

We’ve applied the alerts default configuration for private repositories but it still needs verification to your specific project’s needs.

If you have multiple teams please check the alert configuration per each.

What to do in this step:



1. Overview-enabled alerts if the condition looks ok to you. 

3. Edit alerts or disable if you believe it’s not relevant at this point. 
4. If you aren’t sure about the condition value you may set some higher value and actualize it after data is processed and reports are available.

No worries, you’ll be able to enable or edit alerts anytime later.

More information:



* [Alerts Configuration](https://devactivity.com/help/alertsConfig)

* [Alerts](https://devactivity.com/help/alerts)


### Step 3

We’ve applied the challenges default configuration for private repositories but it still needs verification to your specific project’s needs.

What to do in this step:



1. Overview the challenges if the goals look ok to you. 

3. Edit challenges if necessary: set goals and rewarded XP value. 
4. There are 2 types of XP rewards:
    * For one-time challenges, it’s simply a fixed XP value. For example, 5XP.
  
    * For monthly and accumulative challenges you can set % from Contributor’s XP earned monthly. For example, if he earned 1000 XP during a month and completed a specific challenge with a 3% reward, then he’ll get 30 XP for this challenge completion.
5. If you aren’t sure about the goal you may set some higher value and actualize it later.

More information:



* [Challenges Configuration](https://devactivity.com/help/configureChallenges)

* [Active Challenges](https://devactivity.com/help/activeChallenges)


### Step 4

Use recommendations from the [Implementation Guide](https://devactivity.com/help/gamification-implementation) to integrate gamification even more efficiently.


## See also



* [Gamification Implementation Guide](https://docs.google.com/document/d/1BlzRGzjm522T4qeBy-7doy2HdTopd3lGmv9JP9sHrAY/edit)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Onboarding

## What is Repository Metadata?

Repository Metadata refers to the information and data associated with a GitHub repository. This metadata includes various details such as the repository's name, description, owner, license, creation date, and last update. 

By making repository metadata accessible and well-organized, GitHub ensures efficient collaboration and seamless management of software projects. It helps developers and users better understand and utilize the resources within a repository, making it an essential component of the GitHub ecosystem.


## What types of Repository Metadata?

In addition to providing an overview of a repository's content and structure, repository metadata also includes information about different types of events and changes that occur within the repository. This metadata allows users to retrieve general information about each event, including contributors, dates and times, and the event type.

Commits store important information about changes made to the repository, such as the commit message, author, date, time, and contents of the changes. This helps developers track the project's progress and understand its history.

Another type of repository metadata is associated with issues and pull requests. Issues track problems, tasks, or feature requests within a repository, while pull requests are proposals for changes or additions to the repository's codebase. The metadata for issues and pull requests includes the title, description, labels, the person who opened the issue or pull request, and the date it was opened or closed.

Overall, repository metadata is a valuable resource for understanding and tracking the various events and changes happening within a repository. It provides users with the necessary information to analyze the repository's history, collaborate with other contributors, and ensure the successful management of the project.


## Is it secure to allow access to the Repo Metadata?

When it comes to allowing access to repository metadata, there are important security considerations to take into account. It is important to note, however, that repository metadata does not include any specific sensitive information related to the source code or project.

The repository metadata mainly consists of general information about events such as commits, issues, pull requests, and other activities. This includes details like the commit message, author, date, and time, as well as information about issues and pull requests such as titles, descriptions, labels, and individuals involved.

While this information may be useful for developers to track and understand the history of a project, it does not expose any sensitive or critical aspects of the codebase. As such, allowing access to repository metadata does not pose significant security risks.


## How long does it take to process initial metadata after app installation?

It depends on the data amount (number of contributions in repository). Typically, first month of data is available in minutes.


## See also



* [Settings](https://devactivity.com/help/settings)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

What is GitHub repository metadata?

## Permissions


<table>
 <tr>
 <td>Org Admin

View

Configure
 </td>
 <td>Team Manager (for assigned team)

View
 </td>
 <td>Org Contributor

View
 </td>
 <td>External Contributor

View
 </td>
 </tr>
</table>


When enabled, the Public Dashboard is accessible to anyone with a link and comprises the following sections:



* Top Contributors (Leaderboard)
* Contribution Stats

* Achievements
* Challenges

Public Dashboard details can be filtered for a specific contributor by utilizing the header dropdown or the “userLogin=githubusername” parameter.


## Configuration

Org Admins can configure Public Dashboard and its sections using [Settings->Public Dashboard](https://app.devactivity.com/settings/?activeTab=publicDashboard).


## Recommendations



* Paste Public Dashboard link to your project’s description to attract new contributors
* Use userLogin=githubusername parameter to get specific Contributor Public Dashboard 

* Share an idea for additional widgets that might be useful for you


## See also



* [Embeddables](https://devactivity.com/help/embeddables)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Public Dashboard

## Permissions


<table>
 <tr>
 <td>Org Admin

View

Configure
 </td>
 <td>Team Manager (for assigned team)

No access
 </td>
 <td>Org Contributor

No access
 </td>
 <td>External Contributor

No access
 </td>
 </tr>
</table>


This section allows to generate markdowns for the following embeddable widgets:



* Top Contributors (Last 3 Months)
* Active Challenges

* Achievements
* Cycle Time (Last 30 Days) 
* Repo Stats (Last 3 Months) 

Simply paste the markdown into your README/CONTRIBUTING files to display widgets.


## Recommendations



* You can edit the markdown for Cycle Time and Repo Stats widgets to embed them partially

* Enable Public Dashboard and communicate it within your Contributors' and Users Communities
* Share an idea for additional widgets that might be useful for you


## See also



* [Public Dashboard](https://devactivity.com/help/publicDashboard)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Embeddables

## Permissions


<table>
 <tr>
 <td>Org Admin

View

Create
 </td>
 <td>Team Manager (for assigned team)

View

Create
 </td>
 <td>Org Contributor

View
 </td>
 <td>External Contributor

No Access
 </td>
 </tr>
</table>


You have the flexibility to establish a personalized challenge linked to specific issues, allowing you to define the associated reward and achievement manually.


## How to Create a Custom Challenge?



1. Go to Rewards -> Configure Challenges.

3. Click on Create Custom Challenge.
4. Specify the Contributor, Title (see ideas below), and Description.
5. Specify the color and icon for the badge (see ideas below).
6. Specify XP reward for selected Contributor.


## Issues Ideas

Leverage these ideas to identify issues that merit the creation of a custom challenge:



1. **Open for a Long Time:**
 * Filter: is:open created:&lt;2022-01-01
 
 * Description: Lists issues that have been open for an extended period, indicating potential complexity or importance.
2. **High Priority:**
 * Filter: label:priority-high is:open
 
 * Description: Identifies issues tagged with a high-priority label, signaling their significance.
3. **Good First Issue:**
 * Filter: label:"good first issue" is:open
 
 * Description: Highlights issues suitable for newcomers, potentially deserving recognition upon successful completion.
4. **Community Voted:**
 * Filter: label:"community-vote" is:open
 
 * Description: Flags issues that the community has voted on, showcasing their collective importance.
5. **Milestone Target:**
 * Filter: milestone:"Next Release" is:open
 
 * Description: Lists issues targeted for an upcoming milestone, signifying their relevance to project goals.
6. **Bug Fixes:**
 * Filter: label:bug is:open
 
 * Description: Focuses on issues labeled as bugs, as resolving them contributes to the project's stability.
7. **Feature Requests:**
 * Filter: label:"feature-request" is:open
 
 * Description: Identifies issues tagged as feature requests, indicating potential for innovation and improvement.
8. **High Impact:**
 * Filter: label:"high-impact" is:open
 
 * Description: Flags issues are marked as having a high impact, making them notable candidates for recognition.
9. **Documentation Tasks:**
 * Filter: label:"documentation" is:open
 
 * Description: Highlights issues related to documentation, acknowledging the essential role of clear documentation in a project.
10. **Security Issues:**
 * Filter: label:security is:open
 
 * Description: Lists issues tagged as security concerns, emphasizing the importance of addressing these for the project's integrity.


## Title Ideas

Look [here](https://devactivity.com/help/customAchievements).


## Color Ideas

Look [here](https://devactivity.com/help/customAchievements).


## Icon Ideas

Look [here](https://devactivity.com/help/customAchievements).


## Recommendations



* Base challenges on real-world scenarios or projects your team is working on or might encounter in the future. 
* Introduce time constraints to simulate real-world project timelines. 
* Provide constructive feedback on completed challenges. 

* Recognize and reward outstanding performance. 


## See also



* [Challenges Configuration](https://devactivity.com/help/configureChallenges)

* [Custom Achievements](https://devactivity.com/help/customAchievements)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Custom Challenges

## Permissions


<table>
 <tr>
 <td>Org Admin

View

Edit
 </td>
 <td>Team Manager (for assigned team)

No access
 </td>
 <td>Org Contributor

No access
 </td>
 <td>External Contributor

No access
 </td>
 </tr>
</table>



## General

This section allows you to configure the Organization’s settings to determine the timezone, work schedule, peer feedback request period, etc.


### Enable Pull Request Comments for achievements, XP, etc

This setting allows the devActivity app to provide a summary comment once a Pull Request is successfully merged, including the following information:



* Cycle Time
* Coding Time
* Pickup Time

* Review Time
* Deploy Time (coming soon)
* Number of Comments 
* XP rewards per Contributor

It’s important to keep it enabled for Open Source projects as it significantly increases the probability of first-time contributor's engagement.


### Slack Integration

[Learn more](https://devactivity.com/help/slack).


### Peer Feedback (Recognition Awards)

Enabling this option facilitates the submission of Recognition Award requests through email or Slack (if configured). Contributors can assign an Award to one teammate per period, accompanied by a comment explaining their choice.


### Additional Analytics

Enabling these options introduces two extra reports in the Analytics section. To access them in the top navigation, simply refresh the page. Note that the additional reports (Contributors and Discussions) are automatically enabled by default for the Open Source plan.


## Teams/Users

This section allows you to:



* Create and assign Teams (one or multiple) to Contributors

* Enable/disable access to devActivity for specific Org Contributors
* Invite External Managers


### Invite External Manager

Use this option to provide access for a person who isn’t a part of your Organization on GitHub but still needs access to analytics and other devActivity features. That might be:



* Project Manager
* Client’s Representative
* HR Manager

* C-level Manager

Please note that this person should have a GitHub account.


### Sync with GitHub

You can initiate sync with GitHub using the appropriate button on the page if any Contributors are missed from the list.


## Billing

[Learn more](https://devactivity.com/help/billing).


## Events Log

This section represents the list of events from authorized repositories processed by devActivity. Researching the work quality metrics anomalies or XP rewarded for specific Contributors might be useful.


## Public Dashboard

You can enable/disable the Public Dashboard or its sections using this setting.

[Learn more](https://devactivity.com/help/publicDashboard).


## Embeddables

Configure the generation of embeddable markdowns for useful widgets using this section.

[Learn more](https://devactivity.com/help/embeddables).


## Recommendations



* Engage Peer Feedback (Recognition Awards) usage across your organization

* For Free/Premium plans: enable Additional Analytics for more information about Contributors and Discussion (if applicable)
* Configure Slack integration to receive notifications/reports


## See also



* [Slack Integration](https://docs.google.com/document/u/2/d/13v1XvyuIdlxlCQbgMhp-TOfxmFI85jIMhUyCjOKZqFQ/edit?usp=drive_web&ouid=101799387986326011511)

* [Workspace Management](https://docs.google.com/document/d/1a4yqxzuIV5-9O4OTMwJQlH6Jk9doohCSim1fEzNOzog/edit?usp=drive_link)
* [Roles and Permissions](https://docs.google.com/document/u/2/d/1rqE17OO8lq1vVocbDZ0MOAZLHh9pn75P_rNyEBDZz3I/edit)


## Questions, Ideas, Improvements



* [General](https://github.com/orgs/devactivity-app/discussions/categories/general)

* [Ideas/Feature Requests](https://github.com/orgs/devactivity-app/discussions/categories/ideas-feature-requests)
* [Questions & Answers](https://github.com/orgs/devactivity-app/discussions/categories/q-a)
* [Bug Report](https://github.com/orgs/devactivity-app/discussions/categories/report-a-bug)

Settings

### Organization (workspace)

Organizations are collections of teams (one or more) that work in one or more repositories.

RELATED:



* [Workspace Management](https://devactivity.com/help/workspace-management)


### Team

Teams are collections of users (admins, managers, and contributors) that usually work in one repository.


### Org Admin

Organisation Admin is someone who administrates a repository in GitHub and has access to all possible permissions in devActivity.

RELATED:



* [Roles and Permissions](https://devactivity.com/help/roles-and-permissions)


### Manager

Manager is a role in the organization, in which someone has greater access to devActivity insights than contributors. Managers can get info for performance reviews, see metrics and statistics, receive reports and alerts based on specified conditions, create challenges and achievements, etc.

RELATED:



* [Roles and Permissions](https://devactivity.com/help/roles-and-permissions)


### Contributor

A contributor engages with a software project, making contributions that enhance the project's functionality, quality, and community. In devActivity, a contributor is an individual whose contributions (actions in the repository) are analyzed and displayed on the dashboard. Contributors have access to see team reports, assign peer recognition, and embed achievement widgets in their profiles.

RELATED:



* [Roles and Permissions](https://devactivity.com/help/roles-and-permissions)


### External Contributor

An External Contributor is a person who makes contributions to some project but is not a part of that organization formally. In devActivity, an External contributor is like a Contributor, but without access to reports or team info.

RELATED:



* [Roles and Permissions](https://devactivity.com/help/roles-and-permissions)
* [Workspace Management](https://devactivity.com/help/workspace-management)


### Contribution

Contribution in the context of software development refers to the developer's positive impact, work, and value they add to a project, codebase, or development team. For example, we include commits, pull requests, tasks, and more.

RELATED:



* [XP (Contribution Score)](https://devactivity.com/help/contribution-score)


### Contribution Score

The contribution score measures the impact and productivity of a software engineer by assigning weight to different types of contributions via the weight coefficient.

RELATED:



* [XP (Contribution Score)](https://devactivity.com/help/contribution-score)


### Performance Review

Performance reviews in software development teams involve assessing and evaluating team members' individual and collective performance to provide feedback, identify areas for improvement, and recognize achievements. By getting a filled-out template (based on devActivity data) with the Contributor's results, the Manager can conduct a deeper and better review of that Contributor.

RELATED:



* [Performance Review](https://devactivity.com/help/perfomanceReview)



### Work Quality Metrics

Tracking work quality metrics is important for optimizing software development. Metrics such as cycle time, coding time, pickup time, review time, and deploy time can help improve software quality, reduce errors and delays, and increase agility in the development team.

RELATED:



* [What is Cycle Time?](https://devactivity.com/help/cycle-time)
* [What is Coding Time?](https://devactivity.com/help/coding-time)
* [What is Pickup Time?](https://devactivity.com/help/pickup-time)
* [What is Review Time?](https://devactivity.com/help/review-time)


### Cycle Time

Cycle Time refers to the duration it takes for a development team to move a user story, task, or feature from the point of initiation (start) to the point of completion (release or deployment). devActivity collects and analyzes information about the type of activity and time stamps.

RELATED:



* [What is Cycle Time?](https://devactivity.com/help/cycle-time)


### Coding Time

Coding Time represents the duration during which developers are actively writing, editing, or modifying source code to implement a specific feature, fix a bug, or accomplish a programming task. It is a subset of the broader development process. devActivity collects and analyzes information about the type of activity and time stamps.

RELATED:



* [What is Coding Time?](https://devactivity.com/help/coding-time)
* [What is Cycle Time?](https://devactivity.com/help/cycle-time)


### Pickup Time

Pickup Time is the duration between the moment a task or user story is assigned to a developer or team member and the point at which they actively begin working on it. It includes the time spent understanding the requirements, preparing to work on the task, and transitioning from the previous task. devActivity collects and analyzes information about the type of activity and time stamps.

RELATED:



* [What is Pickup Time?](https://devactivity.com/help/pickup-time)
* [What is Cycle Time?](https://devactivity.com/help/cycle-time)


### Review Time

Review time is the period during which peers or team members scrutinize a developer's code changes. It includes the time taken for code reviews, feedback discussions, and any necessary revisions before the code is approved for merging. devActivity collects and analyzes information about the type of activity and time stamps.

RELATED:



* [What is Review Time?](https://devactivity.com/help/review-time)
* [What is Cycle Time?](https://devactivity.com/help/cycle-time)


### Deployment Time

Deployment time represents the period during which the software application or system is released, installed, and made available for use in a production environment. It encompasses the activities involved in transitioning the software from development to a live operational state. devActivity collects and analyzes information about the type of activity and time stamps.


### Alert

Alerts are notifications triggered by specific conditions to locate the operational bottlenecks. 

RELATED:



* [Alerts](https://devactivity.com/help/alerts)
* [Alerts Configuration](https://devactivity.com/help/alertsConfig)




### Gamification

Gamification in software involves integrating game-like elements, mechanics, and design principles into non-game applications. Gamification features in devActivity: XP (experience points), badges, leaderboards, and challenges. Using devActivity with gamification contributes to increased developer retention, improved team motivation, and the achievement of desired results.

RELATED:



* [Gamification Implementation Guide](https://devactivity.com/help/gamification-implementation)
* [XP (Contribution Score)](https://devactivity.com/help/contribution-score)
* [XP and Levels](https://devactivity.com/help/xp-levels)
* [Achievements](https://devactivity.com/help/achievements)
* [Custom Achievements](https://devactivity.com/help/customAchievements)
* [Leaderboard](https://devactivity.com/help/leaderboard)
* [Active Challenges](https://devactivity.com/help/activeChallenges)
* [Challenges Configuration](https://devactivity.com/help/configureChallenges)
* [Custom Challenges](https://devactivity.com/help/custom-challenges)


### XP

eXperience Points (XP) are often used to measure a developer's progress, achievements, or contributions within a specific system or platform. devActivity analyzes the developer's contribution and converts it to XP. So, XP is a way to recognize and quantify a developer's engagement, skill development, and contributions.

RELATED:



* [XP (Contribution Score)](https://devactivity.com/help/contribution-score)
* [XP and Levels](https://devactivity.com/help/xp-levels)


## Leaderboard

The leaderboard displays a list of contributors sorted by their level, with progress bars indicating how close they are to achieving the next level.

RELATED:



* [Leaderboard](https://devactivity.com/help/leaderboard)


### Levels

Levels in software development gamification refer to a hierarchical structure that signifies the progression or expertise of individuals within a gamified environment. Developers can progress through levels based on their contributions, and achievements. On the devActivity dashboard, you can see the levels reached by team members. Levels are based on earned XP.

RELATED:



* [XP and Levels](https://devactivity.com/help/xp-levels)


### Badges

Badges in devActivity are virtual representations or symbols awarded to developers based on specific achievements, XP, challenges, or milestones. These virtual badges are indicators of a developer's accomplishments and contributions.

RELATED:



* [Gamification Implementation Guide](https://devactivity.com/help/gamification-implementation)
* [Achievements](https://devactivity.com/help/achievements)
* [Custom Achievements](https://devactivity.com/help/customAchievements)


### Achievement

Achievement refers to the successful accomplishment, realization, or attainment of a challenge. 

RELATED:



* [Achievements](https://devactivity.com/help/achievements)
* [Custom Achievements](https://devactivity.com/help/customAchievements)


### Challenge

Challenge typically refers to a specific task, goal, or mission that developers are encouraged to undertake within a gamified system. Challenges are designed to engage and motivate developers, foster collaboration, and drive specific behaviors that align with organizational objectives.

RELATED:



* [Active Challenges](https://devactivity.com/help/activeChallenges)
* [Challenges Configuration](https://devactivity.com/help/configureChallenges)
* [Custom Challenges](https://devactivity.com/help/custom-challenges)


### Custom Achievement

Custom achievement refers to a unique or individualized accomplishment that is specific to a developer or team, that's set by a manager.

RELATED:



* [Achievements](https://devactivity.com/help/achievements)
* [Custom Achievements](https://devactivity.com/help/customAchievements)


### Custom Challenge

Team leads or managers could choose or define in devActivity custom challenges based on the team's goals, project priorities, or areas that need improvement. By completing custom challenges, developers receive XP and badges.

RELATED:



* [Gamification Implementation Guide](https://devactivity.com/help/gamification-implementation)
* [XP (Contribution Score)](https://devactivity.com/help/contribution-score)
* [XP and Levels](https://devactivity.com/help/xp-levels)
* [Achievements](https://devactivity.com/help/achievements)
* [Custom Achievements](https://devactivity.com/help/customAchievements)
* [Leaderboard](https://devactivity.com/help/leaderboard)
* [Active Challenges](https://devactivity.com/help/activeChallenges)
* [Challenges Configuration](https://devactivity.com/help/configureChallenges)
* [Custom Challenges](https://devactivity.com/help/custom-challenges)


### Peer Recognition

Peer Recognition refers to devActivity feature that allows developers to acknowledge and appreciate the contributions of their peers within the development team. 

RELATED:



* [Peer Recognition](https://devactivity.com/help/peerRecognition)




### Embeddables

Embeddables in devActivity are built-in widgets relevant to open-source projects and intended for use in the README or CONTRIBUTING files to indicate important points about this project. For example, most active members, active calls, achievement, cycle length, repo statistics, and more.

RELATED:



* [Peer Recognition](https://devactivity.com/help/peerRecognition)


### Public Dashboard

Public Dashboard allows teams or devs to create and share visual representations of key performance metrics or insights related to development projects. This dashboard is accessible to a wider audience, providing transparency and visibility into the overall performance and status of development initiatives.

RELATED:



* [Public Dashboard](https://devactivity.com/help/publicDashboard)
* [Dashboard](https://devactivity.com/help/dashboard)


### Open Source Plan

The open source plan means that the use of the devActivity service with all functionality is free for all public repositories (so far for GitHub).

RELATED:



* [Billing](https://devactivity.com/help/billing)


### Public Repository

A public repository on GitHub is a version-controlled storage space where developers can host and share their code openly with the GitHub community and the public. It allows collaborative development, issue tracking, and facilitates transparency by providing visibility into the source code and project history.

RELATED:



* [What is GitHub repository metadata?](https://devactivity.com/help/repository-metadata)


### Private Repository

A version-controlled storage space in GitHub that provides a secure and private environment for hosting code. Unlike public repositories, the content of a private repository is visible only to the repository owner and collaborators who have been explicitly granted access. It is often used for proprietary or sensitive projects.

RELATED:



* [What is GitHub repository metadata?](https://devactivity.com/help/repository-metadata)


### Work Schedule

A working schedule is a plan that shows when someone is supposed to work. It includes the hours and days they need to be doing their job. Alerts will be sent according to the working hours of the team member/contributor.

RELATED:



* [Settings](https://devactivity.com/help/settings)
* [Alerts](https://devactivity.com/help/alerts)
* [Alerts Configuration](https://devactivity.com/help/alertsConfig)




### devActivity App for Slack

devActivity works synchronously with Slack. With devActivity, team members can receive real-time alerts in their designated channel, ensuring everyone stays up-to-date on important project activities.

RELATED:



* [Settings](https://devactivity.com/help/settings)
* [Slack Integration](https://devactivity.com/help/slack)

Help