[RFC]: status dashboard for tracking stdlib repositories build failures

[anxhukumar]

Full name

Anshu Kumar

University status

No

University name

No response

University program

No response

Expected graduation

No response

Short biography

I am a 23-year-old, currently living in Bangalore, India. I have done my bachelor's in Business Administration. I have been curious and interested in programming and development for a very long time and have taken several online bootcamps and free resources to supplement my self-learning experience. As of now, I am very familiar with JavaScript and the MERN stack. I am also learning Python, C and GoLang to focus more on the backend development side.

Even though, I do not have a conventional Computer Science Bachelors degree, I am committed towards learning Computer Science from low-level concepts to higher-level abstractions.

Timezone

Indian Standard Time (IST) – UTC+5:30

Contact details

email: contact.anshukumar@protonmail.com, github: anxhukumar

Platform

Linux

Editor

VSCode is my preferred code editor now. I started my programming learning journey with VSCode and have not switched to another editor yet, as I am more focused on my coding skills as of now.

Although I have plans to learn NeoVim at some point, as I have seen people achieve really good speed with it as they have almost zero dependence on the mouse, due to the motions Vim provides.

Programming experience

I started learning to code in JavaScript 1.2 years ago. I am well-versed in the MERN stack, and am fully capable of creating full-stack web applications at this point. I also know Python and C, but do not have much hands-on practice with them.

I have created a full-stack blog application from scratch with a minimalist UI. I have implemented Authentication and taken all the other security measures to protect against XSS attacks and other vulnerabilities.

Here is a link to the repo: https://github.com/anxhukumar/Personal-blog-website.git

JavaScript experience

I have been using JavaScript for the past 1.2 years. I am at a level where I can easily create backend APIs using it and work with frontend frameworks like React.js.

My favorite feature of JavaScript is its simple syntax and the flexibility it provides to create both backend and frontend prototypes with ease.

I don’t have any least favorite feature of JavaScript in mind at the moment.

Node.js experience

I have been using the Node.js runtime environment since I started my programming journey. I have built full-fledged applications with it.

C/Fortran experience

I am familiar with the basics of C and I practice some simple C problems on a regular basis. Although I haven't made any significant project using C as of now.

A codebase written in C is not completely gibberish to me, and I can figure some things out in it currently.

I started learning C in order to start reading and understand this book called "Computer Systems: A Programmer's Perspective" as it has C as a prerequisite to understand the low-level operations.

I have zero knowledge of Fortran at this point.

Interest in stdlib

I find Stdlib to be a beast of a library for JavaScript. It gives so much power to JavaScript users where they don't have to look at other languages for the mathematical and scientific computing.

My favourite feature of Stdlib is the ease with which one can use the functionalities in their project, using just few lines of code.

Version control

Yes

Contributions to stdlib

Total Pull Requests: 12

---

Merged Pull Requests: 7

• Features: 2
• Bug Fixes: 5

1. Added stats/incr/nanmeanabs package. [✅ Merged]
2. Added stats/incr/nanmean package. [✅ Merged]
3. Fixed an example return value in documentation. [✅ Merged]
4. Fixed the usage of new Array() to comply with the linting rule. [✅ Merged]
5. Fixed incorrect jsDoc type from ComplexArray to Complex64Array. [✅ Merged]
6. Fixed the lint error by replacing tabs with spaces in manifest.json. [✅ Merged]
7. Fixed the lint error by adding process module. [✅ Merged]

Link to my closed PR's: https://github.com/stdlib-js/stdlib/pulls?q=is%3Apr+author%3Aanxhukumar+is%3Aclosed

---

Open Pull Requests: 5

• Features: 3
• Bug Fixes: 2

1. Added stats/incr/nanmeanabs2 package.
2. Added stats/incr/nanmmae package.
3. Added stats/incr/nanmmaxabs package.
4. Fixed benchmark to measure binet correctly.
5. Fixed styling and corrected the return values of documentation and comments.

Link to my open PR's: https://github.com/stdlib-js/stdlib/pulls/anxhukumar

stdlib showcase

I have created a Stdlib tutorial for beginners to help them understand the library and use its features in the most common ways.

My idea is to create an easy-to-understand webpage with two cartoon characters having a conversation about the implementation of the library.

