<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.9.0">Jekyll</generator><link href="https://ajadi-abiola.github.io/feed.xml" rel="self" type="application/atom+xml" /><link href="https://ajadi-abiola.github.io/" rel="alternate" type="text/html" /><updated>2022-03-18T17:02:07+00:00</updated><id>https://ajadi-abiola.github.io/feed.xml</id><title type="html">Abiola Ajadi</title><subtitle>Front-End Engineer, Outreachy Intern @ Debian</subtitle><author><name>Abiola Ajadi</name><email>briannaajadi03@gmail.com</email></author><entry><title type="html">Outreachy-And it’s a wrap!</title><link href="https://ajadi-abiola.github.io/blog/Outreachy-Wrap-up" rel="alternate" type="text/html" title="Outreachy-And it’s a wrap!" /><published>2022-03-04T00:00:00+00:00</published><updated>2022-03-04T00:00:00+00:00</updated><id>https://ajadi-abiola.github.io/blog/Outreachy%20Wrap-up</id><content type="html" xml:base="https://ajadi-abiola.github.io/blog/Outreachy-Wrap-up">&lt;h2 id=&quot;outreachy-wrap-up&quot;&gt;Outreachy Wrap-up&lt;/h2&gt;
&lt;p&gt;Project Improve Debian Continuous Integration UX &lt;br /&gt;
Project Link: &lt;a href=&quot;https://www.outreachy.org/outreachy-december-2021-internship-round/communities/debian/#improve-debian-continuous-integration-ux&quot;&gt;https://www.outreachy.org/outreachy-december-2021-internship-round/communities/debian/#improve-debian-continuous-integration-ux&lt;/a&gt; &lt;br /&gt;
Code Repository: &lt;a href=&quot;https://salsa.debian.org/ci-team/debci&quot;&gt;https://salsa.debian.org/ci-team/debci&lt;/a&gt; &lt;br /&gt;
Mentors: Antonio Terceiro, Paul Gevers and Pavit Kaur&lt;/p&gt;

&lt;h2 id=&quot;about-the-project&quot;&gt;About the project&lt;/h2&gt;
&lt;p&gt;Debci exist to make sure packages work currently after an update, How it does this is by testing all of the packages that have tests written in them to make sure it works and nothing is broken
This project entails making improvements to the platform to make it easier to use and maintain.&lt;/p&gt;
&lt;h2 id=&quot;deliverables-of-the-project&quot;&gt;Deliverables of the project:&lt;/h2&gt;
&lt;ul&gt;
  &lt;li&gt;Package landing page displaying pending jobs&lt;/li&gt;
  &lt;li&gt;web frontend: centralize job listings in a single template&lt;/li&gt;
  &lt;li&gt;self-service: request test form forgets values when validation fails&lt;/li&gt;
  &lt;li&gt;Improvement to status&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;work-done&quot;&gt;Work done&lt;/h2&gt;
