Release 0.4 Progress I & II : Telescope Migration

-
So since 2 weeks ago, we've been tasked to start working on our final release 0.4 assignment which is to make a real meaningful contribution, bigger than our previous releases, to any repo of choice. So the first week was generally spent conceptualizing and searching for a repo of choice, while the second week was to start working on it. Next week we are expected to make our finishing touches to the release. The requirements of the release are pretty ambiguous, since our prof mentioned it can vary from to contributing to a number of bug fixes, or a a large feature addition, but the main point is to really dive deep into a repo to understand and help in pushing the program/app forward.

Last week I dove into GitHub explore to look for repos that I may contribute to, and I have to say, it was much easier back in October when people were generally welcoming and looking for open source contributions from a variety of programmers. Now, though a large number of issues still exist in the whole of GitHub, it was quite tough to find one that would meet the level of skill and requirement to meet the assignment for myself. I was eyeing a repo (a VST/Virtual Instrument program for music producing) that I was interested to work on, but it seemed like a lot of technology to learn with the timeframe given. Therefore I'll set that goal aside for my free time and work on something else for the meanwhile.

I ended up deciding on working on telescope again, for a few number of reasons. I was already quite familiar with the frameworks/technologies that built it, which means it'll be easier for me to make a significant contribution (e.g. feature contribution, multiple bug fixing, etc.) Secondly, I've had a lot of great experiences working on it for the past 2 releases and would love to really advance this communal web app forward to make it as great as possible. Finally, we're in the process of migrating the front end to a different framework, so this is a great opportunity to contribute to a such a large task/milestone for the project and I'm really excited to help out as much as I can.




So my task as of now is to migrate the back to top button component, but that's not all I'm planning to contribute to, after I successfully done that, I'll probably search for another component and help out some more. I want to progress the migration process forward as much I can and really put some effort into bestowing the best contribution I can give.

Thanks for reading


Comments

Post a Comment

Popular posts from this blog

HacktoberFest Entry No.2

-
Image
So around last week I found a great github repo of a chrome extension that previews contents of a webpage when you hover over a link. I stumbled upon it after a suggestion from my professor about taking a look at chrome extensions for a possible repo to contribute to. I'm glad I did because this was a chrome extension that was interesting, seemed practical and had a maintainer who was keen on receiving contributions to better his program. The extension is called Survol First I had to install it and test it out first, can't just contribute to a repo meaninglessly just to force a pr. I tested the extension and liked the functionality, it was useful and is well designed. Makes it all the more exciting for me to try and contribute to it. So I read the docs and learned how the extension worked. It uses a javascript file to inject html elements through the dom and uses mousemove event to detect anchor links to request information of a page, and positions and fills the div with conten...
Read more

Lab 1 : Our First Open Source Contributions

-
So for Lab 1 our tasks were fairly simple. Find a partner to review a repo on and make contributions, no matter the scale, to their code. Be it a suggestion for their code, reporting an issue, or even fixing up small details in their readme. So through slack I partnered up with one of my coursemates  Niaz Much like me, he wrote his code in nodejs, so it was perfect since I can go through his code easier through my understanding of node. His code, though written in the same language, differed from mine a lot. For one, he didn't use yargs so he had to process the arguments manually, and secondly he didn't use fetch and opted for a module called linkinator. No problem, in fact it's an opportunity for me to understand the logic and components that he used. I forked a copy of the repo, cloned it and tested it out for myself. The code worked perfectly as intended and processed urls well. Functionally, I couldn't find find anything in the code I could identify as a flaw or imp...
Read more

Hack.... vemberfest.. PR No. 3

-
Image
OK so this is pretty long overdue (sorry Prof!) And I still have one more pull request to go and that's on me yes. BUT, this week I spent working (or should I say learning) on our course's aggregated blog website which coincidentally, our prof is making us work on this week for the lab, so I guess I got a good head start going on.  So I took on an issue that seemed pretty straight forward in the repo. It was to change the functionality of the search bar when filtered by author. Seemed pretty straightforward enough, so I went ahead, forked the repo and cloned it on my computer. Now the reading begins, the lengthy process of coding. And the fact that this was a whole website coupled with different technologies that I'm not familiar with only made it waaayyy longer, which maybe is a sign that I should have started working on this much much earlier. But that's what happens when your time management skills is hot garbage. Anyways, I spent the next few days learning about eac...
Read more