Skip to content

Commit

Permalink
pre release to public
Browse files Browse the repository at this point in the history
  • Loading branch information
mykola-den committed Jan 29, 2018
1 parent d898d2d commit 47f8526
Show file tree
Hide file tree
Showing 2 changed files with 77 additions and 23 deletions.
57 changes: 54 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,58 @@
# algorithm_club

## IS UNDER CONSTRUCTION
## FAQ

![](https://media.giphy.com/media/89U4ODjFSNdV6/giphy.gif)
### What are we learning?

**Draft** Plan for setup and jump start located [here](/course_setup.md).
- **[OSS Stanford Algorithm course](https://lagunita.stanford.edu/courses/course-v1:Engineering+Algorithms1+SelfPaced/)**
- Skiena's book or for additional tasks

### What should I know and have before I join?

1. Have optimusm and responsibility enough to keep track and endure the whole course.
1. Know at least one programming language suitable for completing course.
1. Know git and github enough to sen pull requests with your completed work.
1. Have a laptop to join our workshops/offline meetings.

### How do we organize our work?

- offline meetings twice per week.
- keeping track on progress
- peer review
- additional tasks presenting and review
- no restrictions on programming language to use, but we should be able and willing to explain our code to those unfamilliar with *my_beloved_programming_language*

### How to join?

>since we are just starting - we will be happy to welcome new participants
0. join our gitter chat linked to this project
1. Fork this repo.
2. Create subdirectory `%username%` in `\tasks` directory.
3. Send a pull request your work could be included and reviewed
4. All work is ought to be organized in `\tasks\user\week1\solution_1` manner.

### Are there any online sessions planned?

Yes, there are. Starting from February 8th, every Thursday from 19-30 to 21-00 there will be a google hangout session devoted to answering questions and helping each others.

### [Peer review Schedule](https://docs.google.com/spreadsheets/d/1J5AVhcWFsSCvLhU5mMZtLa0S6piCMq0WeNeX43D2Lp0/edit?usp=sharing)


>list of participants will be ordered by random.org
|| reviewer\Week number | week 1 | week 2 | week 3 | week 4 | week 5 | week 6 | week 7 | week 8 | week 9 |
|--|--|--|--|--|--|--|--|--|--|--|--|--|
| |||||review |kottan |number|
| 1 | username 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 2 |
| 2 | username 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 1 | 3 |
| 3 | username 3 | 4 | 5 | 6 | 7 | 8 | 9 | 1 | 2 | 4 |
| 4 | username 4 | 5 | 6 | 7 | 8 | 9 | 1 | 2 | 3 | 5 |
| 5 | username 5 | 6 | 7 | 8 | 9 | 1 | 2 | 3 | 4 | 6 |
| 6 | username 6 | 7 | 8 | 9 | 1 | 2 | 3 | 4 | 5 | 7 |
| 7 | username 7 | 8 | 9 | 1 | 2 | 3 | 4 | 5 | 6 | 8 |
| 8 | username 8 | 9 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 9 |
| 9 | username 9 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 1 |


>Plan for setup and jump start located [here](/course_setup.md).
43 changes: 23 additions & 20 deletions course_setup.md
Original file line number Diff line number Diff line change
@@ -1,19 +1,13 @@
# algorithm_club

## Plan for start
## List of students

### STATUS: DRAFT

## Duration

**6 weeks** -- optimistic scenario
**8 weeks**

>+2 weeks for unexpected jorney
>![](https://media.giphy.com/media/D0vg2MvsCxGrS/giphy.gif)
***29.01.2018 - 12.02.2018***

*if there will be the consensus dates may be shifted*. volontiers appreciated
***03.02.2018 - 12.02.2018***

## Mission

Expand Down Expand Up @@ -44,12 +38,30 @@ Here explanation needed. Hence we are driven to improve our code writing and cod

- twice per week in co-working

### venue list
- Data-hub m. Shulyavka [booking](https://data-hub.com.ua/datahub-coworking-meeting-room/) 250 uah/h



### Peer review Schedule

|| your reviewer\Week number | week 1 | week 2 | week 3 | week 4 | week 5 | week 6 | week 7 | week 8 | week 9 |
|--|--|--|--|--|--|--|--|--|--|--|--|--|
| 1 | username 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 2 |
| 2 | username 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 1 | 3 |
| 3 | username 3 | 4 | 5 | 6 | 7 | 8 | 9 | 1 | 2 | 4 |
| 4 | username 4 | 5 | 6 | 7 | 8 | 9 | 1 | 2 | 3 | 5 |
| 5 | username 5 | 6 | 7 | 8 | 9 | 1 | 2 | 3 | 4 | 6 |
| 6 | username 6 | 7 | 8 | 9 | 1 | 2 | 3 | 4 | 5 | 7 |
| 7 | username 7 | 8 | 9 | 1 | 2 | 3 | 4 | 5 | 6 | 8 |
| 8 | username 8 | 9 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 9 |
| 9 | username 9 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 1 |

## Group size

- expecting 10 max 15 people
- for each part of course there will be division into sub-groups
- optimistic drop-out rate 40%
> at the end we will invite to the alumni party all those who didn't make it to cheer you, as you actually made an effort to start and that deserves admiration ;)

### Activities between meetings

Expand All @@ -61,19 +73,10 @@ Here explanation needed. Hence we are driven to improve our code writing and cod

- peer review;
- each sub group prepares mini-task from **placeholder_algorithm_book** and present the story of solution;
>| Concerns:| -- | How to deal with|
>|--------- | -- | ----------------|
>| presentation equipment within co-working | -- | needs facility investigation
>| time limit during meetings | -- | 10 minutes * 15/2 group number == 75 minutes. decline time to 5 minutes or make this activity optional |
>| public speaking feare | -- | make this activity optional |


- task discussion;

## Peer review procedure

>**here discussion appreciated**

1. the one, who participate make fork of this repo
1. the one, who participate create a folder in `/tasks/%username%` location
Expand All @@ -83,4 +86,4 @@ Here explanation needed. Hence we are driven to improve our code writing and cod
1. each task is done in own fork and then a pull-request made to kottans repo
1. Pull request is sent for review to fellow kottan - each new **PR** to **next** kottan;
1. ???? - means review here
1. Pull request accepted and those from group who have write access merge PR to master;
1. Pull request accepted and those from group who have write access merge PR to master;

0 comments on commit 47f8526

Please sign in to comment.