100-DFR-Habbit

KO | EN

gitlite — search

#javascript #python #react #llm #go #machine-learning #linux #docker #java #awesome-list #vue #pytorch #security #ios

(★ 9)

Habbit helps learners upskill through live classes and communities from creators who made a sustainable lifestyle out of these new-age creative and digital skills. ✨

100-DFR-Habbit 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Habbit in 100 Days of Feature Request

We are so excited to have Habbit in the first edition of 100 Days of Feature Request. This is the offcial repository of brand Habbit for 100 Days of Feature Request, where you will be able to submit your Pull Request regarding any new feature as a contribution for the contest.

# About the Brand

Habbit helps learners upskill through live classes and communities from creators who made a sustainable lifestyle out of these new-age creative and digital skills. Learners create hands-on projects and build a portfolio for themselves which is used to connect and collaborate with other peers, creators, and organizations. Habbit also helps provide discoverability for the creators to learners seeking mentorship and helps creators monetize to become micro-entrepreneurs through a revenue-sharing model from payments done by the learners on the platform.

Our immediate plans are to make our live classes and communities more seamless, interactive, and engaging while expanding our creator base. Our long term plans are to help learners achieve a tangible outcome by making their portfolios discoverable to other peers, creators and organizations for collaboration opportunities. We're also working on providing our creators more ownership, discoverability, and monetization strategies through services to their loyal fan base developed by delivering value through live interaction and communities. Our vision is to make Habbit the go-to platform and community to learn, connect, create and collaborate for creators.

# Problem Statements

- Suppose Habbit's uninstall rate is very high. We need to improve how many users stay on the app. Develop a metric which will be able to track App uninstalls and Active users on app.
- We see a lot of churn from "Free users" to "Paid Users". Develop a metric that will be able to track Conversion rate from Free users to Paid Users.

You can find the same problem statements as **issues**. <b>Read the issues and mention them while submitting a Pull Request.</b>

# Rewards

Habbit will be rewarding to the contributors in 100 Days of Feature Request. The following are their token of appreciation:
- Merchandise and Swags
- Discounts for Courses

# Table of Contest

* [Contributing](#contributing)
     * [Getting Started](#getting-started)
     * [Submission Guide](#submission-guide)
     * [Creating Pull Requests](#creating-pull-requests)
     * [Commenting on Pull Requests](#commenting-on-pull-requests)
     * [Labelling Pull Requests](#labelling-pull-requests)
     * [Reviewing Pull Requests](#reviewing-pull-requests)
* [Building and Validating](#building-and-validating)

## Contributing

### Getting Started

To get started with the contribution in the Habbit repository, simply fork it into your local GitHub account. Make the changes in the forked repository. In this case, the change will be related to the feature that you will be putting in. You can also clone the repository first, and then fork and push it along with the changes. This will also raise a PR.

**Note**: <b>Please be aware that Habbit will not share any codebase for this challenge. You are free to develop your own solution using your creativity and imagination (Like that in a hackathon). But, you have to keep the problem statament in mind while developing a solution.</b>

### Submission Guide

To make a submission for the brand Habbit in 100 Days of Feature Request, as a first step, fork the repository by clicking the fork button at the right hand corner. In the forked repository, you will be able to make changes and upload your code regarding the feature that you will be making and contributing.

In the forked repository, create a folder and in that folder, add all the required codes and documents needed for the feature. The folder name should contain your name and the name of the feature which you have built. After naming the folder and later on adding and uploading the contents inside the folder, you will be ready to raise a pull request.

**In the folder, you must have to make a README.md file which will have a detailed description about the feature solution.**

When you are raising a Pull Request, keep in mind to give a proper title of the PR which will be relevant to the changes. In the description section, give a proper description that will tell the summary of the feature request that you have built. Also, you can use markdown in the description that will help you to embed any link or add anything relevant with the description.

### Creating Pull Requests

1. When you're ready to submit your changes, add a descriptive title and comments to summarize the changes made.
2. Select **Create a new branch for this commit and start a pull request**.
3. Check the **Propose file change** button.
4. Scroll down to compare changes with the original document.
5. Select **Create pull request**.

### Commenting on Pull Requests

Once a pull request is submitted, multiple committers may comment on it and provide edits or suggestions which you can commit directly. You can also add line comments. Take a look at [Commenting on pull requests](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request) for more details.

### Labelling Pull Requests

A raised Pull Request will be labelled according to the work that has been done in the Pull Request. There are several labels to determine the work that is on-going with the Pull Request. For example, we requested a change in the pull request from the submitter, then the PR will be labelled as *awaiting submitter action*.

### Reviewing Pull Requests

The Pull Requests will be reviewed on a first come first serve basis. The community and product team of SAWO Labs will be responsible for the reviewing of Pull Requests. Keep in mind that spams will not be tolerated.

While reviewing the Pull Requests, we may contact the submitter of the PR regarding any changes that need to be made. If the submitter doesn't respond even after making several calls, then we will be forced to close the PR by labelling it as *incomplete*.

Once the review process is complete, the change is either merged into master and pushed immediately or merged into the release branch and pushed in alignment with the release. The branch is then deleted.

## Building and Validating

If you've downloaded the repository and are making a feature on your local machine, you can generate the HTML files from markdown. You can review your changes before you commit them or create pull requests.

**Note:** Commands can be executed on Linux, Mac, and Windows (using Powershell).

1. Open a terminal window, then clone a forked copy of the Habbit repository by running the following command::
```sh
https://github.com/Sawo-Community/Habbit.git
```
2. Install [pipenv](https://docs.pipenv.org/) by using one of the following commands based on your operating system:

For Mac users where Homebrew is installed:
```sh
brew install pipenv  
```
For other operating systems
```python
pip install pipenv 
```

100-DFR-Habbit

100-DFR-Habbit 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

100-DFR-Habbit

100-DFR-Habbit 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README