This site uses cookies. Visit our cookies policy page or click the link in any footer for more information and to change your preferences.

Accept all cookies Accept only essential cookies

Code development platform for open source projects from the European Union institutions :large_blue_circle: EU Login authentication by SMS has been phased out. To see alternatives please check here

Skip to content
Snippets Groups Projects
Commit 83f450ed authored by Aurora GUALTIERI's avatar Aurora GUALTIERI
Browse files

Update file README.md

parent 800b1ab9
Branches
Tags
No related merge requests found
Show whitespace changes
Inline Side-by-side
Showing
with 17 additions and 80 deletions
README.md
+ 17
− 80
View file @ 83f450ed
# BDTI Introduction and Pilots
# ABOUT
The Big Data Test Infrastructure (BDTI) was created by the European Commission in 2019 and is funded by the [Digital Europe Programme (DEP)](https://digital-strategy.ec.europa.eu/en/activities/digital-programme). With a planned overall budget of €7.5 billion, the DEP aims to accelerate the economic recovery and shape the digital transformation of Europe’s society and economy, increasing the availability, quality and usability of public sector information in compliance with the requirement of the [Open Data Directive](https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1561563110433&uri=CELEX:32019L1024).
The DEP is one of the activities supporting the implementation of the [European Data Strategy](https://digital-strategy.ec.europa.eu/en/policies/strategy-data), adopted by the European Commission in 2020, which aims to create a single market for data, ensuring that more data becomes available for use in the economy and society in Europe, keeping the companies and individuals who generate the data in control of them.
## Getting started
# The regulatory environment
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
In response to the public consultation on the European Strategy for Data, the European Commission published the [Data Governance Act](https://digital-strategy.ec.europa.eu/en/policies/data-governance-act) in 2020, which is intended to foster a framework to facilitate data sharing across the EU and between sectors.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
During February 2022, the commission presented a new [Data Act](https://europa.eu/!GMcVf8), which complements the Data Governance Act, regulating who can access and use data generated in the EU in all economic sectors and under which conditions.
## Add your files
The [Interoperable Europe Act](https://europa.eu/!n3cbmF), adopted in March 2024 establishes an interoperability governance structure with a view to creating an ecosystem of shared interoperability solutions for the EU’s public sector.
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
The [AI Act](https://europa.eu/!Yh74XM) is the first legal framework on AI, which addresses the risks of AI and positions Europe to play a leading role globally. The AI Act aims to provide AI developers and deployers with clear requirements and obligations regarding specific uses of AI.
```
cd existing_repo
git remote add origin https://code.europa.eu/bdti/bdti-introduction-and-pilots.git
git branch -M master
git push -uf origin master
```
# BDTI for European public administrations
## Integrate with your tools
BDTI provides a free of charge cloud-based analytics test environment for public administrations in the European Member States to experiment with open-source tools and to prototype solutions before deploying them in the production environment on their own premises. Any public administration at any level can request to use BDTI to perform analysis and experiments on their public sector information, for a period of six months, completely for free.
- [ ] [Set up project integrations](https://code.europa.eu/bdti/bdti-introduction-and-pilots/-/settings/integrations)
The test environment provided by the BDTI consists of several open-source solutions, data sources and the required cloud infrastructure that includes the virtual machines, analytics clusters, storage facilities and networking facilities. BDTI offers public administrations the opportunity to derive insights from public information, and move towards data-driven decision making.
## Collaborate with your team
# Presenting BDTI
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
| **Date** | **Session Title** | **Description** | **Recording Video** |
|------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------|
| 10/05/2022 | Data: From Hype to Action, Service Architecture and Hands-on Use Case | This live webinar introduced BDTI, noting its status as an offshoot of the Digital Europe Programme. | [https://www.youtube.com/watch?v=un8mU17_zlk](#) |
| 03/03/2022 | Introduction to the Big Data Test Infrastructure | This webinar showcases a pilot project conducted within BDTI. | [https://www.youtube.com/watch?v=Vyig44_fv88](#) |
| 24/06/2021 | Technical Showcase Webinar | This technical webinar showcases how BDTI services support the analysis and visualization of data and models. | [https://www.youtube.com/watch?v=uv6rWkF86pY](#) |
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment

For further information about the platform and support, please see https://code.europa.eu/info/about