Hi Harsh, brief answers: - in the interest of fairness of all applicants, we can not have "private" exchanges with any of them; everything will be on this mailing list in the open for everyone to see and learn from. This is very much the spirit of Open Source. Feel free to share whatever designs and proposals you come up with and we can all comment on them and discuss them. 1. on the UI framework: as we have discussed, nothing has been decided and we will carefully review any proposal -- as long as it uses only Open Source components, obviously. Therefore, NextJS (or ReactJS) would definitely be a valid alternative. 2. CSS frameworks: once again, no strong preferences for anything. 3. users of the app will be... people who would like to get information on different packages. They will be, for the majority of cases, users of the specific Linux distributions who would like to gain some insight in the components. I have sent a previous reply to this list describing some of the information that might be presented. 4. an "admin panel" falls in the "nice-to-have, very low priority" category for this project. I cannot easily think of any functionality it will provide. 5. no, there will be no information scrapping from random repositories. This is about information on packages available in Linux distributions, so I expect the information will be coming from the distributions themselves. An extension would be to handle more package locations, but it is definitely low priority -- and I think it will be handled almost automatically, since all the package locations are structured the same. 6. this is a textbook example of well-structured information, readily convertible to relational tables. As such, SQL is the way to go and any other approach would be inferior. Please note that, once again, no specific database software has been prescribed and any SQL solution can be proposed and will be considered (e.g. SQLite, PostgreSQL, MariaDB, etc.). In general, always keep in mind that we are looking for a simple solution to a (well-defined) rather simple problem -- any unwarranted introduction of complexity is a disadvantage in a proposal. Thanks for your questions, On Sat, Mar 13, 2021, at 18:23, Harsh Bardhan wrote: > Hello Sir, > > Thanks for having me here! > > I am really obliged to have your reply and support from your side and I > hope to capitalize on this opportunity. I completely agree with your > point on being fair with all the participants, so I would be using this > thread for all communication and discussions. > > However, I would like to know if I can share *proprietary* and > *intellectual information *like *Rough Proposals, UI/UX Wireframes *and > *Architectural Diagrams *through Google Drive, with the access shared > only to you. The primary reason why I am requesting this, is because > some of these would form part of my *Strategic Analysis *and > *Information Architecture*, which should be as unique as possible. > Please let me know if this can be worked out this way, provided all our > discussions and brainstorming would be available in public. I would be > highly obliged if you can grant me this request. > > Coming to the proposal part, I have started working on the *Index Page > UI/UX Design *and the *Server-Side Architecture flow. *It is my first > time doing both, on a professional scale so I would appreciate any > feedback on both of them, once they are ready to share. Some of the > important inspirations were taken from popular package managers like > *PyPi, NPM *and *Crate.io*, and I am combining their design > philosophies to come up to a basic workflow. > > By the next week, I would be able to present you the *User Stories, > UI/UX Wireframes *and *Server Architecture *on my own bidding. All of > these would form a part of my Strategic Analysis and Information > Architecture work prior to my proposal. For this point, I have a few > questions, which I hope you can address that would make things easier > for me to understand: > > 1. Since we have decided to use ReactJS, will we be using the standard > *create-react-app *or using a proprietary React-based framework like > NextJS ? > > 2. Shall I study about the various CSS Frameworks that we can use with > the same? I have particular hands-on experience with Material UI and > React Bootstrap but would like to know if we have a strong preference > for something else. > > 3. Who are the users for this project? This question is the most > essential for my understanding because we cannot jump into the UI > without understanding what the users/clients need. I would be obliged > if we can define the user base of this project and how exactly would > someone be using it. > > 4. Do we need an Admin Panel for this Web Application? An Admin Panel > would be something that would allow us to manage our database > altogether and present the necessary information to the user. My > understanding requires that we need an admin panel to overall regulate > the platform, where everything on the user side is read-only. > > 5. Would we be scrapping packages from Github, Gitlab or similar Git > providers? I overall want to understand how we will collect the data > for all of these packages. It can be either done manually through the > admin panel or we can build an automation workflow that would update > the database as new packages are discovered. I would like to have more > clarity on this. > > 6. My last question: Are we flexible with our Database? I have a > personal preference for NoSQL Databases for our scalability needs so > can we use a NoSQL Database like MongoDB for our case. Or otherwise if > we are sticking to MySQL, can we use Amazon RDS for our deployment > needs. > > I would love to gain a perspective on my understanding so far and would > like to know more about my questions. I would be looking forward > towards a positive response from the Mentors. > > Yours Sincerely, > Harsh Bardhan Mishra > > On Fri, Mar 12, 2021 at 4:42 PM Alexios Zavras <zvr+eellak [ at ] zvr [ dot ] gr > <mailto:zvr%2Beellak [ at ] zvr [ dot ] gr>> wrote: > > Hi Harsh -- thanks for your interest in the project. > > > > You've found the right place for reaching out and discussing; > > it is this list. Once we move to further steps of the GSoC program > > and concrete work is under way, there will be more focused > > ways of communicating for a single project. > > > > As the project description says, this is a new project > > so we are completely open to any framework for the front end, > > for example -- and your proposal of ReactJS is totally fine. > > > > You are correct that some of the work -- at least the thinking and designing part -- > > should be done before the start of the official coding period. > > It will also help you formulate a better proposal. > > > > I m here and I can try to answer any specific questions. > > In order to be fair to all applicants, any communication before the selection > > will be done in the open, on this list. > > > > Greta to have you on board! > > > > On Wed, Mar 10, 2021, at 10:00, Harsh Bardhan wrote: > > > Respected Mentors and Maintainers, > > > > > > With due respect, I'm Harsh Bardhan Mishra, a Junior Year Student at > > > Sathyabama Institute of Science and Technology, Chennai, India. I am > > > currently majoring in Computer Science and Engineering, and I would > > > like to reach out to you on the prospects of working on the > > > *PackageInfo WebApp* through the Google Summer of Code 2021. > > > > > > I came across the project through the Google Summer of Code '2021 Ideas > > > Page listed here > > > <https://ellak.gr/wiki/index.php?title=Google_Summer_of_Code_2021_proposed_ideas#Brief_Explanation>. I was surprised at the ingenuity of projects, which I can work on during my Summer and even beyond. With an avid interest in Full Stack Web Development and DevOps, I would like to work on PackageInfo Web App under the guidance of *Alexios Zavras. * > > > > > > Previously I have worked as a Software Engineer Intern at Qxf2 and an > > > Explorer Fellow at Major League Hacking. Given the Project Idea, I > > > would like to work on this Project and I have explored some of the > > > technology stacks that can be used for the same: > > > > > > * *Frontend Framework/Library: *ReactJS (Professional-Level > > > Experience) > > > * *Server-Side Framework: *Flask/FastAPI (Professional-Level > > > Experience) > > > * *Database: *MySQL (Intermediate-Level Experience) > > > * *DevOps: *Docker, Github Actions > > > As of now, I would like to break the whole ideation process into these > > > parts: > > > * *Strategic Analysis: *To brainstorm on the specifics that we are > > > looking for in the Web Components. > > > * *Information Architecture:* Planning on how accessible the > > > information should be to the Users > > > * *Wireframing:* Using a prototyping tool (Adobe XD/Figma) to come up > > > with simple wireframes and communicate the overall idea and aesthetics > > > of the UI > > > * *Technical System Design: *Decide the Tech Stack, workflow and > > > integration > > > While this ideation process can be done when the Coding Period would > > > officially start, I would like to complete as much as possible during > > > the proposal process, so that I can get cracking on the project really > > > fast. > > > > > > I would love to gain a perspective on my understanding so far and would > > > like to know what we can go ahead with next. I would be looking forward > > > towards a positive response from the Mentors. > > > > > > Yours Sincerely, > > > Harsh Bardhan Mishra > > > > > > ---- > > > Λαμβάνετε αυτό το μήνυμα απο την λίστα: Λίστα αλληλογραφίας και > > > συζητήσεων που απευθύνεται σε φοιτητές developers \& mentors έργων του > > > Google Summer of Code - A discussion list for student developers and > > > mentors of Google Summer of Code projects., > > > https://lists.ellak.gr/gsoc-developers/listinfo.html > > > Μπορείτε να απεγγραφείτε από τη λίστα στέλνοντας κενό μήνυμα ηλ. > > > ταχυδρομείου στη διεύθυνση <gsoc-developers+unsubscribe [ at ] ellak [ dot ] gr <mailto:gsoc-developers%2Bunsubscribe [ at ] ellak [ dot ] gr>>. > > > > > > > -- > > -- zvr - -- -- zvr -
---- Λαμβάνετε αυτό το μήνυμα απο την λίστα: Λίστα αλληλογραφίας και συζητήσεων που απευθύνεται σε φοιτητές developers \& mentors έργων του Google Summer of Code - A discussion list for student developers and mentors of Google Summer of Code projects., https://lists.ellak.gr/gsoc-developers/listinfo.html Μπορείτε να απεγγραφείτε από τη λίστα στέλνοντας κενό μήνυμα ηλ. ταχυδρομείου στη διεύθυνση <gsoc-developers+unsubscribe [ at ] ellak [ dot ] gr>.