SPO600 Lab 1

 In the first lab of SPO600 course, my work is to explore two open-source software projects. As an Android user, who like to root my phone (I have a Pixel 6, and I saw you are having one too), I am using several applications that take advantage of root permissions. One of those apps is Adaway – an application that blocks ads system-wide.

Source: https://adaway.org/


Looking at its source code on Github, I found the software is distributed under GNU GENERAL PUBLIC LICENSE - Version 3. In short, PGLv3 is a copyleft license, which requires copies or modifications of the source must also be released under the same license.

Everyone can make contributions to the project by reporting bugs, suggesting enhancements, or translating to languages. For example, look at the most commented pull request – pull request number 784:



Source: https://github.com/AdAway/AdAway/pull


Source: https://github.com/AdAway/AdAway/pull/784

There were 21 commits and months needed in total to resolve the issue. There were five people involved in the process. The author of the project was the one who opened the case, and then people joined the conversation to contribute their efforts to help the author fixes the bugs. Most of the commits were done by the author in the branch he created before merging to the master branch.

 

Another open-source project I am currently using is GrapheneOS – a customer Android version


Source: https://github.com/GrapheneOS

In order to find bugs in the project, the developers of GrapheneOS created an independent repository just for issue tracking. The users can report a problem they encounter during daily use by opening a new issue ticket. For instance, these are examples of active issues that need to be fixed:

Source: https://github.com/GrapheneOS/os-issue-tracker

People can join the threads and make suggestions, comments, and solutions:

Source: https://github.com/GrapheneOS/os-issue-tracker/issues/159

If an issue is fixed, the issue ticket will be closed:

Source: https://github.com/GrapheneOS/os-issue-tracker/issues?q=is%3Aissue+is%3Aclosed

Before you want to make a contribution to an open-source project, you should check the guidelines for the project. The guidelines will tell you what you should know in advance to start contributing. For example, Adway author suggests that you should discover the software’s structure and how to build it.


Source: https://github.com/AdAway/AdAway/blob/31d0b78b9e87de13727b758b42438ab14ff899cb/CONTRIBUTING.md

Additionally, there are also style guides you have to know if you make a commitment to Github to avoid style conflicts with different developers in the projects. In the case of GrapheneOS, the author recommends the contributors to visit a website, which includes all the instructions and rules for the project (https://opensource.guide).





Comments

Post a Comment

Popular posts from this blog

SPO600 Lab 2

Image
 Lab 2, where I have a given 6502 assembly code: lda #$00 ; set a pointer at $40 to point to $0200 sta $40 lda #$02 sta $41 lda #$07 ; colour number ldy #$00 ; set index to 0 loop: sta ($40),y ; set pixel at the address (pointer)+Y iny ; increment index bne loop ; continue until done the page inc $41 ; increment the page ldx $41 ; get the current page number cpx #$06 ; compare with 6 bne loop ; continue until done all pages My job is to play around with the code, calculate the performance of the given code, and try to optimize the code to have a better performance. First, starting to run the code on  http://6502.cdot.systems/  - a website that stimulates a 6502 emulator, I got a result of a yellow screen, which consists of 4 pages.  Let's look at the performance by calculating the number of cycles and cycle count. We will do this on Microsoft Excel to have a clear perspective. After doing some calculations on Excel, I got a result of 0.012 seconds. How did I fin
Read more

SPO600 Project Stage 3

Image
 We finally reached the final stage of the project!   In the last stage, I will perform a comparison of how jpeg-compressor’s performance differs in different architecture platforms. There are SSE (Intel) version, SVE2 (ARM) version, and the original source without any optimizations. The mutual system the three programs will run on is an X86_64 machine (portugal.cdot.systems)   Let’s start off with the original one. First, we need to disable SSE in jpgd.cpp by setting JPGD_USE_SSE2 to 0 because it is enabled by default. Then we config Cmake to build our program. After running the program with an image. Here is the result: Next, SSE is enabled: We can clearly see the decompress time is hugely different between 2 versions: 908 ms in non-optimized vs 830 ms in SSE optimized. Note that SSE optimization is only in decompress function, and there is no optimization in the encoder file (jpge.cpp). SSE has shown us a jump in performance compared to the original code without opti
Read more