&lt;h5 id=&quot;package-landing-page-displaying-pending-jobs&quot;&gt;Package landing page displaying pending jobs&lt;/h5&gt;
&lt;p&gt;Previously, Jobs that were pending were not displayed on the package page. Working on this added a feature to display pending jobs on package landing. 
Working on this task made it known that the same block of codes was repeated in different files which led to the next task
&lt;a href=&quot;https://postimg.cc/yDPhhW5v&quot;&gt;&lt;img src=&quot;https://i.postimg.cc/7LvBk2N8/Screenshot-2022-03-04-at-02-03-06.png&quot; alt=&quot;Screenshot-2022-03-04-at-02-03-06.png&quot; /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://salsa.debian.org/ci-team/debci/-/merge_requests/221&quot;&gt;Merge request&lt;/a&gt;&lt;/p&gt;
&lt;h5 id=&quot;web-frontend-centralize-job-listings-in-a-single-template&quot;&gt;web frontend: centralize job listings in a single template&lt;/h5&gt;
&lt;p&gt;Jobs are listed in various landings such as status packages, Status alerts, status failing, History, and so on. The same Code was repeated in these pages to list the jobs, I worked on refactoring it and created a single template for job listing so it can be used anywhere it’s needed. 
I also wrote a test for the feature I added. &lt;br /&gt;
&lt;a href=&quot;https://salsa.debian.org/ci-team/debci/-/merge_requests/223&quot;&gt;Merge request&lt;/a&gt;&lt;/p&gt;
&lt;h5 id=&quot;self-service-request-test-form-forgets-values-when-validation-fails&quot;&gt;self service: request test form forgets values when validation fails&lt;/h5&gt;
&lt;p&gt;When one tries to request for a test and it fails with an error, originally the form does not remember the values that were typed in the package name, suite field et. c. This fix ensures the form remembers the values inputted even when it throws an error.
&lt;img src=&quot;https://i.postimg.cc/jSjT7GVd/Screenshot-2022-03-04-at-02-05-29.png&quot; alt=&quot;Image of request test page&quot; /&gt;
N/B: The form checks all architecture on the load of the page&lt;br /&gt;
&lt;a href=&quot;https://salsa.debian.org/ci-team/debci/-/merge_requests/219&quot;&gt;merge request&lt;/a&gt;&lt;/p&gt;
&lt;h5 id=&quot;improvement-to-status&quot;&gt;Improvement to status&lt;/h5&gt;
&lt;p&gt;Originally the Status pages were rendered as static HTML pages but I converted these pages to be generated dynamically, I wrote endpoints for each page.
Since most of the status pages have a list of jobs I modified it to use the template I created for job-listing. 
Previously, the status pages had a mechanism to filter such as &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;All&lt;/code&gt;, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Latest 50&lt;/code&gt; et.c which wasn’t paginated. I  removed this mechanism added a filter by architecture and suites to these pages and also add pagination.
Last but not the least, I wrote tests for these implementations carried out on the status page. 
&lt;img src=&quot;https://i.postimg.cc/pLjwzxGv/Whats-App-Image-2022-03-04-at-3-17-02-AM.jpg&quot; alt=&quot;Image of Status failing page&quot; /&gt;&lt;/p&gt;

&lt;p&gt;merge request:&lt;br /&gt;
&lt;a href=&quot;https://salsa.debian.org/ci-team/debci/-/merge_requests/228&quot;&gt;first task&lt;/a&gt; &lt;br /&gt;
&lt;a href=&quot;https://salsa.debian.org/ci-team/debci/-/merge_requests/224&quot;&gt;second task&lt;/a&gt;&lt;br /&gt;&lt;/p&gt;
&lt;h2 id=&quot;major-take-aways&quot;&gt;Major take-aways&lt;/h2&gt;
&lt;p&gt;I learnt a lot during my internship but most importantly I learnt how to:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;write Tests in Ruby and how writing tests is an important aspect of software development&lt;/li&gt;
  &lt;li&gt;maintain good coding practice, Paying attending to commit messages, Indentation et.c are good areas I developed in writing code.&lt;/li&gt;
  &lt;li&gt;make contributions in Ruby Programming Language.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;acknowledgement&quot;&gt;Acknowledgement&lt;/h2&gt;
&lt;p&gt;I can not end this without saying thank you to my mentors Antonio Terceiro, Paul Gevers, and Pavit Kaur for their constant support and guidance throughout the entire duration of this Internship. It has been a pleasure Interacting and learning from everyone.&lt;/p&gt;

&lt;h2 id=&quot;review&quot;&gt;Review&lt;/h2&gt;
&lt;p&gt;Outreachy has helped me feel more confident about open-source, especially during the application phase. I had to reach out to the community I was interested in and ask questions on how to get started. 
The informal chats week was awesome I was able to build my network and have interesting conversations with amazing individuals in open-source. 
To round up, Always ask questions and do not be afraid of making a mistake, as one of the outreachy blog post topics says &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Everyone struggles!&lt;/code&gt;, but never give up!&lt;/p&gt;</content><author><name>Abiola Ajadi</name><email>briannaajadi03@gmail.com</email></author><category term="Outreachy" /><category term="Debian" /><category term="Technology" /><summary type="html">Outreachy Wrap-up Project Improve Debian Continuous Integration UX Project Link: https://www.outreachy.org/outreachy-december-2021-internship-round/communities/debian/#improve-debian-continuous-integration-ux Code Repository: https://salsa.debian.org/ci-team/debci Mentors: Antonio Terceiro, Paul Gevers and Pavit Kaur</summary></entry><entry><title type="html">Career Interest!</title><link href="https://ajadi-abiola.github.io/blog/Career-Interests" rel="alternate" type="text/html" title="Career Interest!" /><published>2022-03-01T00:00:00+00:00</published><updated>2022-03-01T00:00:00+00:00</updated><id>https://ajadi-abiola.github.io/blog/Career-Interests</id><content type="html" xml:base="https://ajadi-abiola.github.io/blog/Career-Interests">&lt;p&gt;Hi, Welcome back.
In this blog, I will be discussing my career interests and what I plan to pursue after my internship.&lt;/p&gt;