I have used React and Tailwind to create this.

Here is the link to the repository: https://github.com/anxhukumar/stdlib-tutorial.git

Goals

1. Express.js Backend API

• A well-structured codebase with standard practices for files and folder distribution.
• Clear routes for each type of request.
• Clear code documentation on each code section to help future contributors understand the
  codebase easily.
• Follow the clean coding practices of the stdlib codebase, as observed during contributions and
  through feedback from maintainers.
• Error handling using try and catch blocks.
• Fetch data from the database using Prisma ORM (if approved by mentors), or use vanilla SQL to
  query the PostgreSQL database.

2. React.js Frontend

• A React frontend codebase created using the Vite bundler.
• A separate components directory to ensure component reusability and maintain a cleaner main
  app file.
• Use Redux for state management (if approved by mentors), or else use the useState hook.
• Use Tailwind CSS to integrate styling in a cleaner and more efficient manner.
• A minimalist UI to serve the purpose of tracking build failures.
• Use Axios for API calls from the backend.

3. Documentation

• A comprehensive setup and installation guide for running the code files on a local machine.
• API documentation for backend services.
• General guide for dashboard features.

Why this project?

When I first looked at this project in the list of ideas, I immediately knew I was going to submit a proposal for it.

I could visualize the project, and I knew that it was achievable with the skill set I have.

Even from a personal skill development perspective, it is interesting that I can create a web application to track the current status of repository failures.

I am gonna enjoy working on this.

Qualifications

I have taken several online bootcamps and learned to develop web applications from the ground up. As a self-taught developer, I have experience with JavaScript, React.js, Express.js, MongoDB, and PostgreSQL. I have built and deployed full-stack applications using the MERN stack. My ability to work with both the frontend and backend makes me suitable for the proposed project.

Prior art

I couldn't find any such implemented project as of now that specifically tracks the build failures of repositories, except the example shared in your documentation of the npm dashboard. All the projects I find are mostly a very complex dashboard to show multiple metrics.

I will update this section if I find anything valuable.

Commitment

I can dedicate myself to the project for the entire duration of GSoC. I can give 40 to 50 hours per week to the project and can treat it as a full-time responsibility.

Throughout the contribution period, I will have no other personal or professional commitments that could impact my availability. This will enable me to focus fully on the project, maintain consistency, and meet all deadlines for deliverables.

Schedule

Related issues

No response

Checklist

• I have read and understood the Code of Conduct.
• I have read and understood the application materials found in this repository.
• I understand that plagiarism will not be tolerated, and I have authored this application in my own words.
• I have read and understood the patch requirement which is necessary for my application to be considered for acceptance.
• I have read and understood the stdlib showcase requirement which is necessary for my application to be considered for acceptance.
• The issue name begins with [RFC]: and succinctly describes your proposal.
• I understand that, in order to apply to be a GSoC contributor, I must submit my final application to https://summerofcode.withgoogle.com/ before the submission deadline.

[kgryte]

@anxhukumar Thank you for opening this RFC. A few comments/questions:

1. Do you have any mockups/wireframes you can share to help visualize what you envision for this dashboard?
2. You've suggested using React, which suggests you are wanting to create an SPA. Why is an SPA appropriate for this dashboard? Are you planning on showing multiple views?
3. Why Express? For our current Node.js servers, we use fastify, so I'm curious to understand why Express is more appropriate in this case.

[anxhukumar]

@kgryte

1. Figma wireframe: https://www.figma.com/design/npc3fBxtjskTxHniJGGdtu/Stdlib-UI-(GSOC)?node-id=0-1&p=f

I created this Figma wireframe a while ago. After reading some of your feedback on questions asked by other contributors, I feel it might have some issues, such as:

• It might be too complex, which is not expected.

• The cards displaying individual repositories could be made smaller to reduce unnecessary pagination.

2. I believe React will provide flexibility for adding more complexity in the future if required. Additionally, implementing functionality to click on an individual repository card to view more details will be easier with React.

3. I don’t have a specific reason for choosing Express.js, it's simply the framework I am most comfortable with at this point. However, if the project strictly requires Fastify, I am open to using it. It shouldn’t take long for me to familiarize myself with the framework.