Search results

Jump to navigation Jump to search

Page title matches

  • #REDIRECT [[Development process]]
    33 bytes (3 words) - 12:13, 28 February 2020
  • ''Note (@ripcurlx): This is just a stub where we can detail the development processes. Just added it to link the existing process for critical bugs'' === Development within priorities ===
    344 bytes (43 words) - 12:15, 28 February 2020

Page text matches

  • ''Note (@ripcurlx): This is just a stub where we can detail the development processes. Just added it to link the existing process for critical bugs'' === Development within priorities ===
    344 bytes (43 words) - 12:15, 28 February 2020
  • #REDIRECT [[Development process]]
    33 bytes (3 words) - 12:13, 28 February 2020
  • See [[Development Process]]
    278 bytes (30 words) - 22:14, 21 January 2022
  • * Merge pull requests per the [[Development Process]]
    794 bytes (102 words) - 01:57, 19 June 2020
  • [[Trading_fees|Trading fees]] are paid to the Bisq DAO to fund development of the Bisq software.
    886 bytes (143 words) - 09:28, 20 December 2021
  • This is not a technical maintainer role—meaning it is not about development, but rather about managing the process for adding and maintaining payment m
    2 KB (208 words) - 16:54, 17 November 2020
  • ...and [https://github.com/bisq-network/proposals/issues/365 #365] led to the development of this procedure.
    2 KB (252 words) - 16:51, 16 October 2022
  • ...q-network/bisq/blob/master/docs/README.md developer docs] to set up a Bisq development environment. # Familiarize yourself with [https://ossec-docs.readthedocs.io/en/latest/docs/development/oRFC/orfc-1.html C4: The Collective Code Construction Contract]. It’s a s
    7 KB (1,071 words) - 22:07, 2 March 2022
  • ...oceed to put together a pull request that fixes the bug as per the usual [[Development Process]].
    3 KB (525 words) - 05:32, 19 June 2020
  • GitHub is the place where development of Bisq happens.
    4 KB (596 words) - 17:30, 26 February 2022
  • ...pective. This is somewhat intuitive for development-related tasks, but non-development contributors should strongly consider making issues in the appropriate repo
    11 KB (1,828 words) - 19:28, 22 January 2022
  • * In development: Schnorr signatures, which will improve network privacy and capacity
    5 KB (818 words) - 20:31, 16 April 2021
  • * [https://global.strike.me/en/ Strike Global (in development)]
    6 KB (932 words) - 23:01, 22 November 2021
  • ...best to first float your idea in the channels for that area. For example, development-related ideas can be discussed in #dev on Matrix or in [https://github.com/
    7 KB (1,130 words) - 19:08, 22 January 2022
  • ...a [[compensation]] perspective. If you are a maintainer, do NOT group your development and review activities together with your maintainer role in your compensati
    9 KB (1,275 words) - 19:18, 22 January 2022
  • ...project needs to be financially sustainable to fund ongoing operations and development. But traditional means of handling revenue and revenue distribution are nec
    10 KB (1,579 words) - 00:04, 29 April 2021
  • ...to be paid in regular, predictable ways to ensure continual (and reliable) development, service, and growth; the Bisq DAO enables this to happen by distributing t
    27 KB (4,506 words) - 18:59, 24 April 2024