Skip to content
This repository was archived by the owner on Sep 16, 2023. It is now read-only.

Commit bfde463

Browse files
committed
first commmit
0 parents  commit bfde463

5 files changed

+82
-0
lines changed

.gitattributes

+4
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
*.zip filter=lfs diff=lfs merge=lfs -text
2+
*.pdf filter=lfs diff=lfs merge=lfs -text
3+
*.docx filter=lfs diff=lfs merge=lfs -text
4+
*.doc filter=lfs diff=lfs merge=lfs -text

README.md

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# eGaming Analytics
2+
3+
This is a group project that using AI for eGaming analytics to discover community interactions and interests.
4+
5+
## Table of Contents
6+
7+
- [Backgournd](#background)
8+
- [Contributors](#contributors)
9+
10+
## Background
11+
12+
eGaming is one of the popular entertainments nowadays. Twitch is a live streaming site popular with gamers that lets you share live game play for others to watch and comment on in real time. You can also watch playbacks of games being played and chat to other gamers. As a result, it created groups of communities which are eager on eGaming, and always discuss and comment on the eGames, and other hot topics. Therefore, the aim of this project is to analyse the eGaming discussion in Twitch. The analysis can be the hot topics discussion, favorite eGamers, eGaming scenes, etc. The project outcomes are expected to help the sports managers to know more about the fans’ favorite eGames, eGaming stars, eGaming scenes, etc., for future eGaming super stars recruitment, eGaming design, and eGames marketing.
13+
14+
## Software Guide
15+
16+
Because when working on this project, some of our members are new to programming, there are some materials maybe useful for coding.
17+
18+
Check the [guide](software-guide.md) here.
19+
20+
## Contributors
21+
22+
Thanks to all team members.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
version https://git-lfs.github.com/spec/v1
2+
oid sha256:e44a8b7cba63e9be85c9480259fcb3b2d4c6a5fd78dc9e31bde37150c3d245c1
3+
size 13157
Binary file not shown.

software-guide.md

+53
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# Software Guide
2+
3+
## Getting Started
4+
5+
Since all the group members (expected me :joy:) are using MacBook. These steps can help you set up a workstation.
6+
7+
1. Install [Homebrew](https://www.howtogeek.com/211541/homebrew-for-os-x-easily-installs-desktop-apps-and-terminal-utilities/).
8+
2. Install [iTerm2](https://www.iterm2.com/) (recommended).
9+
3. Install Fish and [Oh My Fish](https://theworkaround.com/2016/10/11/installing-fish-on-osx.html) (recommended).
10+
`brew install fish`
11+
4. Install python3.
12+
`brew install python3`
13+
5. Install pip (should be installed with python3 if you used Homebrew, use `pip3 --version` to check).
14+
6. Install Git
15+
`brew install git`
16+
7. Install Git LFS
17+
`brew install git-lfs`
18+
8. [Create ssh key and upload public key to github](https://www.testingexcellence.com/install-git-mac-generate-ssh-keys/)
19+
20+
## Coding Style
21+
22+
We are using Python and we can follow the [coding style of Google](https://google.github.io/styleguide/pyguide.html).
23+
24+
25+
## Git(Hub)
26+
27+
If you have time, you can read the [Pro Git](https://git-scm.com/book/en/v2) book. But I know we all have many other works to do. So I just write some topics about Git that we will encounter in the our project.
28+
29+
### Key points
30+
31+
1. Create a new branch from master branch when you are working. (DO NOT commit to master branch directly)
32+
2. Don't have multiple long-term maintained branches.
33+
3. Don't commit to other teammates' branches.
34+
4. After your work is finished, created a PR (pull request) to master and add a reviewer to review your code.
35+
5. Use `git lfs` to track large files and certain binary files.
36+
37+
### GitHub workflow
38+
39+
This is a team project, we want to have a simple and clean history of our work. We need to [understand the GitHub flow](https://guides.github.com/introduction/flow/).
40+
41+
### Basic usage of git
42+
43+
https://rogerdudler.github.io/git-guide/
44+
45+
The most simple way is to remember whenever you make changes to you work, you use the commands
46+
47+
``` git
48+
git add .
49+
git commit -m "<your comment for you commit>"
50+
git push origin <your branch>
51+
```
52+
53+
Replace the contents in `< >` based on your situation.

0 commit comments

Comments
 (0)