Pavan Joshi

Summer Of Bitcoin - Intro and Onboarding Week at Bitcoin

2022-05-16T00:00:00+00:00

Voila, readers 👋! It’s been a week since I started my journey with bitcoin as a Bitcoin Intern. It has been a great learning experience so far.

If you are willing to know more about Bitcoin Internship, kindly check my previous post - Summer Of Bitcoin- A global Internship Program

During the first week of the Bitcoin Internship, I got the opportunity to meet many Tech Bitcoin experts worldwide. We took a deep dive into Bitcoin protocol and how we can enhance career opportunities through this Internship.

We got to hold a welcome session conducted by Summer of Bitcoin Admin Adi Shankara

During this session, we learned about different initial tasks like getting started with (TODOs), Stats of Summer of Bitcoin 2022, Expectations of the program from its selected interns and many different perks and opportunities this internship provides. ✨

For this year, out of 20k applications worldwide, only 82 interns from 15 different countries were selected, making it into Summer of Bitcoin in the first attempt and being a part of those 82 interns makes me feel overwhelmed. 🎉

Session Presentation: Here

The second session was conducted on Communication, Collaboration and Career Development by Caralie Chrisco

During this session, we got to know about various technical interviewing skills and more about technical concepts such as ⏬

Technical Blogging
Network Building
Technical Interviewing
Resume Making
Answering Technical Questions

Resources 🔽

Canva — Free graphic design software 💻
Grammarly — Check your writing ✍️
Hemingway — Improve your writing ✅
Medium — Create your own blog 📃
Meetup — Meet people with similar interests, and build your network! 🧑‍🤝‍🧑
Break-In — Blog for junior devs, with some relevant articles on technical interviewing 🔰

The third session was conducted on Bitcoin and Open-source Development by Adam Jonas

During this session, we learnt many different aspects of Bitcoin and sessions conducted by chain code labs in order to understand Bitcoin protocol development in a better way. 🔀

Resources: Here

The fourth and final session of this week was conducted on Deep-dive into Bitcoin by Matthew Zipkin

In this session, we had a quick glance at Bitcoin, Goals of Bitcoin, Cryptography in Bitcoin, Account-based VS Coin based model, Bitcoin OP codes, Proof of Work etc. 🪙

Session Presentation: Here

For more, stay connected !!

Best Regards ~ Pavan

Summer Of Bitcoin - A Global Bitcoin Internship

2022-04-05T00:00:00+00:00

“Bitcoin will do to banks what email did to the postal industry.”

— Rick Falkvinge, Founder of the Swedish pirate party

Hey readers 👋! I have been selected as a developer in this year’s Summer of Bitcoin 2022 program. Yay!! :stars: 👊 I made it into Bitcoin Internship**_ in my very first attempt.

I consider this as very another achievement after the successful completion of Google Summer of Code 2021.

In this post, I will be discussing what exactly Summer of Bitcoin is and how this internship can help you to get excellent career opportunities in direction of the latest technology and its trends such as Blockchain and Bitcoin.

Bitcoin is a virtual currency designed to act as money that gives individual the power to control thier money without the need for traditional banking intermediaries. 💰

What is the Summer of Bitcoin? 🤔

The Summer of Bitcoin, often abbreviated as SOB is an International Annual Internship Program. It introduces university students to bitcoin development and designing in which Bitcoin award stipends to students who successfully complete coding project during the summer.

Summer of Bitcoin is a competitive event :computer: in which students apply to mentoring organizations and compete with other aspirants for their selection. The one who completes all the rounds and tasks provided in the selection phase gets selected for this internship.

Students who complete Summer of Bitcoin successfully get a handsome amount of $3000 dollars :dollar: as a stipend and Internship Certificate from Bitcoin :boom:.

Along with this many different swags such as Bitcoin hardware wallet (interesting), Hoddies etc are waiting for you.

Summer of Bitcoin Stats 📊

In 2022, 20317 applications came from all around the world for this internship, out of which only 82 participants were able to make it into this internship. After the release of stats, this made me feel great as well as overwhelmed for being one of the selected participants.

Key Benefits of Bitcoin Internship - ☑️

