"Good first issue". Finale.

Status: completion

    Four pull request have been submitted and work seems to be done, so let's recall what we've been working on:
1) AVMf. I believe I should give more detailed 'inside' to this and next projects (MochaJS), since at the time of writing respective post the work wasn't progressing at desired tempo. 

    

    The community welcomed me - a newcomer - nicely and with understanding. The issue was to add tool's logo to README.md and a brief list of features that the tool is capable of. I did my research and found the most recent article that was dating October 2018, which contains a good detailed explanation of the possibilities of AVMf. All I needed to do is to read it and boil it down to the list, which would give an idea of what the tool is for. The community gave me green light on using it as a source and so I did.
    The logo has been added, the list has been created, PR submitted, tests passed, but there hasn't been any reply as of today yet.

Link to the issue.
Link to the PR.

2) MochaJS. The issue - adding a logo to the community's site, not README.md as I though before. This very fact forced me to set up the environment for the contributions (they use Eleventy as a static site generator and self-explanatory markdown-magic). I found out the the site (index.html) getch generated from index.md, which loads 3 different '.md' components to construct its content. So I thought 'heck, why not?' and added a new component, which would dynamically load the requested logo on the site upon build.

index.md


    In the highlighted area you can notice the file 'honorableMentions.md'. It is the one that I created to be loaded with requested logo in it. Let's take a look at the content:

honorableMentions.md


    Here, I load the pic file from an 'assets' folder. Even though there is only one file, I do it in a loop, since there's a possibility that the community decides to mention other individuals/companies, so the functionality is already there, they will just need to slightly modify it.
    But there appeared a problem: another person came in two days after I had submitted my PR for review, and sent his PR to fix the very same issue. I mean, I don't mind, but I highly doubt he didn't see that other people already were working on that. Not nice. 
    PR has been submitted, no response yet.

Link to the issue.
Link to the PR.

3) penguinV. There haven't been any updates since the moment after the issue was closed. The detailed report on it and my frustration can be found in my post here.
    As a side-note, I'd like to say that I am seriously considering contributing to this project because of the following reasons: the community is welcoming and helpful, the tool uses something that I would like to research about (CUDA and OpenCL).

Link to the issue.
Link to the PR.

4) schemaanalytic. No update as well. The PR's been submitted, but no reply has been gotten yet. I will follow up with the community, asking if there's anything else that they would like to fix in the opened issue. Some of the details for this fix can be found in my previous post.

Link to the issue.
Link to the PR.

Comments

Post a Comment

Popular posts from this blog

Two Different Frames of Same VidioCapture

Image
OpenCV Challenge     I believe, this bug is going to be one of the most challenging I have worked on. Not because of complexity of the work, not because of the scale involved, but because the part of the code is brand new to me. STDMETHODIMP SourceReaderCB::OnReadSample(HRESULT hrStatus, DWORD dwStreamIndex, DWORD dwStreamFlags, LONGLONG llTimestamp, IMFSample *pSample) {     CV_UNUSED(llTimestamp);     HRESULT hr = 0;     cv::AutoLock lock(m_mutex);     if (SUCCEEDED(hrStatus))     {         if (pSample)                     CV_LOG_DEBUG(NULL, "videoio(MSMF): got frame at " << llTimestamp);             IMFSample* prev = m_lastSample.Get();             if (prev)             {                 CV_LOG_DEBUG(NULL, "videoio(MSMF): drop frame (not processed)");             }             m_lastSample = pSample;         }     }     else     {         CV_LOG_WARNING(NULL, "videoio(MSMF): OnReadSample() is called with error status: "
Read more

Node.js: fs.open()

    Today, I would like to take a look at one of the widely used functions of Node.js ' fs  library -  open() , and its synchronous version -  openSync() .     The function's purpose is to open a file, specified by a path (the first mandatory parameter of the function). The code of the function is following ( source ): function open(path, flags, mode, callback) {   path = toPathIfFileURL(path);   validatePath(path);   if (arguments.length < 3) {     callback = flags;     flags = 'r';     mode = 0o666;   } else if (typeof mode === 'function') {     callback = mode;     mode = 0o666;   }   const flagsNumber = stringToFlags(flags);   if (arguments.length >= 4) {     mode = validateMode(mode, 'mode', 0o666);   }   callback = makeCallback(callback);   const req = new FSReqCallback();   req.oncomplete = callback;   binding.open(pathModule.toNamespacedPath(path),                flagsNumber,                mode,                re
Read more

Good friend penguinV

Two birds with one "Pull"     As previously said, I was working on OpenCV bug (you can find some details here ). The bug was not something to spend more than 2-3 days on, but the problem that was there - compilation time. OpenCV project is a set of C/C++ files (and CUDA ;-) ), which is supposed to be compiled with "cmake" to generate library(ies), containing compiled code. Everything sounded pretty decent, until the moment when I realized that I would need to compile the entire folder with a bit more than a lot of different modules of different shapes and colours to make any changes to the existing code and test it. And just because the modules with reference one-another, creating a web of dependencies, I would need to compile the whole thing every time, not some of the modules independently ("video" module, "java", "core" etc.). It'd be okay if not the fact that every compilation would take 20 minutes. Not nice. So, I switched
Read more