Powerline is an open, social, streamlined mobile app and web platform that makes it easier for people to change their world through individual or collective action at the local and global levels. Think of it as Twitter/Yammer for democracy or as a community network for civil society (a.k.a. the non-profit and activist space).

Learn more through the Detailed Overview. For new contributors and general questions, check out the FAQ

Powerline is now open source under the AGPL license for development with the Assembly community. Powerline runs as a SaaS application – there is a free “mission” tier as well as paid upgrade plans. With the Assembly platform, all generated revenue from the product is funneled into the project and it's contributors. After subtracting hosting costs and other expenses, 10% goes to Assembly as a fee and the rest is distributed back to project contributors via Assembly based on their ownership (determined by their project contributions).

By contributing to Powerline, you’re making a difference for a fun open source project with a real world-changing mission and, unlike traditional OSS, you’re earning your fair share of the profits, too. To get started simply join us on our Assembly Project Page.

• Get your encrypted dev.tar.gpg from team leader and put it to directory 1 level upper than directory where this project placed (../hosts/dev.tar.gpg)

• Copy build.xml.dist there too:

cp build.xml.dist ../build.xml

• And decrypt dev credentials:

phing unpack-deployment-target -Dtagret.hosts=dev -Dpassphrase=PASSPHRASE

• Copy files to proper location:

cp ../hosts/dev/config/parameters.yml ./backend/app/config/parameters.yml

vagrant up

vagrant ssh

Run next commands to setup dev environment fixtures:

php app/console doctrine:database:create
php app/console doctrine:schema:create
php app/console doctrine:fixtures:load

Although we are hard at work building our new Leader experience, admin.powerli.ne serves as our interim Leader portal. It is built on the symfony framework. At this point, few if any Pull Requests will be merged for symfony backed Leader work. Please see the Powerline Web App or contact us before moving forward.

/vagrant/backend/app/console cache:clear -e=prod
/vagrant/backend/app/console cache:clear -e=dev
/vagrant/backend/app/console cache:clear -e=test_behat

/vagrant/backend/app/console assetic:dump -e=prod
/vagrant/backend/app/console assets:install --symlink

vagrant ssh
cd /vagrant/backend/
bin/behat -p admin
bin/behat -p api

• The config for jMeter (url should be modified according to your local (test) server: backend/src/Civix/LoadBundle/Resources/jmeter/CivixLoadTesting.jmx

• Fixtures (db will be dropped!):

backend/app/console load:scenario --10000
backend/app/console load:scenario --100000
backend/app/console load:scenario --1000000

Want to help build an amazing product? Check out our Powerline Assembly Project for all the latest bounties and roadmap. We follow the GitHub Flow model so pull requests are easy! Although you don’t have to create a feature branch, it helps streamline the merge process.

Our branching strategy is straightforward and well documented . For a detailed look please see A successful Branching Model.

• develop - Our main branch for all features
• master - Production ready code
• feature - Your feature branch (temporary branch)
• release-, hotfix- - temporary branches

Work in progress. Please help us build our documentation! Check out all of our documentation for more details include our API PowerlineApp Documentation.

When your code is ready and on GitHub, create a pull request via the GitHub UI. Once your pull request is created, it is best practice to go to the bounty on Assembly and submit your work with a link to the pull request. If the feature you created does not have a bounty created yet, simply create one explaining what you've done and why. The core team will award the bounty after confirming and merging the contribution. We recommend you include the appropriate unit tests to make things easier for everyone.

After the bounty or work is submitted, add a comment to the pull request with a link to the bounty. This keeps the code review and merging process quick and easy.