Open Source

In this post I will continue to describe what I have done so far to complete my issue . This issue try to conquer problem of integrating React Experimental channel into the Gutenberg project. Steps that I have to do: 1. First I read through all the documentation about Experimental channel and what the ways to implemented. Experimental channel can only be implement on the projects that use React as external library. The reason is because if the project uses React for GUI and there is any bugs or features that can fail it can botched the front end. Gutenberg uses React as external library so that is why they try to see how Experimental will work on Gutenberg and on the other side to test new features. 2. Currently Gutenberg uses React 16.9.0. So after reading through the all documentation I updated version of the React on Gutenberg. Because Gutenberg uses React as an external library there are some changes to be done in the PHP. So here is my files with changes: Af...

This is the first part of release 0.5 and in this post I will talk about steps that I will take in order to solve issue #18216  in Gutenberg Project .  What is issue about: Find a way to integrate React Prerelease channels into WordPress/Gutenberg . React Prerelease channels allows Projects that are not using React as a user-facing application test features that are might will be available in the next releases. By integrating React Prerelease channels into Project community will help in improving React while testing out new features. What needs to be done in Gutenberg : 1. Install Next or Experimental channels  (as I'm waiting for respond which channel I have to integrate Next or Experimental I will talk for now only about Next channel ) inside of the project  In package.json  change version of react and react-dom to  "next" so package.json will look this way: 2. Set up CircleCI or Travis CI in order to run occasionally tests. ...

This is the end. The end of not just release 0.4 but also the end of semester. Many things were planned but as usual not everything is done. I completed 2 issues( external , internal ) and 2 PR ( external , internal ) as were required and still had some extra time and I wanted to keep working on other issues. Indeed, when I reach this last week before exam I realize how time consuming extra work could be. Anyway, I did my best to accomplish at least something. 1. While I was working on my external issue  I have learn and review few things from C++. My goal in this issue was to increase performance of the compiler. In this snipped of code calling _STD invoke(_STD declval<_Types>()...) is very expensive in the meaning of performance. That is because template function invoke() is implemented by calling static function call(). So my task was to use _Invoke::Call(), and this will increase performance. 2. In my internal issue , I faced some problems. I was not able to run w...

I'm writing this post on November 29th. This is mean that the due date for Release 0.4 is due in one week. This is also mean that semester is almost over. This time of the semester usually gets pretty intense. (Projects, Assignments, Releases, etc..).  This week unfortunately I didn't have chance to spend a lot of time on the school project Telescope  or any external project but I'm very eager to spend most of my time for my external and internal projects in the next week. My external issue is fixing issue in Microsoft/STL . In this issue I will have to work on enhancement that will make STL work about 25% faster. This should happend when I will reduce the number of calls  _STD invoke(_STD declval<_Types>()...). As I mention in previous post   I really enjoy to work with Microsoft/STL  because they are very helpful in solving problems and they are very fast in the responding. My internal project. Here I will work on the issue ...

It's been one week since Release 0.4 start and I was able to manage some work in open source. For my external project I picked as always Microsoft/STL . This time I was working on correcting return type as per documentation of STL. Why I always pick issues from Microsoft/STL? This is because the way they explain the bug. It is very well define, there is description how to reproduce the bug and files that are crashing or need updates. Another reason is that there are only 20 contributors to this project and I'm 8th by the amount of contributing (even though it is only 31 line of code). This contributors are very quick to respond if I need any help or to review my PR. My goal for external project is to contribute to Wordpress/Gutenberg . I find it challenging because it is much harder to get in contact with some members of this project and when the issue is exist its not always very well describe. This can take quite a bit of time to solve the bug. As per my internal pr...

In the previous blog I was describing issues that I was planning to work on this week. Indeed I saw many different issues that I would like to contribute on. In the internal project Telescope I was working on Issue that suppose to update Stylelint in order to check only .css files. After few hours of reading through and working on this issue I send my PR . I was also able to create a new issue so I can keep working on this project and contributing to it. As I said before, to work on the Telescope is new experience for me and I hope with professors supervising me and my classmates will be able to create a nice project. For my external issue I was thinking to work on Wordpress/Gutenberg   project but in the end I change my mind and decide contribute to Microsoft/STL . There are many issues that has to be fixed on this project and looks like not too many people have time to help this project solve issue. This week I picked this issue . I'm very glad that I was a...

Release 0.3 is another step that bring me closer to the end of the semester. It is a challenge for me. This task require to work on 2 bugs one is internal and one external. At the first glance seems like nothing new than any other release, but the most difficult  is that we as a group of students have to create piece of software that will be replacement for CDOT Wiki . Before I begin to write what have I done so far I want to share what I feel about this release. At first project Telescope  make me feel like I'm in the tunnel with out a light and trying to find a way to get out. What I have done so far. First I try to to file issue, but a moment after I got 2 comments that saying that someone already file that issue, than I realize that my strategy is wrong and before filing any issue I should read through and see what else has to be done. Well, that is where problem arise because I don't know which steps should be taken and how to accomplish them to reach final produc...