On Thu, May 1, 2014 at 3:41 AM, Sean Hunt wrote:
> Notwithstanding the requirement that multiple Rule Changes cannot
> occur simultaneously, the Rulekeepor CAN, in publishing the Ruleset,
> generally format and make purely editorial changes to the rules as e
> sees fit, and in particular, e CAN:
On Thu, 1 May 2014, Sean Hunt wrote:
> On Thu, May 1, 2014 at 10:04 AM, Kerim Aydin wrote:
> > E should be required to do it by specific announcement, not just in
> > the ruleset (description ok, like "I renumbered R768"), so all
> > changes can be traced back to a specific event.
>
> The inten
On Thu, May 1, 2014 at 10:04 AM, Kerim Aydin wrote:
> E should be required to do it by specific announcement, not just in
> the ruleset (description ok, like "I renumbered R768"), so all
> changes can be traced back to a specific event.
The intent is to allow it to be done by automatic formatting
On Thu, 1 May 2014, Kerim Aydin wrote:
> On Thu, 1 May 2014, Sean Hunt wrote:
> > {{{
> > Notwithstanding the requirement that multiple Rule Changes cannot
> > occur simultaneously, the Rulekeepor CAN, in publishing the Ruleset,
> > generally format and make purely editorial changes to the rules
On Thu, 1 May 2014, Sean Hunt wrote:
> {{{
> Notwithstanding the requirement that multiple Rule Changes cannot
> occur simultaneously, the Rulekeepor CAN, in publishing the Ruleset,
> generally format and make purely editorial changes to the rules as e
> sees fit, and in particular, e CAN:
> 1)
Hey everyone,
I've started a repository at https://github.com/scshunt/agoranomic to
keep track of my reporting, and I encourage others to use their own
repositories for the same. Currently I haven't added score because
it's basically easier to do that by hand.
One of the problems that automated r
6 matches
Mail list logo
