asetalias / asetalias/blog

Sid?

Open
#19 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
11
Forks
22
PR merge metrics
No merged PRs in 30d

Description

Hello generous contributor,

Thank you for being part of ALiAS,
As a valued member you will be writing **one blog per month** (starting from 26 January 2019)
Do remember to go through the following conditions and ensure that the work is done on time and is of the highest quality (passable English at least)

- In the said period of time, the blog should be written on an electronic medium (anything except paper), on a relevant topic, critically reviewed by owner, grammatically accurate, spellchecked, reviewed by peers, informative, genuine and also as brief as possible going up to 200-400 words ensuring quality.
- The said blogs can be written in plain text files, markdown, and HTML by using any of the editors available in the _kitchen sink_ of a market that is today.
- The pull request needs to be this made, reviewed and merged in this repository only.
- Do try to include images, code snippets, GIF's, and whatever the new kids are up to these days.
- Failure to do the task, once published on the repository will attract a fine strictly of 100 rupees going to ALiAS Open-Source Charter of Funds helping with expenses involved in doing events of the core organization, ALiAS.
- Regardless of any and all points listed above, this task is deemed compulsory for any and all members by the ALiAS's mentor @bhanuvrat

**Assigned to**: @sidhu97ss
**Deadline**: 26 February 2019
**Blogs committed**: 3
**Topics** related to, suggested to but not limited to new things you learned, where you learned them, tips and tricks in Linux, new things you found, tools that you created, document your journey with ALiAS and anything at all.

We thank you for your contribution.

Your Treasurer.

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file, test, or specific blog topic is named. Review the repository's existing blog content and its Markdown or HTML conventions first, then determine whether three 200–400-word posts can be added. Done means the required posts are written, reviewed, and submitted as pull requests to this repository.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
content
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.