Skip to content

Instantly share code, notes, and snippets.

View laveshaparker's full-sized avatar

La Vesha Parker laveshaparker

View GitHub Profile

Keybase proof

I hereby claim:

  • I am laveshaparker on github.
  • I am vesha (https://keybase.io/vesha) on keybase.
  • I have a public key ASA7BBasaTCS2PmevGdzEO-7x5pxcvfvMEn3kg-g9MY0Hgo

To claim this, I am signing this object:

I’m on VTO today! This is what I’m looking at doing:

  • Send follow up notes to steering committee from Monday’s meeting
  • Send feedback to Emily about last night’s event
  • See about getting Reboot Dem members on our email list
  • Send follow up thank you email to attendees
  • Figure out theme for next hackday (election? Immigrant rights?), start reaching out to projects (Annie I got you!)
  • Research Venmo for nonprofits
    • Can't use Venmo for nonprofits, in strictly closed beta--likely not working on it anymore
    • PayPal for Nonprofits is another option though!
  • 2.2% + $0.30 per domestic transaction.*

How to get your project rolling at Progressive HackNight

Progressive HackNight exists to make great ideas happen. Sometimes, we see some great ideas proposed at the start of the hacknight, but not many people work on them or stay involved after the night. This can be caused by a multitude of things, but we can reduce the chance of it happening by taking a look at how you can best set yourself up for success, no matter what stage your project is in.

We’ll start with a few basic suggestions that apply to all projects (regardless of what stage of ideation or development they’re in). We’ll later look at what changes you can make as your project develops to improve its effectiveness at the hacknight.

The basics of making your project fun and easy to contribute to

Make your project Open Source!

We absolutely ❤️ open source at Progressive HackNight, and it's easier to contribute to, here and outside the community, as opposed to propriety software.

Know what problem needs to be solved

let mapleader=";"
" ----------------------------------------------------------------------------
" Auto-reload vim after changes made to vimrc
" ----------------------------------------------------------------------------
augroup myvimrc
au!
au BufWritePost .vimrc,_vimrc,vimrc,.gvimrc,_gvimrc,gvimrc so $MYVIMRC | if has('gui_running') | so $MYGVIMRC | endif
augroup END