-
Notifications
You must be signed in to change notification settings - Fork 9
Add contributors to code.json schema? #16
Comments
Hi @lukefretwell . That's a great suggestion! I'll make sure to discuss that with the team and update this issue when we have an update. Tagging @froi for his visibility. |
Thanks for the feedback @lukefretwell and thanks for the ping @DanielJDufour We have all our schemas in our code-gov-data repo. We currently have a release candidate schema version, schema-2.0.1-rc-2.json. We are accepting feedback on it and any other features you would like to see our schemas handle here: GSA/code-gov#15. The release candidate has an additional_information field that serves as a place for our users to supply us with additional metadata they feel should be included. We would love to have your thoughts on this. Would this work or do you think it should be a specific field? If you have any other feedback on our projects, processes, or schemas but are not sure where it would fit you can create a new issue on our code-gov repo. |
@marctjones ☝️ Thank you @froi @DanielJDufour! Marc and I are reviewing this together, so he might have thoughts, as he's more 🤓 than me. The UX/UI in me just thinks, "it would be so nice to see some faces." :-) So, I'm not the best person to comment on schema/fields. My hunch is that would work, but also seems like it might require more data manipulation for the agency code.json maintainer? |
@lukefretwell for some agencies it would. Not all agencies use tools like Gitlab or Github so it might be a bit labor intensive for them to include actual contributors. That being said I don't think it's a bad idea to have an optional field where they can give a shout out to people that have worked to make the project succeed. The team will brainstorm on it and present it to gauge interest. In the next couple of weeks, we are going to roll out some new features that fetch data from Github and it includes the contributors to the projects. We're still tweaking it and updating the frontend but stayed tuned 😄 |
@froi awesome! Thank you! |
In reviewing the code.json schema, I don't see a 'contributors' fields, which would be great to include as optional, as it could really put a face(s) on the projects and perhaps compelled folks and humanize the code.
Along those lines, would be great to figure out what fields might give the data more of a sense of activity, action. This could make the projects (and code.gov) feel more 'alive.'
The text was updated successfully, but these errors were encountered: