Re: DIS: PAoaM Patch status

[Aris Merchant]

It wasn't pended because there were substantial problems it didn't fix. I
posted them in a thread replying to the proposal, and they haven't been
fixed yet. I'll have a go at fixing them and looking for any others over
the weekend, and I'd encourage others to do the same. It would be best if
we could find everything now, rather than bumping into other problems later.

-Aris

On Mar 16, 2018 1:37 PM, "Reuben Staley"  wrote:

ATMunn pended it just a few hours ago.

El vie., 16 de mar. de 2018 14:36, Kenyon Prater 
escribió:

> It still isn't pended right? Is there a reason/what still needs to happen
> before that?
>

DIS: Re: OFF: [Promotor] Distribution of Proposals 8027-2028

[Kerim Aydin]

On Sun, 11 Mar 2018, Aris Merchant wrote: 
> //
> ID: pp1
> Title: PAoaM Patch
> Adoption index: 3.0
> Author: Gaelan
> Co-authors:
> 
> 
> In Rule 105 “Rule Changes,” replace
> 
>   "If the reenacting proposal provides new text for the rule, the rule
>   must have materially the same purpose as did the repealed version;
>   otherwise, the attempt to reenact the rule is null and void.”
> 
> with
> 
>   “If the reenacting proposal provides new text for the rule, the
>   rule SHOULD have materially the same purpose as did the repealed version."

So, er, now that it's pended...

Does anyone think that not using the word "Amend" in the above will screw 
it up - or is amend implicit enough to meet the R105 clarity requirements?
I mean, I think it is, but I also thought the last one was fine where others
didn't.

(all the other rule changes in the proposal use "Amend", "Enact", or "Re-enact"
so they're fine from that point of view).

Re: DIS: PAoaM Patch status

[Reuben Staley]

ATMunn pended it just a few hours ago.

El vie., 16 de mar. de 2018 14:36, Kenyon Prater 
escribió:

> It still isn't pended right? Is there a reason/what still needs to happen
> before that?
>

DIS: PAoaM Patch status

[Kenyon Prater]

It still isn't pended right? Is there a reason/what still needs to happen
before that?

Re: BUS: Re: DIS: Currency repairs?

[Gaelan Steele]

Always 1.

Gaelan

> On Mar 16, 2018, at 10:06 AM, ATMunn  wrote:
> 
> I pend that proposal with whatever the cost in paper is.
> 
> (probably too vague to work, but oh well :P)
> 
> On 3/16/2018 1:01 PM, Reuben Staley wrote:
>> It's in the proposal pool, unpended. Someone should pend it. Probably me
>> since I caused the issues.
>> El vie., 16 de mar. de 2018 09:19, Kerim Aydin 
>> escribió:
>>> 
>>> 
>>> What's the deal with the big fix for the Map rules?  (Payday
>>> and whatnot).  Did we decide not to do that or what.
>>> 
>>> 

Re: DIS: Currency repairs?

[Reuben Staley]

It's in the proposal pool, unpended. Someone should pend it. Probably me
since I caused the issues.

El vie., 16 de mar. de 2018 09:19, Kerim Aydin 
escribió:

>
>
> What's the deal with the big fix for the Map rules?  (Payday
> and whatnot).  Did we decide not to do that or what.
>
>

DIS: Currency repairs?

[Kerim Aydin]

What's the deal with the big fix for the Map rules?  (Payday
and whatnot).  Did we decide not to do that or what.

Re: DIS: Re: BUS: Blots v1.0

[Kerim Aydin]

Heh.  V1.0 of this particular round of drafting.

If we count from the number of times blots have been defined then
completely repealed, it's the 2nd I think?  Of course during the first
time it went through bunches of changes at least one was enough
of an overhaul to increment the major version #.

On Fri, 16 Mar 2018, Benjamin Schultz wrote:
> On Thu, Mar 15, 2018 at 6:28 PM, Kerim Aydin  wrote:
> 
> >
> > Proposal, 'Blots v1.0', AI-3, co-author = Aris:
> >
> 
> Technical nitpick.  Might this be Blots v2, v3, or whatever incarnation it
> has reached?
> 
> OscarMeyr
> 
> 
> 
> Virus-free.
> www.avast.com
> 
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

DIS: Re: BUS: Blots v1.0

[Benjamin Schultz]

On Thu, Mar 15, 2018 at 6:28 PM, Kerim Aydin  wrote:

>
> Proposal, 'Blots v1.0', AI-3, co-author = Aris:
>

Technical nitpick.  Might this be Blots v2, v3, or whatever incarnation it
has reached?

OscarMeyr



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>