Better venue for development discussion needed #9149

issue rebroad opened this issue on November 13, 2016
  1. rebroad commented at 2:58 AM on November 13, 2016: contributor

    https://botbot.me/freenode/bitcoin-core-dev/2016-09-29/?msg=73959763&page=4 (to show an example of a recent meeting)

    Currently the IRC group is being used for discussion regarding development, but this doesn't allow for people in all time-zones to participate (e.g. it's 2am in Thailand).

    Also the bitcoin-core-dev group is being used to discuss protocol changes, which obviously affects all other Bitcoin variants, so perhaps such topics ought to be moved to non-core specific areas.

    Raising this here as I am unaware of a more appropriate venue currently to raise this, as it is currently a core-specific issue (given it's the core specific chat room).

    Any suggestions on a better forum/software to use for this? Ideally it ought to be something that allows likes/dislikes (as GitHub already has) to previous suggestions - doesn't rely on everyone being present at the same time - and ideally allows for threaded conversations and sub-topics to occur, yet allowing for an overall agenda to persist, perhaps with options to vote on proposals and keep a tally of votes, as well as the membership/status of participants (GitHub also already does this).

    Overall, given the criteria I am inclined to think GitHub may already be the best venue, but I do hope that others can agree that a venue that allows participants from varying timezones and allows inclusion of non-core participants for non-core issues is desirable.

    So, this is two issues really - a better venue for bitcoin core discussion, and a better venue for overall bitcoin development discussion.

  2. jonasschnelli commented at 9:23 AM on November 13, 2016: contributor

    Again. The place for this is probably the bitcoin-dev mailing list.

    The current time-slot has been chosen after asking and arranging with every interested participant finding the best slot that could work for most interested participants. Sure, we can (and probably should) re-evaluate a better, different time-slot every here and there (maybe once every year). But my feeling tells me, that changing the timeslot will make things difficult for some.

    The public IRC meeting is hold in #bitcoin-core-dev (just because it's most convenient there).

    IMO there are already various forums to discuss stuff (ex. https://bitcointalk.org).

  3. jonasschnelli commented at 9:23 AM on November 13, 2016: contributor

    closing

  4. jonasschnelli closed this on Nov 13, 2016

  5. rebroad commented at 4:45 PM on November 13, 2016: contributor

    Bitcoin-dev mailing list seems to be heavily censored. I just got a post rejected today in fact (regarding BIP9). On 13 Nov 2016 16:23, "Jonas Schnelli" notifications@github.com wrote:

    Closed #9149 #9149.

    — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub #9149#event-856962472, or mute the thread https://github.com/notifications/unsubscribe-auth/ABdZq8RnicBwPA4XJpGIoZdMre1AUV5aks5q9tcEgaJpZM4Kwl8N .

  6. Leviathn commented at 5:46 PM on November 13, 2016: none

    That topic had already been flagged and noted that further discussion on it was to be continued on Bitcoin-Discuss. That is hardly censorship, especially when the original note in question was off-topic, and had largely ignored previous information on the topic (see Sipa's post on soft-forks).

  7. venzen commented at 10:28 AM on November 15, 2016: none

    @rebroad I'm sure your persistent problem-invention on every non-issue in this landscape is annoying others too, so let me push back a little for the sake of my own inbox and everyone else's:

    I happen to live in Thailand and the IRC meeting at 3am (Indochina time) makes participation difficult, yes. However, the minutes/summary of the meeting is always made available at bitcoincore.org. In the final analysis, there is no utilitarian outcome in me synchronously participating in the meeting because the matters being discussed, though interesting, are beyond my capacity as a hobbyist to influence or sway.

    The same applies to you, since your repeated failure to make meaningful contribution to this project means you also lack the merit and reputation to influence the course of Core development.

    Please put a plug in the constant revisitation of old issues and public questions you should correctly be researching on your own.

  8. rebroad commented at 4:28 AM on November 16, 2016: contributor

    @venzen With posts like that you might just acquire the merit and influence you claim you lack :) although hopefully it's not all about brown-nosing in order to acquire influence and merit on here. This isn't really the place to discuss further the "non-issues" you refer to. My intention has always been to make bitcoin better, and if I raise an issue it's because I think it's an issue - this is presumably the same reason other people open issues. Subjectivity leads to non-consensus. It's incorrect to suggest either of us has no influence - your post above getting four thumbs-up proves you have influence, and some of my issues raised are considered issues - I am still learning how to determine in advance whether something I consider to be an issue will be considered to be an issue by other people. Please, let's not encourage school-yard behavior on here by dissing people in order to gain favor with others.

  9. DrahtBot locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-22 18:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me