6 Mar
2013
6 Mar
'13
11:20 p.m.
I thought of this during the meeting but didn't want to veer too far off
topic, but since the analogy of articles amendment to software
development (particularly version control) came up, I thought this was
pertinent. At certain points during the Articles of Association, it
might be a good idea to write tests.
Test Driven Development is an integral part of a lot of software
development - coming up with different situations and contexts of how
your software is used. But it can actually be applied here quite easily
- especially to the 'conflict resolution' sections. How well do the
articles we've agreed upon handle different types of conflicts? Well,
we can write test cases for them. For instance:
Test Case 1: Someone has stolen money from the donations jar
Test Case 2: An injury happens at Sudoroom
The more tests we write, the better the coverage of the articles are in
different situations. This may also help elucidate the gaps where our
articles may need amending.
Writing tests also actually helps clarify the meaning and intention of
articles with more obtuse language.
I was going to go create a wiki page on it, but the server rejected me
from creating a login for some reason :(
Bill
7 Mar
7 Mar
12:14 a.m.
You can add to the wiki here, ya'll:
http://sudoroom.org/wiki/Governance_tests
On Wed, Mar 6, 2013 at 11:20 PM, William Budington <bill(a)inputoutput.io>wrote;wrote:
I thought of this during the meeting but didn't
want to veer too far off
topic, but since the analogy of articles amendment to software
development (particularly version control) came up, I thought this was
pertinent. At certain points during the Articles of Association, it
might be a good idea to write tests.
Test Driven Development is an integral part of a lot of software
development - coming up with different situations and contexts of how
your software is used. But it can actually be applied here quite easily
- especially to the 'conflict resolution' sections. How well do the
articles we've agreed upon handle different types of conflicts? Well,
we can write test cases for them. For instance:
Test Case 1: Someone has stolen money from the donations jar
Test Case 2: An injury happens at Sudoroom
The more tests we write, the better the coverage of the articles are in
different situations. This may also help elucidate the gaps where our
articles may need amending.
Writing tests also actually helps clarify the meaning and intention of
articles with more obtuse language.
I was going to go create a wiki page on it, but the server rejected me
from creating a login for some reason :(
Bill
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
3:27 p.m.
I think one way we can improve the amendment process is moving the Articles
into git of some sort (github / gitorious). It fits better:
- explicit distributed development model
- rigorously, clearly tracked and presented changes, branches, releases
- explicit vetting and approval of modifications via pull requests / pulls
I will do this if no one objects.
On Mar 7, 2013 12:14 AM, "Matthew Senate" <mattsenate(a)gmail.com> wrote:
You can add to the wiki here, ya'll:
http://sudoroom.org/wiki/Governance_tests
On Wed, Mar 6, 2013 at 11:20 PM, William Budington <bill(a)inputoutput.io>wrote;wrote:
I thought of this during the meeting but
didn't want to veer too far off
topic, but since the analogy of articles amendment to software
development (particularly version control) came up, I thought this was
pertinent. At certain points during the Articles of Association, it
might be a good idea to write tests.
Test Driven Development is an integral part of a lot of software
development - coming up with different situations and contexts of how
your software is used. But it can actually be applied here quite easily
- especially to the 'conflict resolution' sections. How well do the
articles we've agreed upon handle different types of conflicts? Well,
we can write test cases for them. For instance:
Test Case 1: Someone has stolen money from the donations jar
Test Case 2: An injury happens at Sudoroom
The more tests we write, the better the coverage of the articles are in
different situations. This may also help elucidate the gaps where our
articles may need amending.
Writing tests also actually helps clarify the meaning and intention of
articles with more obtuse language.
I was going to go create a wiki page on it, but the server rejected me
from creating a login for some reason :(
Bill
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
3:54 p.m.
It certainly would be useful to track changes on different branches, and
once an amendment is voted on and approved, merge into master. I see
https://github.com/sudoroom exists, but has no repositories or activity.
Who has control of this account? We may want to change the sudoroom
github user to an organization, so members can freely create projects
under sudoroom from their own github accounts.
Bill
On 03/07/2013 03:27 PM, Anthony Di Franco wrote:
I think one way we can improve the amendment process
is moving the Articles
into git of some sort (github / gitorious). It fits better:
- explicit distributed development model
- rigorously, clearly tracked and presented changes, branches, releases
- explicit vetting and approval of modifications via pull requests / pulls
I will do this if no one objects.
On Mar 7, 2013 12:14 AM, "Matthew Senate" <mattsenate(a)gmail.com> wrote:
You can add to the wiki here, ya'll:
http://sudoroom.org/wiki/Governance_tests
On Wed, Mar 6, 2013 at 11:20 PM, William Budington <bill(a)inputoutput.io>wrote;wrote:
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
I thought of this during the meeting but
didn't want to veer too far off
topic, but since the analogy of articles amendment to software
development (particularly version control) came up, I thought this was
pertinent. At certain points during the Articles of Association, it
might be a good idea to write tests.
Test Driven Development is an integral part of a lot of software
development - coming up with different situations and contexts of how
your software is used. But it can actually be applied here quite easily
- especially to the 'conflict resolution' sections. How well do the
articles we've agreed upon handle different types of conflicts? Well,
we can write test cases for them. For instance:
Test Case 1: Someone has stolen money from the donations jar
Test Case 2: An injury happens at Sudoroom
The more tests we write, the better the coverage of the articles are in
different situations. This may also help elucidate the gaps where our
articles may need amending.
Writing tests also actually helps clarify the meaning and intention of
articles with more obtuse language.
I was going to go create a wiki page on it, but the server rejected me
from creating a login for some reason :(
Bill
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
3:25 p.m.
I agree that this is a good idea to make thinking more concrete.
Unfortunately it is harder to put into practice and impossible to automate
since real people must be involved who ideally would be as invested as they
would be if something real were at stake and would act accordingly.
I proposed something similar in the context of the community democracy
project: that the budgeting procedure they propose actually be carried out
on a regular basis to build experience with it and find bugs.
For sudo room, for our meetings and other routine procedures, we do the
equivalent anyway, and for exceptional things i.e. conflict resolution, the
difficulties mentioned before present themselves.
Even as a repository of thought experiments, it still could be valuable.
On Mar 6, 2013 11:21 PM, "William Budington" <bill(a)inputoutput.io> wrote:
I thought of this during the meeting but didn't
want to veer too far off
topic, but since the analogy of articles amendment to software
development (particularly version control) came up, I thought this was
pertinent. At certain points during the Articles of Association, it
might be a good idea to write tests.
Test Driven Development is an integral part of a lot of software
development - coming up with different situations and contexts of how
your software is used. But it can actually be applied here quite easily
- especially to the 'conflict resolution' sections. How well do the
articles we've agreed upon handle different types of conflicts? Well,
we can write test cases for them. For instance:
Test Case 1: Someone has stolen money from the donations jar
Test Case 2: An injury happens at Sudoroom
The more tests we write, the better the coverage of the articles are in
different situations. This may also help elucidate the gaps where our
articles may need amending.
Writing tests also actually helps clarify the meaning and intention of
articles with more obtuse language.
I was going to go create a wiki page on it, but the server rejected me
from creating a login for some reason :(
Bill
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
4089
days inactive
4089
days old
4 comments
3 participants
participants (3)
-
Anthony Di Franco -
Matthew Senate -
William Budington