1aa0b15c8c
* Move all Diaspora-specific javascripts to app/assets/javascripts * Move all vendored javascripts to vendor/assets/javascripts * Add the appropriate Sprockets require directives to make sure everything gets included in the right order * Remove Jammit dependencies * Fix all templates that were using Jammit's include_javascripts helper * Add handlebars_assets gem for compiling Handlebars templates * Move all Handlebars templates to app/assets/templates and rename from .handlebars to .jst.hbs (this is to keep them in the same global JST namespace that they were in under Jammit) * Add public/assets to .gitignore since these files can and should be re-generated by Heroku or Capistrano during each deploy * Fix a few Handlebars templates that were looking for images in the wrong location (I'm sure there are others, but it's late) * Configure application.rb to precompile all javascript and css assets that were compiled by Jammit in the Rails 3.0 code |
||
|---|---|---|
| app | ||
| config | ||
| db | ||
| features | ||
| graphics | ||
| lib | ||
| public | ||
| script | ||
| spec | ||
| vendor/assets/javascripts | ||
| .foreman | ||
| .gitignore | ||
| .gitmodules | ||
| .pairs | ||
| .rspec | ||
| .rvmrc | ||
| .slugignore | ||
| .travis.yml | ||
| AUTHORS | ||
| Capfile | ||
| config.ru | ||
| COPYRIGHT | ||
| FederationProcfile | ||
| Gemfile | ||
| Gemfile.lock | ||
| GNU-AGPL-3.0 | ||
| Guardfile | ||
| Procfile | ||
| Rakefile | ||
| README.md | ||
| redis-integration1.conf | ||
| redis-integration2.conf | ||
| status-with-photo-backdrop.handlebars | ||
Diaspora
Welcome to the Diaspora project, the privacy aware, personally controlled, do-it-all, open source social network. Diaspora Project
Diaspora is currently going through a huge refactoring push, the code is changing fast! If you want to do something big, reach out on IRC or the mailing list first, so you can contribute effectively <3333
THIS IS ALPHA SOFTWARE AND SHOULD BE TREATED ACCORDINGLY. IT IS FUN TO GET RUNNING, BUT EXPECT THINGS TO BE BROKEN.
TL;DR
Are you a user?
You can get an account on many Diaspora pods, or sign up for an invite at the pod run by the original development team at https://joindiaspora.com
Are you a developer?
Read on for how to get started.
We need you to fill out a contributor agreement form before we can accept your patches. This dual license agreement allows us to release limited pieces of Diaspora under the MIT license. You can find it here.
Installation Guides
We have guides for pod admins (called podmins) here.
Contributing to Diaspora
Information on contributing to the Diaspora project can be found on the wiki. You can check our Issue tracker (bugs), learn how we work with git, and become more familiar with our system
Here are a few good places to start:
- Take a look at the issue tracker and pick a bug. Write a spec for it, so it's easy for another developer to fix it.
Catches must be tested, and all your tests should be green, unless you're marking an existing bug, before a pull request is sent. Unit tests should be in Rspec, Javascript tests should be in Jasmine, and integration tests should be in Cucumber.
Please make your changes in a branch to ensure that new commits to your master are not included in the pull request, and to make it easier for us to merge your commits.
Please do not rebase our tree into yours. See here for when to rebase.
Resources
Here is our bug tracker and our roadmap. Also, you can find see what the core team is up to here.
Ongoing discussion:
- Diaspora Developer Google Group
- Diaspora Discussion Google Group
- #diaspora IRC channel (join via the web client)
- #diaspora-dev IRC channel (join via the web client)
General info and updates about the project can be found on our blog, our devblog, and on Twitter. Also, be sure to join the official mailing list.
If you wish to contact us privately about any exploits in Diaspora you may find, you can email exploits@joindiaspora.com, corresponding public key (keyID: 77485064).