From 0ceb79713fff73710ecc374ad69c8161d8ef3d6f Mon Sep 17 00:00:00 2001 From: Kirstie Whitaker Date: Fri, 10 Aug 2018 09:52:54 -0700 Subject: [PATCH 01/12] Tiny edit to open new branch --- reports/Google-2018-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index 4fe3c628..7ca39cb5 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -1,6 +1,6 @@ Please note this report is regarding the BIDS Starter Kit. -If you have reached this page from a different source, please visit the front page of the repository at: https://github.com/INCF/BIDS-Starter-Kit +If you have reached this page from a different source, please visit the front page of the repository at: https://github.com/INCF/BIDS-Starter-Kit. ## The Big Picture From 5c321ff65da3fcc795b83508a83b3c2119aecdc5 Mon Sep 17 00:00:00 2001 From: Kirstie Whitaker Date: Fri, 10 Aug 2018 11:15:20 -0700 Subject: [PATCH 02/12] Adjust header --- reports/Google-2018-report.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index 7ca39cb5..d26e2079 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -1,6 +1,8 @@ -Please note this report is regarding the BIDS Starter Kit. +This is Patrick Park's Google Summer of Code final report for his work on the [BIDS Starter Kit](https://github.com/INCF/BIDS-Starter-Kit). -If you have reached this page from a different source, please visit the front page of the repository at: https://github.com/INCF/BIDS-Starter-Kit. +If you have reached this page from a different source, and want an overview of the project, please check out our README file at https://github.com/INCF/BIDS-Starter-Kit. + +The work completed by Patrick Park during the Google Summer of Code is archived on zenodo at: [INSERT DOI] ## The Big Picture From 4828f85e22f44a55e2808f57811a556da81ee481 Mon Sep 17 00:00:00 2001 From: Kirstie Whitaker Date: Fri, 10 Aug 2018 11:25:05 -0700 Subject: [PATCH 03/12] Add a few more details so I can review! --- reports/Google-2018-report.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index d26e2079..4a1819c7 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -15,11 +15,10 @@ prioritize transparency, diversity, and reproducibility to foster collaboration. Imagine you are a carrot farmer trying to make dinner. You could make carrot soup by yourself, but you could also share ingredients with the neighbours to make a much tastier soup with onions, greens, and some salt. Some people may be able to contribute more than others -- but everyone benefits. - - In neuroscience, data such as magnetic resonance images and physiology readings can be costly in both time and money to acquire. This creates a barrier for many underfunded researchers without access to the required equipment. Responsible data sharing can level the playing field, but incompatible specifications cause portability issues between different labs and scientists. The brain imaging data standard (BIDS) is a framework for organizing data that standardizes datasets across different researchers to enable easier sharing. -## Our role + +## My role The primary goal of this project was to simplify the process of learning about BIDS and engage more users. Well before it was funded by Google, the roots of this initiative were being pioneered by a small group of people around the world that were acting as local BIDS ambassadors in their communities. Many of us were already giving presentations at every workshop and conference possible. However, these were only for a limited audience, and there was a need for central organization. We hoped to create a central repository accessible to everyone that would contain easy to read documentation and a collection of useful resources. @@ -56,9 +55,14 @@ As a result, the number of unique visitors grew from less than 5 to peaks of ove :o: **Problem** International project management and communication -:heavy_check_mark: **Solution** The members and collaborators of this project were located in Canada, Britain, the Netherlands, the USA, and India. The strategy for this problem was to work publicly. This meant rather than waiting until completion to share something, we would continuously post our work in progress and incorporate feedback. Specifically, Github milestones and “closing soon” tags were helpful to highlight weekly tasks and mark them for review. +:heavy_check_mark: **Solution** The members and collaborators of this project were located in Canada ([Elizabeth DuPre](https://github.com/emdupre)), Britain ([Kirstie Whitaker](https://github.com/KirstieJane)), the Netherlands ([Dora Hermes](https://github.com/dorahermes)), the USA ([Chris Gorgolewski](https://github.com/chrisfilo) and [Chris Holdgraf](https://github.com/choldgraf/)), and India **[PATRICK - who was in India?? I feel terrible that I don't know!]**. +The strategy for this problem was to work publicly and to demonstrate best practise in open source project leadership. +This meant rather than waiting until completion to share something, we would continuously post our work in progress and incorporate feedback. +Specifically, Github milestones and “closing soon” tags on issues were helpful to highlight weekly tasks and mark them for review. -Despite these strategies, I still felt that the turning point of the project was in June when some of our team finally met in person. Summarizing an unnecessary meeting into a message is efficient, but familiarity is really important too. +Despite these strategies, I still felt that the turning point of the project was in June when some of our team finally met in person at the [Organization for Human Brain Mapping Hackathon](https://ohbm.github.io/hackathon2018/). +I was a recipient of a travel award ($500) for this event and it really made a huge difference to effective I was as maintainer and content creator for BIDS Starter Kit. +Summarizing an unnecessary meeting into a message is efficient, but familiarity is really important too. ## Personal notes @@ -67,5 +71,5 @@ Four months ago, as an electrical engineer, a community development job might ha
Patrick J. Park - +[ADD CONTACT DETAILS HERE] From aa1755c4c7f6d49367ba89f8aad259f7b1484364 Mon Sep 17 00:00:00 2001 From: Kirstie Whitaker Date: Fri, 10 Aug 2018 11:41:57 -0700 Subject: [PATCH 04/12] Add information & links about contributing guidelines --- reports/Google-2018-report.md | 31 ++++++++++++++++++++++++++----- 1 file changed, 26 insertions(+), 5 deletions(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index 4a1819c7..7eff1897 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -20,7 +20,16 @@ In neuroscience, data such as magnetic resonance images and physiology readings ## My role -The primary goal of this project was to simplify the process of learning about BIDS and engage more users. Well before it was funded by Google, the roots of this initiative were being pioneered by a small group of people around the world that were acting as local BIDS ambassadors in their communities. Many of us were already giving presentations at every workshop and conference possible. However, these were only for a limited audience, and there was a need for central organization. We hoped to create a central repository accessible to everyone that would contain easy to read documentation and a collection of useful resources. +The primary goal of this project was to simplify the process of learning about BIDS and engage more users. +Well before it was funded by Google, the roots of this initiative were being pioneered by a small group of people around the world that were acting as local BIDS ambassadors in their communities. +Many of us were already giving presentations at every workshop and conference possible. +However, these were only for a limited audience, and there was a need for central organization. +We hoped to create a central repository accessible to everyone that would contain easy to read documentation and a collection of useful resources. + +**[ADD A FEW SENTENCES HERE ABOUT WHAT **YOU** (Patrick) did for the starter kit.]** + +It was my responsibility over the Google Summer of Code to be the lead maintainer of the repository. +I was in charge of managing issues and pull requests, and for responding to request from the senior developers and new contributors a like. ## Problem definitions and solutions @@ -35,19 +44,27 @@ From there, we broke it down into a series of more discrete problems. :o: **Problem** Which parts of BIDS are people finding most difficult? -:heavy_check_mark: **Solution** Through both formal surveys and informal chats, we got feedback from the newcomers to BIDS. The results showed that people were most confused by the technical jargon and metadata file formats. +:heavy_check_mark: **Solution** Through both formal surveys and informal chats, I got feedback from the newcomers to BIDS. +The results showed that people were most confused by the technical jargon and metadata file formats.
:o: **Problem** The technical documentation about BIDS can be overwhelming. -:heavy_check_mark: **Solution** We developed an easy to read reference called the BIDS Starter Kit Wiki. What started as a two page document quickly grew into a compilation of information, tutorials, examples, a glossary, publications, community resources, and many more. +:heavy_check_mark: **Solution** I developed an easy to read reference called the [BIDS Starter Kit Wiki](https://github.com/INCF/bids-starter-kit/wiki). +What started as a two page document quickly grew into a compilation of information, tutorials, examples, a glossary, publications, community resources, and many more.
:o: **Problem** Engage more users -:heavy_check_mark: **Solution** In person, our team continued to spread the word about the project during any relevant events. Online, we created an animated video to summarize the general idea and make the first step that much easier. We also used the “good-first-issue” principle to periodically leave small mistakes in our repository unfixed, such as a typo or an undefined term in the glossary. Then, we would send out a request and guide a new contributor through the process of using the repository. +:heavy_check_mark: **Solution** In person, our team continued to spread the word about the project during any relevant events. +Online, we created an [animated video](https://camo.githubusercontent.com/aada478abaddf957a3622589a5c370f11bf67642/687474703a2f2f696d672e796f75747562652e636f6d2f76692f425964686a5675427347302f302e6a7067) to summarize the general idea and make the first step that much easier. +We developed [extensive contribution guidelines](https://github.com/INCF/BIDS-Starter-Kit/blob/master/CONTRIBUTING.md) to help new contributors add their expertise to the project. +We include how to [get in touch](https://github.com/INCF/BIDS-Starter-Kit/blob/master/CONTRIBUTING.md#get-in-touch), [write in markdown](https://github.com/INCF/BIDS-Starter-Kit/blob/master/CONTRIBUTING.md#writing-in-markdown), [submit a pull request](https://github.com/INCF/BIDS-Starter-Kit/blob/master/CONTRIBUTING.md#making-a-change-with-a-pull-request) and explanations of where to put [useful code or links in the wiki](https://github.com/INCF/BIDS-Starter-Kit/blob/master/CONTRIBUTING.md#where-to-start-wiki-code-and-templates). +The licence on our repository is CC-BY and these guidelines have already been incorporated into other open source neuroimaging projects such as [NiBetaSeries](https://nibetaseries.readthedocs.io/en/latest/contributing.html). +We also used the [“good-first-issue” principle](https://github.com/INCF/BIDS-Starter-Kit/blob/master/CONTRIBUTING.md#where-to-start-issue-labels) to periodically leave small mistakes in our repository unfixed, such as a typo or an undefined term in the glossary. +Then, we would send out a request and guide a new contributor through the process of using the repository. As a result, the number of unique visitors grew from less than 5 to peaks of over 50 per day. @@ -66,7 +83,11 @@ Summarizing an unnecessary meeting into a message is efficient, but familiarity ## Personal notes -Four months ago, as an electrical engineer, a community development job might have meant laying power transmission lines to a new town. Now it means making sure people don’t get lost on their way. The toughest part at first was definitely the uncertainty -- a document doesn’t have errors and nobody leaves detailed feedback about why they *didn’t* feel welcomed. But I’m glad to have finally learned the natural continuation of what happens as a tool reaches maturity. To every mentor, collaborator, administrator, and user that has been a part of this project so far, thank you for all the help and feel free to message because I’ll still be staying involved! +Four months ago, as an electrical engineer, a community development job might have meant laying power transmission lines to a new town. +Now it means making sure people don’t get lost on their way. +The toughest part at first was definitely the uncertainty -- a document doesn’t have errors and nobody leaves detailed feedback about why they *didn’t* feel welcomed. +But I’m glad to have finally learned the natural continuation of what happens as a tool reaches maturity. +To every mentor, collaborator, administrator, and user that has been a part of this project so far, thank you for all the help and feel free to message because I’ll still be staying involved!
From c030c2c6f98602f856dfff9ce80b523647326789 Mon Sep 17 00:00:00 2001 From: Park-Patrick Date: Fri, 10 Aug 2018 17:57:47 -0400 Subject: [PATCH 05/12] Update Google-2018-report.md --- reports/Google-2018-report.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index 7eff1897..596b26bd 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -2,7 +2,7 @@ This is Patrick Park's Google Summer of Code final report for his work on the [B If you have reached this page from a different source, and want an overview of the project, please check out our README file at https://github.com/INCF/BIDS-Starter-Kit. -The work completed by Patrick Park during the Google Summer of Code is archived on zenodo at: [INSERT DOI] +The work completed by Patrick Park during the Google Summer of Code is archived on zenodo at: [![DOI](https://zenodo.org/badge/102141901.svg)](https://zenodo.org/badge/latestdoi/102141901) ## The Big Picture @@ -26,10 +26,7 @@ Many of us were already giving presentations at every workshop and conference po However, these were only for a limited audience, and there was a need for central organization. We hoped to create a central repository accessible to everyone that would contain easy to read documentation and a collection of useful resources. -**[ADD A FEW SENTENCES HERE ABOUT WHAT **YOU** (Patrick) did for the starter kit.]** - -It was my responsibility over the Google Summer of Code to be the lead maintainer of the repository. -I was in charge of managing issues and pull requests, and for responding to request from the senior developers and new contributors a like. +It way my responsibility over the Google Summer of Code to be the lead developer and maintainer of the repository. When responding to requests from both senior developers and new contributors alike, this meant breaking down requested features into action items that could be assigned to either myself or the relevant expert. Periodically, I would then go through the list of issues to make sure progress on them “die out”. As a content creator, my work was primarily focused on the README and wiki. This included writing content and enhancing user experience by designing a clear framework. ## Problem definitions and solutions @@ -72,7 +69,7 @@ As a result, the number of unique visitors grew from less than 5 to peaks of ove :o: **Problem** International project management and communication -:heavy_check_mark: **Solution** The members and collaborators of this project were located in Canada ([Elizabeth DuPre](https://github.com/emdupre)), Britain ([Kirstie Whitaker](https://github.com/KirstieJane)), the Netherlands ([Dora Hermes](https://github.com/dorahermes)), the USA ([Chris Gorgolewski](https://github.com/chrisfilo) and [Chris Holdgraf](https://github.com/choldgraf/)), and India **[PATRICK - who was in India?? I feel terrible that I don't know!]**. +:heavy_check_mark: **Solution** The members of this project were located in Canada ([Elizabeth DuPre](https://github.com/emdupre)), Britain ([Kirstie Whitaker](https://github.com/KirstieJane)), the Netherlands ([Dora Hermes](https://github.com/dorahermes)), the USA ([Chris Gorgolewski](https://github.com/chrisfilo) and [Chris Holdgraf](https://github.com/choldgraf/)), as well as a collaborator from India ([Madhur Tandon](https://github.com/madhur-tandon)). The strategy for this problem was to work publicly and to demonstrate best practise in open source project leadership. This meant rather than waiting until completion to share something, we would continuously post our work in progress and incorporate feedback. Specifically, Github milestones and “closing soon” tags on issues were helpful to highlight weekly tasks and mark them for review. @@ -92,5 +89,11 @@ To every mentor, collaborator, administrator, and user that has been a part of t
Patrick J. Park -[ADD CONTACT DETAILS HERE] + + +Senior undergraduate student in Electrical Engineering (BESc) at Western University, Canada + +parkpatrickj@gmail.com + +Github: [Park-Patrick](https://github.com/Park-Patrick) From 3676d02265d3ce4a16f84a5580cf2a6e84211c97 Mon Sep 17 00:00:00 2001 From: Kirstie Whitaker Date: Fri, 10 Aug 2018 16:00:49 -0700 Subject: [PATCH 06/12] Update doi link --- reports/Google-2018-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index 596b26bd..403c3ffc 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -2,7 +2,7 @@ This is Patrick Park's Google Summer of Code final report for his work on the [B If you have reached this page from a different source, and want an overview of the project, please check out our README file at https://github.com/INCF/BIDS-Starter-Kit. -The work completed by Patrick Park during the Google Summer of Code is archived on zenodo at: [![DOI](https://zenodo.org/badge/102141901.svg)](https://zenodo.org/badge/latestdoi/102141901) +The work completed by Patrick Park during the Google Summer of Code is archived on zenodo under DOI [10.5281/zenodo.1342122](http://doi.org/10.5281/zenodo.1342122) ## The Big Picture From 0a4446594fb2afefcae09806cae05b05a15a0f9d Mon Sep 17 00:00:00 2001 From: Kirstie Whitaker Date: Mon, 13 Aug 2018 14:32:37 +0100 Subject: [PATCH 07/12] Update Google-2018-report.md --- reports/Google-2018-report.md | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index 403c3ffc..c1b59e53 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -12,10 +12,13 @@ prioritize transparency, diversity, and reproducibility to foster collaboration. sharing-pot -Imagine you are a carrot farmer trying to make dinner. You could make carrot soup by yourself, but you could also share ingredients -with the neighbours to make a much tastier soup with onions, greens, and some salt. Some people may be able to contribute more than others -- but everyone benefits. +Imagine you are a carrot farmer trying to make dinner. You could make carrot soup by yourself, but you could also share ingredients with the neighbours to make a much tastier soup with onions, greens, and some salt. +Some people may be able to contribute more than others -- but everyone benefits. -In neuroscience, data such as magnetic resonance images and physiology readings can be costly in both time and money to acquire. This creates a barrier for many underfunded researchers without access to the required equipment. Responsible data sharing can level the playing field, but incompatible specifications cause portability issues between different labs and scientists. The brain imaging data standard (BIDS) is a framework for organizing data that standardizes datasets across different researchers to enable easier sharing. +In neuroscience, data such as magnetic resonance images and physiology readings can be costly in both time and money to acquire. +This creates a barrier for many underfunded researchers without access to the required equipment. +Responsible data sharing can level the playing field, but incompatible specifications cause portability issues between different labs and scientists. +The brain imaging data standard (BIDS) is a framework for organizing data that standardizes datasets across different researchers to enable easier sharing. ## My role @@ -23,11 +26,15 @@ In neuroscience, data such as magnetic resonance images and physiology readings The primary goal of this project was to simplify the process of learning about BIDS and engage more users. Well before it was funded by Google, the roots of this initiative were being pioneered by a small group of people around the world that were acting as local BIDS ambassadors in their communities. Many of us were already giving presentations at every workshop and conference possible. -However, these were only for a limited audience, and there was a need for central organization. +However, these were only for a limited audience, and there was a need for central organization of these resources. We hoped to create a central repository accessible to everyone that would contain easy to read documentation and a collection of useful resources. -It way my responsibility over the Google Summer of Code to be the lead developer and maintainer of the repository. When responding to requests from both senior developers and new contributors alike, this meant breaking down requested features into action items that could be assigned to either myself or the relevant expert. Periodically, I would then go through the list of issues to make sure progress on them “die out”. As a content creator, my work was primarily focused on the README and wiki. This included writing content and enhancing user experience by designing a clear framework. - +It was my responsibility over the Google Summer of Code to be the lead developer and maintainer of the repository. +When responding to requests from both senior developers and new contributors alike, this meant breaking down requested features into action items that could be assigned to either myself or the relevant expert. +Periodically, I would then go through the list of issues to make sure progress on them did not “die out”. +As a content creator, my work was primarily focused on the README and wiki. +This included writing content and enhancing user experience by designing a clear framework. +Although much of this work was documentation, I had to be able to understand the specification to a high technical standard - including the [BIDS Apps software](http://bids-apps.neuroimaging.io/apps/) that are built from docker images - in order to communicate the information to new users. ## Problem definitions and solutions @@ -90,10 +97,9 @@ To every mentor, collaborator, administrator, and user that has been a part of t Patrick J. Park - Senior undergraduate student in Electrical Engineering (BESc) at Western University, Canada -parkpatrickj@gmail.com +Email: parkpatrickj@gmail.com Github: [Park-Patrick](https://github.com/Park-Patrick) From cded291fd8c4a108e02ca76e023f1b47b06b675f Mon Sep 17 00:00:00 2001 From: Kirstie Whitaker Date: Mon, 13 Aug 2018 14:34:42 +0100 Subject: [PATCH 08/12] Update Google-2018-report.md --- reports/Google-2018-report.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index c1b59e53..8a05dca6 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -82,9 +82,10 @@ This meant rather than waiting until completion to share something, we would con Specifically, Github milestones and “closing soon” tags on issues were helpful to highlight weekly tasks and mark them for review. Despite these strategies, I still felt that the turning point of the project was in June when some of our team finally met in person at the [Organization for Human Brain Mapping Hackathon](https://ohbm.github.io/hackathon2018/). -I was a recipient of a travel award ($500) for this event and it really made a huge difference to effective I was as maintainer and content creator for BIDS Starter Kit. +I was a recipient of a travel award ($500) for this event and it really made a huge difference to in my effectiveness as maintainer and content creator for BIDS Starter Kit. Summarizing an unnecessary meeting into a message is efficient, but familiarity is really important too. + ## Personal notes Four months ago, as an electrical engineer, a community development job might have meant laying power transmission lines to a new town. From 1b0e566184ff7f26ffe76afd1a56d0d73dc35e1c Mon Sep 17 00:00:00 2001 From: Park-Patrick Date: Mon, 13 Aug 2018 12:59:37 -0400 Subject: [PATCH 09/12] Update Google-2018-report.md --- reports/Google-2018-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index 8a05dca6..dfd40302 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -82,7 +82,7 @@ This meant rather than waiting until completion to share something, we would con Specifically, Github milestones and “closing soon” tags on issues were helpful to highlight weekly tasks and mark them for review. Despite these strategies, I still felt that the turning point of the project was in June when some of our team finally met in person at the [Organization for Human Brain Mapping Hackathon](https://ohbm.github.io/hackathon2018/). -I was a recipient of a travel award ($500) for this event and it really made a huge difference to in my effectiveness as maintainer and content creator for BIDS Starter Kit. +I was a recipient of a travel award ($500) for this event and it really made a huge difference in my effectiveness as maintainer and content creator for BIDS Starter Kit. Summarizing an unnecessary meeting into a message is efficient, but familiarity is really important too. From 6811b690f534967ee4626f1d3cfa03eb97921356 Mon Sep 17 00:00:00 2001 From: Park-Patrick Date: Mon, 13 Aug 2018 13:59:31 -0400 Subject: [PATCH 10/12] Update Google-2018-report.md --- reports/Google-2018-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index dfd40302..4216da3d 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -2,7 +2,7 @@ This is Patrick Park's Google Summer of Code final report for his work on the [B If you have reached this page from a different source, and want an overview of the project, please check out our README file at https://github.com/INCF/BIDS-Starter-Kit. -The work completed by Patrick Park during the Google Summer of Code is archived on zenodo under DOI [10.5281/zenodo.1342122](http://doi.org/10.5281/zenodo.1342122) +The work completed by Patrick Park during the Google Summer of Code is archived on zenodo under v1.0.2 at https://zenodo.org/badge/latestdoi/102141901 ## The Big Picture From bc76530b134e81324b4833f51f7177a195009d4f Mon Sep 17 00:00:00 2001 From: Park-Patrick Date: Mon, 13 Aug 2018 14:04:20 -0400 Subject: [PATCH 11/12] Update Google-2018-report.md --- reports/Google-2018-report.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index 4216da3d..77df5347 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -88,9 +88,8 @@ Summarizing an unnecessary meeting into a message is efficient, but familiarity ## Personal notes -Four months ago, as an electrical engineer, a community development job might have meant laying power transmission lines to a new town. -Now it means making sure people don’t get lost on their way. -The toughest part at first was definitely the uncertainty -- a document doesn’t have errors and nobody leaves detailed feedback about why they *didn’t* feel welcomed. + +As my first foray into community development and international project handling, the toughest part at first was definitely the uncertainty -- a document doesn’t have errors and nobody leaves detailed feedback about why they *didn’t* feel welcomed. But I’m glad to have finally learned the natural continuation of what happens as a tool reaches maturity. To every mentor, collaborator, administrator, and user that has been a part of this project so far, thank you for all the help and feel free to message because I’ll still be staying involved! From 52a87fa2631761495c6d162094580af02c648e62 Mon Sep 17 00:00:00 2001 From: Park-Patrick Date: Mon, 13 Aug 2018 14:14:05 -0400 Subject: [PATCH 12/12] Update Google-2018-report.md --- reports/Google-2018-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reports/Google-2018-report.md b/reports/Google-2018-report.md index 77df5347..f175fb0c 100644 --- a/reports/Google-2018-report.md +++ b/reports/Google-2018-report.md @@ -2,7 +2,7 @@ This is Patrick Park's Google Summer of Code final report for his work on the [B If you have reached this page from a different source, and want an overview of the project, please check out our README file at https://github.com/INCF/BIDS-Starter-Kit. -The work completed by Patrick Park during the Google Summer of Code is archived on zenodo under v1.0.2 at https://zenodo.org/badge/latestdoi/102141901 +The work completed by Patrick Park during the Google Summer of Code is archived on zenodo under at [DOI] ## The Big Picture