Help the Project

From Flouzo

If you wish to contribute to the project or take part in the alpha-test, you can have some bearing on a whole range of elements. No need to be a developer to help!

So, if you are looking for a job or if you work on a freelance basis, don’t forget to have a look at the Jobs page, and feel free to send us a résumé.

[edit] Help the project be known

Either in real life or online, don’t hesitate to talk about the project around you. Recommending Flouzo to a project holder, posting about Flouzo in a forum or asking a news site to write an article about it is nothing much, but can have great repercussions for the project awareness. The idea is not to spam people, simply to objectively inform them as a good opportunity arises. Go over the press coverage page to know the list of websites to contact or make suggestions.

[edit] Submit a campaign

We need to create several campaigns in order to finish off the behaviour and specifications of the software while we are writing the code. And we could really use your help here. If you are thinking about a campaign you would like to test, fill in the alpha-test form and talk about it in the forum.

[edit] Discuss the running of Flouzo and make suggestions

We have ideas and views regarding Flouzo, but we are aware of the fact that they are certainly not flawless. To complete them, improve them and bring them into question, we are counting on the comments you might have. To do so, there are a few things you can do:

• List the ideas in the Pool of ideas;
• Discuss those ideas in the forum;
• Turn an idea that begins to look accomplished into a specification suggestion.

We dig for ideas at all levels, and – depending on whether we can afford it – we develop or have the validated specification suggestions developed.

[edit] Documentation

[edit] Write new documents

When confronted with a problem and when trying to solve it, do not hesitate to write things down as you do so in the wiki, if needs be make it a new page. Likewise, if you think that some documents are lacking, go ahead and write them! You can also turn exchanges from the forum into documentation in the wiki; this way, subsequent visitors will be more likely to find the solution to their problem without difficulty, and the document will be simpler to maintain.

[edit] Improve the existing documentation

Some sections of the documentation in the wiki can seem obscure, not specific enough or even erroneous. Feel free to edit these documents directly, to correct or complete them.

[edit] Look into the TO-DO of the Wiki

Go to this page of the wiki, listing the documents that have to be written or the corrections that have to be brought in the wiki (cleaning up, listing forum posts to put in the wiki, pages to improve or create...). Don’t hesitate to edit it, for it to reflect the current state of the wiki, to add your own suggestions, even to do a part of the work described there...

[edit] Support & Assistance

Don’t hesitate to answer the messages of people looking for assistance in the forum, if you have the solution to the problems encountered.

[edit] Translation

Translating pages of the wiki increases the potential number of users and contributors, or improves its user-friendliness. The wiki contains numerous pages that only exist in French, if you happen to speak English, it will be welcome!

Likewise, if you can speak any other language, tell us in the forum; if Flouzo is released in your language, we will get in touch with you.

[edit] Art

Flouzo could really use new themes (Website, Donation Meter, etc.), banners, icons, etc. to offer a greater variety of choice. Feel free to submit new ones in the forum, or contact us to find out about the most urgent needs.

[edit] Test & Bug reports

One of the most important components of the quality of the platform is the quantity of tests to which it has been submitted. During your everyday use of the site, or during test sessions, don’t hesitate to report the bugs you find in the tracker, or to complete existing bug reports.