VulsMeetup #1 How to contribute Vuls

# vuls

![vuls_logo.png](https://qiita-image-store.s3.amazonaws.com/0/55672/f892eb92-7472-a9ca-444e-b6b3a97ada8b.png)


---

# Agenda

1. Who am I
2. Happy stories Vuls aims for
3. Contribution by coding
4. Contribution by documentation
5. Conclusion

---

# Who am I

- Sadayuki Matsuno([Github](https://github.com/sadayuki-matsuno), [Facebook](https://www.facebook.com/sadayuki.matsuno.7))
- Future Architect, Inc. Japan

![1473693753.jpeg](https://qiita-image-store.s3.amazonaws.com/0/55672/19d744a1-599d-0657-5571-a9f13878a52e.jpeg)

---

# Thank you for stocking my article

<img width="1187" alt="スクリーンショット 2016-09-26 18.32.40.png" src="https://qiita-image-store.s3.amazonaws.com/0/55672/fcd04fdf-8b6a-fd18-d978-e17dd7460831.png">


---

# The Origin of Vuls

India is the origin of Vuls.
[kotakanbe](https://github.com/kotakanbe) returned from india, and he decided to contribute the World Peace.

![Flag_of_India.svg.png](https://qiita-image-store.s3.amazonaws.com/0/55672/aef495aa-f9e7-b922-df86-f0cfdf779000.png)



---

# kotakanbe's Hope

He wish everyone will be happy with Vuls.
Vuls users will and Vuls contributor as well.

![ダウンロード.jpeg](https://qiita-image-store.s3.amazonaws.com/0/55672/c3c97863-64c9-6174-d542-c13e3db870b2.jpeg)


---

# Vuls Welcome Pull Requests

Vuls will be glad to accept new features and also misspells of README.

<img width="1001" alt="スクリーンショット 2016-09-26 18.39.53.png" src="https://qiita-image-store.s3.amazonaws.com/0/55672/f7e3ba26-e6ae-6117-8a09-a1c5c7bb33fd.png">

---

# You can be HAPPY by the coding contribution

By coding contributions, you can ...

- customize vuls as you like.
- receive coding reviews from kotakanbe.
- be a famous programmer as a big OSS contributor.

<img width="511" alt="スクリーンショット 2016-09-26 18.41.23.png" src="https://qiita-image-store.s3.amazonaws.com/0/55672/c4e68fcd-31fb-018b-1d5c-3ca1e751c17b.png">



---

# How to develop Vuls

I recommend you develop vuls under $GOPATH/src/github.com/future-architect/vuls.
when running your vuls code, you execute `go run main.go` or `go build && ./vuls` 
see http://blog.campoy.cat/2014/03/github-and-go-forking-pull-requests-and.html

After developing something you want, you push the vuls code into your fork repository, and make a pull request.

---

# Important Points

There are 3 points we should confirm before making pull request.

1. Codeing Style.
  - kotakanbe, of course, has the own coding style. you should check it at codes. If you are unable to make a decision, you can casually ask kotakanbe at the vuls slack team.

1. Rebase.
    - The vuls owner(kotakanbe) will be glad if you fix conflict before sending the pull request.
1. Combining multiple commits into one.
    - a pull request that is consisted of one commit, is simple and easy to read.
    - If you want to separate your commits, it's better to separate your pull request.

Finally, Im looking forward to your pull requests.

---

# How to make the Vuls develop environment

I made vuls cloudformation and vuls cookbook.
Unfortunately, this is under development.

[cookbook](https://github.com/sadayuki-matsuno/vuls-cookbook)
[cloudformation](https://github.com/sadayuki-matsuno/vuls-cf)

<img width="561" alt="スクリーンショット 2016-09-26 18.50.25.png" src="https://qiita-image-store.s3.amazonaws.com/0/55672/8ec059b4-9d3f-67d2-6441-47cb20147f36.png">


---

## You are not a golang programmer?　 Don't worry about it.

---

# Vuls documentation project is coming...

---

# You can be HAPPY by the document contribution too

We will start the Vuls documentation project.（Perhaps, next week）
If you can not contribute Vuls by coding, you can do it by documentations.

---

# Let's become HAPPY with Vuls.

![082cb2e0b1560a656efc79093cf342bd.png](https://qiita-image-store.s3.amazonaws.com/0/55672/92f95b7d-9b3d-a963-5e0c-a394f2f0b90d.png)