Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BASTA Tenant File App #149

Open
8 of 17 tasks
lizard12995 opened this issue Nov 21, 2019 · 7 comments
Open
8 of 17 tasks

BASTA Tenant File App #149

lizard12995 opened this issue Nov 21, 2019 · 7 comments
Milestone

Comments

@lizard12995
Copy link

lizard12995 commented Nov 21, 2019

What problem are you trying to solve?

Tenants, especially low-income tenants, and advocates need to be save and organize records related to units and complexes.
Records include photos, receipts, the lease terms, notes from the landlord, fees/fines, and incident reports. We're looking for an accessible platform designed for those that BASTA works with -- easy to text or upload in, making metadata clear, and with flexible security settings.

That would be version 1.

Who will benefit (directly and indirectly) from your project?

For later versions:
Eventually, we'd also like to be able to auto-generate forms and complaints for repair requests and code complaints.
Include nudges/to-do lists to let tenants and others know when to submit records or take other actions.
Incorporate Appraisal District and Census datasets.
Display data publicly on a map / something visually appealing.

Who will benefit (directly and indirectly) from your project?

Tenant organizers and tenants facing gaslighting, neglect, or abuse by landlords.

What other resources/tools are currently serving the same need? How does your project set itself apart?

Justfix.nyc creates tech to help tenants, but only for those residing in New York City. PDF checklist for Texans is here. Other big PDF handbooks also exist.

Where can we find any research/data available/articles?

Audrey McGlinchy writes about housing, zoning, and eviction in Austin. This recent article discusses ways in which tenants are taken advantage of with mandatory fees.

What help do you need now?

We're relatively new to legit web development, so we need help with...everything! We want to think through the most reasonable way to get this set up in stages -- first being very simple, then building out from there.

What are the next steps (validation, research, coding, design)?

How can we contact you outside of Github(list social media or places you're present)?

@e_shackney on twitter


  • Create this idea issue
  • Flesh out the who, where, and what questions above
  • Start the conversation about this idea on Slack
    Find us here: #p-tenant-file-app

Checklist for ACTIVE projects 🔥

Let's get this project started! When this idea starts taking off, the Projects Core Team will start helping this project's lead(s) out with project management and connecting you to resources you may need. To get there, please complete and check off the following:

  • Post an update at least once a month to this issue. Use BASEDEF for ideas, but it's ok even if your update is just "nothing new happened this month" or "we saw a small increase in traffic to our app this month". If there's no activity for two months, that's no problem, life happens. We'll just label this as backlog so others know you'll get back to it when you have the time. If nobody hears from you at all in more than two months, we may mark it as abandoned so that others can pick up this idea and run with it.
  • Take 30 minutes to complete Open Leadership 101
  • Create a GitHub repository. Ask for help setting up permissions if you want your repository to be within the Open Austin Github organization.
  • Create a README file in your project repository. This file should help newcomers understand what your project is, why it's important, and kinds of help you're looking for.
  • Create issues to describe each task that you plan to do or need help with and how a contributor can get started on that task. You might start and stop a lot, so consider issues as your to-do list.
  • Create a team for your core contributors
    • This will make it easier for you to manage your github repo access. People on a team have the same level of access. Admin access will allow your trusted contributors to make changes as needed.
    • You can remove and add people to your team as needed.
    • View some of our teams: https://github.com/orgs/open-austin/teams
    • Note: You can also allow collaborators outside of your team and give them more limited access.
  • Create a user group in Slack so you can "@" your core contributors all at once, without bothering other people who use the Slack channel. You'll need permission from a Slack admin, so just mention @Leadership on Slack to get this set up.
  • Create a Google Drive, Dropbox, or other cloud storage to share larger files. Github and Data.World are good for code and data, respectively, especially when you need version control. But they're not good for very large files, documentation, articles, etc. A cloud storage option will allow you to easily share, create, and collaborate on documents with your team and help organize ideas and thoughts.
    • Doing this early on can help your team stay organized and to onboard new contributors who wouldn't have access to files you all have shared over email.

Checklist for FEATURED Projects 🎉

To have your project FEATURED on Open-Austin.org, complete the following documentation. In past projects, well-documented featured projects have more contributions than other projects.

If you get stuck at any point, feel free to reach out to the leadership team on Slack by adding @Leadership to your message. We're here to help you make real changes to our city.

@Woodley
Copy link

Woodley commented Nov 22, 2019 via email

@mscarey mscarey mentioned this issue Nov 22, 2019
17 tasks
@mscarey mscarey changed the title BASTA Tenant File App 2 BASTA Tenant File App Nov 22, 2019
@lizard12995
Copy link
Author

@Woodley Absolutely! We'll add this to our agenda to discuss. I'm wondering how you feel reporting should be integrated into this project -- are we asking tenants to self-disclose, or would that be information we could keep private and only legal advocates would access it? Or, are you suggesting that we ensure that this program is accessible to people with disabilities? (which I definitely want to be the case!!)

@Woodley
Copy link

Woodley commented Nov 23, 2019 via email

@mscarey mscarey added this to the Active milestone Dec 2, 2019
@mscarey
Copy link
Contributor

mscarey commented Dec 5, 2019

Here's an organization that seems to have made a lot of progress on a similar problem https://gbls.org/MADE

@lizard12995
Copy link
Author

Hi @Woodley - these are super important aspects to keep in mind! Thank you. We're gathering our thoughts now and will be able to provide a bit more direction after this week. @mscarey, this is good, and I've met Quentin (who was the muscle behind this) at a legal services IT conference. Their approach is more of a guided interview, and very focused on eviction. We'll have some materials to explain how we want to simultaneously build power, not just deliver a service.

@lizard12995
Copy link
Author

Diagrams - Scanned.pdf

See our original thought process in these diagrams :)

@geworfenheit
Copy link

@lizard12995 Hey Lizzie, this is Aaron R!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants