Skip to main content

Act 1 Scene 1 Exeunt

Act 1 Scene 1

This year, I was able to dabble in open-source for the first time. It was a dream-come-true: a dream I long thought impossible to attain for my lack of understanding in programming language. How far have I changed since: not only is some of my code part of a program used by others, I am also hosting and developing a program as a part of the open-source community. Small, but a community.
This all started thanks to DPS909 class.

Act 1 Scene 2

The Act is still on. I am just getting warmed up. What will scene 2 have for me in store? Only time will tell. For now, I am going to enjoy cultivating a community while also belonging to many others, finding my way through, contributing as I am able. Perhaps that will be my scene 2. It will be beautifully ugly, and I will love every moment of it.

To my audience, even if imaginary

If you are reading this and thinking there is nothing you can do to make a meaningful contribution to a program that you love, I am glad to say you are dead wrong. Take a look at it. There's probably something lacking, or something wanting. Ask somebody. Ask me. Ask anyone. We all need a helping hand.

Exeunt

This concludes my submission to DPS909. I will continue the path I was set on, nonetheless. Perhaps I will be joined by my colleagues who would take the same course and explore the same community I dabbled in. I would like that. I would look forward to that.
Labels:

Comments

Post a Comment

Popular posts from this blog

Creating a patch for GNU GCC using Git

Overview and Target Audience The GNU GCC project followed a blend of a traditional method with contemporary git tools when it comes to contributing code, making the experience unique from some other, git-based projects. This blog post will explore different aspects of the process, helpful commands, and various scripts that would make the experience more pleasent for new contributors. While this blog aims to help new contributors get acustomed to the GNU GCC code culture and make contributing easier, it must be stressed that this is not in any way in-depth exploration of the process. This should help you put your first foot forward; the community will help you take the rest of the steps from that point on. This post also assumes the user is in a POSIX environment (e.g. Linux, FreeBSD). Git and GNU As stated in this phoronix post , GNU GCC made a full transition to git early 2020. As of this writing, the community seems to be adjusting to the new tools. GNU GCC hosts its own git serve...
Post a Comment
Read more

Debugging with GCC: GIMPLE

GCC and GIMPLE One of the very first thing GCC asks the GSoC applicants to do, even before writing the application, is to try various different debugging techniques using GCC. I was personally familiar with the basic, compile-with-g-flag-and-use-gdb method. Turns out, there's more: GIMPLE. A Simple but Non-trivial Program Problem Description The instruction asks to compile a simple but non-trivial program with some flags that generates debugging information: -O3 -S -fdump-tree-all -fdump-ipa-all -fdump-rtl-all . Because I was keep reading on ways to debug GCC just prior to the statement, I immediately thought "GCC" and tried make -j8 CXXFLAGS="-O3 -S -fdump-tree-all -fdump-ipa-all -fdump-rtl-all" . This was a mistake: turns out, GCC can't be compiled with those flags. Thankfully, GCC developers have a very active IRC channel for me to signal SOS. Resolution jakub and segher were quick to respond to my call for help. jakub: it isn't meant that y...
1 comment
Read more

Project: Boost-free goblins

The headache: Boost Don't take me wrongly: Boost library is a powerful set of tools for bleeding-edge technology. Much of it gets absorbed into the C++ Standard Libraries. The problem lies in our project being inactive for 7 years, which means it is relying on a library that is 7 years behind. Installing such an old library is a chore, and securing a pre-built package is problematic at best. The project is even incompatible with the later versions of Boost. It may have once given the original developers a powerful technology to propel their project in the past, but now we are stuck with clock stopped at 2011. Along with libtcod being stuck also in 2012, dealing with Boost is critical to bringing the project up-to-date. Options There are several ways to address the issue. Option 1 : Upgrade We can read each related source code, research how Boost has modified the relevant function calls, and either fix the expected return type or required input type, This may lead to mor...
Post a Comment
Read more