&lt;h2 id=&quot;what-comes-next-after-the-internship&quot;&gt;What comes next after the internship&lt;/h2&gt;
&lt;p&gt;After working a while with Debci project, I was able to learn better software development practices and love the open source community. I will love to build my career path around open-source.&lt;/p&gt;

&lt;h2 id=&quot;what-i-am-looking-for&quot;&gt;What I am looking for&lt;/h2&gt;
&lt;p&gt;Prior to starting my internship, I have worked as a front-end developer with react and javascript. During my internship with Debci I learn Ruby and also how to write tests 😊😊. I am also passionate about community which is one of my core-values, I build and organize communities.
I am looking for opportunities in areas of front-end development, Ruby, React.&lt;/p&gt;

&lt;p&gt;i am also open to opportunities in developer relations/community management where i  can be part of building or managing a community, Interacting with developers, meeting new people.&lt;/p&gt;

&lt;p&gt;I am based in lagos, Nigeria and can work remotely, but also open to relocation.&lt;/p&gt;

&lt;p&gt;You can connect with me on &lt;a href=&quot;https://www.linkedin.com/in/barakatajadi/&quot;&gt;linkedin&lt;/a&gt;&lt;/p&gt;</content><author><name>Abiola Ajadi</name><email>briannaajadi03@gmail.com</email></author><category term="Outreachy" /><category term="Debian" /><category term="Technology" /><summary type="html">Hi, Welcome back. In this blog, I will be discussing my career interests and what I plan to pursue after my internship.</summary></entry><entry><title type="html">Modifying expectations!</title><link href="https://ajadi-abiola.github.io/blog/Modifying-expectation" rel="alternate" type="text/html" title="Modifying expectations!" /><published>2022-02-17T00:00:00+00:00</published><updated>2022-02-17T00:00:00+00:00</updated><id>https://ajadi-abiola.github.io/blog/Modifying%20expectation</id><content type="html" xml:base="https://ajadi-abiola.github.io/blog/Modifying-expectation">&lt;p&gt;Hi everyone!&lt;/p&gt;

&lt;p&gt;In today’s blog post I will be talking about the progress i have made , the hurdles I encountered and how my current progress differs from my original expectations.&lt;/p&gt;

&lt;p&gt;I applied to Debian community with a particular timeline and expected it to go that way, but after starting out i realized i had alot to learn in Ruby and the codebase. 
So far i have worked on issues i am proud of and when i use Debci i see some of the changes i added for example the self-service form remembering values that was filled after an error message / it reloads.
Another milestone for me is writing test cases, I learnt about test driven development which is an awesome process is developing software. 
Looking back at the beginning before the internship started I can see how much experience i have gained and also improvement I made.&lt;/p&gt;

&lt;h2 id=&quot;road-block&quot;&gt;Road block&lt;/h2&gt;
&lt;p&gt;Some tasks took longer than expected for example writing the test cases as i was new to this way of building and also i had to refactor some code, I was very careful doing this as i wanted to make sure i do it the right way.&lt;/p&gt;

