About two months ago, I heard Steemit and started to follow and dig the project. In this period, I read Steem Whitepaper and get more excited about the project but I couldn't join in since I had issues with registration. One of these days, I continued to follow and read through Steemit, and then I was introduced to Utopian.io and fell in the idea of helping open source community rise and being able to contribute full time since open source contributors can make a living off things they do for the good ever after. This was a life-changing moment and I started writing as soon as I could manage to buy an account.
Since I discovered Utopian Community, I spend almost 100% of my time reading posts in Steemit, mostly on Utopian. After a while, I realized that moderation process for posts are not as fast as it should be. I thought this is a once in a lifetime opportunity to help Utopian and open source community as my full-time job. Due to these reasons, I want to participate in the Utopian Team if you find me skilled enough.
Briefly, I'm a full-stack developer, advanced Linux user, open source contributor and a dropout Physicist. My full name is Rojhat Sinan Balka and I spend most of my time reading online in subjects related to both computers and science. I am a native speaker of Turkish and I also speak English.
Back then, I started programming when I was 10 years old and I got my first role as a moderator in a cybersecurity forum at my 12. Then, I ran some of my own IT and cybersecurity forums when they were popular. In this journey, I worked as a full-stack web developer and within these years I wrote mostly PHP, JavaScript, HTML, and CSS. After some years in web development, I switched to OS and scripting languages like C/C++, Python and recently I started writing Golang.
In the college years, I voluntarily worked as a web developer in student projects like online radios and student society websites, created a brand with my Chemist friends and played as a captain of a Curling team in National 2nd League. In the light of these, I trust my management and communication skills and I think that those are keys in any kind of teamwork.
I started contributing by translating Bitcoin's original whitepaper and preparing a GRUB tutorial. And since the first day, I try to remain loyal to my "one contribution per day at least" rule. On the days I do translations, I prepare documentation for my future contributions and blog series on Linux Architecture and Programming. Some of my past contributions are the following:
Since my main goal is to help speeding up the moderation process, I want to work in the most contributed categories, which are translations, tutorials, and video tutorials.
If a team preference is possible, I want to participate in @Ruah 's team. To my observations in my talks with supervisors, I found that Ruah is the one I could easily get along with. Since this is just a preference, it is not too important and depends on him and status of his team.
I picked some Utopian posts to show how I would evaluate them if I were a moderator.
Your contribution can not be approved since it doesn't follow the Utopian Rules:
- End-user focused tutorials must address a minimum of three substantial concepts that are unique to the Open Source project and essential learning requirements for end-users. Preference is given to tutorials that are part of a curriculum (series) of tutorials all of which are sequential and built on previously learned skills and knowledge. Ubiquitous functions, such as Save, Open, and Print are unacceptable as substantial concepts.
- This tutorial is too simple and doesn't contain any technical aspects.
Thank you for the contribution. It has been approved.
Your contribution cannot be approved since it doesn't follow the Utopian Rules:
- End-user focused tutorials must address a minimum of three substantial concepts that are unique to the Open Source project and essential learning requirements for end-users. Preference is given to tutorials that are part of a curriculum (series) of tutorials all of which are sequential and built on previously learned skills and knowledge. Ubiquitous functions, such as Save, Open, and Print are unacceptable as substantial concepts.
Thank you for the contribution. It has been approved.
Thank you for the contribution. It has been approved.
