diff --git a/README.md b/README.md index 654543c6933ff023188347fbeaf6a1e1e304f1d8..a38371df7ac9ad2a6a902f5ea15468cbc392f376 100644 --- a/README.md +++ b/README.md @@ -1,92 +1,56 @@ -# Co-Afina 2022 +# Hackathon Co-Afina 2022 -Hackathon Co-Afina 2022 +Desde LA-CoNGA physics nos hemos planteado interrogantes que relacionan los datos abiertos con la educación y con el impacto social del conocimiento cientÃfico ¿Cómo pueden ayudarnos los datos abiertos para mejorar la enseñanza de la ciencia? ¿Qué conceptos pueden enseñarse utilizando los millones de datos abiertos? ¿Qué iniciativas podrÃan aplicar para comunicar la ciencia con estos datos? Los animamos a resolver retos para mejorar la comunicación de la ciencia y la educación, usando datos abiertos. -## Getting started +Quienes organizamos Co-Afina 2022 estamos comprometidos.as a fomentar un ambiente abierto, seguro y amigable y a garantizar la participación de todas las personas en nuestras actividades y espacios virtuales sin importar edad, género, orientación sexual, discapacidad, apariencia fÃsica, nacionalidad, raza, etnia. , religión (o falta de ella), ideologÃa u opciones tecnológicas. Todas las personas que participen en Co-Afina, incluidos los miembros del equipo coordinador, colaboradores, equipo asesor y participantes, deben aceptar y respetar el [código de conducta](coc.md) -To make it easy for you to get started with GitLab, here's a list of recommended next steps. +## Retos Co-Afina -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)! +- [Reconocimiento automatizado de imágenes de animales para fines pedagógicos](challenges/reto01.md) +- [Relación de variables ambientales con datos de cultivos para optimizar decisiones en comunidades agrÃcolas](challenges/reto02.md) +- [Estrategias para el uso escolar de datos ambientales](challenges/reto03.md) +- [Mejorando en Twitter la conversación pública sobre la ciencia](challenges/reto04.md) +- [Visualiza el tiempo atmosférico de la tierra - y aprendamos de ello](challenges/reto05.md) +- [FÃsica de partÃculas en el detector más grande del mundo : ATLAS](challenges/reto06.md) +- [Tributo al Bosón de Higgs en su X aniversario](challenges/reto07.md) -## Add your files +## Equipos ganadores -- [ ] [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: +### Primer lugar: Los guardianes del clima -``` -cd existing_repo -git remote add origin https://gitmilab.redclara.net/laconga/co-afina-2022.git -git branch -M main -git push -uf origin main -``` +Integrantes: +- Roberto Flórez 🇧🇷 +- Bárbara Montañes 🇻🇪 +- Miguel Sevillano 🇵🇪 +- Olga BenÃtez 🇲🇽 +- Sebastián Flórez 🇨🇴 -## Integrate with your tools +Solución https://www.youtube.com/watch?v=T9D695X7zQY -- [ ] [Set up project integrations](https://gitmilab.redclara.net/laconga/co-afina-2022/-/settings/integrations) +### Segundo lugar: Mineros de Twitter -## Collaborate with your team +Integrantes: +- Jorge Gutiérrez 🇪🇨 +- Kevin Cárdenas 🇪🇨 +- Francis Villacrés 🇪🇨 -- [ ] [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/) -- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) +Solución https://www.youtube.com/watch?v=_lixqfa2LiQ -## Test and Deploy +### Tercer lugar: Aephys -Use the built-in continuous integration in GitLab. +Integrantes: +- Mariana Urasma 🇻🇪 +- Franks Cortez 🇻🇪 +- Gustavo Mendoza 🇻🇪 +- David Oviedo 🇻🇪 -- [ ] [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) +Solución https://www.youtube.com/watch?v=Ny4fMcYw8J0 -*** -# Editing this README +## Organizaciones patrocinadoras -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!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. +Evento financiado por Code for Science and Society (CS&S). Organizado por Latin-American alliance for Capacity buildiNG in Advanced physics (LA-CoNGA physics) en colaboración con Latin American Advanced Networks Cooperation (RedCLARA), Corporación Ecuatoriana para el Desarrollo de la Investigación y la Academia (CEDIA) y Creative Commons Venezuela Chapter -## 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. +| CS&S | LA-CoNGA physics | RedCLARA | CEDIA | CC Ven | +|:---------------------:|:----------------:|:--------:|:-----:|:------:| +|  |  |  | |  |