Get to learn about the working latest technology trends and Bitcoin which is one of the world’s biggest monetary revolutions :dizzy:.
Handsome amount of $3000 dollars as a stipend along with internship swags 🤩.
Bitcoin Internship Certification :stars:.
Direct job referrals in Bitcoin companies around the world
Fundings for different Bitcoin based startups, get connected with investors and advisors
Open Source annual grants

Summer Of Bitcoin Journey ⬇️

After completing my Google Summer of Code 2021, I become more enthusiastic for working on challenging codebases and solving harder problems. One of my friend introduced me to Summer of Bitcoin.

Initially, I had no prior experience in blockchain and working of Bitcoin. I was able to crack screening round through my coding skills and elevated myself in the direction of Bitcoin and Blockchain by learning more about it.

During this time, I got to meet many different Bitcoin contributors from different parts of the world. It really excited me to give my best in this direction.

This is my acceptance letter from Bitcoin 🔥

Project Details 📑

I will be working on making Bitcoin payments transactions smart with structured metadata with Alby Community. This is possible by extending the latest technologies such as WebLN and LNURL which are being build on top of the Bitcoin and Lightning Network.

The aim of this project is to extend existing standards such as Webln and lnurl to enrich transactions with additional information as structured metadata so that transactions containing static data contain more meaningful information giving more interactivity to the transactions.

Objectives 💻

Research different use cases which supports the concept of making transactions smarter with structured metadata.
Markup metadata so that it is structured and properly organized using specifications such as schema.org.
Writing specifications for extending standards such as Webln on client-side as well as Alby wallet side.
Implementation of the specifications in Alby.
Different prototypes demonstrating use cases.

For more, stay connected!!!

Best Regards ~ Pavan

Final Report - GSoC’2021

2021-08-31T00:00:00+00:00

This blog report summarizes the work, I executed during the 10 weeks of Google Summer of Code 2021. GSoC’2021 Coding Period was started on June 7, and officially ended on August 16.

My Project Details 📋

Internationalization mainly aims at creating I18n architecture for the CircuitVerse platforms to localize or translate them into multiple languages.

During GSoC, I aimed to create an I18n infrastructure such that CircuitVerse platforms can be internationalized into global languages. And the platforms can be emerged as the Global Platforms.

I also aimed to create an I18n architecture for 5 major technologies used on different CircuitVerse platforms. They are:-

Ruby on Rails (CircuitVerse Main Platform)
JavaScript (CircuitVerse Simulator)
Jekyll (CircuitVerse Interactive Book)
Flutter (CircuitVerse Mobile App)
DocsifyJs (CircuitVerse Docs)

Final Report 📃

During the first five weeks of the GSoC coding period (Phase One), I did work in the major portions of the Rails codebase. Phase two was majorly dedicated to working on Simulator, Mobile App and DocsifyJS as well.

More Details about my work in Phase one can be found here: I18n Phase One Report

Phase Two :-

Simulator 🔌

We cannot use Rails I18n in webpacker served JavaScript modules directly. A Wikipedia library banana-i18n is used to localize JavaScript-based product.

In order to localized Simulator I divided it into different sections ⬇️

Simulator Configuration Modules and features such as Verilog, CombinationalAnalysisalong, SubCircuits etc along with third-party npm packages.
Simulator Circuit Element Modules
1. Circuit Element Modules
2. Sequential Element and TestBench Modules
3. Project Data, Hotkey Binders, themers etc

Week 6: Begin with Localizing Simulator Configuration Modules 📂

In total, there were 36 configuration modules written in JavaScript, which I had to check and localize without breaking any code.

Following tasks were achieved during this week ⏬

I18n in Simulator controls interface in UX.js
I18n in Simulator Guide in tutorials.js
I18n in Simulator functionalities such as Verilog, SubCircuits, CombinationalAnalysis etc.
Completing I18n and testing in all the remaining 36 configuration Modules and functionalities.

Week 7: Localizing Simulator Circuit Element Modules 🔄

I started working with circuit element modules, hotkey binders, themers, testbench and sequential circuit element modules.

Following tasks were achieved during this week ⏬

I18n in 67 different JavaScript modules which belong to circuit elements, sequential circuit elements, testbench, mutable properties of circuit elements etc
I18n in Themers and Hotkey Binders, Project Data configurations etc
Documentation

I finished working on the Simulator which required 800+ lines of code changes. 🎉

