Back

What legal structures to carry digital commons? #Introduction

#2 - Practical information: Acculturation of public-sector players to SCIC law

Published on 05 October 2023

Summary

I. The approach

II. Acculturation of public-sector players to SCICs

« "Today, there is no government-approved documentation to guide you in setting up and running a SCIC, unlike what exists for GIPs in particular". »

Benjamin Gueraud-Pinet - RTES

Recommendation no. 1

Bring together all the resources produced for public-sector use in a single knowledge base, under the aegis of a recognized authority.

Recommendation no. 2

Include a compilation of existing SCIC statutes in the knowledge base.

Recommendation 3

Include a FAQ on SCICs in the body of documentation, following on from RTES's work on the subject, and supplied by public players.

Recommendation 4

Include feedback from local authorities that have set up and are members of SCICs in the knowledge base.

III. Acculturation of public-sector players to the use of SCICs to carry digital commons

Recommendation 5

Draw on MedNum's bylaws to clarify the relevance of the SCIC to the objective of supporting a digital commons project.

Recommendation 6

Include in the bylaws, following the corporate purpose, an article stipulating that "Members undertake to operate according to the principle of agile development methodologies, with a prevalence of user feedback".

Recommendation 7

The methodologies adopted are described in detail in the "Miscellaneous Provisions" section or in dedicated internal regulations.

Recommendation 8

Balance the powers of the General Meeting and the Board of Directors in the SCIC's bylaws.

Recommendation 9

Restricting the content of SCIC bylaws to the legal minimum

Recommendation 10

Draw up internal regulations to complement the articles of association and detail the way the cooperative operates.

Recommendation 11

Produce a multi-year agreement of objectives, applied to SCICs and geared towards the production of digital commons.

What legal structures to carry digital commons? #Introduction

#2 - Practical information: Acculturation of public-sector players to SCIC law

I. The approach

II. Acculturation of public-sector players to SCICs

« "Today, there is no government-approved documentation to guide you in setting up and running a SCIC, unlike what exists for GIPs in particular". »

Benjamin Gueraud-Pinet - RTES

Recommendation no. 1

Bring together all the resources produced for public-sector use in a single knowledge base, under the aegis of a recognized authority.

Recommendation no. 2

Include a compilation of existing SCIC statutes in the knowledge base.

Recommendation 3

Include a FAQ on SCICs in the body of documentation, following on from RTES's work on the subject, and supplied by public players.

Recommendation 4

Include feedback from local authorities that have set up and are members of SCICs in the knowledge base.

III. Acculturation of public-sector players to the use of SCICs to carry digital commons

Recommendation 5

Draw on MedNum's bylaws to clarify the relevance of the SCIC to the objective of supporting a digital commons project.

Recommendation 6

Include in the bylaws, following the corporate purpose, an article stipulating that "Members undertake to operate according to the principle of agile development methodologies, with a prevalence of user feedback".

Recommendation 7

The methodologies adopted are described in detail in the "Miscellaneous Provisions" section or in dedicated internal regulations.

Recommendation 8

Balance the powers of the General Meeting and the Board of Directors in the SCIC's bylaws.

Recommendation 9

Restricting the content of SCIC bylaws to the legal minimum

Recommendation 10

Draw up internal regulations to complement the articles of association and detail the way the cooperative operates.

Recommendation 11

Produce a multi-year agreement of objectives, applied to SCICs and geared towards the production of digital commons.