ReachOut FAQ


Below, you will find a set of questions and answers about ReachOut. If you have a question and don't find it here, please suggest a question or help refine the answers by contacting us.

Project Campaign Manager FAQ

What is my role as a Campaign Manager?

As the person in charge of exploitation and/or dissemination activities within a EU-funded Research project, you can oganise and promote your beta-testing campaign using the ReachOut platform. We are supporting you while preparing the beta version of your software, guides, workshops and more. Industry end-users and beta testers will be able to download your software from the ReachOut platform. Then, they will provide you precious user experience feedbacks.

Where is my dashboard?

Once registered to the ReachOut platform as a Campaign Manager, you can access to your own campaign dashboard from your homepage. This dashboard is your campaign management graphic interface; it provides you with 24 checkpoints to monitor the progress of your beta-testing campaign.

What's in a questionnaire?

The questionnaire is the method by which feedback from beta testers is collected on the ReachOut Platform. A pre-registered template is provided that you can customise to mirror the specifics of your beta-testing campaign.

How can I customize the questionnaire?

When updating  your questionnaire, keep in mind this balanced ratio: offer two third generic questions, and one third specific ones. Your new questions might focus on software deployment, user experience, tutorial, documentation, integration or exploitation opportunities. Find more about customizing the ReachOut questionnaire in this presentation.

Can I update my Campaign Page?

The campaign page is the web page introducing your beta-testing campaign. Initial information results from the input fields provided during the project registration step. Updating this page allows you to offer incentives, interactive webinars, hands-on workshops and other recognition signs. Show your appreciation to the beta testers as they can identify business needs, provide a valuable viewpoint and grow your ecosystem community.

How do I package by Beta Version and make it available to Beta Testers?

You may already have the Beta Version of your software packaged by your own means. 

If you haven't packaged your Beta Version yet, you may optionally use the ReachOut Factory in order to do so. Using the ReachOut Factory, you will create an Appliance Template for the Beta Version using the Factory, and then:

  • either export the Appliance Template
  • or generate a machine image and download it
    and then store it inside your own project infrastructure.

In all cases, you should provide a download link to the Beta Version files together with the installation instructions in the Campaign Page.

Where is my Communication Package?

The Communication Package is a set of templates for communication resources such as mails, press releases, and flyers to help you implement best practices.

I need more coaching. Who can I contact now?

You may need more face-to-face contact to start your campaign or interpret ReachOut reports. Contact the ReachOut team now and check with us if we could participate in your next project plenary meeting or attend your next public workshop where we could help you implement best practices for your beta-testing campaign.

Beta Tester FAQ

What is my role as a Beta Tester?

To become an eligible beta testers, you should not belong to the project team developing the software. However you can contribute to improve the software as a software engineer, a developer or a business user who has downloaded and tried the Beta then provided your own view, appreciation or suggestions.

What kind of software ReachOut is promoting?

Software provided on the ReachOut website are direct outcomes of European research projects, partially funded by the European Commission. The projets can offer one or several beta software including documentation and "hello world" examples. From the ReachOut website, you can register as a beta tester, download and test these software, then report your feedback to help improve the software before the final or commercial version.

Why should I spend my time experimenting a beta version of software?

As a developer or as a power user, you will find new opportunities by evaluating the software provided on the ReachOut platform in your environment. Moreover, the feedback you provide may highlight relevant features or business models the team could add in a next release. You learn about cutting-edge software, improve your vision and your skills. Beta-testing advanced software enhances your professional profile. And beta-testing campaigns offer rewards to beta testers. As minor as your contribution may seems, its a potential creative step toward a new emerging ecosystem.

Why using ReachOut rather than GitHub or any other software repository?

Your time is limited to explore new software features that might be relevant in your business environment. ReachOut aggregates stable software packaged with proper documentation and beta-testing scenarios, along with a GDPR notice, support contacts, mailing list and more.

Where should I start?

Browse the ReachOut website home page and check out the beta software proposed for evaluation.

The Reachout project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement number 825307.

flagEU.svgThe information in this document is provided “as is”, and no guarantee or warranty is given that the information is fit for any particular purpose. The content of this document reflects only the author`s view – the European Commission is not responsible for any use that may be made of the information it contains. The users use the information at their sole risk and liability.

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 9.11.8 - Documentation