Mobile App 📱

Despite some of the benefits of Flutter, such as rapid Mobile-App development. Flutter was quite in discussion for its uneasiness for internationalization (I18n).

Previously provided configuration of I18n used a complex approach to feed translations in the app, and needs to be upgraded to a cleaner workflow.

The Mobile App interface in Flutter is made of several built-in widgets and custom widgets

Built-in widgets provided Flutter API for Rapid App Development.
Custom Widgets created by Developers for specific purposes.

Week 8: Upgrade I18n Workflow and Begin Working with Mobile App 📈

Following tasks were achieved during this week ⏬

Upgrade I18n workflow with the more appropriate one.
Localization of built-in widgets using flutter_localizations package(package supports 80 different locales)
Localize Custom Widgets(UI of Flutter) using Intl package.

Week 9: Continue Localizing Custom Widgets 🚧

Following tasks were achieved during this week ⏬

Create a Language Switcher using the locale provider package.
Continue localization in Custom Widgets.
Localize interpolated strings using concept of companion messages.
Fix unit tests for all the Custom Widgets.
Documentation

I finished working on the Mobile App which required 2400+ lines of code changes. 🎉

Week 10: I18n Architecture in DocsifyJS and Final Enhancements ✨

Following tasks were achieved during this week ⏬

I18n in DocsifyJS via a designing mechanism for loading sidebar, navbar, and markdown dynamically into the Page.
Language Switcher for DocsifyJS.
Fixes in Rspec tests and enhancing Language switcher for Rails and Simulator capable of handling scenarios such as -
1. Language switching when the user is not logged in(session-based).
2. Language switching when the user is logged in.
3. Taking care that, Language switching through switcher and User Form does not conflict with each other.

Implementation 💻

Major MileStones Achieved ☑️

Complete Infrastructure for Internationalization of Rails Platform.
Complete Infrastructure for Internationalization of Simulator Platform.
Complete Infrastructure for Internationalization of Mobile-App.
Complete Infrastructure for Internationalization of CircuitVerse-Docs.

I felt amazing after completing my work on the different technologies and codebases during this journey! 🥳

Future Scope ℹ️

I believe that I18n is not a time-bounded project and has a scope of continuous enhancements.

Some of the major enhancements which can be done are as follows -

Translation System for translation management. Example
Localization of CircuitVerse API to generate a localized JSON response
Localization of Model Data

Final Thoughts 💭

Firstly, I would like to thank the CircuitVerse community for giving me this amazing opportunity.

Special thanks to Aboobacker MK, my mentor. I got opportunity to work under his guidance, during my initial contributions to the community and in GSoC’2021 as well.

I had a great enhancement in my coding skills from reviews I got from mentors and during GSoC’2021 journey. cheers! 🎉

Signing off

Thankyou

GSoC Coding Period - Week10 Report

2021-08-22T00:00:00+00:00

Today marks the end of my 10-week programming journey at CircuitVerse under Google Summer of Code.🥳

All the code served to community, initial reviews, improvements in existing code, blogging, weekly catchup calls with mentors and team members felt awesome!!

This blog post summarizes my work done in last week of GSoC coding period.

As I have already finished my working in major 3 platforms i.e. Main Platform, Simulator, and Flutter Mobile App, it was the time to work on DocsifyJS and do relevant improvements in the previous work.

Mechanism behind I18n for DocsifyJS 💻

DoscifyJS is simple JavaScript framework, when loaded into HTML file gives theming facility to the documentation. Such project structures can be simply served using Python Simple HTTP servers.

As it is a very simple structure, it is a very good practice to design general i18n mechanism without using any external tool.

For this, three tasks need to be done :-

1️⃣ Load NavBar and SideBar dynamically according to the language.

2️⃣ Mechanism so that language switcher works well.

3️⃣ Load content(Markdown) dynamically in the DOM of web page accoring to the current active language.

All the above tasks can be performed simply using basic logic to workaround the concept of generating links for each file.

Week 10: I18n Architecture in DocsifyJS and Final Enhancements ✨

Following tasks were achieved during this week ⏬

