Skip to content

Anti-Corruption March Website #41

@anticorruptionmarch

Description

@anticorruptionmarch

What problem are we trying to solve?

Hey everyone! Thanks for having Jacqi and I at your Hacknight last month. We are organizing an Anti-Corruption March, uniting a coalition of people and organizations, to call upon the US government to be accountable to all people in the nation, and for the people to hold the government responsible for its decisions.

We are enlisting your aid to ensure the success of the anti-corruption movement by jump starting our online presence. With this website, people can become informed on the issues and have access to comprehensive action items that encourage civic engagement.

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

Citizens of the United States and other countries willing to participate in the anti-corruption movement.

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

https://docs.google.com/document/d/1PgD0jKrs3CW_Utve2LsKl7p9zMxr5ITZncBI74TneKY/edit?usp=sharing

https://github.com/anticorruptionmarch/anticorruptionmarchsite

What help is needed at this time?

Website development: APIs, interactive maps, revision on website layout and design.

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

Coding, design.


Project management

Checklist for NEW ideas 👶

Hey, you're official! You're now part of the growing Progressive HackNight community. Here's a few things to get started (a couple you've probably already done).

  • Create this idea issue
  • Flesh out the who, where, and what questions above
  • Join our Slack
  • Join the #project-leads channel.
  • Ping an organizer to get started (The organizer in charge of onboarding new projects will be listed in the channel topic)

Checklist for ACTIVE projects 🔥

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 [email protected] or come find an organizer at a HackNight. We're here to help bring great ideas to life!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions