Research Study: MuseScore

As part of the learning curve of Open Source Development, it is good to browse and study further existing projects for inspiration, information, ideas and more. After some research on my part, I have found an Open Source project which interests me and I will share it with you using this post.

 MuseScore

 The name of the project is as shown in the post title; MuseScore. It is an Open Source project allowing professional music notation through its software developed in C++. The software itself offers many features, but all revolve around creating and playing sheet music from a wide variety of musical instruments. 

 The MuseScore project started around 2008, and quickly became one of the best platforms that allowed powerful and easy-to-use music notation to create high-quality sheet music. You can find more information on this with the following links:

 https://musescore.com/
https://musescore.com/team
https://musescore.com/press

 Technical Information

 Language: English
Open Issues: Currently 13 Active Pull Requests, 0 Active Issues.
Contributors: 114

Comments

Post a Comment

Popular posts from this blog

DPS909 Release 02: My First Open Source Contribution Part 1

Image
Our second Open Source project was to solve a "good-first-bug" in any project that suited our interests. Since I mostly prefer doing Java and/or C++ programming, I looked at many places for opportunities to solve bugs in those languages. Unfortunately, I couldn't find what I was looking for and I settled with solving a JavaScript bug in the Brave laptop-browser project on GitHub. Github Project Repository: https://github.com/brave/browser-laptop Brave Browser regular download: https://www.brave.com/ "Brave is open source, and built by a team of privacy focused, performance oriented pioneers of the web, founded by the inventor of Javascript and co-founder of Mozilla." This blog post will attempt to highlight all the major steps in the development of this project, including finding the bug, solving it, and contributing to the Brave community. To help visualize the timeline of this project, these following questions and answers will illustrate my progress bet
Read more

Fixing a Bug, Adding Tests

In this lab, we were asked to work on the Brave browser, but more specifically to see how it compares to other browsers in certain niche tests. To do this, we studied the testing code for the Brave browser to try to understand it at its base, compared to FireFox and Chrome as examples. Following this analysis, we would find some bugs or odd behaviour that Brave did but other browsers didn't. So our task was to fix those behaviours, and add tests to it before submitting a pull request to our local branches. Here's some insight on how it went; P.S.: I worked with a classmate on this lab, his name is Owen Mak 1- Which URL string cases did you have trouble with in Brave vs. other browsers? " https://www.google.ca/search?q=dog cat " and " file:///Users/humphd/repos/browser-laptop/dog cat.txt " mainly. We used both these cases to test since they both resulted in different behaviour when comparing Brave to Chrome or FireFox. In the first case, Chrome/FireFo
Read more

Running Test Suites and playing with ECMA Standards

In this lab, we looked into language standards, as well as testing test suites for the first time. Additionally, simple tests were contributed, with the possibility of posting as a contribution if need be. Here are some questions that cover the work that was done; 1-  When you run the tests, do all the tests pass or do any of them fail for you? After following the instructions and forking over the repo from https://github.com/bterlson/test262-harness#test262-harness, the "test262-harness test/**/*.js" command let me find out which tests would pass and fail. After a short compilation of the tests, I've found out that out of 205 tests, 199 passed and 6 failed. The failed tests concerned 'locale' related errors for the most part. 2- Examining existent test ' https://github.com/tc39/test262/blob/master/test/built-ins/String/prototype/toUpperCase/S15.5.4.18_A2_T1.js' and providing observations The sets of tests ran by this code include some defined conventi
Read more