From: Amir Taaki <zgenjix@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Meeting 21:00 UTC #bitcoin-dev Freenode IRC
Date: Mon, 2 Jan 2012 08:04:46 -0800 (PST) [thread overview]
Message-ID: <1325520286.43835.YahooMailNeo@web121005.mail.ne1.yahoo.com> (raw)
This meeting is to discuss the new OP_EVAL changes coming to bitcoin.
A good summary of the past discussion so far by justmoon can be found:
http://privatepaste.com/4088b049af
Hopefully this can become a weekly thing. For now this is to discuss and inform about the coming changes to bitcoin.
----------
Where: Freenode IRC #bitcoin-dev
When: 21:00 UTC (16:00 New York time) until 22:00*
What: OP_EVAL
Bitcoin is starting decentralising as any healthy free thinking community
should. Projects are thiving and the economy is growing. New ideas are
being realised and will edge out old models disruptively.
My hope is that we don't all become fractured. By having weekly regular
meetings, projects can harmonise in lock step. Concepts and algorithms can
be proposed and debated. You'd be surprised what having a scheduled regular
platform can achieve. A soap-box on an island in central waters.
For me, I don't have time to wade through IRC discussions, forum posts and
mailing lists. At least if the important things are discussed in one place
it makes bitcoin development and the system more accessible.
Before meeting:
- A wiki page is created for in advance of a weekly meeting.
- Announced on forums/mailing lists.
- Throughout the week talking points are added to the meeting page.
After:
- Log of discussion is posted online.
- I will type an accessible summary for the community at large on
http://bitcoinmedia.com/
- Next weekly meeting is scheduled.
Amir Taaki
*We can go over this hour, but this is to stop meetings dwindling off topic
into banal banter and stay focused.
next reply other threads:[~2012-01-02 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 16:04 Amir Taaki [this message]
2012-01-02 21:24 ` Matt Corallo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1325520286.43835.YahooMailNeo@web121005.mail.ne1.yahoo.com \
--to=zgenjix@yahoo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox