This site uses cookies. By continuing to browse the site, you agree to our use of cookies. Find out more about cookies.
Skip to main content
Metadecidim's official logo
  • English Triar la llengua Elegir el idioma Choose language
    • Català
    • Castellano
Sign Up Sign In
  • Home
  • Processes
  • Assemblies
  • Initiatives
  • Consultations
  • Conferences
  • Help

Decidim.GOV: Democratic Governance for an open community

#decidimgov Internal organization, democracy and decision making

Phase 8 of 8
Accountability 2019-02-17 - 2019-02-28
Process phases
  • The process
  • Meetings
  • Proposals
  • Statutes proposal
  • Internal regulations proposal
  • Statutes approval
  • Coordination Committee Approval
  • News
More
  • Coordination Committee Approval
  • News

Supports are subject to the following rules:

  • You can support up to 10 proposals.
  • In order to be validated proposals need to reach 5 supports
  • Each proposal can accumulate more than 5 supports
chevron-left Back to list

[ES] Proceso para aceptar contribuciones a la rama master / [EN] Process for accepting contributions to the master branch

Avatar: Carol Romero Carol Romero verified-badge
19/12/2018 12:55  
Accepted

[ES] El proceso actual de contribución al código no garantiza que, una vez abierto un PR (Pull request), éste termine mergeado en Master (el repositorio principal de código). Uno de los motivos es que cualquier funcionalidad (habiendo sido validada previamente por la comunidad) puede resolverse técnicamente de maneras diferentes, y por tanto la valoración técnica es subjetiva.
Publicar las condiciones claras para que un PR sea aceptado y abrir más la comunicación una vez que se abre el PR en github para negociar si es necesario y asegurar que se puede llegar a mergear.
[EN] The current process of contribution to the code does not guarantee that, once a PR (Pull request) is opened, it ends up merged in Master (the main code repository). One of the reasons is that any functionality (having been previously validated by the community) can be solved technically in different ways, and therefore technical validation is subjective.
Publish clear conditions for a PR to be accepted and open more communication once the PR is opened in github to negotiate if necessary and ensure that it can be merged.

  • Filter results for category: 7.1. Code governance 7.1. Code governance

This proposal has been accepted because:

Propuesta aceptada que se ha considerado y se ha tenido en cuenta en la categoría 4. Toma de decisiones y resolución de conflictos de la propuesta de Reglamento Interno.

1/5 Support
Need more supports
Endorsements count0
Endorse[ES] Proceso para aceptar contribuciones a la rama master / [EN] Process for accepting contributions to the master branch
[ES] Proceso para aceptar contribuciones a la rama master / [EN] Process for accepting contributions to the master branch Comments 0

Reference: MDC-PROP-2018-12-13434
Version number 2 (of 2) see other versions
Check fingerprint

Fingerprint

The piece of text below is a shortened, hashed representation of this content. It's useful to ensure the content hasn't been tampered with, as a single modification would result in a totally different value.

Value: c03fc0544e1462b0c427117c27d1de47a2ac53c63093ccaa770073a47b47c389

Source: {"body":{"es":"[ES] El proceso actual de contribución al código no garantiza que, una vez abierto un PR (Pull request), éste termine mergeado en Master (el repositorio principal de código). Uno de los motivos es que cualquier funcionalidad (habiendo sido validada previamente por la comunidad) puede resolverse técnicamente de maneras diferentes, y por tanto la valoración técnica es subjetiva. \r\nPublicar las condiciones claras para que un PR sea aceptado y abrir más la comunicación una vez que se abre el PR en github para negociar si es necesario y asegurar que se puede llegar a mergear. \r\n[EN] The current process of contribution to the code does not guarantee that, once a PR (Pull request) is opened, it ends up merged in Master (the main code repository). One of the reasons is that any functionality (having been previously validated by the community) can be solved technically in different ways, and therefore technical validation is subjective.\r\nPublish clear conditions for a PR to be accepted and open more communication once the PR is opened in github to negotiate if necessary and ensure that it can be merged."},"title":{"es":"[ES] Proceso para aceptar contribuciones a la rama master / [EN] Process for accepting contributions to the master branch"}}

This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data.

Share:

link-intact Share link

Share link:

Please paste this code in your page:

<script src="https://meta.decidim.org/processes/decidim-gov/f/961/proposals/13434/embed.js"></script>
<noscript><iframe src="https://meta.decidim.org/processes/decidim-gov/f/961/proposals/13434/embed.html" frameborder="0" scrolling="vertical"></iframe></noscript>

Report inappropriate content

Is this content inappropriate?

Reason

0 comments

Order by:
  • Older
    • Best rated
    • Recent
    • Older
    • Most discussed

Add your comment

Sign in with your account or sign up to add your comment.

Loading comments ...

  • Terms and conditions of use
  • About the community
  • Download Open Data files
  • Metadecidim at Twitter Twitter
  • Metadecidim at Instagram Instagram
  • Metadecidim at YouTube YouTube
  • Metadecidim at GitHub GitHub
Creative Commons License Website made with free software.
Decidim Logo

Confirm

OK Cancel

Please sign in

decidim Sign in with Decidim
Or

Sign up

Forgot your password?