[
https://issues.apache.org/jira/browse/WHIMSY-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954553#comment-16954553
]
Sam Ruby commented on WHIMSY-297:
---------------------------------
This has, indeed, come up several times. And as [~sebb] suggests, it is not up
to Whimsy to set policy; Whimsy tools automate existing practices.
That being said, whether or not the proposed change has been rejected in the
past doesn't mean that the question can't be reexamined. The easiest way to
resolve this is to agree that the Secretary is responsible for the records, and
ask [~mattsicker] how he wants the minutes to read going forward.
Glancing at the code, it does not appear to be a difficult change. That being
said, there always are the chances of unforeseen consequences, and if this
change is made, I would ask that for the next few months that Matt carefully
examine the checkboxes provided for post-meeting actions before proceeding.
What say you, Matt?
{{rubys@rubyimac:~/git/whimsy/www/board/agenda$ git grep tabled | wc -l}}
{{ 13}}
> Never, never say "tabled"
> -------------------------
>
> Key: WHIMSY-297
> URL: https://issues.apache.org/jira/browse/WHIMSY-297
> Project: Whimsy
> Issue Type: Bug
> Reporter: Ted Dunning
> Priority: Major
>
> The secretary tool in whimsy uses the term "table" to mean that a decision on
> an item is deferred. Unfortunately, that means exactly the opposite in
> British English.
> It would be much better to use the term "deferred" to avoid confusion.
> Here is an example from a recent board report:
> {quote}The following resolutions were passed unanimously:
> Establish the Apache Submarine Project (Wangda Tan, VP)
> Establish the Apache SINGA Project (Wang Wei, VP)
> The Establish the Apache Petri Project resolution was *tabled*
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
