[RFC]: build a developer dashboard for tracking ecosystem build failures

[alextes90]

Full name

Aleksandr Teslin

University status

No

University name

No response

University program

No response

Expected graduation

No response

Short biography

I have started developer career after RS-school courses (2019). (It is very strong practical oriented JS courses conducted with the help of EPAM and is woking on outsource principal. They are free and after success graduated they a welcome yesterday's student to take part in learning process as mentors, now I am taking part there as mentor).

After school I was working on the following projects:

1. E-commerce platform. Stack: Typescript, React, NextJs, Docker, Scss, Headless CMS, MUI. Frontend Developer. (2020)
2. Streaming media platform. Stack: Typescript, React, Next.js, NextUI, SCSS, CI/CD - Vercel. Frontend Developer. (2021)
3. Advice Platform. Stack: TypeScript, React, Next.js, tRPC, react-query, Prisma, TailwindCSS, PostgreSQL, shadnc-ui, Zustand, next-i18next, Clerk.io. Full-stack Developer (2022/2023)
4. Publicis groupe. Stack: TypeScript, React, Astro js, TailwindCSS, Playwright, Node.js. Full-stack developer (2023 - current time)

My general interest are: TS/JS, frontend development and all modern way of writing of writing applications. I am learning now AWS and app architecture.

Timezone

+9

Contact details

email:[email protected],github:alextes90

Platform

Mac

Editor

VSCode

Programming experience

3 years.
Here I want to share an app. https://app.niceadvice.pl/en.
This app use T3 stack. (NextJS, Prisma, Tailwind, tRPC). Back and front fully type saved. Monorepo. Very interesting and quick way of creating full-stack app. And it is very similar to what is need for dashboard for tracking ecosystem build failures.

JavaScript experience

3 years.
I am big fan of Typescript. And I am not that big fun of JS. Particular I do not like dynamic typing.
What I like is modern way of working with array. And especially spread operator.

Node.js experience

1.5 years
I have pasted nodeJS courses. And woking with it for the begging as part on NextJS, but then as separate app creating.
I have minor experience with NestJS as well.
Can write server on my own with NestJS, express.

C/Fortran experience

Now previous experience

Interest in stdlib

I have not used stdlib before.
Nevertheless I am a big fun of math and it is cool that you have created such a library. As the will be opportunity to use it, I will do with great pleasure.

Version control

Yes

Contributions to stdlib

stdlib-js/stdlib#1773
It is still open, but only some Lint issues have to be fixed

Goals

I can suggest to use T3 stack (NextJS, TypeScript, Tailwind, tRPC).
As for me for now it is the easiest and fastest way of creating not big full-stack app. The solution is rather new and at the same time stable enough to work with.
Front will be like React based (as NextJS is a framework creating on top of React. We can chose between 13 and 14 version. I suggest 13 as more stable)
Backend - nodejs wich is part of NextJS. To work with database I suggest Prisma. (As I see the number of tables to query in not that big)
The cons of using NextJS it will send some working HTML even if JS will be disabled in browser. Which could not been achieved using vanilla React

Why this project?

I like that it will be greenfield project and we can test there modern frontend approach.

Qualifications

I have created one project exactly with T3 stack. (https://app.niceadvice.pl/en)
I work with NextJS for more than 3 years, as well as TypeScript, Tailwind, React. Less with NodeJs

Prior art

There is a link to already existing project in ideas (https://npm.github.io/statusboard/)

Commitment

I expect to contribute up to 30 hr/week during GSoC and up to 4 hr/week before and after

Schedule

Assuming a 12 week schedule,

• Community Bonding Period:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 1:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 2:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 3:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 4:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 5:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 6: (midterm)

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 7:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 8:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 9:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 10:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 11:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Week 12:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

• Final Week:

working days - up to 4 hr/day
weekends - up to 8 hr/day
~30 hr/day

Notes:

• The community bonding period is a 3 week period built into GSoC to help you get to know the project community and participate in project discussion. This is an opportunity for you to setup your local development environment, learn how the project's source control works, refine your project plan, read any necessary documentation, and otherwise prepare to execute on your project project proposal.
• Usually, even week 1 deliverables include some code.
• By week 6, you need enough done at this point for your mentor to evaluate your progress and pass you. Usually, you want to be a bit more than halfway done.
• By week 11, you may want to "code freeze" and focus on completing any tests and/or documentation.
• During the final week, you'll be submitting your project.

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.
• 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.