{ "version" : "https://jsonfeed.org/version/1", "content" : "news", "type" : "single", "title" : "Code.gov User Interviews — What We Learned |Digital.gov", "description": "Code.gov User Interviews — What We Learned", "home_page_url" : "/preview/gsa/digitalgov.gov/cm-topics-button-component/","feed_url" : "/preview/gsa/digitalgov.gov/cm-topics-button-component/2017/09/05/code-gov-user-interviews-what-we-learned/index.json","item" : [ {"title" :"Code.gov User Interviews \u0026#8212; What We Learned","summary" : "This post was originally published by Code.gov on Medium. It’s been a year since the federal government published the Federal Source Code Policy, which created the foundation for Code.gov. In honor of the policy’s anniversary, we checked in with our users to learn more about them, their needs, and the challenges they face. Our users","date" : "2017-09-05T02:00:20-04:00","date_modified" : "2024-04-02T09:45:13-04:00","authors" : {"code-gov" : "Code.gov Team"},"topics" : { "research" : "Research", "software-engineering" : "Software Engineering" },"featured_image" : { "uid" : "question-mark-rawpixel-ltd-istock-thinkstock-180823703", "alt" : "Folks holding question marks in front of their faces." },"branch" : "cm-topics-button-component", "filename" :"2017-09-05-code-gov-user-interviews%e2%80%8a-%e2%80%8awhat-we-learned.md", "filepath" :"news/2017/09/2017-09-05-code-gov-user-interviews%e2%80%8a-%e2%80%8awhat-we-learned.md", "filepathURL" :"https://github.com/GSA/digitalgov.gov/blob/cm-topics-button-component/content/news/2017/09/2017-09-05-code-gov-user-interviews%e2%80%8a-%e2%80%8awhat-we-learned.md", "editpathURL" :"https://github.com/GSA/digitalgov.gov/edit/cm-topics-button-component/content/news/2017/09/2017-09-05-code-gov-user-interviews%e2%80%8a-%e2%80%8awhat-we-learned.md","slug" : "code-gov-user-interviews-what-we-learned","url" : "/preview/gsa/digitalgov.gov/cm-topics-button-component/2017/09/05/code-gov-user-interviews-what-we-learned/","content" :"\u003cblockquote\u003e\n\u003cp\u003e\u003cem\u003eThis post was originally published by \u003ca href=\"https://medium.com/codedotgov/user-interviews-what-we-learned-9a41812e5a3\"\u003eCode.gov on Medium\u003c/a\u003e.\u003c/em\u003e\u003c/p\u003e\n\u003c/blockquote\u003e\n\u003cp\u003eIt’s been a year since the federal government published the Federal Source Code Policy, which created the foundation for \u003ca class=\"markup--anchor markup--p-anchor\" href=\"https://code.gov/\" target=\"_blank\" rel=\"noopener nofollow\"\u003eCode.gov\u003c/a\u003e. In honor of the policy’s anniversary, we checked in with our users to learn more about them, their needs, and the challenges they face. Our users were responsive, proving insights we translated into our newly released \u003ca class=\"markup--anchor markup--p-anchor\" href=\"https://code.gov/#/policy-guide/docs/compliance/inventory-code\" target=\"_blank\" rel=\"nofollow noopener\"\u003emetadata schema\u003c/a\u003e that powers the Code.gov platform.\u003c/p\u003e\n\u003cp id=\"4296\" class=\"graf graf--p graf-after--p\"\u003e\n We interviewed federal developers, product owners, Federally Funded Research and Development Center (FFRDC) consultants, and developers from across the open source community. We asked interviewees what they knew about the \u003ca class=\"markup--anchor markup--p-anchor\" href=\"https://medium.com/@CodeDotGov/the-journey-to-sharing-americas-code-10a162d26418\" target=\"_blank\" rel=\"noopener\"\u003eFederal Source Code Policy\u003c/a\u003e, Code.gov, what features they would like to see in future iterations, and how they discover news about open source software and technology in general. Common themes emerged quickly after just a couple of interviews.\n\u003c/p\u003e \u003cdiv\n class=\"image\"\n\u003e\u003cimg\n src=\"https://s3.amazonaws.com/digitalgov/question-mark-rawpixel-ltd-istock-thinkstock-180823703_w800.jpg\"\n \n alt=\"A crowd of anonymous people holding up question mark signs in front of their faces.\"\n srcset=\"https://s3.amazonaws.com/digitalgov/question-mark-rawpixel-ltd-istock-thinkstock-180823703_bu.jpg 48w,https://s3.amazonaws.com/digitalgov/question-mark-rawpixel-ltd-istock-thinkstock-180823703_w600.jpg 600w,https://s3.amazonaws.com/digitalgov/question-mark-rawpixel-ltd-istock-thinkstock-180823703_w400.jpg 400w,https://s3.amazonaws.com/digitalgov/question-mark-rawpixel-ltd-istock-thinkstock-180823703_w200.jpg 200w\"\n\n sizes=\"(max-width: 800px) 100vw, 800px\"\n /\u003e\u003c/div\u003e\n\n\n\u003ch2 id=\"cd47.graf.graf--p.graf-after--p\"\u003eSearch\u003c/h2\u003e\n\u003cp id=\"18af\" class=\"graf graf--p graf-after--p\"\u003e\n Nearly all of our interviews mentioned a need for a robust search function — search by category, language, technology, subject matter, type of project (such as web app, time tracking, mobile app, etc.) Our users do not just want the ability to search, they want the ability to search any way they choose. Some users even want the search capability to be more dynamic — presenting them information they want right away, similarly to how Flipboard or Medium curates information for you based on your preferences. The search component is an important feature to our users and we have been brainstorming around it nonstop.\n\u003c/p\u003e\n\u003ch2 id=\"bfd3.graf.graf--p.graf-after--p\"\u003eCategorization\u003c/h2\u003e\n\u003cp id=\"4f3b\" class=\"graf graf--p graf-after--p\"\u003e\n Many recommendations were aimed at categorizing information — easily seeing repos, listing popular projects, and being able to see what projects federal agencies are working on. Our users suggested having a featured projects section, or grouping projects so that they can easily see what is most relevant to them. Others recommended a dashboard that shows languages, schema, agency contributions, or a word cloud of popular tags used in repositories.\n\u003c/p\u003e\n\u003ch2 id=\"f52c.graf.graf--p.graf-after--p\"\u003eEase of Use\u003c/h2\u003e\n\u003cp id=\"3c57\" class=\"graf graf--p graf-after--p\"\u003e\n Other users made recommendations that would make the platform easier for them to use and incentivize them to come back. An example would be the ability to bookmark a project for a later date. One user suggested having his own profile on Code.gov or a byline that links to all his projects so he could use it when applying to his next job. Some users also thought the ability to communicate with Code.gov project owners would add value.\n\u003c/p\u003e\n\u003cp id=\"4da4\" class=\"graf graf--p graf-after--p\"\u003e\n Our users also helped us identify challenges and barriers to success. Some users did not know who within their organizations was responsible for implementing the Federal Source Code Policy and how to submit their open source projects for consideration. Some shared that there were some in their organizations who had misconceptions around security and open source. Finally, we identified long approval processes at some agencies to post an open source project to a repository.\n\u003c/p\u003e\n\u003ch2 id=\"96c5.graf.graf--p.graf-after--p\"\u003eWhat’s Next\u003c/h2\u003e\n\u003cp id=\"331d\" class=\"graf graf--p graf-after--p\"\u003e\n Overall, a year after the Federal Source Code Policy was announced, our users continue to come to Code.gov to find reusable government code for their projects. That’s because Code.gov is growing into the nation’s primary platform for sharing and improving government software.\n\u003c/p\u003e\n\u003cp id=\"0c5a\" class=\"graf graf--p graf-after--p graf--trailing\"\u003e\n Want to make sure your voice is heard for the next leg of our journey to sharing America’s code? Join our \u003ca class=\"markup--anchor markup--p-anchor\" href=\"https://bit.ly/2pnRlYN\" target=\"_blank\" rel=\"nofollow noopener\"\u003eCode.gov mailing list\u003c/a\u003e and follow us on Twitter (\u003ca class=\"markup--anchor markup--p-anchor\" href=\"https://twitter.com/CodeDotGov\" target=\"_blank\" rel=\"nofollow noopener\"\u003e@CodeDotGov\u003c/a\u003e) to receive the latest updates and calls for user interviews.\n\u003c/p\u003e\n"} ] }