<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ria Gupta on Medium]]></title>
        <description><![CDATA[Stories by Ria Gupta on Medium]]></description>
        <link>https://medium.com/@guptaria?source=rss-d8ba8aa054d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6EkSvWxCp9ckZueW.jpg</url>
            <title>Stories by Ria Gupta on Medium</title>
            <link>https://medium.com/@guptaria?source=rss-d8ba8aa054d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:07:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@guptaria/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Week 11: Coding Period 3]]></title>
            <link>https://medium.com/@guptaria/week-11-coding-period-3-7ac413f798c9?source=rss-d8ba8aa054d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ac413f798c9</guid>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[social-currency]]></category>
            <category><![CDATA[future-prospects]]></category>
            <dc:creator><![CDATA[Ria Gupta]]></dc:creator>
            <pubDate>Mon, 24 Aug 2020 03:24:30 GMT</pubDate>
            <atom:updated>2020-08-24T03:24:30.817Z</atom:updated>
            <content:encoded><![CDATA[<h4>Consolidating Code files</h4><p>Last week, we realised the importance of having a “Role” specified for each record while Tagging. It helps in demarcating conversations between Core contributors, Regular contributors and Casual Contributors. There is an “onion” study in GrimoireLab, which is used for extracting this information. This week, I executed the study on the enriched index of SCMS enrichers. Onion Study by default creates a new index and noticed that simple binary operations would not be sufficient to have both the indexes(enriched, onion index) combined. For this reason, We have added this task as a task for a future iteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Olhj6Aj-lInwu-6_" /><figcaption><a href="https://www.agiledrop.com/">https://www.agiledrop.com</a></figcaption></figure><p>I had a meeting on 21 August, the minutes of the meeting are <a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-08-21-coding-prd-3-3.txt">here</a>. We discussed the future aspects of the project and its maintenance. We discussed the format of the final report, and we’ll be having CHAOSS case study added in the report in the form of an interview. I’ll also be writing a blog for SC.O summarising the weekly work done. The report would essentially comprise of the implementation steps, a demo video, and all weekly work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*HUsQSnAl3KrZGWBg.jpg" /><figcaption><a href="https://www.cio.com/">https://www.cio.com/</a></figcaption></figure><p>Elizabeth aptly pointed out the future limitation of Google Sheet, and we would have to move all tagged records from the GSheet to a database and continue tagging the new data. Additionally, we also mulled the possibility of having an end-to-end pipeline for SCMS and setting it to get executed each week/month automatically, brewing up all community interactions into the GSheet.</p><p>I have combined the scripts used for implementing SCMS. This week, I’ll be pushing my scripts to the Pull request, and get it merged. I’ll also be sharing the draft of the final report with the mentors, and have it ready to be submitted.</p><p>With the end of this week, begins the last week of Google Summer of Code! Already feeling overwhelmed! 🙌</p><p><em>Thanks for reading!<br>That’s it for this week.😃 Make sure you have a look at the project updates on Github </em><a href="https://github.com/ria18405/GSoC"><em>#ria18405/GSoC</em></a><em>. Pull request: </em><a href="https://github.com/chaoss/grimoirelab-elk/pull/924"><em>#pull/924</em></a><em>. All questions and comments are welcomed! Stay tuned for more weekly updates. 🙌</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ac413f798c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 10: Coding Period 3]]></title>
            <link>https://medium.com/@guptaria/week-10-coding-period-3-b7004e46a676?source=rss-d8ba8aa054d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7004e46a676</guid>
            <category><![CDATA[community-interactions]]></category>
            <category><![CDATA[social-currency]]></category>
            <category><![CDATA[dashboard]]></category>
            <category><![CDATA[inference]]></category>
            <category><![CDATA[community-health]]></category>
            <dc:creator><![CDATA[Ria Gupta]]></dc:creator>
            <pubDate>Sun, 16 Aug 2020 12:01:11 GMT</pubDate>
            <atom:updated>2020-08-16T12:01:11.986Z</atom:updated>
            <content:encoded><![CDATA[<h4>Sneak-peek into the CHAOSS dashboard</h4><p>This week, I converted the 200+ tagged records into a dashboard! From the dashboard, I have made some inferences regarding the community’s health. Some suggestions on how to improve the social currency value were discussed in the meeting, and have tried to include them below pointwise.</p><p>We had a calibration and analysis meeting on 2020–08–14 (<a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-08-14-coding-prd-3-2.txt">minutes of the meeting</a> ), where we discussed everyone&#39;s concern regarding definitions and usage of terms present in the codex for future regular use. Now, we have a fully functional codex, which can be used for tagging weekly data.<br>We also saw some other dashboards, where drilling down into subterms held significant importance. I discussed some naive approaches for drilling down into subcategories, and with limited tweaking of the existing code, it could be possible. For advanced usages, we’ll need to consider friendlier approaches.</p><p>These are a few snapshots of the dashboard for CHAOSS community and have listed some inferences below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YD0Fm6t_Mwv5XzOLWQpI8Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UiAmPgWfIJQ8xrMlIv5Z4A.png" /></figure><blockquote><strong>Analysing Trends and Patterns: Dashboard</strong></blockquote><ol><li>Utility reached its peak in Oct’2019, having a value of 12. At all other times, the value of utility has been around 2–3, expressing an odd utility state. We could infer, that measures should be taken to <strong>make Utility more uniform! 👷</strong></li><li>Transparency has been fairly consistent throughout the last 2 years. (Kudos!) 😌 🎉</li><li>The value of all other social currencies like Trust, Merit, Consistency has been very low throughout, the value is around 1–2 in each month. To uplift the overall social currency, we’ll need to work to increase Trust, Merit and Consistency in the community. One possible way around would be to <strong>convert utility and transparency towards Merit! 👷</strong></li><li>We found 42.86% of emails categorised as Administrative, and only 14% of mails involve community content, which means <strong>Increasing contributor participation is imperative! 👷</strong></li><li>IRC conversations involve more technical support discussions(32%) or interpersonal discussions(owing to it being a chat system)- (24%)</li><li>38% of tweets are about community content and 42% of tweets are about Conferences (owing to the nature of the forum).</li><li>In all platforms, we can see that <strong>+ve weights overweigh -ve weights</strong>, meaning most community discussions are relevant to projects and other people involved. (Kudos!) 😌 🎉</li><li>Also, we see “<strong>Transparency</strong>” as the most popular social currency of the CHAOSS community. 😌 🎉</li></ol><p>In the end, These assessments are recorded from 200 conversations only, as more tags come in, we’ll get more clarity towards the community’s nature. ✨</p><p>It was super fun making inferences through the dashboard, and confirming trends! This entire roller coaster journey is so worth the satisfaction!! ❤️</p><p>A big thanks to <a href="https://medium.com/u/5c1aaa5582d8">Elizabeth Barron</a> for holding up with us, and investing her precious time for understanding the system, giving super valuable inputs, designing the codex and finally tagging the spreadsheet!! 🤗 ❤️</p><p><em>Thanks for reading!<br>That’s it for this week.😃 Make sure you have a look at the project updates on Github </em><a href="https://github.com/ria18405/GSoC"><em>#ria18405/GSoC</em></a><em>. Pull request: </em><a href="https://github.com/chaoss/grimoirelab-elk/pull/924"><em>#pull/924</em></a><em>. All questions and comments are welcomed! Stay tuned for more weekly updates. 🙌</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7004e46a676" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 9: Coding Period 3]]></title>
            <link>https://medium.com/@guptaria/week-9-coding-period-3-1444a048be?source=rss-d8ba8aa054d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1444a048be</guid>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[social-currency]]></category>
            <category><![CDATA[calibration-software]]></category>
            <dc:creator><![CDATA[Ria Gupta]]></dc:creator>
            <pubDate>Sun, 09 Aug 2020 19:38:49 GMT</pubDate>
            <atom:updated>2020-08-09T19:38:49.422Z</atom:updated>
            <content:encoded><![CDATA[<h4>Calibrations and Google Sheets</h4><blockquote>Can&#39;t believe!! Here begins the third phase of Google Summer of Code! ❤️</blockquote><blockquote>This is the second week of the case study with CHAOSS, and we are all so excited and looking forward to making inferences, and analyse the social currency of CHAOSS!! 😬</blockquote><p>In the last meeting, we observed that the size of each mail is huge, and it became very hard to read, understand and tag the mail text. So, This week, I made a function in JavaScript for Google Sheets to clip the mails. Now, the Google Sheets looks much cleaner, as each conversation is clipped to just 3 lines.</p><p>Also, Now we have a 70% completed codex, and more than 150 records have been tagged till now. We are looking forward to having around 200 records tagged, after which I’ll be generating a dashboard for it. Yay!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/0*FLP2rvgB4CV5Au-y.png" /></figure><p>In the meeting on 07-Aug-20 (<a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-08-07-coding-prd-3-1.txt">minutes of the meeting</a>), we <strong>calibrated</strong> in-depth and solidified the codex. Since scoring records on the basis of happiness was becoming a difficult task, as most comments seemed neutral, we decided to continue with a relevance score only. Scoring on the basis of “Relevance” suggests the most relevant comment would be scored as high as +3, and the least relevant comment would get a -3. We mulled over the category “Administrative”, and “Operational”, and then finally decided to consider all actions taken by power leaders as Administrative. All others’ actions are subdivided into categories like Onboarding, Community Content etc.</p><blockquote>Fingers crossed for CHAOSS Dashboard :🤞</blockquote><p><em>Thanks for reading!<br>That’s it for this week.😃 Make sure you have a look at the project updates on Github </em><a href="https://github.com/ria18405/GSoC"><em>#ria18405/GSoC</em></a><em>. Pull request: </em><a href="https://github.com/chaoss/grimoirelab-elk/pull/924"><em>#pull/924</em></a><em>. All questions and comments are welcomed! Stay tuned for more weekly updates. 🙌</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1444a048be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 8: Coding Period 2]]></title>
            <link>https://medium.com/@guptaria/week-8-coding-period-2-6fc59e81bc78?source=rss-d8ba8aa054d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fc59e81bc78</guid>
            <category><![CDATA[metrics-and-analytics]]></category>
            <category><![CDATA[community-interactions]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[social-currency]]></category>
            <dc:creator><![CDATA[Ria Gupta]]></dc:creator>
            <pubDate>Sun, 02 Aug 2020 15:10:09 GMT</pubDate>
            <atom:updated>2020-08-02T15:10:09.833Z</atom:updated>
            <content:encoded><![CDATA[<p>Case Study 1: CHAOSS</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kGtdSJj4M4z3Lh-_" /></figure><p>As written in the previous blog, we are advancing SCMS to the next level, the experimentation. We are planning to undergo two case studies, CHAOSS (Community Health Analytics and Open Source Software) and Mautic Community.</p><blockquote>A case study would mean allowing different communities to use the SCMS to quantitatively analyse community interactions and determine community health holistically.</blockquote><p>We are performing these case studies to have a clear vision of how the meaning and relevance of social currencies evolve for different communities.<br><strong>Case studies hold paramount importance to understand community interaction and assist to tweak SCMS in a way that enhances User Experience. This case study would further result in increasing our knowledge of the significance of SCMS in open source communities.</strong></p><p>This week, we started with setting up the SCMS Google Sheets implementation for the CHAOSS community, considering three interaction channels for now: Mails on the Mailing lists, conversation on IRC, Tweets on Twitter. Since, for GrimoireLab, we found Github comments rather than Tweets, I wrote an SCMS Twitter Enricher, and its tests this week. After extracting all data, I set up the Google Sheet by converting the Elastic Search index into a spreadsheet. We decided to tag around 25 records each of this spreadsheet manually and collaborate with the team to determine concrete definitions of the SCMS currencies.</p><p>We had a collaboration meeting on the regular weekly meeting day, Friday, 31 July 2020. The minutes of the meeting is <a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-07-31-coding-prd-2-4.txt">here</a>. A collaboration meeting comprises of bringing up the most critical comment that we encountered during tagging and explaining the reasoning used to tag it. After some discussion, it leads to defining Social Currencies at a consensus, which helps in solidifying the codex. We saw some spaces where SCMS could enhance its Usability and User Experience and will be working on it in the coming week.</p><p><em>Thanks for reading!<br>That’s it for this week.😃 Make sure you have a look at the project updates on Github </em><a href="https://github.com/ria18405/GSoC"><em>#ria18405/GSoC</em></a><em>. Pull request: </em><a href="https://github.com/chaoss/grimoirelab-elk/pull/924"><em>#pull/924</em></a><em>. All questions and comments are welcomed! Stay tuned for more weekly updates. 🙌</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fc59e81bc78" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 7: Coding Period 2]]></title>
            <link>https://medium.com/@guptaria/week-7-coding-period-2-60ce079802fa?source=rss-d8ba8aa054d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/60ce079802fa</guid>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Ria Gupta]]></dc:creator>
            <pubDate>Sun, 26 Jul 2020 19:44:40 GMT</pubDate>
            <atom:updated>2020-07-26T19:44:40.827Z</atom:updated>
            <content:encoded><![CDATA[<h4>SCMS Documentation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AAXyh0clsUX2HYcS6PqY-A.jpeg" /></figure><p>User-friendly documentation explaining all steps to implement SCMS was essential for other contributors to extend it, and for other communities to incorporate it. Documentation can be found <a href="https://github.com/ria18405/Working-Directory/blob/master/README.md">here</a>.</p><p>As suggested, I made a new git local branch, rebased the original one with the master, and submitted a new PR (<a href="https://github.com/chaoss/grimoirelab-elk/pull/924">#pull/924</a>). This PR does not have the scripts used to implement SCMS, they are being consolidated and being polished, and will be ready soon.</p><p>Manual Tagging for GrimoreLab is also complete, and a script to bring the Tagged Google Spreadsheet into the required form for converting into JSON is also complete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/263/0*ZpaNk60vpFNrU5Uh.jpg" /></figure><p>Now, we move towards the next phase of our project, the <strong>Case Studies! </strong>We will be evaluating two communities and analysing their community interactions via SCMS, <strong>CHAOSS</strong> and <strong>Mautic</strong>! 😬</p><p>I had a meeting with my mentors and the community manager of CHAOSS, Elizabeth on 24 July, the minutes of the meeting are <a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-07-24-coding-prd-2-3.txt">here</a>. We explained the SCMS system to her and decided on the path of the case study for CHAOSS. She suggested that we should consider Twitter as the channel to monitor discussions for SCMS for CHAOSS. This week, I’ll be writing a Twitter Enricher for SCMS in GrimoireLab. After collecting, and converting the required data into a Google Sheet, we will codify the codex and start the tagging procedure! <br>Its gonna be super fun dealing with real community tagged data, I can sense the excitement ahead of time XD</p><p>Thanks for reading!</p><p>That’s it for this week.😃 Make sure you have a look at the project updates on Github <a href="https://github.com/ria18405/GSoC">#ria18405/GSoC</a>. Pull request: <a href="https://github.com/chaoss/grimoirelab-elk/pull/924">#pull/924</a>. All questions and comments are welcomed! Stay tuned for more weekly updates. 🙌 <br><a href="https://www.canva.com/learn/blog-traffic/">[1]</a><a href="https://foresite.com/case-study-preparing-auditor/">[2]</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60ce079802fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 6: Coding Period 2]]></title>
            <link>https://medium.com/@guptaria/week-6-coding-period-2-52bdfbe4cd38?source=rss-d8ba8aa054d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/52bdfbe4cd38</guid>
            <category><![CDATA[unit-testing]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[community-interactions]]></category>
            <dc:creator><![CDATA[Ria Gupta]]></dc:creator>
            <pubDate>Sun, 19 Jul 2020 16:30:14 GMT</pubDate>
            <atom:updated>2020-07-19T16:30:14.617Z</atom:updated>
            <content:encoded><![CDATA[<h4>Unit Tests, CHAOSS community data</h4><p>This week I have written all the unit tests for all enrichers to ensure the enrichers are accurately implemented. The PR containing all unit tests is <a href="https://github.com/chaoss/grimoirelab-elk/pull/887">#pull/887</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zcZ9GfzGfQDCO3IZ80gl8w.png" /></figure><p>Since we’ll be moving towards a case study of CHAOSS community, I collected all CHAOSS community interactions data and converted it into a Google Sheet. It includes all conversations from GitHub issues and Pull Requests (across different project repositories), mailing lists, IRC channel. The project.json file can be found <a href="https://github.com/ria18405/GSoC/blob/master/Work/Coding%20Period%202/Week%202/projects.json">here</a>. The Google Sheet containing 67k+ records can be found <a href="https://docs.google.com/spreadsheets/d/1wXBO-Xvgm7qWcgqDSMBfnXhUMEMX3N-zQEnnGZeQktE/edit?usp=sharing">here</a>.</p><p>I also added a new visualisation used to measure the values of weight and tags at one glance.</p><p>I have made rough documentation of the steps involved in using SCMS. I have divided the process into two parts; one includes the conversion of Enriched index to a Google Sheet. And the second part involves the conversion of Google Sheet into a Dashboard. Markdown for documentation can be found <a href="https://github.com/ria18405/Working-Directory/blob/master/README.md">here</a>.</p><p>I had a meeting with my mentors on 17–07–20, the meeting details are <a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-07-17-coding-prd-2-2.txt.txt">here</a>. We had an in-depth discussion about the future path of the project. We had multiple directions where we could take SCMS, and we collectively brainstormed, realised the setbacks and uses of each track. Our initial idea was to apply a training model or a keyword analysis algorithm, which would automate the tagging procedure. The possible setback was a reasonable low accuracy and possible missing out on some trends. The other possible path was making.</p><p>I’ll be working to have a refined documentation guide for users and contributors in the next week. I will also be adding the required enrichers based on the communication channel followed by the communities involved in the case studies.🙌</p><p>Thanks for reading!</p><p>That’s it for this week.😃 Make sure you have a look at the project updates on Github <a href="https://github.com/ria18405/GSoC">#ria18405/GSoC</a>. Pull request: <a href="https://github.com/chaoss/grimoirelab-elk/pull/887">#pull/887</a>. All questions and comments are welcomed! Stay tuned for more weekly updates. 🙌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52bdfbe4cd38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 5: Coding period 2]]></title>
            <link>https://medium.com/@guptaria/week-5-coding-period-2-53b8ea29418c?source=rss-d8ba8aa054d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/53b8ea29418c</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[dashboard-design]]></category>
            <dc:creator><![CDATA[Ria Gupta]]></dc:creator>
            <pubDate>Sun, 12 Jul 2020 15:34:50 GMT</pubDate>
            <atom:updated>2020-07-12T15:34:50.915Z</atom:updated>
            <content:encoded><![CDATA[<p>Dashboard and IRC Enricher</p><p>Coding period 2 officially begins, and I’m Thankful to the mentors and the community which supported me throughout the journey! I have successfully passed the first phase, Now the second leap begins! 🎉</p><p>I have made an enricher for Supybot to enrich IRC data and followed similar procedure done earlier for other channels, i.e Converting ES index to Excel, randomly tagging, converting Excel to ES using JSON by executing a study. This time, while randomly tagging the data, I also added “Weight” and “Category” in the excel sheet to better interpret SCMS data. Five categories have been added namely: “Transactional”, “Operational”, “Interpersonal”, “Incoming Request” and “Outgoing Request”. Weight has a scale from -3 to +3. The theory behind Weight is that a more negative weight would indicate a less relevant comment and as we go towards the positive scale, the relevancy of the comments increase.</p><p>This week I have made a dashboard to represent the Social Currency Metric System, I had taken reviews after making a first draft and modified it accordingly. The dashboard consists of a help text which will guide us through all visualisations present. It contains a scoring gauge indicating the average and median score of the data. It has three pie charts which indicate the ratios of each tag, category and data source present in our data. Other than this, It has a Time Series which indicates the trends observed by each tag. The tag cloud is for better representation of tags. Author names and authors email domain has been added as a Data Table, along with the table containing the number of records for each channel(Github, Mbox and IRC). <br>After the dashboard, I have also made a header of “SCMS” in the dashboard menu for easier usability. The dashboard looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*u8XrzHUo6ko56B0B-Y-WWA.gif" /><figcaption>SCMS Dashboard</figcaption></figure><p>I had a meeting with my mentors on 03–07–20 and 10–07–20, the meeting details are <a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-07-03-coding-prd-2-0.txt">here</a> and <a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-07-10-coding-prd-2-1.txt">here</a> respectively. We had an in-depth discussion about the structure of the dashboard and about the theory of weight to be used. We also had a collaboration meeting where we aligned our ideas of different tags and their usage in grimoirelab. We have made some changes in the category field, which will get updated in the dashboard shortly.</p><p>I’ll be working to integrate SCMS with Grimoirelabs in the next week. 🙌</p><p>Thanks for reading!</p><p>That’s it for this week.😃 Make sure you have a look at the project updates on Github <a href="https://github.com/ria18405/GSoC">#ria18405/GSoC</a>. Pull request: <a href="https://github.com/chaoss/grimoirelab-elk/pull/887">#pull/887</a>. All questions and comments are welcomed! Stay tuned for more weekly updates. 🙌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53b8ea29418c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 4: Coding Period 1]]></title>
            <link>https://medium.com/@guptaria/week-4-coding-period-1-b7bfddd37693?source=rss-d8ba8aa054d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7bfddd37693</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[visualization]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[google-summer-of-code]]></category>
            <dc:creator><![CDATA[Ria Gupta]]></dc:creator>
            <pubDate>Sun, 28 Jun 2020 17:11:43 GMT</pubDate>
            <atom:updated>2020-06-28T17:11:43.841Z</atom:updated>
            <content:encoded><![CDATA[<h4>Collaboration &amp; Visualisations</h4><p>We had a prolific collaboration meeting on 26 June’20, the meeting log can be found <a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-06-26-coding-prd-1-4.txt">here</a>. We discussed the trends observed by tagging the data and discussed the future path of SCMS. As expected, out of all 5 tags, the most observed tag was “Utility”, as GrimoireLab provides very useful tools for software development analytics. Further, we discussed the noise elements observed in the data. IRC messages rendered some noise, and those records could not be tagged. Since we can&#39;t leave these records untagged, we have planned to remove such instances from the google sheets implementation, so that we could focus on meaningful texts. Some examples of noises are: “abc_is now known as xyz” or “ChanServ sets mode: +o collabot`”.</p><p>“Category” is a way to classify our records for more fruitful analysis. For instance, a comment in which a user is asking for help in any issue might be indicative of ‘troubleshooting’. For GrimoireLab, since the majority of GitHub comments were related to troubleshooting, we decided to split this category into 2 categories namely “Incoming Request” and “Technical Support”. This was because having categories as precise as possible would help in analysing data efficiently. Categories like “Interpersonal”, “Operational” and “Transactional” were also ideated to be added.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*OOFExANrb-aazdD6ss-5mQ.png" /><figcaption>Basic Visualisations</figcaption></figure><p>Apart from tagging data, I also spent the week learning the process of making a visualisation. I made some of the basic visualisations using the index which contained randomly tagged data. Visualisations included a pie chart of 5 different tags, a bar chart of the number of comments received per week, data indicating the number of conversations from different channels etc.</p><p>Thanks for reading! This week marks the end of the first coding period, It has been a wonderful month coding, brainstorming, blogging, interacting with the so-awesome mentors! 🙈</p><p>That’s it for this week.😃 Make sure you have a look at the project updates on Github <a href="https://github.com/ria18405/GSoC">#ria18405/GSoC</a>. All questions and comments are welcomed! Stay tuned for more weekly updates. 🙌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7bfddd37693" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 3: Coding Period 1]]></title>
            <link>https://medium.com/@guptaria/week-3-coding-period-1-e0f53643ee74?source=rss-d8ba8aa054d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0f53643ee74</guid>
            <category><![CDATA[gsoc-2020]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[qualitative-data]]></category>
            <dc:creator><![CDATA[Ria Gupta]]></dc:creator>
            <pubDate>Sun, 21 Jun 2020 06:25:01 GMT</pubDate>
            <atom:updated>2020-06-22T04:10:03.005Z</atom:updated>
            <content:encoded><![CDATA[<h4>Codex Sheet</h4><p>In the first week, I had exported the extracted data to an Airtable view. I didn’t realise it till the previous week, that Airtable has a limit of 1200 records per base only for a free version. Our initial goal was to collect as much data as possible to represent the community’s sentiments holistically and make SCMS usable by other open-source communities as well. Thus, we decided to shift the implementation to Google Sheets. So, I collected all data from Github, Mailing lists of Grimoirelab and IRC channel of CHAOSS. Then, randomly tagged it (as done in Week 2), and exported to Google Sheets using an API. Google Sheets do not allow more than 5 million cells, which is adequately enormous.</p><p>After looking at the data carefully, we noticed that we had Github comments by Coveralls indicating the coverage increased or decreased. Other than this, we had lots of IRC messages indicating a person has joined the channel or has left the channel. This data is not providing us with any additional information about the community and is not a user sentiment. So, we planned to remove all those unnecessary records. We collected around 5.6k filtered data from Github, Mailing list, IRC channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b5zGPNG4ZB2g7LIPllGk3w.png" /><figcaption>Google Sheets representation</figcaption></figure><p>A major part of the week was planned to be devoted to building a <strong>Codex</strong> Sheet. Codex helps us to rely on Qualitative data rather than Quantitative data. To reduce the subjectivity of this qualitative data, it is imperative to define a codex table which can help in tagging data points accurately. It also helps in collaborating with the team to keep similar ideas running. It contains the definitions of metrics wrt the organisation (here it is Grimoirelab), and an example to illustrate the definition. It also consists of “when to use” and “when-not-to-use” a metric.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9k7Fjghzng9_5ybBX3V58g.png" /><figcaption>Codex Sheet</figcaption></figure><p>I also made a short rough draft of an overview of SCMS to be published for the CHAOSS blog. Other than this, since we have a full version of data present in google sheets, I converted this entire Excel sheet data to the ElasticSearch index(precisely as done in Week 2). The only difference is the number of records being used. Earlier, I could only have limited records containing the “extra_scms_data” in the Enriched index, Now, every meaningful record(i.e. ignoring comments by coveralls) has an additional field present in its ElasticSearch index.</p><p>I had a meeting with the mentors on 19 June’20, minutes are <a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-06-19-coding-prd-1-3.txt">here</a>. We discussed Dashboarding and expanding on the SCMS. We’ll be having a collaboration meeting on Friday,26 for discussing the findings of tagged data. Till then, in the next week, I’ll be focusing on writing tests and making a basic dashboard. 🎉</p><p>That&#39;s it for this week.😃 Make sure you have a look at the project updates on Github <a href="https://github.com/ria18405/GSoC">#ria18405/GSoC</a>. All questions and comments are welcomed! Stay tuned for more weekly updates. 🙌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0f53643ee74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 2: Coding Period 1]]></title>
            <link>https://medium.com/@guptaria/week-2-coding-period-1-c6b103dee0ce?source=rss-d8ba8aa054d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6b103dee0ce</guid>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[social-currency]]></category>
            <category><![CDATA[elasticsearch]]></category>
            <category><![CDATA[gsoc-2020]]></category>
            <dc:creator><![CDATA[Ria Gupta]]></dc:creator>
            <pubDate>Sun, 14 Jun 2020 07:19:51 GMT</pubDate>
            <atom:updated>2020-06-21T05:36:10.784Z</atom:updated>
            <content:encoded><![CDATA[<h4>Enriching Extra data from Excel to ElasticSearch</h4><p>This week was oriented according to the timeline. We had planned first to make the pipeline ready, and then to move forward with the rest of the procedures. So, in the first week, I had extracted the required data from ElasticSearch and converted to an Airtable view. This week, I have randomly tagged the datasheet with five metrics and have linked the additional data back to ElasticSearch via a ‘study’ called ‘enrich_extra_data’.</p><p>To explain what this exactly means and looks like, I’ll explain in detail the steps involved. The first step was to randomly tag the dataset by all possible combinations of the social currency parameters, i.e. Trust, Transparency, Merit, Consistency, Utility in an Excel Sheet. Here, we have added another column in the excel sheet by the name of ‘scms_tags.’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tv_pLJHZ5Lzjzj86XYvX6w.png" /><figcaption>Addition of new column of randomised tags</figcaption></figure><p>The second step is making a python script Excel2Json which could convert Excel to a specific type of JSON which will be used as an input to the study. You can find the JSON <a href="https://gist.githubusercontent.com/ria18405/630346bac7856658fd19ed63bce4d9c0/raw/687bec24b7739d06f8bdde110c6f9702663c01d3/json_file.json">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*cptpqBhJQNfyNH_AiyNEFg.png" /><figcaption>Input JSON to the study</figcaption></figure><p>Now, we need to execute a study called ‘enrich_extra_data’ in grimoirelab-ELK. Edit Setup.cfg according to the study, input the URL of JSON made above. After successfully performing the study, we can see that ElasticSearch indexes have the extra parameter of scms_tags in the dump. 🎉 The study appends an ‘extra’ to the field name, So the field name is ‘extra_scms_tags’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*NumtxN9GlwPzQyjelSiYpA.png" /><figcaption>Output of Elasticdump has the required fields.</figcaption></figure><p>I understood the importance of codex sheet in training set up in the meeting on 12 June ’20. The minutes of the meeting are <a href="https://github.com/ria18405/GSoC/blob/master/Meetings/2020-06-12-coding-prd-1-2.txt">here</a>. Defining the codex table helps to increase universality and decrease the subjectivity of the data. It also allows us to rely more on qualitative data rather than quantitative data. After the training, we discussed the path for the next week. In the next week, I’ll be making a codex table which will contain the definitions of each trend observed and will contain the ‘when to-use’ and ‘when not-to-use’ cases. We found the limit in the number of records in Airtable, so we planned to shift the implementation to Google Sheets.</p><p>This week went off well, looking forwards to the next week! 😄</p><p>Make sure you have a look at the project updates on Github <a href="https://github.com/ria18405/GSoC">#ria18405/GSoC</a>. All questions and comments are welcomed! Stay tuned for more weekly updates. 🙌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6b103dee0ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>