<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ritik Malik on Medium]]></title>
        <description><![CDATA[Stories by Ritik Malik on Medium]]></description>
        <link>https://medium.com/@ritik18406?source=rss-30fb0a45fd59------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IMsPm2JFvMxoJm1F3_L0Fg.jpeg</url>
            <title>Stories by Ritik Malik on Medium</title>
            <link>https://medium.com/@ritik18406?source=rss-30fb0a45fd59------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:25:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ritik18406/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Kareri Lake Trek — Bullet Points Itinerary ]]></title>
            <link>https://ritik18406.medium.com/kareri-lake-trek-bullet-points-itinerary-67135a07ba4e?source=rss-30fb0a45fd59------2</link>
            <guid isPermaLink="false">https://medium.com/p/67135a07ba4e</guid>
            <category><![CDATA[zostel]]></category>
            <category><![CDATA[solo-trek]]></category>
            <category><![CDATA[dhauladhar]]></category>
            <category><![CDATA[kareri]]></category>
            <category><![CDATA[kareri-lake-trek]]></category>
            <dc:creator><![CDATA[Ritik Malik]]></dc:creator>
            <pubDate>Tue, 14 May 2024 17:05:19 GMT</pubDate>
            <atom:updated>2024-05-14T17:05:19.357Z</atom:updated>
            <content:encoded><![CDATA[<h3>Kareri Lake Trek — Bullet Points Itinerary 🏞</h3><p>Don’t have time to go over long stories and want a last minute bullet listed trek guide for Kareri Lake? Here you go! 🤸‍♂️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AVYnKcgyDrW36Off4ZWU7Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jM7bNw_WZuOWTWgkw0KsxQ.jpeg" /><figcaption>All hail the Mighty Dhauladhar! 🏔🗿</figcaption></figure><h3>🛠 <strong>Few points to note:</strong></h3><ul><li>A short bullet point itinerary of Kareri Lake Trek</li><li>This was a solo trek with no personal vehicle, so the experience may differ</li><li>I trekked in early May, so the weather also experience may differ</li><li>I stayed overnight and descended the next day</li></ul><h3>🚌<strong> Day 0: Delhi to Dharamshala</strong></h3><ul><li>Standard overnight Volvo bus journey (private Volvo ~ 1200 INR)</li><li>Carry an eye-mask if required</li><li>Try to arrive Dharamshala around 9ish if possible<br>- Since shops/cafes/museums are mostly closed early morning</li><li>Local fruit shops are open early morning</li><li>Only temples and wilderness can be visited before 9–10<br>- Or you can travel around till McLeodganj and Bhagsu for breakfast</li></ul><h3>🏡<strong> Day 1: Dharamshala to Kareri Zostel</strong></h3><ul><li>Around 45 mins journey of around 11 KMs</li><li>No direct bus, have to take a local taxi</li><li>Taxi costs around 1000–1200ish INR after bargain (Lord Alto Supremacy!)</li><li>Beware! Zostel admin might say no direct taxi available from Dharamshala to Zostel<br>- Since they charge more for their personal vehicle</li><li>Zostel Plus Kareri is quite clean and nice<br>- Swimming pool, snooker, TT, swings, etc to play around<br>- Food is a bit expensive and not that good<br>- You can get your own booze/they have a bar — an expensive one!<br>- Overall property is quite big and nice!<br>- I stayed in capsule room, they were ~800 per night</li><li>Not much to explore around the Zostel<br>- The Kareri Village is still 15ish mins drive away<br>- Can explore nearby temples at a short hike<br>- Collect nearby fallen pines — they are good<br>- A few eateries/stalls around with cheaper options<br>- Local folks are really nice &amp; friendly</li></ul><h3>🏕 <strong>Day 2: Trek to Kareri Lake</strong></h3><ul><li>Kareri Lake Trek start point is 30 mins drive from Zostel<br>- Start out early around 8 in the morning<br>- Can fix a ride till there from a local taxi<br>- On sharing in 4, it’s usually 300 per person (one way)<br>- Cab drivers might offer tent accommodations at Lake too (more on it later)<br>- Zostel offers relatively expensive cab/tents for obvious reasons</li><li>The overall trek distance is 10 KMs from the starting point to the Lake as mentioned on the billboard<br>- But I think it is actually 12–13ish?</li><li>Try to start the trek around 9 so you can reach by 2–3</li><li>Online it says moderately difficult, my first trek so not much clue</li><li>They sell a poncho outside the starting point<br>- It’s always safe to get one coz weather is very unpredictable<br>Luckily I didn’t get to use it coz it was sunny, so they took it back later at half price — 50 INR</li><li>Guide is not needed as it’s a pretty straightforward trek<br>- Just follow the obvious trail and intuitions</li><li>Try to travel on weekdays, it’ll be less crowded</li><li>4–5 shacks on the way up<br>- They mostly open on weekends<br>- Omelettes and Maggi were the only good options<br>- Some of them do prepare pancakes, rajma chawal, etc occasionally though</li><li>There is no network on the entire trek except 1 place<br>- That place is roughly 2 KMs from the start<br>- Can use that place to contact your driver when descending<br>- Airtel SIM works best in that terrain</li><li>Drinking water is best from the running stream<br>- Can fill the bottles directly from it</li><li>Most of the trek way is along the stream<br>- Some places at the stream are marked for swimming!</li><li>A metal bridge will indicate almost half way</li><li>There’s a lot of stinging nettle (Bichu Buti) in the way, so avoid touching them</li><li>As for wildlife there are just local village dogs and sheep</li><li>On reaching the top you’ll find many camps by the riverside<br>- Can book camps from the local driver itself (they got contacts uphill)<br>- Can book camps directly on site<br>- Can carry your own<br>- Their camp package include evening Tea, Dinner, Breakfast &amp; nightcamp (1200 per person)</li><li>There are other shacks with all kinds of packaged eatables</li><li>No electricity/signal up there, locals use solar for batteries &amp; nightlight<br>- They cook in a nearby cave!</li><li>Do carry a good powerbank and set your phone to airplane mood to save battery<br>- Since there is already no signal, switch off unessential data services</li><li>The overall time we took was around 5 hours (including multiple stops)</li><li>Kareri Lake is 200m from the camping area<br>- Earlier camping was allowed near the lake<br>- Thanks to the <strong>educated</strong> campers for littering and getting it banned!</li><li>I went in early May, so mostly the snow was gone<br>- Only little to no snow on the hike</li><li>The lake was beautiful with a good view of Dhauladhar range</li><li>Beside the lake there is a huge patch of grassland with sunset point<br>- Sunset point is a good place to get echos!<br>- As soon as the sunset it’ll get very cold &amp; windy<br>- So pack clothes/caps/gloves till the sunset point</li><li>Night sky is full of stars and milky way was visible with naked eyes during 3–4 in the night</li></ul><h3>🏔 <strong>Day 3: Descend from Kareri Lake</strong></h3><ul><li>Try to get up early to witness the sunrise from the Dhauladhar range</li><li>Most campers descend around 8-9 in the morning</li><li>Descend is way faster in about 3–4 hrs</li><li>Remember to call your cab driver in that small range of network (ask locals shacks for location)</li></ul><h3>— THE END — 🎬</h3><h3>🍿 <strong>Extras!</strong></h3><ul><li>Some people do the climb and descend in a single day, while some takes 2 days to reach (so it’s really upto you)</li><li>Guide is really not needed. It was my first solo trek and I did fine without a guide. Just go with the flow<br>- Not sure about winters though, since the trail might be difficult to follow in the snow<br>- Don’t attempt the trek in monsoon</li><li>Get good shoes/boots and clothing, they’ll be worth it</li><li>Pro Tip: Petrol pumps are really good stops for 2 reasons:<br>- number 1 and ofc number 2 (iykyk)</li><li>From the lake view of Dhauladhar, there is another trek till the top of that icy peak<br>- The local guide up there charges around 5k per person<br>- Guide is really advisable for that since they know their way in the snow and you require special clothing &amp; ropes<br>- Usually people go there with 2 guides and at 5 in the early morning, since snow starts to melt as you descend by around 9–10 AM</li><li>From the Kareri Lake start another trek: Dhauladhar 7 Lakes trek<br>- Kareri Lake is one of them</li><li>Don’t litter! Take your trash with you, you trash!</li></ul><h3>🎥 <strong>Postscript</strong></h3><p>Hi there! 🐈</p><p>Hope the guide helped you in planning your trek. This was my first trek and that too solo. I really enjoyed and had a great experience.</p><p>On my trip I befriended a lot of people from different places. Some were from Ladakh, some from Pune, Mumbai, Palampur, NCR (ofc), monks etc. It was really fun mingling with ethnically diverse people and sharing experiences. Specially the locals were really friendly and good.</p><p>If you plan for a longer workation of around a month or more, the locals do rent our their rooms for it. They are going to be much cheaper: around 7k per month (ofc excluding food and laundry). It’s a really good and economical option.</p><p>If you got more time, do visit Bhagsu and Dharamkot. Bhagsu is a really beautiful town with various temples/monasteries and a waterfall. The street shopping experience is also good. Dharamkot will remind you of Majnu ka Tila in Delhi, those slim lanes are packed with beautiful cafes with good aesthetics and great food (they are a bit expensive though). You’ll find plenty of foreigners there, specially Israelis (half the menus &amp; signboards are in Hebrew). It’s fun to connect with them too. Then in McLeodganj there are prime monasteries, main market and Italian kitchens. Try to travel in weekdays to avoid the rush.</p><p>Do comment if you had a good read/got any doubts. I’m too free to answer them!</p><p>Meanwhile, enjoy the photo gallery! 📸</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sAsmV_jMWgQ5kkRlNsPJCA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qjRjQCg_nCCYgVbuxmms7Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*74P0TA-iEmdZkGkuOy8zAg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RCcqZKceZCROyCskft6qDg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9sJBY3N-45hp3Tyno_ZZ-g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rTvD-zfFDESlVF85eKBR1w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rtVWOCe55sBYs3fICZpMAA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tkeu_IrYlHNdND6GK-W68Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HO1NFM4IYbMtuBGWWTb_pw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A_0ymVJdoDRSSg4NPBsoVA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K9b8hquYdVINYoQBhmffNw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yx10RcC2IqCL8wCwnSKkpw.jpeg" /><figcaption>Trip in a nutshell 🥜🐿️</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67135a07ba4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC ’21 — The Conclusion]]></title>
            <link>https://ritik18406.medium.com/gsoc-21-the-conclusion-bdbb0c1d082c?source=rss-30fb0a45fd59------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdbb0c1d082c</guid>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[gsoc2021]]></category>
            <category><![CDATA[chaoss]]></category>
            <dc:creator><![CDATA[Ritik Malik]]></dc:creator>
            <pubDate>Sat, 21 Aug 2021 10:48:02 GMT</pubDate>
            <atom:updated>2021-08-21T10:48:02.568Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC ’21 — The Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ng8mL4gx2m58Pf1cjHaJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*svt0-0AVxSyxMqwbF9ycZw.png" /></figure><p>Finally, it’s an end to the beautiful 3 month long journey of Google Summer of Code with the CHAOSS Community! This blog serves to summarize my experience.</p><p>It all started with a minor typo fixing in the website and now we’ve our own new repository for our M.A.R.S. project! We manage to accomplish all the proposed goals well in time. It has been such a memorable experience attending all the mentor mentee meetings, the weekly community calls and the various working group meetings!</p><p>About <strong>M.A.R.S. </strong>—</p><p>CHAOSS metrics have been defined to provide an in-depth view into the various features of an open-source project. The metrics are also a key input to help organizations strategically invest their resources.</p><p><strong>M.A.R.S. (Metrics Automated Release System)</strong> aim is to automate &amp; improve the metric release process. Keeping in mind the ever evolving CHAOSS, the system is scalable and flexible enough for easy tweaking in the future.</p><p>The final outcome is generation of reports for the metrics and their translations counterparts respectively.</p><p>Summary of Coding Periods —</p><p><strong>Coding Period 1:</strong></p><ul><li>Initially me and Yash had some different approaches to the project. Soon we realized that merging them would be the best choice. My idea was to the yml file structure while he proposed to use the LaTeX tree structure.</li><li>Then we decided to rename our project to MARS! And started making templates for the focus-areas tex files.</li><li>We created these standard templates (for focus-area READMEs and the metric markdowns) which resides in the governance repository.</li><li>Then we decided that it would be best if we could containerize the project with Docker to make it cross platform.</li><li>Finally we’re able to generate a prototype PDF release, with dynamic 3 level Table of Contents, and also included Focus-areas tables in the report.</li><li>The basic Docker implementation was done and we were able to launch to MARS on Linux and Mac OS/X</li><li>Alongside, we were also working on standardization of all the Working Group Repositories. For the Docker part, we also made an automation script.</li></ul><p>Then we had our 1st evaluations, which we passed!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/435/1*fNN9Kopp6M_WcGA5V4dm1Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/515/1*neSJ-02QfYeMcOmk8axUmw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/577/1*fg6qxjBn-Flb1vj3ZHfh_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*MCuKUuSabCYEf4LzDCi8_A.png" /><figcaption>Glimpses of M.A.R.S. automation script</figcaption></figure><p><strong>Coding Period 2:</strong></p><ul><li>We found some issues with Docker in Mac and tried to fix them.</li><li>Then we had a basic user testing from new contributors and the mentors. And we renamed a few scripts for more descriptive names.</li><li>We made some great progress in the standardization of WGs.</li><li>The last 3 weeks were pretty busy and crucial for MARS. We made separate yml config and cover files for translations. We implemented the translation system for MARS along with a language menu.</li><li>For translations we made a new Docker image on DockerHub since the Chinese characters needed a separate package in LaTeX.</li><li>Then we focused on the documentation part and creating translation guidelines for the community handbook.</li><li>The mentors then suggested some brilliant ideas and we merged the English and translation scripts and made it more dynamic. This was the new MARS model.</li><li>The 2nd phase of user testing failed! The Docker automation script had some issues and we made some drastic changes in our approach.</li><li>The mentors were finally able to produce the release PDF and we even had quite a few live demos for the same.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*h9ElckSBlAqmu1spBum7hA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*OkIhTH5Ei-8xLWI2JQk8uA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*1PfHwng2mRQrARMsDDp9XQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*fJ6BX4m6cCDxsZCATNe7wA.png" /><figcaption>M.A.R.S. Output: The English Release PDF</figcaption></figure><p>You can refer to my previous blogs for more detailed weekly reports.</p><p>Overall, the process was a great success for CHAOSS and will help a lot in during the biannual release process!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*mNYpfY_3prqWNyTv93d6dg.jpeg" /></figure><h3>Future Scope</h3><p>The MARS project is designed keeping in mind the current and future demands as the CHAOSS Project grows. Certain features, however, can be added to increase flexibility and simplify the release process. Some of them are listed below.</p><p><strong>Suggestions for MARS</strong></p><ul><li>Use of one Dockerfile for Linux as well as Mac OS.</li><li>Support to run the scripts on Windows OS.</li><li>Incorporate file formats other than markdown.</li><li>Provide support for the release of metrics in languages that may be housed in a separate repository in future</li><li>Provide support for tables in markdown format.</li><li>Remove the metrics template’s one-line gap rule between text and images.</li><li>Auto detect and warn the use of HTML in metric markdowns.</li></ul><p><strong>Suggestions for Translations Process</strong></p><ul><li>Automatically create an issue in the translations repo whenever a metric is updated (GitHub Actions)</li><li>Maintain a database for individual metrics to keep track of their update status</li><li>Use of translations-tools such as Weblate to provide version control.</li></ul><h3>Things I Learned</h3><p>GSoC has been a good opportunity to improve my technical and communication skills. I learned to:</p><ul><li>Adapt with teams across different timezones</li><li>Understanding and implementing the opinion and suggestions of different stakeholders in the project</li><li>Studying the workflow of projects and possible customization that can be made</li><li>Analyzing different approaches to solve a problem along with their pros and cons</li><li>Writing clean and well-commented code</li><li>Understanding, reviewing and modifying others’ code</li><li>Implementing checks and error handling to alert the user in case of any malfunctioning.</li><li>Working with different tools such as Git, Gitbook, Python, Docker, Shell, LaTeX, Pandoc, Lucidchart and many more.</li><li>Effectively communicating the project details by writing weekly blogs and sending updates to the whole community</li></ul><p><strong>I’m truly thankful to —</strong></p><blockquote><a href="https://medium.com/u/d8ba8aa054d2">Ria Gupta</a> and <a href="https://medium.com/u/e4f2a34fa04c">Venu Vardhan Reddy Tekula</a> for helping and advising me before and during this journey</blockquote><blockquote>My partner <a href="https://medium.com/u/9fe5911def73">Yash Prakash</a> for being an awesome companion on our way to MARS</blockquote><blockquote>All the mentors — <a href="https://github.com/GeorgLink">Georg Link</a>, <a href="https://github.com/klumb">Kevin Lumbard</a>, <a href="https://github.com/germonprez">Matt Germonprez</a>, and <a href="https://github.com/jaskiratsingh2000">Jaskirat Singh</a> for their constant support and guidance during and even before the project</blockquote><blockquote>The entire CHAOSS Community for their welcoming support</blockquote><p>GSoC with the CHAOSS Community has taught me a lot about how an organization works and gave me exposure to the industry. I would be happy to contribute to it as an active member!</p><h3>Some Useful Links</h3><ul><li><a href="https://github.com/chaoss/mars">CHAOSS MARS Repository</a></li><li><a href="https://summerofcode.withgoogle.com/projects/#6676319141625856">Project Selection Link</a></li><li><a href="https://gist.github.com/ritik-malik/github.com/ritik-malik/microtasks">Microtask Repository</a></li><li><a href="https://drive.google.com/file/d/1HJ2tHSVkZ3TJQUNDrmucDKkGXSVLQlr1/view?usp=sharing">Project Proposal</a></li><li><a href="https://github.com/ritik-malik/GSoC">Project Tracker</a></li><li><a href="https://ritik18406.medium.com/">Medium Blogs</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdbb0c1d082c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Period 2: Week 10]]></title>
            <link>https://ritik18406.medium.com/coding-period-2-week-10-433cf5b98d3c?source=rss-30fb0a45fd59------2</link>
            <guid isPermaLink="false">https://medium.com/p/433cf5b98d3c</guid>
            <category><![CDATA[chaoss]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[gsoc2021]]></category>
            <dc:creator><![CDATA[Ritik Malik]]></dc:creator>
            <pubDate>Sun, 15 Aug 2021 21:56:29 GMT</pubDate>
            <atom:updated>2021-08-15T21:56:29.850Z</atom:updated>
            <content:encoded><![CDATA[<p>Begins the ending of a beautiful journey… Last and final week of the 2nd coding period of Google Summer of Code ’21.</p><p>The weekly mentor mentee meeting didn’t take place this week because the mentors were busy with some chores. BUT, we’ll have a meeting next week instead, for the compensation! Probably the last one for MARS :(</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*AppercGvkLqt5wlBbbYtzw.jpeg" /><figcaption>I swear it started just a month ago :((</figcaption></figure><p>This week we had some good progress on MARS, it started with with the improvements in the scripts — better comments and neatness in the code, better naming conventions and updating the READMEs. The GIF updation will be performed after the next meeting, once the project is reviewed by the mentors.</p><p>Other than that — we had some great progress in the translations system. Yash and the mentors attended the biweekly Asia Pacific call and made some major advancements in the translations process. The draft for the translations guidelines is now merged in the CHAOSS community handbook and can be found <a href="https://handbook.chaoss.community/community-handbook/community-initiatives/metrics#guidelines-for-translation-of-metrics-and-release">here</a>.</p><p>We also made a rough flowchart for the translations process. Received constructive feedback from the mentors and are working to improve it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwytMe49pjAcHlx3B6qcYQ.png" /><figcaption>Didn’t see that coming, did ya? :)</figcaption></figure><p>That was pretty much for this week. It was a relaxed one, mainly focused on reviewing things and improving them.</p><p>Next week, we’ll be updating the metric release process in the community handbook, work on the flowchart for the translations guidelines and prepare the final report.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*GwPwwU5IW5QhI-0GWJSpsA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=433cf5b98d3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Period 2: Week 9]]></title>
            <link>https://ritik18406.medium.com/coding-period-2-week-9-fe703084df3e?source=rss-30fb0a45fd59------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe703084df3e</guid>
            <category><![CDATA[gsoc2021]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[chaoss]]></category>
            <dc:creator><![CDATA[Ritik Malik]]></dc:creator>
            <pubDate>Mon, 09 Aug 2021 20:07:03 GMT</pubDate>
            <atom:updated>2021-08-09T20:07:03.211Z</atom:updated>
            <content:encoded><![CDATA[<p>The second last week of the 10 week program is here! Started with an awesome weekly mentor mentee meeting, and a demo for the new MARS model —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*lmmTYGc-Io8-ZYwCW5KdVQ.jpeg" /><figcaption>This is what happened exactly!</figcaption></figure><p>Last week, we definitely did merge English and translation release into 1 directory, but they still had 2 different scripts and English for treated separate from translation. More on this later…</p><p>This week we planned a lot of minor things to be accomplished like updating the documentation with the new MARS model — adding GIFs for English and Chinese release process for better visualization and understanding.</p><p>Then we created a new guide for adding new language and the mentors decided that the Release Notes and Board Members page should be added at the end, rather than the front of the PDF. These mini and easy tasks were performed initially.</p><p>Later in the week the mentors performed user testing of MARS on their system —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*e9hgT7vMu_3xnIkKD4qlMg.jpeg" /></figure><p><strong>anddddd…. it failed!</strong> There were some unexpected errors in Mac —</p><blockquote>There is no Docker group so the user can’t be added to it</blockquote><blockquote>A new user in the container can’t be created with the same GID as current user</blockquote><blockquote>Some commands not found — those were specific to Linux distro</blockquote><p>These were some failure points to name a few. However the mentors figured out ways to bypass these limitations and were still able to run the container and produce the PDF by modifying the code. This served as a critical feedback for us. They also suggested a lot desirable changes —</p><blockquote>Merge “english_release.py” and “translations_release.py” into 1 single file</blockquote><blockquote>add new “repo-location” parameter in yml config file, to point to the location of “focus-areas” in the repo</blockquote><blockquote>Make a “words.yml” in “passive_user_input” which contains a dictionary for language translations for words — focus-areas, goal, metric, question, TOC, etc.</blockquote><blockquote>Remove “table_templates.py” and make 3 new “.tex” templates in “passive_user_input”</blockquote><blockquote>Giving some meaningful names to the sanity checks in scripts</blockquote><blockquote>Improve documentation in code and giving files some more descriptive names</blockquote><p>These were some major changes suggested along with fixing the Docker issues in Mac. So our weekend stood pretty busy to implement these ideas —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Fx_emKf9fCEFU_se-4Ngmg.jpeg" /></figure><p>We were able to implement most of these suggestion. I was able to fix the Docker issue in Mac —</p><p>Docker in Mac runs in a Virtual Machine unlike Linux — so it doesn’t require sudo permission, so I implemented a function to detect the platform and proceed accordingly. I was able to fix this issue and tested it on my friend’s Mac. Later, the mentors were also able to produce the PDF without any issues!</p><p>I also designed a little ASCII art banner for MARS —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/395/1*YT5zfjcBQ2wfpKgek_U_3w.png" /><figcaption>I ❤ ASCII art!</figcaption></figure><p>Meanwhile Yash was working hard to combine the English and translations scripts into one. Here, virtually we are now treating English as any other translated language like Spanish and Chinese, the only difference is in the GitHub repos and paths. Yash was also successfully able to add those extra parameters in the yml file and improve the code documentation.</p><p>It has been a busy and productive week for MARS with some significant changes. Next week we will implement the other suggestions that are left make general improvement and changes documentation accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*zwqqkE-78wPzeS1S9veMPw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe703084df3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Period 2: Week 8]]></title>
            <link>https://ritik18406.medium.com/coding-period-2-week-8-12e22d54b323?source=rss-30fb0a45fd59------2</link>
            <guid isPermaLink="false">https://medium.com/p/12e22d54b323</guid>
            <category><![CDATA[chaoss]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[gsoc2021]]></category>
            <dc:creator><![CDATA[Ritik Malik]]></dc:creator>
            <pubDate>Sun, 01 Aug 2021 16:03:49 GMT</pubDate>
            <atom:updated>2021-08-01T16:03:49.473Z</atom:updated>
            <content:encoded><![CDATA[<p>Week 8 has been a pretty busy week for us and quite productive for MARS. It witnessed some major unexpected but desirable changes in the workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Xpk_rFQKEUbIta0-m1GJMA.gif" /><figcaption>Loved this movie!</figcaption></figure><p>Beginning with the weekly mentor mentee meeting, we discussed upon a few alternative approaches to the current workflow of MARS. Last week we were done with the English release system and were planning to create another system for the translations. The idea of merging both of them and having one common system for all was tossed in the meeting, followed by a list of steps to be implemented to accommodate the new changes. New MARS model —</p><blockquote>Using user input for language selection — English, Spanish, Chinese, etc.</blockquote><blockquote>Creating a dynamic structure to auto-detect the languages in translation repo</blockquote><blockquote>Auto-detect and select appropriate yml file and cover page</blockquote><blockquote>Error handling and sanitize user inputs</blockquote><p>Since we would be using separate yml file and cover page (with the same structure) for each language, we came up with a naming convention to avoid conflicts —</p><blockquote>&lt;language&gt;_working-groups-config.yml</blockquote><blockquote>&lt;language&gt;_cover.tex</blockquote><p>Next step was to add a new language menu for the user along with error handling. It was an easy task. Then we decided to create separate scripts for English and translations, and another script for common functions and classes to be used by both.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*NYuMGDKNXzKi0NzP1K6qPA.jpeg" /></figure><p>This process took quite a planning and me &amp; Yash had a few meetings to plan the layout for the approach, and we started to implement it. It took the whole the week but the result was worth it!</p><p>We were able to auto-detect the translation languages, implement proper user input sanitization and error handling. The beta PDF for Chinese release was ready and was approved by the Chinese community! (though they still need to translate a few other stuff like Release Notes at the end). For the Spanish one, we need to first standardize the repo structure. We can expect a Spanish PDF next week.</p><p>Next step was to containerize the new MARS structure on Docker —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*HFFxP29_dame-TB2vysNUg.jpeg" /><figcaption>Yes, I’m obsessed with Tarantino!</figcaption></figure><p>For the Spanish translation we didn’t require any extra packages, but for the Chinese one, we do. The package we came up with was <em>xeCJK </em>which is the Chinese-Japanese-Korean language pack for LaTeX. Integrating it in Docker was no big issue, however the image size was considerably doubled! The image size before was around 1.2GB, but after the language pack it rocketed to 2.2GB. The compressed image is although ~ 850MB (the actual download size). We decided to proceed with this unless we find any alternate smaller Chinese lang package with regular updates.</p><p>By the end of this week 8, the new model for MARS is ready and up and running — we might have another round of user testing next week.</p><p>Other than that, We standardized focus-area READMEs and metric markdowns in Spanish and Chinese translations. We also had some great progress in the translation guidelines. Yash attended the Asia-Pacific meeting and had a healthy discussion on how to proceed on the with the guidelines. The document is almost complete and probably next week we’ll be putting it up on the community handbook.</p><p>Next week we’ll be completing the documentation of MARS, updating the flowchart and doing user testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*zgBnMEtWvauAfkxi4M372g.jpeg" /><figcaption>We won’t disappoint you sire!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12e22d54b323" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Period 2: Week 7]]></title>
            <link>https://ritik18406.medium.com/coding-period-2-week-7-a0d498054184?source=rss-30fb0a45fd59------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0d498054184</guid>
            <category><![CDATA[gsoc2021]]></category>
            <category><![CDATA[chaoss]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <dc:creator><![CDATA[Ritik Malik]]></dc:creator>
            <pubDate>Sat, 24 Jul 2021 17:17:32 GMT</pubDate>
            <atom:updated>2021-07-24T17:23:46.071Z</atom:updated>
            <content:encoded><![CDATA[<p>We are into Week 7 of our 2nd coding period! The project has been going great so far. This week started with the mentor mentee meeting —</p><p>Since the Docker was now running rootless, we showed another demo to our mentors and it went great. Now our automation system was ready for the English release and we sent it for user testing via CHAOSS mailing list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*cDmGjFhhiyYWQUFnSHRjEA.jpeg" /></figure><p>We had a new member in CHAOSS — Nico, and he was the first one to review it. He was successfully able to replicate and generate the PDF from MARS. Reviews from mentors and community members are due next week. We hope to improve the system based on community feedback.</p><p>This week I was mostly busy with some university stuff, so was a bit unproductive. While Yash was active in the translations community attending meetings and opening issues and PRs as we started working on MARS for translation parallely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*2XNmorN0LUfkNJWm9oDLcA.png" /></figure><p>I made some minor changes in the READMEs of English release to make it more intuitive to the user, and also accommodating for the new <em>active_user_input</em> — <em>cover.tex</em> file.</p><p>Also, huge thanks to Kevin for completing the task of CHAOSS website migration. Following on this, I was able to standardize the Working Group Common by renaming all the focus-areas. We also saw addition of some new metrics in various working groups. Currently they are undergoing the review period and we’ll add them to our yml file as soon as they are finalized.</p><p>In the next week we plan to work on MARS for Chinese and Spanish translations. We need to make a separate yml file, separate scripts and a Docker image for the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*1vFvqWcGfvTVubZsDIfZbw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0d498054184" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Period 2: Week 6]]></title>
            <link>https://ritik18406.medium.com/coding-period-2-week-6-95fa52118ff4?source=rss-30fb0a45fd59------2</link>
            <guid isPermaLink="false">https://medium.com/p/95fa52118ff4</guid>
            <category><![CDATA[gsoc2021]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[chaoss]]></category>
            <dc:creator><![CDATA[Ritik Malik]]></dc:creator>
            <pubDate>Fri, 23 Jul 2021 12:56:55 GMT</pubDate>
            <atom:updated>2021-07-23T12:56:55.625Z</atom:updated>
            <content:encoded><![CDATA[<p>Finally! We had our first evaluations and we passed with flying colors! I would like to thank <a href="https://medium.com/u/9fe5911def73">Yash Prakash</a> for collaborating on MARS and to all the mentors and the amazing CHAOSS community for their constant support and guidance.</p><p>Now begins the week 6 of our 2nd coding period —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0LZ4ElEF_oTLm9ziX7lp5g.jpeg" /></figure><p>Week 6 started with our weekly mentor mentee meeting. Initially we had our demo for Docker, since our MARS image was up and running. The demo was successful and we were able to generate the PDF. Mentors were satisfied except 1 small thing — the automation script was meant to be run as root user.</p><p>Here I completely agreed with them and it’s a reasonable concern, running a shell script with root permission is NOT a safe idea, specially when you are downloading it from internet. I’ve thought before that we maybe encounter this issue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*VXsMXjlThQzjpd0Po9uJaA.png" /></figure><p>So our first and the foremost task was to run our Docker image for MARS as a non root user. Aaaaaaand it was quite a tedious job than we imagined! We had to take a deep dive into the Docker documentation, Stackoverflow, and many other resources.</p><p>Firstly we had to run Docker commands as rootless user, so we added the our user to the Docker group. Now we made many attempts to run it but they all failed with permission errors either while running the scripts in Docker or creating new files in the environment. Finally we came up with a new approach —</p><blockquote>Create a new user in Dockerfile</blockquote><blockquote>Extract user ID and group ID from current user</blockquote><blockquote>This new user will have the user ID and group ID as your current user</blockquote><blockquote>Switch to the new user in Docker</blockquote><blockquote>Use ‘gosu’ binary to change privileges</blockquote><blockquote>Now we can copy and run MARS scripts with bind mount</blockquote><p>All the files that are created (logs, PDF, etc) will have the same permission as Docker user, which in-turn has the same permission as your current user!</p><p>So finally we were able to solve the rootless docker issues. We believe in Stackoverflow supremacy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*FLATe4SVBw3oaqMcuj1kWA.jpeg" /><figcaption>This was the exact feeling, ngl</figcaption></figure><p>The next step was to work on the Documentation for the same. We made a new README as an installation guide for MARS. It was an easy task and is almost finalized with a few tweaks left.</p><p>The Documentation can be found <a href="https://github.com/chaoss/MARS/tree/main/automation-english">here</a>.</p><p>Apart from helping in the above tasks, Yash was also working on the translations repo. He attended the Asia Pacific meetings and opened issues and PRs for regarding the translations guidelines.</p><p>Next week, we will continue standardization for working groups (almost complete) once the migration of website is over. We’ll also work on the translation repo and make MARS available for user testing and reviews for the English release version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*lLeaGWiKmchb1pzq00iCQg.jpeg" /><figcaption>just an appreciation for Stackoverflow :)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95fa52118ff4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Period 1: Week 5]]></title>
            <link>https://ritik18406.medium.com/coding-period-1-week-5-1d64c433a929?source=rss-30fb0a45fd59------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d64c433a929</guid>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[chaoss]]></category>
            <category><![CDATA[gsoc2021]]></category>
            <dc:creator><![CDATA[Ritik Malik]]></dc:creator>
            <pubDate>Sun, 11 Jul 2021 17:49:28 GMT</pubDate>
            <atom:updated>2021-07-11T17:49:47.182Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the last week of our Coding Period 1, and precedes our 1st evaluations…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*sSkajL8YKKyYL67sxKBFOw.png" /></figure><p>Week 5 witnessed no weekly mentor mentee meeting because of the public holiday in the U.S. Week 5 was a busy one, for me as well as my partner Yash. While he was occupied with his university exams, I had some chores from the university too.</p><p>Nonetheless, we were still able to manage the deliverables for this week in time. This week we were expected to continue on the standardization of Working Group repositories and <strong><em>automate</em></strong> the docker implementation for M.A.R.S.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*OlMfSybcMWDvVMeW_aMX6A.jpeg" /></figure><p>For the standardization part, we attended the amazing weekly meetings for various working groups and made several pull requests for the standardization of READMEs of focus-areas according to the proposed templates and corrected metric markdown files according to the new updated metric template, which would help us to resolve some issues we faced in the PDF initially (like overflowing of images, HTML/tables not rendering, etc.)</p><p>For the docker part, we decided to even automate the creation of images, containers and removal of same after the scripts are done running. For this we spend quite a while studying Docker in-depth for mounting volumes, detecting containers, error handling, etc. and we were able to automate the stuff for Linux (Debian based) and Mac OS/X.</p><p>For these 2 platforms, we made a simple bash script that would first perform a variety of checks —</p><blockquote>Check for root permission</blockquote><blockquote>Check if Docker is installed</blockquote><blockquote>Check if Docker is running</blockquote><blockquote>Check if the current directory is correct</blockquote><blockquote>Check if the Dockerfile exist</blockquote><p>The above checks will also throw solutions and suggestions to resolve the same. They acted as a sanity check before proceeding to the main task. The main task is to —</p><blockquote>Build the Docker image from the Dockerfile (if the image isn’t already present, download and build it, else use cache)</blockquote><blockquote>Remove dangling images (if any)</blockquote><blockquote>Check if mars-container is already present (if yes, delete it)</blockquote><blockquote>Run docker image with bind mount (the output PDF will be saved)</blockquote><blockquote>Remove the Docker container</blockquote><blockquote>Change permission for output files and PDF (since script is run as root)</blockquote><blockquote>Give a success message and display commands to remove to image (if required)</blockquote><blockquote>Show paths to the log file and the output PDF</blockquote><p>If any of the above command fails, it gracefully exits then and there displaying error (future work — and a workaround for the same).</p><p>This bash script is tried and tested on Linux and Mac OS/X platform and it works just fine! For windows first we thought of powershell script or a batch file, but windows doesn’t allow us to run these scripts by default due to security reasons and some configurations have to be made. Since WSL2 is a prerequisite for Docker in Windows, we thought why not run this same bash script in WSL2 instead. (we are working on this)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WkOdTFYa0AXbic-om9Oe0w.jpeg" /><figcaption>Ezekiel 25:17</figcaption></figure><p>Meanwhile Yash is working on the translation guidelines for the translation counterparts, the README is good and is yet to be verified by the mentors and to be added to the community handbook.</p><p>Next week, we’ll continue on Docker for Windows, finalize the translation guidelines and work on the standardization process.</p><p>And we hope our 1st evaluations goes well, fingers crossed…😬🤞</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d64c433a929" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Period 1: Week 4]]></title>
            <link>https://ritik18406.medium.com/coding-period-1-week-4-11c9d4daeebc?source=rss-30fb0a45fd59------2</link>
            <guid isPermaLink="false">https://medium.com/p/11c9d4daeebc</guid>
            <category><![CDATA[gsoc2021]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[chaoss]]></category>
            <dc:creator><![CDATA[Ritik Malik]]></dc:creator>
            <pubDate>Sun, 04 Jul 2021 18:58:57 GMT</pubDate>
            <atom:updated>2021-07-04T18:58:57.809Z</atom:updated>
            <content:encoded><![CDATA[<p>Week 4 of Coding period 1 is here! Just 2 weeks left for our 1st evaluation😬. As always, it started with the awesome mentor mentee meeting on Google Meet :D</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*7I-2HXAjAXYU_FF9-Gmeqw.jpeg" /><figcaption>Arnold would be proud</figcaption></figure><p>Since the core work for M.A.R.S. was ready and pushed to our <a href="https://github.com/chaoss/MARS">github repo</a>, so we showed a little demo to our mentors of how the PDF is generated and a high level view of the workflow.</p><p>The generated PDF was satisfying, since the focus-areas tables were now being generated automatically (reference to previous post), and a table of content was also automatically created, 3 levels deep —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*ugPliWjSb4N_0QMKbCnOOA.png" /></figure><p>We decided that the yml config file deserves it’s own README since it is the only and important input to the scripts, so the user should be pretty clear about it. It can be found <a href="https://github.com/chaoss/MARS/tree/main/automation-english/active_user_input">here</a>.</p><p>Also, the Working Group heading page in the PDF was being displayed empty, not anymore — as we decided to auto generate the focus-areas table belonging to that particular WG, and we were successful for the same —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*1xIxjQNkuL4NcbbsK57y6Q.png" /></figure><p>This focus-areas table is dynamic, and configured based on the input of yml file. Suppose a focus-area has some metrics but not included in the yml file, so that focus-area will also be skipped in this table, which provides us much flexibility than just copying the entire table from GitHub READMEs.</p><p>More small yet significant improvements were made like — Till now the naming convention for the focus-areas in the base folder was just focus-area.tex, but since 2 focus-areas could have same name, we decided to put the WG prefix to it — WG_focus-area.tex</p><p>Also, we continued with the standardization process of the Working Groups and made PRs for the same, as it would help us to achieve a unified structure for WGs, focus-areas and metrics, and also help us with the PDF release.</p><p>Last but not the least, the idea of using Docker for cross platform was approved by the mentors! So most of our the week was spend learning Docker and making images and testing them for Linux, Windows and Mac/OS X. We searched for LaTeX images on Docker hub but most of them were either too big (3~4 GB) with extra software or outdated. So we decided to build one our own. Our image was a bare minimum installation of <a href="https://www.overleaf.com/learn/latex/XeLaTeX">texlive-xelatex engine</a> and some essential utilities like git, pandoc, python3-pip, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Dd7PiL5NMuWZ_dfTWDohLA.jpeg" /><figcaption>Yes, this did happen with me (:</figcaption></figure><p>Our new image size after compression was just ~ 478 MB (the actual download size) while the full image was just 1.32 GB (compared to 4~5 GB previously). We tested the containers on Linux and Windows platform and were successfully able to run the scripts! Mac/OS X is a work in progress for now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*30xE0UnjvooAHgMTTwRHtw.jpeg" /><figcaption>Just finished this <a href="https://en.wikipedia.org/wiki/Back_to_the_Future">awesome trilogy</a> :D</figcaption></figure><p>Soon we’ll be working on the documentation for the same. After the discussion with the mentors we decided to use the main README for documentation of Docker as well. We’ll be also continuing on the standardization process and attending Working Group meetings.</p><p>Also, since Monday, 5 July, 2021 is a public holiday for Independence Day in the United States, our next meeting stands postponed for now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11c9d4daeebc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Period 1: Week 3]]></title>
            <link>https://ritik18406.medium.com/coding-period-1-week-3-f7f715f8f200?source=rss-30fb0a45fd59------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7f715f8f200</guid>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[chaoss]]></category>
            <category><![CDATA[gsoc2021]]></category>
            <dc:creator><![CDATA[Ritik Malik]]></dc:creator>
            <pubDate>Sun, 27 Jun 2021 12:28:07 GMT</pubDate>
            <atom:updated>2021-06-27T12:28:07.709Z</atom:updated>
            <content:encoded><![CDATA[<p>Week 3 has been a little rough ride for me. This week I got my first vaccine jab of <em>covishield </em>on 23rd June, Wednesday, so as expected I had weakness and was unproductive for 2 days :( <em>OR conversely it was just a peaceful break :D</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*IFRUwGMZ8-SAQRNbBHhYeA.jpeg" /><figcaption>Yes! Memes are back :D</figcaption></figure><p>Nonetheless, this week kicked off with our refreshing weekly mentor mentee google meet. As always it was amazing to share our work progress, getting doubts resolved, etc.</p><p>So we discussed things about how to proceed with the translation counterparts of the reports. The <a href="https://github.com/chaoss/MARS">M.A.R.S. repo</a> was also revised as we updated our <a href="https://github.com/chaoss/MARS/blob/main/assets/MARS_workflow.png">workflow</a> for the project. We decided to remove static <em>focus-areas.tex</em> file from <em>active_user_input, </em>since we were going to auto generate it! And now the <em>yml</em> config file has separate <a href="https://github.com/chaoss/MARS/tree/common-dev-1/automation-english/active_user_input">README</a> for it, as an instruction manual.</p><p>My main task this week was to automate the creation of <em>focus-areas.tex</em> file, earlier we decided to keep a duplicate copy but that didn’t seem appropriate. So I made a simple template with flags where the focus area goals, the metrics names and question would be replaced, then I simply extracted the same from the respective READMEs. The template and final version looked something like this -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/488/1*mdbagAhFU3quM05gbFx8Bg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*I2gnqbkokbSaM_fUUiGgOw.png" /><figcaption>Before vs After</figcaption></figure><p>In the 2nd image we can see that the <em>$FOCUS_AREA_NAME</em> and <em>$FOCUS_AREA_GOAL</em> is replaced with appropriate terms.</p><p>After this, Yash’s job was to replicate the original PDF release structure that we were having, and he did that beautifully. <a href="https://github.com/chaoss/MARS/blob/common-dev-1/automation-english/Output.pdf">PDF link</a></p><p>Then we decided to carry on with the process of standardization of Working Group repositories, mainly because of 2 reasons -</p><ol><li>These templates and well defined structure would be helpful while introducing a new metric, focus-area or an entire working group</li><li>Having a standard structure will ease us in extracting the focus-area goals, metrics names and questions from the READMEs</li></ol><p>For now, we have various template for the same and can be found in the governance repo <a href="https://github.com/chaoss/governance/tree/master/templates">here</a>.</p><p>So we planned to attend all the Working Group meetings and propose new changes according to structure since most of them weren’t following it. We prepared a small checklist of items that we need to verify for each Working Group -</p><blockquote>A list of checks that need to be verified in all Working Group repos which serves as a prerequisite for the automation process -</blockquote><blockquote>High priority :<br>● Focus-areas READMEs following the <a href="https://github.com/chaoss/governance/blob/master/templates/focus-areas.md">template</a><br>● Metric markdowns following the <a href="https://github.com/chaoss/metrics/blob/master/resources/metrics-template.md">metric template</a><br>● Atleast 1 \n (newline) between -&gt; 2 images, images + text, images + headings (to solve wrapping problem)<br>● All images having ![]() format<br>● All images using relative paths<br>● No tables in metrics markdowns (use image instead)<br>● HTML shouldn’t be used in metrics markdowns</blockquote><blockquote>Low priority :<br>● Main README of WG following the template</blockquote><p>BUT, as I was inactive due to vaccination, I couldn’t attend the meetings, so kudos to Yash for doing the chore from my side. I plan to compensate for the same in next week.</p><p>Also, this week I was learning docker (it might be helpful to M.A.R.S. in future, I’ve thought of something…), and prepared a small cheatsheet for the same. You can find my GitHub Gist on Docker <a href="https://gist.github.com/ritik-malik/045d5fa7c7b314563e99db4fd290e538">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/422/1*3cvXxI1UC9fZY508Pfq2og.jpeg" /><figcaption>Should I continue with memes in blogs? WDYT?</figcaption></figure><p>Next week, we we’ll be pushing code in repo and continue the work on Standardization of Working Groups.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7f715f8f200" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>