&lt;h2 id=&quot;the-journey-continues&quot;&gt;The journey continues&lt;/h2&gt;
&lt;p&gt;I had to modify my initial expectations and my mentors have been so supportive. I hope to add more features to Debci and also write more tests.
So far, it has been a great experience. Till next time!&lt;/p&gt;</content><author><name>Abiola Ajadi</name><email>briannaajadi03@gmail.com</email></author><category term="Outreachy" /><category term="Debian" /><category term="Technology" /><summary type="html">Hi everyone!</summary></entry><entry><title type="html">Debci- An introduction for beginners!</title><link href="https://ajadi-abiola.github.io/blog/Think-about-your-audience" rel="alternate" type="text/html" title="Debci- An introduction for beginners!" /><published>2022-01-17T00:00:00+00:00</published><updated>2022-01-17T00:00:00+00:00</updated><id>https://ajadi-abiola.github.io/blog/Think%20about%20your%20audience</id><content type="html" xml:base="https://ajadi-abiola.github.io/blog/Think-about-your-audience">&lt;p&gt;Hello again!&lt;/p&gt;

&lt;p&gt;Been a minute! for this blog i will continue from my previous article where i explained Debci you can read more about it &lt;a href=&quot;https://ajadi-abiola.github.io/blog/Everyone-Struggles!&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;In my previous article I mentioned Debci stands for Debian Continous Integration and it exist to make sure packages work currently after an update by testing all of the packages that have tests written in them to make sure it works and nothing is broken.
For my internship, I am working on improving the user experience through the UI of the debci site making it easier to use.&lt;/p&gt;

&lt;h1 id=&quot;debci-consist-of-the-following-major-terms&quot;&gt;Debci consist of the following major terms:&lt;/h1&gt;

&lt;ul&gt;
  &lt;li&gt;Suite&lt;/li&gt;
  &lt;li&gt;Architecture&lt;/li&gt;
  &lt;li&gt;Packages&lt;/li&gt;
  &lt;li&gt;Trigger&lt;/li&gt;
&lt;/ul&gt;

&lt;h1 id=&quot;how-it-works-together&quot;&gt;How it works together&lt;/h1&gt;
&lt;p&gt;There are three releases in the active maintenance which are Unstable, Testing, and stable(these are known as the suite). What do they mean?
Unstable:
This is where active development occurs and packages are initially uploaded. This distribution is always called sid. 
Testing:
After packages undergone some degree of testing in &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;unstable&lt;/code&gt;, they are installed into the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;testing&lt;/code&gt; directory. This directory contains packages that have not yet been accepted into the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;stable&lt;/code&gt; release but are on their way there.
Stable:
The &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;stable&lt;/code&gt; distribution includes Debian’s most recent officially released distribution. The current &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;stable&lt;/code&gt; release which is Debian 11 is codenamed &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Bullseye&lt;/code&gt;.
Also we have the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;oldstable&lt;/code&gt; which is the previous stable release. The Debian 10 is now old stable which was codenamed &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;Buster&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Architectures: These are known as the CPUs achitecture and there are various ports like amd64, arm64, i386 et.c.&lt;/p&gt;

&lt;p&gt;An scenerio for example is if a user wants to test a package such as &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;acorn&lt;/code&gt; in Testing on arm64 along with a package X from Unstable this would be a pin-package (Pin packages are packages that need to be obtained from a different suite than the main suite that selected.), which means the package the user wants to test with the initial Package selected.Finally, trigger can be described as the name of the test job which is optional. This test is done to check if those packages in unstable can be migrated to Testing.&lt;/p&gt;

&lt;p&gt;This is a break down of Debci and I hope you enjoyed learning about what my internship entails. Till next time!&lt;/p&gt;

&lt;p&gt;references:
&lt;a href=&quot;https://www.debian.org/releases/&quot;&gt;Debian releases&lt;/a&gt;.
&lt;a href=&quot;https://www.debian.org/ports/&quot;&gt;Ports&lt;/a&gt;&lt;/p&gt;</content><author><name>Abiola Ajadi</name><email>briannaajadi03@gmail.com</email></author><category term="Outreachy" /><category term="Debian" /><category term="Technology" /><summary type="html">Hello again!</summary></entry><entry><title type="html">Outreachy-Everyone Struggles!</title><link href="https://ajadi-abiola.github.io/blog/Everyone-Struggles!" rel="alternate" type="text/html" title="Outreachy-Everyone Struggles!" /><published>2021-12-27T00:00:00+00:00</published><updated>2021-12-27T00:00:00+00:00</updated><id>https://ajadi-abiola.github.io/blog/Everyone%20Struggles!</id><content type="html" xml:base="https://ajadi-abiola.github.io/blog/Everyone-Struggles!">&lt;p&gt;Hello Everyone!&lt;/p&gt;

