No Amazon HQ2

[rockycodes]

What problem are we trying to solve?

Keep Amazon HQ out of NYC

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

NYC residents, especially those living and working in and around Long Island City.

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

https://nypost.com/2018/12/12/amazon-workers-threaten-to-unionize-over-hellish-working-conditions/ https://www.vanityfair.com/news/2018/06/amazon-seattle-repeal-head-tax-homelessness

What help is needed at this time?

Engineers and designers.

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

Solidify wishlist and get started on the site!

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

rockycodes@protonmail.com

---

Project management

Checklist for ACTIVE projects :fire:

Let's get this project started! When this idea starts taking off, the Progressive HackNight 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:

• [ ] Update your project at least once a month. This can be either an update on this issue, a ping in the project-ideas channel, rsvp-ing to hacknight, or a conversation with one of the organizers managing project progress (the one listed in the channel topic).
  • 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 nobody hears from you at all in more than one month, we may mark it as abandoned so that others can pick up this idea and run with it.
• [ ] Create a GitHub repository and Slack channel for work.
• [ ] 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.
  • Note: You can also allow collaborators outside of your team and give them more limited access.
• [ ] 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.

If you get stuck at any point, feel free to reach out to the leadership team in the slack channel or with an email to organizers@progressivehacknight.org or come find an organizer at a HackNight. We're here to help bring great ideas to life!

[rockycodes]

Neighbors Beyond Amazon was successful in blocking the development of HQ2 in LIC! This happened before we were able to get the website up and running, but overall this project was moving in a really great direction and we were able to produce work quickly and effectively. The Coalition was impressed by our organization and momentum. Here are some reflections on what worked well and what could have been improved while working on this project:

What worked well:

• First of all, the existence of Progressive Hacknight! It was clear from the first conversation that it made sense for Progressive Hacknight to "own" the production of the website since we already have the infrastructure and talent pool to support a quick turnaround.
• Once the project was established, we worked hard to clarify division of labor upfront which allowed people to be autonomous and empowered to contribute. We wrote out clear tickets and had them ready for folks to work on when they asked.
• We took comprehensive notes during meetings and quickly followed up with new people who expressed interest with a concrete way that they could contribute. We posted meeting notes publicly in Slack so folks could catch up if they missed the meeting.
• Rapi's close partnership with the Coalition provided a good flow of information between our working group and the Coalition when we needed guidance and/or had status updates. It was easy to get the answers we needed to move forward.

  What could have been improved:

• Comprehensive site design from the beginning! It took us awhile of fiddling with CSS and asking for feedback before we realized we needed a designer to mock up a comprehensive design! In the future I would include this from the start.
• Having multiple leaders (Rocky, Chris, Rapi) can create confusion around who is responsible for what. We could have done a better job of communicating in advance about the plan for work nights to make sure we were all on the same page.