To help public defenders better serve their clients, Open Sentencing shows racial bias in data such as demographics providing insights for each case
License: Apache License 2.0
The main repository for information on Call for Code for Racial Justice projects that are hosted by The Linux Foundation. Learn more about the history and context of each in this Black History Month blog post.
Please see CONTRIBUTING.md for general project contribution guidelines. Each project may also have its own Technical Steering Committee.
If you'd like to join our weekly community meeting, comment below and tag @demilolu.
Meeting topics:
In the aggregator, the following options for race are as below. Are these the correct values? For example, White [Hispanic/Latino] is confusing.
Get a clear list of the which race options are valid and how they should be displayed.
Sentencing for various charges might differ by county, etc. Thus granularity of location is needed to better assess potential racial bias in sentencing.
Gather new data sources for sentencing data from various counties, states.
Manual cloud deployments are tedious.
Once we've validated our manual deployments we would like to have CI/CD to deploy easily to cloud across all Open Sentencing repositories.
Add github actions for:
Related Issues:
Thank you @sforsyth089 and @joannhh for finishing #54. The team decided to create a table or add a list in the assets readme describing the content of the folder. That will help whoever comes to the assets folder for the first time. We should also add a link to the assets folder in the main project readme.
Add a list of files in the assets folder to the assets readme
Add a list of files in the assets folder to the assets readme
Assigning to @joannhh
Developers learn best by example and demonstration. We would like you to create a tutorial, or lab, for new developers to run through and get the application running in a sandbox environment.
See example lab from Legit Info project.
Lab that walks learner through Open Sentencing solution and sets up dependencies to run the application.
Functioning lab in the sandbox environment
We want users to identify whether they are the office staff or public defender. Then we will give access based on who is utilizing the tool.
We need roles in Excel. Then across Columns - put entitlement (Read Only, Update Only, Etc).
Try two stories read & write, and read only. Need at minimum. Can see from there is there are other things.
First do the write up on access and who sees what for the Story
Then team members can do the programming part of it.
Break down incremental (maybe MS cohort can do some of it)
Create a Pull Request Template for Open Sentencing
Add a .md file to the .github/ folder to create a new pull request template
copy the text in the following link: https://raw.githubusercontent.com/Call-for-Code-for-Racial-Justice/Hacktoberfest/main/.github/pull_request_template.md
Create a new file in the Open Sentencing .github folder
Paste the copied text from above into file
name the file: pull_request_template.md
commit the change to your branch and create a pull request
A design refresh involves style updates that don’t impact the underlying structure or functionality of the interface. Think updated font stacks, revised color palettes, or a new style direction for supporting assets. These types of changes breathe new life while still maintaining familiarity with users.
Develop a plan to give the website a facelift to modernize the look and feel and functionality of the website. There are many examples of opensource systems you can use around user experience and interaction design.
Many CFCFRJ solutions use IBM's Carbon Design System which follow the IBM Accessibility Checklist based on WCAG AA, Section 508, and European standards. You can investigate other design options here.
Develop wireframes that represent the experience and clickthroughs to achieve the tasks already implemented on the site. Not all changes need to be high fidelity - hand drawn or design software like Figma can suffice as a representation of the experience. Alternately to a complete design change you can benchmark with smaller releases that can be tested with future user groups and receive ample opportunity to warm your audience to upcoming changes, gauge initial reactions, and gives greater leeway for addressing issues as they arise.
The website should reflect a more modernized application that allows for visitors to accomplish the same functionalities as before, but more intuitively and with delight. The app should also reflect Level 1 accessibility guidelines based on the IBM Equal Access Toolkit
Read more about Accessibility Testing #53
Readme file needs to be edited to be consistent with the Call for Code starter kit.
Software, whether it is web enabled or not, has the ability to function and behave in a way to help those who have certain disabilities. For example, by incorporating certain bits of code, a blind user can navigate an application and hear a screen reader recite every position their keyboard focus lands. Incorporating other bits of code can help a person who has very low vision to see the screen content; or a person who cannot use a mouse; or a person who is deaf. Even a slide deck used in a presentation can be made accessible; for example, making sure the text colors have a sufficient contrast with the background color, or adding descriptive text into the properties for each image used.
IBM's Equal Access Toolkit provides three levels of achievement for accessibility requirements:
Level 1: Essential requirements with high user impact, normally with the least investment. These cover safety, color contrast, text alternatives, navigation, operation, and errors.
Level 2: Adds to Level 1 the next-most important requirements that enable more users to fully use a product. These include pointer interaction, use of color, text style, auto-playing content, and responsive design.
Level 3: The full set of IBM accessibility requirements that includes the Web Content Accessibility Guidelines (WCAG), US Revised 508, and European EN 301 549 requirements.
WCAG 2.1: Web Content Accessibility Guidelines 2.1 extends WCAG 2.0 and was published as a W3C Recommendation on 05 June 2018. Many regulations reference WCAG 2.1 Level A and AA Success Criteria.
US 508: US Revised 508 Standards provide requirements for information and communication technology (ICT) in the federal sector.
EN 301 549: Accessibility requirements for ICT products and services, V3.1.1 sets requirements to meet European accessibility regulations.
Note: The Equal Access Toolkit provides guidance only on WCAG requirements. It divides tasks and considerations by role involved in each phase into these three levels of progression for web applications.
At minimum, complete Level 1 for accessibility testing for Open Sentencing
Step 1: Run verification test for Open Sentencing deployment (you can run a test on your local machine)
You can verify with automated tools, manual inspection, and with a screen reader. It is recommended that you do all three in the given order. It is counterproductive to continue to manual testing until the automated tool produces a report free of Violations or issues that Need Review. Once the automated test returns a clean result, move on to manual tests.
Step 2: Review violations and needs review
The IBM accessibility requirements and automated tools are numbered and aligned to the international standards, so it makes gathering and recording the results simple. Once you have a list of items that need attention, create a plan of action to resolve issues. Be sure to capture what elements are design, UX/UI, or developer focused activities
Step 3: Resolve violations and needs review items needed to achieve Level 1 accessibility for Open Sentencing
You can review Level 1 requirements by setting the filter to Level 1 on the lefthand side of the screen. Please ensure all of the boxes for Standards and Technology are checked
See Level 1 accessibility testing requirements
Open Sentencing has existing documentation on frontend application and backend services. We would like you try out the application and suggested improvements to the documentation.
During this cohort your team members will also be making updates to the Open Sentencing application. We would like to document these new changes in our documentation as well.
repositories:
Adding new documentation
Related Issues:
Fixing existing Documentation
Our code currently lacks unit testing, which is needed for test driven development practices: easy debugging, functional testing, etc.
Provide unit tests for various Open Sentencing repositories:
Open Sentencing needs to improve its web accessibility to be more inclusive of our end-users.
To this end in this project we'd like to:
Create a Bug Report Template for Open Sentencing
Add a .md file to the Github Issues Templates to create a new template
copy the text in the following link: https://raw.githubusercontent.com/Call-for-Code-for-Racial-Justice/Hacktoberfest/main/.github/ISSUE_TEMPLATE/bug-report-template.md
Create a new file in the Open Sentencing folder: .github/ ISSUE_TEMPLATE
Paste the copied text from above into file
name the file: bug_report_template.md
commit the change to your branch and create a pull request
Each of our repos have a set of issues that we need help with, please refer to these repos here. Also, please make sure to slack us with questions
Slack: https://app.slack.com/client/TAHDYCZ6H/C01DJ8J1QP2/thread/C01D7MS0G0K-1603572137.017300
UI: https://github.com/Call-for-Code-for-Racial-Justice/Open-Sentencing-UI/issues
Aggregator: https://github.com/Call-for-Code-for-Racial-Justice/Open-Sentencing-Aggregator/issues
Open Sentencing Model: https://github.com/Call-for-Code-for-Racial-Justice/Open-Sentencing-Model/issues
Our app currently lacks the data we need to be able to provide public defenders with statistics they need on
We need to gather and specify our data requirements for the open sentencing app.
Standards we believe this issue must reach to be considered complete and ready for a pull request. E.g precisely all the user should be able to do with this update, performance requirements, security requirements, etc as appropriate.
Create issues to track ideas, enhancements, tasks, or bugs. Use the default github labels good first issue and help wanted to flag issues that community can help with.
| Label | Description |
|---|---|
| bug | Indicates an unexpected problem or unintended behavior |
| documentation | Indicates a need for improvements or additions to documentation |
| duplicate | Indicates similar issues or pull requests |
| enhancement | Indicates new feature requests |
| good first issue | Indicates a good issue for first-time contributors |
| help wanted | Indicates that a maintainer wants help on an issue or pull request |
| invalid | Indicates that an issue or pull request is no longer relevant |
| question | Indicates that an issue or pull request needs more information |
| wontfix | Indicates that work won't continue on an issue or pull request |
Stacy will find 1-2 cases and write the user stories.
Once user stories are in place... we'll have a
1.5 Hour meeting with this team to go through UI/data connection. @wisdomkeeper @siranjujugi @upkarlidder
Overall, we've done work on finding sentencing data. It varies by County, State, Federal. Sometimes race data isn't available, sometimes it is. Sometimes it's not accessible readily on websites, sometimes it is. We'd like a concise write up about our challenges to bring to attention of policy groups that could help draw attention to this. Without great data, we are going to be limited in where our solution can be used.
Complete a write up of our experience. Cite places that did well vs. places that could improve.
Approval by Open Sentencing Team.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
A clear and concise description of what you want to happen.
Description of the development tasks needed to complete this issue, including tests,
Standards we believe this issue must reach to be considered complete and ready for a pull request. E.g precisely all the user should be able to do with this update, performance requirements, security requirements, etc as appropriate.
Create a Documentation Template for Open Sentencing
Add a .md file to the Github Issues Templates to create a new template
copy the text in the following link: https://raw.githubusercontent.com/Call-for-Code-for-Racial-Justice/Hacktoberfest/main/.github/ISSUE_TEMPLATE/documentation-template.md
Create a new file in the Open Sentencing folder: .github/ ISSUE_TEMPLATE
Paste the copied text from above into file
name the file: documentation_template.md
commit the change to your branch and create a pull request
We woud like to be able to translate what users see in the future. Enabling the repos for translation is step 1 of that.
Research the possibility of coordinating with https://measuresforjustice.org/ about possible data sources? They don't have current data on their website. Newest seems to be 2017.
Sprint Priorities updated 9/3/21
Done
Tasks
Decision Points
Aggregator redo: net-new : authentication, (Decision made, will keep current one and modify as needed)
Discussion on changing database (from Cloudant - more suitable for big data that's static), with our cases and attorneys we need something dynamic. Move to: DB2? (look like we'll stick with Cloudant for a while)
moving to jHipster vs Liberty (same as above)
Community Decisions
Moving authentication to back-end
switching to be aggregator to be class and not swagger based (Rick has started research week of 9/3)
Blockers
The solution does not have data for all states.
Add a form / information to let users within the interface to know when data is not available. (see Legit Info's solution). Might go at case info screen.
Add a component to the solution that filters by state.
add a case step@wisdomkeeper
Standards we believe this issue must reach to be considered complete and ready for a pull request. E.g precisely all the user should be able to do with this update, performance requirements, security requirements, etc as appropriate.
Sprint Priorities
Tasks
Blockers
Bugs
Decision Points
Community Decisions
Community Requests:
Based on reviewing/implementing updates from the user stories, work on figuring out any data missing or still needed. Document clearly.
Once User Stories put into place, figure out if all data is there or more is needed. Document clearly.
Mark the data going into / out of each step. Document clearly any gaps.
A quick start guide is essentially a series of commands you can run from a "clean" directory to get the basic functionality running.
This will make it easier for new adopters to get started, if they're not already comfortable with Docker.
Links to more detailed setup instructions if needed would be good.
@sforsyth089 created user stories for #52. We need to transfer them to a md file in the main repo.
@wisdomkeeper
The user stories have been copied to the main repository.
New users to Open Sentencing might be a little confused in following the documentation
Suggest updates to documentation
Standards we believe this issue must reach to be considered complete and ready for a pull request. E.g precisely all the user should be able to do with this update, performance requirements, security requirements, etc as appropriate.
Sprint Priorities
New info: Rensselaer Polytechnic Institute offered to help us out. Upkar will talk on Slack/add to the meeting.
merge UI update PRs (@upkarlidder @wisdomkeeper) (UI) Upkar finishing
Unit Testing!!! @RickPoleshuck : all repos:
Related PRs (@upkarlidder to review)
CI/CD for aggregators to deploy easily to cloud (automated deployment) @RickPoleshuck : aggregator/UI
Call-for-Code-for-Racial-Justice/Open-Sentencing-Aggregator#30
Generate swagger from Java classes @RickPoleshuck aggregator
Call-for-Code-for-Racial-Justice/Open-Sentencing-Aggregator#31
App ID authentication for aggregator @yochanah (aggregator) - Call-for-Code-for-Racial-Justice/Open-Sentencing-Aggregator#22 [depends on earlier issue Rick working on- updated in issue]
Shift to aggregator to create dummy data for UI Akilah (aggregator) - Call-for-Code-for-Racial-Justice/Open-Sentencing-Aggregator#32 [dependent on API/back-end] Stacy/Akilah will connect with @siranjujugi
Creating Data requirements that we need @sforsyth089 @joannhh (general) - #29 (comment) [Want to think about better break-ups of tasks] (we are finding lacking data that has race info)
Identify risk considerations goes along with data gathering - #31
Data cleaning and collection work with Hui -#34
Akilah's UI updates: updating actual UI to be similar to prototype PRs here:
new issue for bug for App ID error @wisdomkeeper Call-for-Code-for-Racial-Justice/Open-Sentencing-UI#56
Tasks
Blockers
Bugs
Decision Points
-[x] Update Angular CLI - 12.0.5 ? 9? - Call-for-Code-for-Racial-Justice/Open-Sentencing-UI#51
Carbon Discord chat: https://discord.gg/SYjvP8epkM
Community Decisions
Community Requests:
Deprioritized til demo sites/ are needed/
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
A clear and concise description of what you want to happen.
Description of the development tasks needed to complete this issue, including tests,
Standards we believe this issue must reach to be considered complete and ready for a pull request. E.g precisely all the user should be able to do with this update, performance requirements, security requirements, etc as appropriate.
We need to clearly understand the risks/considerations involved in adding more data to our solution. We'll then determine any follow-ups.
Data Gathering: We'd love your help!
Data.Source.Inventory.Open.Sentencing (1).xlsx
Please go ahead and edit
Anyone of any skill level can help!
Start with brainstorming a list. We can work as a team to take action. Consider a clear tracking spreadsheet or other method to ensure we've identified and cleared all risks.
In researching data, make edits to the Excel sheet. Think about the following to track.
We need to keep looking out for any new risks as we make changes. Need someone to review/comment if we see any news risks in terms of data, licenses, or other ideas.
A write up after someone reviews for risks.
Write up in issue. Approval by a team member.
Once we determine the races that the front-end will show, we need ETL to translate data from each data source.
We'd like to add a greeting bot that provides a comment when a new pull request or issue is made
Use Github Actions to create a greeting bot for new issues and new pull requests in the Open-Sentencing repository.
Learn more about Github Actions here:
greetings.ymlgreetings.ymlRefer to #75 and implement.
A clear and concise description of what you want to happen.
Description of the development tasks needed to complete this issue, including tests,
Standards we believe this issue must reach to be considered complete and ready for a pull request. E.g precisely all the user should be able to do with this update, performance requirements, security requirements, etc as appropriate.
Sprint Priorities
merge UI update PRs (@upkarlidder @wisdomkeeper) (UI)
Unit Testing!!! @RickPoleshuck : all repos:
(manual deployment) @upkarlidder : aggregator/UI:
Call-for-Code-for-Racial-Justice/Open-Sentencing-Aggregator#29
CI/CD for aggregators to deploy easily to cloud (automated deployment) @RickPoleshuck : aggregator/UI
Call-for-Code-for-Racial-Justice/Open-Sentencing-Aggregator#30
Generate swagger from Java classes @RickPoleshuck aggregator
Call-for-Code-for-Racial-Justice/Open-Sentencing-Aggregator#31
App ID authentication for aggregator @yochanah (aggregator) - Call-for-Code-for-Racial-Justice/Open-Sentencing-Aggregator#22
Shift to aggregator to create dummy data for UI Akilah (aggregator) - Call-for-Code-for-Racial-Justice/Open-Sentencing-Aggregator#32
Creating Data requirements that we need @sforsyth089 @joannhh (general) - #29 (comment) (This is a group activity that will include many people)
Done
Under Review
Tasks
Blockers
Bugs
Decision Points
Community Decisions
Community Requests:
We will have to reach out to multiple entities for data. Ideally we have an easy to use/adjust started document for this purpose.
A template email for getting in touch with states/ etc explaining our needs.
Team approves and represents our project well.
THINGS TO CONSIDER:
Side comment: Is there any IBM budget for this at all?
@Sabine-Justilien We want to talk about the items above with you to think about enhancing our data collection.
After enabling the repos for translation, we can pull out the hardcoded English strings and put them into a translated strings file.
Depends on #15 - we have to choose the open source translation library we want to use first. Then the intent of this issue (#16) is to pull all of the English strings into a file in whatever format that library uses.
Then in #17 we can get that English file translated.
After #16 is working with English strings, we need translated strings for other languages.
Getting started with IBM ID SSO can be difficult for non-IBMers.
We should add support for other authentication providers.
The UI and Aggregator would need to both support the same providers to get this working end to end.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.