sg_dlb_2017's Introduction

Danbury Artificial Intelligence

Deep Learning Study Group

A repo for our deep learning book study group launched in October 2017. This is a living repo that is subject to rapid change. Also, most work is in progress, and nothing should be taken as final unless marked so. If you'd like to contribute, join our meetup group and message the organizers.

Featured Jupyter Notebooks

In this group we aim to disseminate knowledge through code, prose, and mathematics -- a lovely combination that Jupyter Notebooks provide. Here are our best Notebooks so far.

Machine Learning Basics

Most Active Members

About Danbury AI

Danbury AI is a public AI meetup group hosted by the Danbury Hackerspace that aims to stimulate discussion in the vast field of artificial intelligence and bring together locals that foster a passion for the field. We hold our in person meetings on the first Tuesday of every month at which we host a variety of presenters, discussions, and workshops. We maintain a lively web presence via slack so the conversation never stops.

sg_dlb_2017's People

Contributors

Stargazers

Watchers

sg_dlb_2017's Issues

prince book exercises

this commit needs check

Verification of Work

Typically there is some verification process when we merge a pull request into a branch. This is called integration testing. We aren't, however, writing one code base, so integration testing upon merge is a bit weird. There are a few methods, as discussed, how we could go about verifying that the materials published here are reviewed by the group so that we are not committing garbage to the world.

Verification procedure:

Depends on our method chosen below.
Method 1: We commit a file to our fork, then make a pull request from our fork to the master branch.
Method 2: We commit a file to our fork of the dev branch, then make a pull request from our dev branch fork to the dev branch master.
Make an issue to discuss the verification of the commit.
When we decide a file is verified by conversation on the verification issue, we again use a procedure by one of the methods outlined below.

Syntax for verification commit message: Verified verification_issue_id

Method 1: Last commit saying verified.
While the last commit message is not verified, it means that it is in progress or has not been verified by the group. Once the file has been through the verification procedure, we make a final commit on that file saying passed verification with a link to the verification issue.

Method 2: Have a working branch and a verified branch
On the in progress branch we will have all non-verified files, the other verified files. Once a file has been trough the verification procedure, we push the file to the verified branch with a commit message saying that file saying passed verification with a link to the verification issue.

I vote for method 1 with the procedure being:

We commit a file to our fork, then make a pull request from our fork to the master branch.
The pull request is merged.
When we are done working on the file, we make an issue to discuss verification.
When the file has been verified, we make another commit to our fork saying Verified .
We again make a pull request from our fork to the master branch.
That pull request is merged into master with the same commit message ( Verified verification_issue_id)

danburyai / sg_dlb_2017 Goto Github PK

sg_dlb_2017's Introduction

Danbury Artificial Intelligence

Deep Learning Study Group

Featured Jupyter Notebooks

Linear Algebra

Probability, Statistics, and Information Theory

Numerical Computation

Machine Learning Basics

Most Active Members

About Danbury AI

sg_dlb_2017's People

Contributors

Stargazers

Watchers

Forkers

sg_dlb_2017's Issues

Recommend Projects

Recommend Topics

Recommend Org