Skip to content

Commit fc7d17a

Browse files
committed
[INIT] Initializing blog post with book review of .
0 parents  commit fc7d17a

9 files changed

+244
-0
lines changed

.gitignore

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
_site
2+
.sass-cache
3+
.jekyll-metadata

Gemfile

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
source "https://rubygems.org"
2+
ruby RUBY_VERSION
3+
4+
# Hello! This is where you manage which Jekyll version is used to run.
5+
# When you want to use a different version, change it below, save the
6+
# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
7+
#
8+
# bundle exec jekyll serve
9+
#
10+
# This will help ensure the proper Jekyll version is running.
11+
# Happy Jekylling!
12+
gem "jekyll", "3.3.1"
13+
14+
# This is the default theme for new Jekyll sites. You may change this to anything you like.
15+
gem "minima", "~> 2.0"
16+
17+
# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
18+
# uncomment the line below. To upgrade, run `bundle update github-pages`.
19+
# gem "github-pages", group: :jekyll_plugins
20+
21+
# If you have any plugins, put them here!
22+
group :jekyll_plugins do
23+
gem "jekyll-feed", "~> 0.6"
24+
end

Gemfile.lock

+56
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
GEM
2+
remote: https://rubygems.org/
3+
specs:
4+
addressable (2.5.0)
5+
public_suffix (~> 2.0, >= 2.0.2)
6+
colorator (1.1.0)
7+
ffi (1.9.14)
8+
forwardable-extended (2.6.0)
9+
jekyll (3.3.1)
10+
addressable (~> 2.4)
11+
colorator (~> 1.0)
12+
jekyll-sass-converter (~> 1.0)
13+
jekyll-watch (~> 1.1)
14+
kramdown (~> 1.3)
15+
liquid (~> 3.0)
16+
mercenary (~> 0.3.3)
17+
pathutil (~> 0.9)
18+
rouge (~> 1.7)
19+
safe_yaml (~> 1.0)
20+
jekyll-feed (0.8.0)
21+
jekyll (~> 3.3)
22+
jekyll-sass-converter (1.5.0)
23+
sass (~> 3.4)
24+
jekyll-watch (1.5.0)
25+
listen (~> 3.0, < 3.1)
26+
kramdown (1.13.1)
27+
liquid (3.0.6)
28+
listen (3.0.8)
29+
rb-fsevent (~> 0.9, >= 0.9.4)
30+
rb-inotify (~> 0.9, >= 0.9.7)
31+
mercenary (0.3.6)
32+
minima (2.1.0)
33+
jekyll (~> 3.3)
34+
pathutil (0.14.0)
35+
forwardable-extended (~> 2.6)
36+
public_suffix (2.0.4)
37+
rb-fsevent (0.9.8)
38+
rb-inotify (0.9.7)
39+
ffi (>= 0.5.0)
40+
rouge (1.11.1)
41+
safe_yaml (1.0.4)
42+
sass (3.4.23)
43+
44+
PLATFORMS
45+
ruby
46+
47+
DEPENDENCIES
48+
jekyll (= 3.3.1)
49+
jekyll-feed (~> 0.6)
50+
minima (~> 2.0)
51+
52+
RUBY VERSION
53+
ruby 2.3.1p112
54+
55+
BUNDLED WITH
56+
1.13.7

_config.yml

+34
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# Welcome to Jekyll!
2+
#
3+
# This config file is meant for settings that affect your whole blog, values
4+
# which you are expected to set up once and rarely edit after that. If you find
5+
# yourself editing this file very often, consider using Jekyll's data files
6+
# feature for the data you need to update frequently.
7+
#
8+
# For technical reasons, this file is *NOT* reloaded automatically when you use
9+
# 'bundle exec jekyll serve'. If you change this file, please restart the server process.
10+
11+
# Site settings
12+
# These are used to personalize your new site. If you look in the HTML files,
13+
# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
14+
# You can create any custom variable you would like, and they will be accessible
15+
# in the templates via {{ site.myvariable }}.
16+
title: Jaysinh's own heed
17+
18+
description: > # this means to ignore newlines until "baseurl:"
19+
Write an awesome description for your new site here. You can edit this
20+
line in _config.yml. It will appear in your document head meta (for
21+
Google search results) and in your feed.xml site description.
22+
baseurl: "" # the subpath of your site, e.g. /blog
23+
url: "blog.jaysinh.com" # the base hostname & protocol for your site, e.g. http://example.com
24+
twitter_username: jaysinhp
25+
github_username: ultimatecoder
26+
27+
# Build settings
28+
markdown: kramdown
29+
theme: minima
30+
gems:
31+
- jekyll-feed
32+
exclude:
33+
- Gemfile
34+
- Gemfile.lock

_config.yml~