I18n in DocsifyJS via a designing mechanism for loading sidebar, navbar, and markdown dynamically into the Page.
Language Switcher for DocsifyJS
Fixes in Rspec tests and enhancing Language switcher for Rails and Simulator capable of handling scenarios such as -
1. Language switching when the user is not logged in(session-based).
2. Language switching when the user is logged in.
3. Taking care that, language switching through switcher and user form should not conflict with each other.
Implementation 🔄
I18n in CircuitVerse Main Platform (3000 lines of code)
I18n in CircuitVerse Simulator (1100 lins of code)
I18n in CircuitVerse Mobile App (2500 lines of code)
I18n in CircuitVerse Docs (excluding markdown content - 100+ lines of code)

Major MileStones Achieved ☑️

Complete Infrastructure for Internationalization of Rails Platform.
Complete Infrastructure for Internationalization of Simulator Platform.
Complete Infrastructure for Internationalization of Mobile-App.
Complete Infrastructure for Internationalization of CircuitVerse-Docs.

I felt amazing after completing my work on the different technologies and codebases during this journey! 🥳

Final Evaluations 📧

In the upcoming days, mentors will be reviewing my code and will be uploading my results on GSoC portal. Lets hope for the best🤞!!

For more, stay connected!!

Best Regards ~ Pavan

GSoC Coding Period - Week8 and Week9 Report

2021-08-17T00:00:00+00:00

After finishing my work on the Rails and JavaScript codebase, I started my work with CircuitVerse Mobile App written in Flutter.

Flutter is widely used and popular Open Source Software Development tool and It is used to develop cross platform applications for Android, iOS, linux etc.

Despites of some of the benefits, such as rapid mobile app development, Flutter was quite in discussion for its uneasiness for internationalization (I18n).

Major I18n packages provided by Dart community were the intl and flutter_localizations package. Their previous configuration of I18n uses a complex approach to feed translations in the app and needs to be upgraded to a cleaner workflow.

Here is the glance of previous I18n workflow provided 👀

This requires CLI commands to generate localization class generation and needs to follow the steps given below -