&lt;p&gt;Three weeks into my internship and it’s been great so far with Awesome Mentors. I am currently learning a new Language which is Ruby and this is the perfect time to remind myself that everyone struggles! I struggled a bit getting farmiliar with the codebase and pushing my first merge request during the internship. I won’t say i have a perfect understanding of how everything works, but i am learning.&lt;/p&gt;

&lt;h2 id=&quot;what-is-debci&quot;&gt;What is Debci?&lt;/h2&gt;

&lt;p&gt;Debci stands for Debian Continous Integration before i move on, what is continous integration? according to Atlassian ‘Continuous integration (CI) is the practice of automating the integration of code changes from multiple contributors into a single software project. It’s a primary DevOps best practice, allowing developers to frequently merge code changes into a central repository where builds and tests then run. Automated tools are used to assert the new code’s correctness before integration.’&lt;/p&gt;

&lt;p&gt;From the official documentation; The Debian continuous integration (debci) is an automated system that coordinates the execution of automated tests against packages in the Debian system.&lt;/p&gt;

&lt;p&gt;Debci exist to make sure packages work currently after an update, How it does this is by testing all of the packages that have tests written in them to make sure it works and nothing is broken. It has a UI for developers to see if the test passes or not.&lt;/p&gt;

&lt;h2 id=&quot;progress&quot;&gt;Progress&lt;/h2&gt;
&lt;p&gt;This week; 
I have learnt how to write automated test and Squashing multiple commits into one single commit.&lt;/p&gt;</content><author><name>Abiola Ajadi</name><email>briannaajadi03@gmail.com</email></author><category term="Outreachy" /><category term="Debian" /><category term="Technology" /><summary type="html">Hello Everyone!</summary></entry><entry><title type="html">Outreachy- Get to know me!</title><link href="https://ajadi-abiola.github.io/blog/Outreachy-Get-to-know-me!" rel="alternate" type="text/html" title="Outreachy- Get to know me!" /><published>2021-12-08T00:00:00+00:00</published><updated>2021-12-08T00:00:00+00:00</updated><id>https://ajadi-abiola.github.io/blog/Outreachy-Get%20to%20know%20me!</id><content type="html" xml:base="https://ajadi-abiola.github.io/blog/Outreachy-Get-to-know-me!">&lt;p&gt;Hello Everyone!&lt;/p&gt;

&lt;p&gt;I am Abiola Ajadi from Lagos, Nigeria. I have my B.sc in computer science from the University of Ilorin where I was involved in various community building and also a student leader.
In my free time, I love watching anime, reading comics also surfing the net. I enjoy learning about different cultures and will love to travel the world soon! 
Concerning pets, I love dogs(they are so cute!!)&lt;/p&gt;

&lt;h2 id=&quot;my-core-values&quot;&gt;My core values&lt;/h2&gt;

&lt;p&gt;I will use the 3Cs to describe my core values, which stands for Curiosity, Compassion and Community.&lt;/p&gt;

&lt;p&gt;Curiosity: Being curious builds the thirst and interest for knowlegde and how things work. I believe being curious helps us as individuals be vigilant and gain knowledge.
Compassion: This is one of my core values because i love to support people the way i can, especially in technology which is why community will be the third C. the role of community is very important i enjoy being with people who share the same goals and mindset with me.&lt;/p&gt;

&lt;h2 id=&quot;why-i-applied-to-outreachy&quot;&gt;Why I applied to Outreachy.&lt;/h2&gt;

&lt;p&gt;I have been curious about open source and how to get started. I wasn’t sure of the right way to start so i made some research and spoke to a friend who introduced me to outreachy as a good place to start. I submitted my initial application and made it to the contribution stage. It was exciting to see my first merged contribution to open source. I look forward to an exciting internship with the Debian community and Outreachy!&lt;/p&gt;</content><author><name>Abiola Ajadi</name><email>briannaajadi03@gmail.com</email></author><category term="Outreachy" /><category term="Debian" /><category term="Technology" /><summary type="html">Hello Everyone!</summary></entry></feed>