Frequently Asked Questions

Can anyone use this Toolkit?

Yes, this work is free and open to everyone to reuse and edit. This goes hand in hand with our FLOSS culture concept (for more, see our learning material here). Consequently, we have licensed it under a Creative Commons Attribution-ShareAlike 4.0 International License and translated the content to several languages.

What are the exact terms of use?

The Creative Commons Attribution-ShareAlike 4.0 International License is a copyleft licence used by major FLOSS projects such as Wikipedia and its sister initiatives (Wikibooks, Wikidata etc). It is one of the Creative Commons (CC) licenses serving as public copyright licenses that enable the free distribution of an otherwise copyrighted “work”. A CC license is used when an author wants to give other people the right to share, use, and build upon a work that they (the author) have created (for more, see our learning material here). 

What is FLOSS and FLOSS culture?

FLOSS refers to Free and Libre Open Source Software as initially defined by Richard Stallman  (for more, see our learning material here). However, the FLOSS culture goes beyond the software and hardware production area to engage a spectrum of activities including education and art, economy and production, law and copyright, governance and policy making… It is both a theoretical and practical movement, expanding horizontally as much to daily practices, as to socioeconomic models. 

What can I do with it? 

Our main objective is to create a comprehensive space for trainers and trainees to start their learning journey to FLOSS culture. In a nutshell, the Toolkit includes detailed training scenarios, organised in separate learning sessions. Each learning session comes with learning material (definitions, explanations, facts, exercises) and presentations piloted locally during our OPEN-AE piloting activities.   

What can I find inside?

We propose you to think and teach FLOSS culture and skills using 18 autonomous modules. These modules include both generic (for example, The FLOSS culture or DigCompEdu framework for a common and open education), initiative based (for example, Wikidata, SlideWiki), activity specific (for example, Open coding with Scratch, Open robotics with Arduino), or methodological (for example, FLOSS resources for employment E-Learning with FLOSS tools) learning activities. 

Why is this different from all the other educational repositories and resources around me?

We have done some work to define why this work is unique and here are our main arguments:

  • This a comprehensive place for anyone to get a grip and share, teach on the FLOSS culture themes.
  • The Toolkit proposes training scenarios, learning sessions and material for an autonomous learning or training approach.
  • Our architecture (Framagit) allows for participants to edit existing and propose new content.  

Sorry, what is Framagit?

Framagit is a web-based collaborative software platform (software) facilitating collaborative programs development. All these services are personal datas and private life respectful. The data is hosted on Framacloud. We have used another FLOSS software, Jekyll, to create our user interface for our Toolkit. 

What about evaluation and certification?

Our modules are linked to badges and every certificate issued from the OPENAE partners reflects the modules that the trainee has followed and competed. Here is an illustration:

You can find all these materials in an editable form into our website.  

Are there any local communities that I can get in touch with?

Oh yes, there are so many. We have done an initial work to map them to our IO1 (online link needed). But the best way throughout this is to contact one our partners in Italy, Spain, Belgium and Switzerland (see how here

Was the FLOSS movement active during the COVID 19 pandemic ?

Definitely ! Some community driven examples include:

At the end of the day, can I edit the content of the Toolkit, now?

Yes, we have created a step by step pathway to this. You can find it following this link to our Toolkit.