+34
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# Welcome to Jekyll!
2+
#
3+
# This config file is meant for settings that affect your whole blog, values
4+
# which you are expected to set up once and rarely edit after that. If you find
5+
# yourself editing this file very often, consider using Jekyll's data files
6+
# feature for the data you need to update frequently.
7+
#
8+
# For technical reasons, this file is *NOT* reloaded automatically when you use
9+
# 'bundle exec jekyll serve'. If you change this file, please restart the server process.
10+
11+
# Site settings
12+
# These are used to personalize your new site. If you look in the HTML files,
13+
# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
14+
# You can create any custom variable you would like, and they will be accessible
15+
# in the templates via {{ site.myvariable }}.
16+
title: Jaysinh's own heed
17+
18+
description: > # this means to ignore newlines until "baseurl:"
19+
Write an awesome description for your new site here. You can edit this
20+
line in _config.yml. It will appear in your document head meta (for
21+
Google search results) and in your feed.xml site description.
22+
baseurl: "" # the subpath of your site, e.g. /blog
23+
url: "" # the base hostname & protocol for your site, e.g. http://example.com
24+
twitter_username: jaysinhp
25+
github_username: ultimatecoder
26+
27+
# Build settings
28+
markdown: kramdown
29+
theme: minima
30+
gems:
31+
- jekyll-feed
32+
exclude:
33+
- Gemfile
34+
- Gemfile.lock
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
layout: post
3+
categories: book review
4+
title: Book review 'i want 2 do project tell me wat 2 do'
5+
tag: books
6+
---
7+
8+
## One line review
9+
10+
Inspirational book for students who are at a fresher level.
11+
12+
## Detailed review
13+
14+
The book is small and you can read it in a day or two. The author has mentioned important points for a newcomer with plenty of quotations. I believe these words are good advice for students. Some guidelines are very realistic. Even I have faced them during my academic years. The book depicts the wise experience of the writer. Your confusions with FOSS will mostly be resolved after reading this book.
15+
16+
Following are a few of my observations:
17+
18+
* Giving away email access to social networking sites
19+
* The importance of sending plain text emails
20+
* Not responding to email digest
21+
* Time management of project
22+
* Avoiding last minute changes in the code
23+
* Habit of daily committing the development work
24+
* Difference between shallow and fast vs deep and slow learning
25+
* Taking project decisions without informing mentors due to overconfidence
26+
* Selecting the programming language for your project
27+
* Not to fall for market trends
28+
* Ways of reporting a bug
29+
* Importance of automated build and deployment systems
30+
* Diverse types of documentation and their usage
31+
* The value of reading and writing and how to amend them
32+
* Benefits of going to conferences, hackathons etc.
33+
34+
I would like to suggest following improvements to this book. Some references are repeatedly cited, I think they can be referenced commonly without repeating them at the end of chapter. Examples of source code is not written with a different font. It is good to have syntax highlighting for keywords of programming language used. While informing students on mailing list etiquette, it will be good to guide them about mail encryption technologies (GnuPG, etc) too. As a reader, I will prefer to have one common section of coding related guidelines rather than small section in many chapters.
35+
36+
Overall this book deserves “must read” if you are a student or you are an experienced professional who don’t have much exposure to FOSS. The book is “worth reading” even if you are a contributor of any project. It clearly explains the initial steps of FOSS mentorship. The book is an independent piece of work and is not specific to any FOSS project or community. The guidelines given in the book are applicable for any FOSS community or project. I congratulate Shakthi for his inspirational writing. Such efforts are required to inspire upcoming generation.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
layout: post
3+
categories: book review
4+
title: Book review 'i want 2 do project tell me wat 2 do'
5+
tag: books
6+
---
7+
8+
## One line review
9+
10+
Inspirational book for students who are at a fresher level.
11+
12+
## Detailed review
13+
14+
The book is small and you can read it in a day or two. The author has mentioned important points for a newcomer with plenty of quotations. I believe these words are good advice for students. Some guidelines are very realistic. Even I have faced them during my academic years. The book depicts the wise experience of the writer. Your confusions with FOSS will mostly be resolved after reading this book.
15+
16+
Following are a few of my observations:
17+
18+
* Giving away email access to social networking sites
19+
* The importance of sending plain text emails
20+
* Not responding to email digest
21+
* Time management of project
22+
* Avoiding last minute changes in the code
23+
* Habit of daily committing the development work
24+
* Difference between shallow and fast vs deep and slow learning
25+
* Taking project decisions without informing mentors due to overconfidence
26+
* Selecting the programming language for your project
27+
* Not to fall for market trends
28+
* Ways of reporting a bug
29+
* Importance of automated build and deployment systems
30+
* Diverse types of documentation and their usage
31+
* The value of reading and writing and how to amend them
32+
* Benefits of going to conferences, hackathons etc.
33+
34+
I would like to suggest following improvements to this book. Some references are repeatedly cited, I think they can be referenced commonly without repeating them at the end of chapter. Examples of source code is not written with a different font. It is good to have syntax highlighting for keywords of programming language used. While informing students on mailing list etiquette, it will be good to guide them about mail encryption technologies (GnuPG, etc) too. As a reader, I will prefer to have one common section of coding related guidelines rather than small section in many chapters.
35+
36+
Overall this book deserves “must read” if you are a student or you are an experienced professional who don’t have much exposure to FOSS. The book is “worth reading” even if you are a contributor of any project. It clearly explains the initial steps of FOSS mentorship. The book is an independent piece of work and is not specific to any FOSS project or community. The guidelines given in the book are applicable for any FOSS community or project. I congratulate Shakthi for his inspirational writing. Such efforts are required to inspire upcoming generation.

about.md

+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
layout: page
3+
title: About
4+
permalink: /about/
5+
---
6+
7+
This is the base Jekyll theme. You can find out more info about customizing your Jekyll theme, as well as basic Jekyll usage documentation at [jekyllrb.com](http://jekyllrb.com/)
8+
9+
You can find the source code for the Jekyll new theme at:
10+
{% include icon-github.html username="jekyll" %} /
11+
[minima](https://github.com/jekyll/minima)
12+
13+
You can find the source code for Jekyll at
14+
{% include icon-github.html username="jekyll" %} /
15+
[jekyll](https://github.com/jekyll/jekyll)

index.md

+6
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
# You don't need to edit this file, it's empty on purpose.
3+
# Edit theme's home layout instead if you wanna make some changes
4+
# See: https://jekyllrb.com/docs/themes/#overriding-theme-defaults
5+
layout: home
6+
---

0 commit comments

Comments
 (0)