Sounds great ... thank you very much, Laure. Best. =ppy
On Fri, Nov 5, 2010 at 10:17 AM, Laure Vieu <vieu@xxxxxxx> wrote:
> Peter, that's an excellent suggestion!
> yes, we can easily add html links in the Manymoon comments, I already
> used that.
> so the best policy could be:
> - (of course) track all tasks, regardless of importance, on Manymoon
> - use Manymoon comments for chat-like unimportant local issues
> - use the mailing list for all the other, AND add a comment in the
> relevant task on Manymoon with the link to the message just sent (that
> we get from the message archive)
> I will try this right away with a pointer to this message in the "Setup
> and test" task.
> the remaining issue is to see if we can desactivate the option of
> sending the comments to all project members via email, and limit it to
> those the task is assigned to, since in principle, the chat-like
> comments should be directed to them only.
> but this is more a detail.
> enjoy your trip
> Laure (02)
> Le 5/11/10 17:56, Peter Yim a écrit :
>> Dear Laure and All,
>>> [LV] Peter suggested NOT to use the Manymoon comments at all and
>>> use the mailing list only ...
>> [ppy] during the Nov-3 IAOA-EC meeting, I actually updated that to
>> suggesting "we use manymoon to track assignments and status, *and* use
>> its comment facilities to only capture transitory remarks ... but,
>> instead, use the mailing list for anything that is worth archiving --
>> so that the disposition or the process of how we got there, could be
>> referenced in the future."
>> Of course, that still does not solve your issue, specifically in your
>> finding that "it is very demanding for me to keep track of what is
>> said in messages."
>>> [LV] My suggestion would be to use the comments in the tasks only for
>>> local simple issues. All important or more general issues should be
>>> discussed through the mailing list.
>> [ppy] As a task tracker, it is useful to put ALL tasks there (even if
>> we don't use it as a discussion space).
>> I also don't prefer casual (transitory) chats be brought over to the
>> mailing list either, as all EC members are subscribed to all committee
>> mailing lists (although, of course, we can still easily skip things by
>> just looking at the list prefix or the subject line ... if people are
>> careful enough to make sure the subject lines correspond to the
>> messages properly.)
>> I don't know if manymoon support html links on the comment , if it
>> does, may I suggest that we use the mailing list for our detailed
>> discussion, and then in quick comments under manymoon, we can just
>> point to (a purple numbered link in the message archive) to bring over
>> the exact details. ... I think this would give us the best of both
>>  sorry, I can't try it out now, I am leaving for the airport in
>> 1 hour (for Shanghai/ISWC; will be away for a week). Will talk more,
>> when I get back.
>> Best. =ppy
>> -- (03)
>> On Fri, Nov 5, 2010 at 4:12 AM, Laure Vieu <vieu@xxxxxxx> wrote:
>>> Dear Peter, dear all,
>>> I've tried to understand how we could make Manymoon send messages to the
>>> mailing list when we insert comments about the tasks, in order to both
>>> have the comments about a given task easily accessible from within
>>> Manymoon, and to properly archive those comments.
>>> Unfortunately, there is no obvious system that I can see for this. The
>>> help section doesn't say anything about comments.
>>> The only solutions that come to my mind are:
>>> - to make the mailing list a member of the project
>>> - more locally, to assign the task to the mailing list
>>> - use the "share with" option, although I do not see how to use it as it
>>> seems fixed to "project members" without possibility to change it or
>>> add anything (perhaps this is a feature for pay versions only?)
>>> I'm not sure if these are technically possible, especially if Manymoon
>>> can send messages to the list, and if we can correctly go through the
>>> confirmation procedure.
>>> Peter, what are the mailing restrictions on the list?
>>> Assuming it is, adopting this solution means that all comments are sent
>>> to the list and to the regular members. So, some people will receive
>>> these twice by email.
>>> In addition, for unimportant comments, there is no way to avoid sending
>>> them to the list as all others.
>>> So it is not so clear that this is what we want.
>>> If this is not possibile or not desirable, then, we need to decide what
>>> to do.
>>> Peter suggested NOT to use the Manymoon comments at all and use the
>>> mailing list only, arguing that when the information is spread it gets
>>> lost, and that it is a good thing to get all properly archived.
>>> However, I strongly feel the need to have things organized. Personnally,
>>> it is very demanding for me to keep track of what is said in messages.
>>> It would require a strict subject-naming policy to be able to retrieve
>>> the messages relevant to a same task, something I'm not sure we will be
>>> able to implement. This is why I believe Manymoon is a very useful tool,
>>> also with its comments facility.
>>> My suggestion would be to use the comments in the tasks only for local
>>> simple issues. All important or more general issues should be discussed
>>> through the mailing list.
>>> Hoping such a vague categorization is clear enough to be implementable...
>>> Feedback welcome
>>> Laure (04)
Msg Archives: http://ontolog.cim3.net/forum/iaoa-infrastructure/
Committee File-share: http://iaoa.cim3.net/file/work/Committee/Infrastructure/
Committee Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?IaoaInfrastructure
Activities Blog: http://iaoa-activities.blogspot.com/ ...(coming!)
To join: please email committee chair or to: info @ iaoa.org
IAOA website: http://iaoa.org (05)