-
Notifications
You must be signed in to change notification settings - Fork 102
Talk to us
We want to make it super-easy for Blueflood users and contributors to talk to us and connect with each other, to share ideas, solve problems and help make Blueflood awesome. Here are the main channels we're running currently, we'd love to hear from you on one of them:
[Blueflood Google Group] google-group
The Blueflood Google Group (aka blueflood-discuss) is a good first stop for a general inquiry about Blueflood or a specific support issue (e.g. trouble setting Blueflood up). It's also a good forum for discussions about the roadmap or potential new functionality.
#blueflood
We're big fans of IRC here at Blueflood. We have a #blueflood channel on Freenode - stop by and say hi, you can even use [Freenode's webchat service] freenode-webchat so don't need to install anything to access it. Soon, this channel will be linked to our GitHub - so you can see new issues, merged pull requests and so on as they happen.
[Blueflood issues] issues
If you spot a bug, then please raise an issue in our main GitHub project (rackerlabs/blueflood). Likewise, if you have developed a cool new feature or improvement in your Blueflood fork, then send us a pull request!
If you want to brainstorm a potential new feature, then the Blueflood Google Group (see above) is probably a better place to start.
[[email protected]] community-email
If you want to talk directly to us (e.g. about a commercially sensitive issue), email is the easiest way.