Fork me on GitHub

Fusebox

Volunteers

 

How To Help

 
Fusebox is built and maintained by volunteers, and we welcome anyone who wants to help us out.
 
To help out, please go to our contact form, select "Volunteers" and tell us how you want to help.
 
There are many areas we need help with:
 
Development and Testing
 
Core files
The core files are the heart of Fusebox, and are what makes Fusebox applications work.
 
If you are a strong ColdFusion or PHP developer and would like to help develop and fix the core, please volunteer!
 
People Responsible:
Sean Corfield (ColdFusion core)
Mike Ritchie (PHP core)
Wiki page:
FuseboxCoreFiles
Testing
Testing is a vital part of developing Fusebox, ensuring backwards compatibility with previous releases, and that new features work as intended.
 
Testing can be as simple as downloading the latest cores and running existing applications on them, and seeing if anything in the application is broken. Help in regression testing and automated test builds is also needed.
 
People Responsible:
Barney Boisvert
John Paul Ashenfelter
Wiki page:
FuseboxTesting
Sample Applications
Sample applications are always needed to help people learn different techniques and features.
 
If you would like to help develop some sample apps, check the wiki page and then contact the Team Leaders.
 
People Responsible:
Kevin Roche
Mike Tangorre
Jared Rypka-Hauer
Wiki page:
FuseboxSampleApps
Spreading the Word on Fusebox
 
Marketing
It is important to spread the word of Fusebox to show people what it can do for them, and marketing the Fusebox brand is an important part of this.
 
Helping out can be as simple as purchasing a fashionable "Got Fusebox" T-Shirt, but the Fusebox Team also requires people to help with promoting and exhibiting Fusebox.
 
If you have experience in this area, get in touch with the Group Leader for more details.
 
People Responsible:
Adam Howitt (Group Leader)
Wiki page:
FuseboxMarketing
Case Studies and Success Stories
Case studies can help show how Fusebox has been a success in organisations, and can be a useful tool in convincing management on the usefulness of Fusebox in organizations.
 
If you have a case study or are willing to write one, please contact us.
 
People Responsible:
Jeff Peters
Mike Tangorre
Presenting Fusebox
Presenting on Fusebox at User Groups is a great way to show developers what Fusebox can do and how it can make their development life easier.
 
If you think you've got what it takes to give a presentation on Fusebox, contact the Team Leaders to let them know.
 
People Responsible:
Michael Smith
Simeon Bateman
Wiki page:
FuseboxPresenting
 
Website and Documentation
 
Website
The Fusebox website is the public face of Fusebox, providing people with information about Fusebox, help on how to to use it, and so on.
 
If you would like to help with running the website, download the contributors guide, check the two wiki pages for details of what is involved and where it is going, and then contact us to say how you want to help.
 
People Responsible:
Sandy Clark
Brian Kotek
Wiki pages:
FuseboxWebSite
FuseboxWebsiteVision
Documentation
Documentation helps developers to learn about and extend their Fusebox knowledge, providing explanations of functionality, tutorials, tips and tricks.
 
If you have the skill to explain things in a way that lets people easily understand, then use the Contact Form to tell the Team Leader about how you can help.
 
People Responsible:
Cameron Childress
Mailing List:
Fusebox-documentation-L@teratech.com
Wiki page:
FuseboxDocumentation
Proof Reading
If you are fascinated by words and obsessive about punctuation, why not help the Fusebox Team in ensuring documentation and website articles are typo-free and have perfect grammar.
 
People Responsible:
Sandy Clark
Brian Kotek
Mailing List:
Fusebox-proof-reading-L@teratech.com
Wiki page:
FuseboxProofreading
Articles
Written articles are a great way to inform people about Fusebox concepts, and to give ideas about what Fusebox can do.
 
If you would like to write a Fusebox article, take a look at the wiki page for ideas, and then check in with the Team Leaders for details of how to start.
 
People Responsible:
Brian Kotek
Jeff Peters
Mailing List:
Fusebox-write-articles-L@teratech.com
Wiki page:
FuseboxArticles
Others
 
Fusebox LifeCycle Process
The Fusebox LifeCycle Process (FLiP) is a project management methodology for producing repeated software project successes.
 
Whilst FLiP grew from early Fusebox best practises, it can also be used for non-Fusebox projects too.
 
People Responsible:
Michael Smith
Fusedocs
FuseDocs is an XML vocabulary for defining responsibility, properties, and I/O of a code module. Whilst it grew out of Fusebox, it is not restricted to applications implementing Fusebox.
 
People Responsible:
Sandy Clark
Mailing List:
Hosted on Yahoo
Wiki page:
FuseDocs
CFEclipse Integration
CFEclipse is the top ColdFusion editor, and as such it is important that Fusebox can work well with it. If you use the CF Frameworks Explorer plugin for CFEclipse, you can help with ensuring Fusebox is integrated and works well.
 
People Responsible:
Kevin Roche
Scaffolding
Scaffolding allows developers to quickly build an application with CRUD facilities, which can then be extended into more complex forms.
 
If you are interested in helping with the Fusebox Scaffolding plugin, take a look at the scaffolding code in the SVN repository then get in touch with Kevin Roche.
 
People Responsible:
Kevin Roche
Peter Bell
Wiki page:
Scaffolding
 
If you are interested in helping out in any way, please feel free to contact us.