Create string resources for all the strings present in app
Create AppLocalizations class and AppLocalizationsDelegate
Generate .arb files from string resources
Convert them into dart code by creating ```messages_all.dart``
Translations can be feed using AppLocalizations.of(context).title

This was updated to more cleaner workflow as follows -

Upgraded workflow will provide easy steps to provide optimal I18n support in Flutter and considered to be used 🔽

Add intl package and flutter_localizations package with flag generate:true
Create l10n.yaml describing path of translation directory and name of localization class.
Add localization delegates to the flutter main.dart
Create .arb files for providing translations.
Run flutter packages to trigger automated localization class generation.
Use AppLocalizations.of(context).key_name to provide translation.

Upgraded workflow provides automated localization class generation and easy workflow to fill translations in existing translation files.

Week8 - Upgrade I18n Workflow and Begin Working with Mobile App 🔄

Mobile App interface in Flutter is basically made of a number of built in widgets and custom widgets

Built in widgets provided Flutter API for rapid App Development
Custom Widgets created by Developers for specific purposes

Following tasks were achieved during this week ⏬

Upgrade I18n workflow with the more appropriate one
Localize built in widgets using flutter_localizations package(package supports 80 different locales)
Localize Custom Widgets(UI of Flutter) using Intl package

Week9 - Continue Localizing Custom Widgets 💻

As most of the Flutter UI is made of Custom Widgets, corresponding sections took ample amount of time for doing I18n in them.

Flutter uses the concept of companion messages for interpolation, and hence I had to use companion messages wherever Interpolation was needed.

Companion messages generally convert localization key names into methods and hence we can pass variables as an argument so that there is no need of breaking string.

Along with this I had to find solutions for the unit tests, unit tests for localized Flutter widgets needs delegates and current locale to be defined explicitly.

Following tasks were achieved during this week ⏬

Create a Language Switcher using the locale provider package.
Continue localization in Custom Widgets
Fix unit tests for all the Custom Widgets

A major problem here is we can’t use the I18n function outside the BuildContext i.e I18n will work fine in widgets but not outside the widgets. App also contains models, services and constants which need to be localized.

Currently I am trying to find the solution for the same. ☑️

For more, stay connected!!

Best Regards ~ Pavan

GSoC Coding Period - Week6 and Week7 Report

2021-08-01T00:00:00+00:00

Completing my Ruby on Rails codebase work, I started working with JavaScript coded CircuitVerse Simulator during these two weeks 💻 .

The simulator is currently integrated into Rails using WebPacker gem to deliver JavaScript on the frontend and Ruby as well.

We cannot use Rails I18n in Simulator as individually it was a node-based (ES6) product. As decoupling of Simulator is going on in parallel, I only had to work on JS files served by WebPacker and not interface of Simulator written in Ruby ERB template

The simulator structure is divided as follows ⬇️

Configuration files in simulator/src along with third-party npm packages.
Digital Circuit elements in form of modules (General modules, Sequential modules and Testbench modules).
Relevant tools like themers, hotkey binders (to run custom shortcuts through the keyboard), and data folder handling project-based scenarios.

Week6 - Localizing Configuration files 📁

In total there were 36 configuration files written in JavaScript, which I had to check as well as localize without breaking any piece of code.

Following tasks were achieved during this week ⏬

I18n in Simulator controls interface in UX.js
I18n in Simulator Guide in tutorials.js
I18n in Simulator functionalities such as Verilog, SubCircuits, CombinationalAnalysis etc.
Completing I18n and testing in all the remaining 36 configuration files and functionalities.

Week7 - Localizing Circuit modules and some basic services ☑️

Here I worked with element modules, hotkey binders, themers, testbench and sequential circuit element modules

Following tasks were achieved during this week ⏬

I18n in 50 Circuit modules and a total of 17 sequential circuit element modules and testbench as well.
I18n in themers and hotkey binders
I18n in mutable properties of Circuit Elements (If Any)
I18n in configuration handling Current Project Data

However, some problems encountered in themers and hotkey binders are that they render JavaScript object keys directly to represent the corresponding field names that can’t be touched as it breaks the back-end package.

In the end, I finished working on the Simulator which required 800+ code changes and started working with Flutter based Mobile App 📱.

For more, stay connected!!

Best Regards ~ Pavan

GSoC’2021 - Phase One Evaluations

2021-07-17T00:00:00+00:00

This blog report summarizes my work which was done during the first phase of Google Summer of Code 2021 coding period. First phase of GSoC’2021 was started from June 7 and officially end on July 12.

My Project Details 📋

Internationalization mainly aims at creating I18n architecture for the CircuitVerse platforms in order to localize or translate them into multiple languages.

My aim during GSoC is to create I18n infrastructure so that CircuitVerse platforms can be internationalized into global languages and platforms can be emerged as a Global Platform.

During GSoC my aim is to create I18n architecture for 5 major technologies used in different CircuitVerse platforms.

Ruby on Rails (CircuitVerse Main Platform)
JavaScript (CircuitVerse Simulator)
Jekyll (CircuitVerse Interactive Book)
Flutter (CircuitVerse Mobile App)
DocsifyJs (CircuitVerse Docs)

Phase1 Report :-

Week 1: Turning Coffee into Code (☕ - 💻)

In this week, I started setting up fresh repositories for Rails codebase along with linters and my favourite extension RuboCop for Rails.

Following tasks were achieved during this week ⏬ :-

Adding locale to CircuitVerse API endpoint.
Update JSON Schema and validate RSpec tests to adapt new changes.
Generate array of locale codes following ISO 639-1 standards (130+ locales).
Advancement in Current I18n setup in Rails.
Localize Teachers and Simulator module (partially).

Week 2: Begin with Localizing CircuitVerse Modules

In my 2nd week, I started preparing for a bunch of localization rules so that consistency in I18n is maintained throughout the codebase by me as well as by future contributors.

For this task, I had to take proper overview of the codebase and design module specific rules for running quality I18n processes throughout the module.

Following tasks were achieved during this week ⏬ :-

Preparing localization Rules.
i18n-js : First I18n architecture for Simulator (Depends on Ruby).
Localization of CV Modules - Views (10 modules localized).

Week 3: Continue working with CircuitVerse Modules

In this week, I worked on localization process of CV modules and other aspects of project.

Following tasks were achieved during this week ⏬ :-

i18n-js : Second I18n architecture for Simulator (Depends on Rails I18n Mapping).
Localization of CV Modules - Views (13 modules localized).
Localize string oriented gems commentator, activity notifications, mailers, paginators etc.

Week 4: Working on Library, Documentation and Modules

4th week consisted of working on major aspects such as library, documentation and modules of project.

Following tasks were achieved during this week ⏬ :-

banana-i18n : backend independent I18n architecture for Simulator (Finalized and Merged).
Official documentation written on CircuitVerse wiki pages.
Localization in controllers and form attributes (All accomplished).

Week 5: Starting work on Simulator and Mobile App

In my final week, I started working on simulator and mobile app.

Following tasks were achieved during this week ⏬ :-

Localize CombinationalAnalysis.js.
Design Language Switcher and I18n test Suite for Rails.
Start of initial work in Mobile App.

Implementation

Additional Information

All the commitments I have made for phase-1 of the coding period had been achieved. Instead of CircuitVerse Docs, I have started my work with Mobile App in parallel and I18n for Docs will be done in the ending weeks as it becomes ready for I18n.

Blog Posts

I have also created this blog covering my GSoC journey as well as my preparation during pre-GSoC, in order that future GSoC aspirants receive an advantage from it .

Kindly check other posts! Blog

Final Thoughts

I would like to thank the CircuitVerse community for providing me this amazing opportunity. Open Source contributions at CircuitVerse helped me a lot in enhancing my coding skills and soft skills as well.

Special thanks to my mentors Aboobacker MK and Nitish Aggarwal. It was a great learning experience for me to work with them during phase one.

Looking forward for an exciting phase two!

Thankyou

GSoC Coding Period - Week5 Report

2021-07-12T00:00:00+00:00

Currently, I am in the 5th week of the coding period before GSoC phase one evaluations. During this week, I had a relaxing time, as major commits done for phase one evaluations were already completed.

We had a slight change in the timeline for this week. Instead of working on Docsify.js framework, I started working with Simulator and Mobile App. Along with this, I had to focus on preparing my code for Phase one evaluations.

Week 5: Starting work on Simulator and Mobile App

Major portions of Ruby code was already covered and consequently, I started working on Simulator and Mobile App.

Following tasks were achieved during this week ⏬ :-

Start localizing JavaScript-based Simulator Code.
Design Language Switcher and I18n test Suite for Rails.
Start of initial work in Mobile App.
Working on I18n documentation

Waiting for the results of phase one evaluations ahead!!!

For more, stay connected!!

Best Regards ~ Pavan

GSoC Coding Period - Week3 and Week4 Report

2021-07-04T00:00:00+00:00

Hey Readers!👋 The first two weeks of coding period was a great learning experience for me, along with positive feedbacks by mentors on my pull requests.🤩😎

In that duration, I created the I18n infrastructure for the first 10 CV modules along with some parallel coding work and experimentations. 🏁

Week 3: Working with CV Modules - Ruby Gems - Mailers 💻

It was the beginning of completing my work on the remaining major modules. Some of the modules like logix took 500 lines of code changes.

It was quite hard to understand and get familiar with part of codebase I haven’t visited before. Unfamiliar modules took an ample amount of time in understanding Ruby code and JavaScript based logic along with running quality I18n processes on them.

Working with modules
- This week I completed my work in 6 major modules along with provisional completion of the remaining 7 modules.
- Testing and experimentation will be carried in upcoming weeks before the final deployment to the CircuitVerse Servers.
Working with gems
- I also had a strong hand on understanding the structure of different gems such as devise, activerecord error messages, commentator, activity notifications, mailers, paginators etc.
- I also got introduced with the awesome gem MailCatcher which can catch mails send locally and can show us direct results.

At the end of this week, I finally completed my major work on all 23 modules which is a single modules on its own 💠 3 PRs merged and current two under review.

Week 4: `banana-I18n` Integration - Other Modules ⏬

During this week, I felt relaxed as major work required was already done locally. I started working on banana-I18n JavaScript library along with working on controllers, helpers etc on Rails side.

Before banana-I18n I proposed two integrations of i18n-js in different ways. Second integration still landed with dependency of Rails I18n mapping 😶😶.

Working with banana-I18n library
- banana-I18n library is a Pure JavaScript form of Jquery-I18n library developed by wikipedia. They also provide React and Vue bindings of the library for use in specific environments.
- In our case JavaScript modules are statically compiled by webpacker and are served on frontend. As banana-i18n is written purely in JavaScript it was a good choice at first glance.
- Basically this library allows us the instantiation of a constructor which can hold an object named messages which when passed to the constructor, the library interprets it through their scripts and provides I18n support for JS based modules.
Working with Loading Mechanism

Oops!😬 Library don’t provide their own Asynchronous mechanism to load JSON in the library, Here I had to implement loading mechanism by myself.

Here I tested three Asynchronous loading mechanisms ⤵️
- Use of Fetch API in Web Environment
- Keeping configuration in Web Environment and implement CommonJs methods via RequireJs library
- Use ES6 or CommonJs environment provided by webpacker
Selecting Loading Mechanism
- First method is a very basic method but uses HTTP calls for Asynchronous loading. This won’t play nicely in offline apps hence was eliminated after discussion with mentors.
- Second method depends on external dependency, consequently I tried to avoid using this method.
- Third method seemed more promising as dynamic loading is also applicable in CommonJs Environment, however ESLint yelled at me for my approach frequently.

Finally I decided to go with CommonJs methods to dump JSON files into the library, and basic JavaScript to switch between Default language JSON and Current locale JSON.

If a JSON for the current locale is not available, I had to load default JSON, which can be done easily using try{}.. catch{} JavaScript syntax.

Here we can instantiate default JSON in object directly and use try{}... catch{} for current locale JSON, even if asynchronous loading fails for current locale, object will already have a default json file and library will be good to go in any exceptional case.

What Next ✨

After the end of the upcoming week, Phase one Evaluations will be held from 12 July onwards. According to GSoC timeline mentors will review code and will pass and fail students after analysing the work they had done till now.

I have completed almost all the tasks that I had committed before Phase one evaluations.🥳🥳 In the upcoming week I will design a test suite for I18n, language switchers and prepare for my phase one evaluations. ☑️
I will also start working parallely on Mobile App and Simulator as well.◾✍️

For more, stay connected!!

Best Regards ~ Pavan

GSoC Coding Period - Week1 and Week2 Report

2021-06-20T00:00:00+00:00

Hey folks! :wave: GSOC coding period was officially started on 7 June :man_technologist: :man_technologist:. After the community bonding period this is my first article on coding period, sharing my first two weeks coding period experience with CircuitVerse.

My Project Details 📋

Internationalization mainly aims at creating I18n architecture for the different platforms in order to localize or translate them in multiple languages.

In short, my aim during GSoC is to make CircuitVerse platform a Global Platform so that it can be introduced at global level. It will help both Indian as well as foriegn clients to use it efficiently and make the most out of it.

During GSoC I will be creating I18n architecture for 5 major technologies used in different CircuitVerse platforms.

:one: Rails (CV main platform)
:two: JavaScript (CV simulator)
:three: Jekyll (CV interactive book)
:four: Flutter (CV mobile app)
:five: DocsifyJs (CV docs)

Week 1: Turning Coffee into Code (☕ - 💻)

In this week, I started setting up fresh repositories for Rails codebase along with linters and my favourite extension RuboCop for Rails.

Prior to the coding period, the complete project was divided into multiple tasks. Among them, following tasks were acheived during Week 1.

Adding locale to CircuitVerse API endpoint
- CircuitVerse API exports ruby objects in form of JSON via data serialization techniques using FastJsonapi. Mobile app renders such data to show content of main platform in mobile app.
- Adding locale value and updating JSON Schema of User API will help in using same locale value used by user in main platform in mobile app also.
Using ISO standards for locale on frontend
- Next task was to convert locale acronymns into full names following ISO 639-1 standard language codes. and integrating them with CV forms. This is helpful in picking up desired language almost instantly.
Initial I18n setup in Rails
- Basic I18n setup to make use of nested directory structure
- Fixing rspec test to adapt new changes and updating JSON schema for users as well as project API.
- Other relevant tasks including prepation of yml directory structure, translating page in alternate locale, etc.

My first PR was merged with the awesome feedback by mentors 🤩

During this week, I also had a call with my mentors for discussing I18n architecture for Simulator.

Week 2: Begin with Localizing CV Modules ⏬

Preparing localization Rules
- 2nd week started with preparing bunch of localization rules for CV Rails platform and document them so that consistency in I18n is maintained throughout the codebase by myself as well as by future contributors.
- This includes designing module specific rules by having proper overview of codebase.
Introducing first I18n architecture for Simulator
- I decided to go with famous i18n-js library for giving I18n architecture to Simulator. Integration worked great in perspective of I18n but failed in terms of dependency on Rails.
- I18n-js is present in form of gem as well as npm library but module they are using are still written in ruby and requires erb loader with webpacker for its integration.
- CV simulator needs backend independent architecture so that it can be decoupled in future and integrated in other platforms such as mobile app.
  
  Currently, I am working further and doing more research on proper backend independent JS libarary for Simulator.
Localization of CV Modules
- Week 2 was the beginning of localizing 23 modules. Out of which 10 modules where localized in 2nd week.
- Pushing a bunch of changes in single PR is irrelevant and also hard to review for mentors. Regarding this, I decided to create different PR for each module. Hence a proper workflow of 2 PR’s was created for review and merge at a time.

Some of the aspects where more care is to be taken while doing I18n in modules were 🔷

Use of proper designed module specific rules.
Taking care that logic doesn’t break while introducing I18n
Use of powerful features of Rails I18n API.
Directory Structure
Key-value pair naming conventions along with interpolation and pluralization.

What I learned 🎯

More exposure to API and data serialization
Creation of localization rules to give best possible infrastructure.
Working with RSpec tests and behaviour driven development
Experience of integrating different JavaScript libraries
Designing backend independent I18n solutions.
Core knowledge of I18n and about localization of modules

For more, stay connected!!

Best Regards ~ Pavan

Pavan Joshi

Summer Of Bitcoin - Intro and Onboarding Week at Bitcoin

Summer Of Bitcoin - A Global Bitcoin Internship

What is the Summer of Bitcoin? 🤔

Summer of Bitcoin Stats 📊

Summer Of Bitcoin Journey ⬇️

Project Details 📑

Objectives 💻

Final Report - GSoC’2021

My Project Details 📋

Final Report 📃

Phase Two :-

Simulator 🔌

Week 6: Begin with Localizing Simulator Configuration Modules 📂

Week 7: Localizing Simulator Circuit Element Modules 🔄

Mobile App 📱

Week 8: Upgrade I18n Workflow and Begin Working with Mobile App 📈

Week 9: Continue Localizing Custom Widgets 🚧

Week 10: I18n Architecture in DocsifyJS and Final Enhancements ✨

Implementation 💻

Major MileStones Achieved ☑️

Future Scope ℹ️

Final Thoughts 💭

GSoC Coding Period - Week10 Report

Mechanism behind I18n for DocsifyJS 💻

Week 10: I18n Architecture in DocsifyJS and Final Enhancements ✨

Implementation 🔄

Major MileStones Achieved ☑️

Final Evaluations 📧

GSoC Coding Period - Week8 and Week9 Report

Week8 - Upgrade I18n Workflow and Begin Working with Mobile App 🔄

Week9 - Continue Localizing Custom Widgets 💻

GSoC Coding Period - Week6 and Week7 Report

Week6 - Localizing Configuration files 📁

Week7 - Localizing Circuit modules and some basic services ☑️

GSoC’2021 - Phase One Evaluations

My Project Details 📋

Phase1 Report :-

Week 1: Turning Coffee into Code (☕ - 💻)

Week 2: Begin with Localizing CircuitVerse Modules

Week 3: Continue working with CircuitVerse Modules

Week 4: Working on Library, Documentation and Modules

Week 5: Starting work on Simulator and Mobile App

Implementation

Additional Information

Blog Posts

Final Thoughts

GSoC Coding Period - Week5 Report

Week 5: Starting work on Simulator and Mobile App

GSoC Coding Period - Week3 and Week4 Report

Week 3: Working with CV Modules - Ruby Gems - Mailers 💻

Week 4: banana-I18n Integration - Other Modules ⏬

What Next ✨

GSoC Coding Period - Week1 and Week2 Report

My Project Details 📋

Week 1: Turning Coffee into Code (☕ - 💻)

Week 2: Begin with Localizing CV Modules ⏬

What I learned 🎯

Week 4: `banana-I18n` Integration - Other Modules ⏬