[uf-discuss] hResume - Marking up experience and "present" date

[Tantek Ç elik]

On 10/19/06 3:27 PM, "Jeremy Boggs" <jeremyboggs at gmail.com> wrote:

>> Agreed, for now, this is an excellent point to start:
>> 
>>  http://microformats.org/wiki/hresume-issues
> 
> Thanks for setting this up, Tantek. So, if we want to discuss further
> issues with this problem, should we post them there, on that wiki
> page, or continue making comments through email? A while ago I
> responded to Ciaran's last message in this thread, but if that
> response (or at least some form of it) should go on the wiki, I'll be
> glad to do that.

Excellent questions Jeremy.

There is no simple hard and fast rule, but I have found that the following
guidelines seem to help.

1. Discussions work better on the email list (or IRC channel - which is
often faster than email).

2. Conclusions/opinions are better recorded on the wiki.

In general, I tend to prefer the combination of IRC+wiki, but that is
largely my personal preference - YMMV.  Clearly email works better for
discussing more in depth issues.  I've simply found that I am often unable
to keep up with all the different threads, and thus end up not replying to
some for many days (weeks, months), and then important concluding points get
lost because they are never persisted in any form in a place where people
can easily find them.

That is, the wiki is more "reader friendly" than email because you can go to
the wiki and understand "the current state" of things, whereas email
archives are both hard to search and you have to typically read through a
whole thread to understand what points were resolved and how.

Thus even for "issues" - if you believe you have a solid understanding of
what an issue is, and that it is an issue, you could add it directly to the
appropriate *-issues page.  You could then use email as a notification
mechanism that you have raised the issue and provide a URL to it on the
wiki.  OTOH if you're not certain about an issue, then posting to the list
can help to clarify/refine it at which point it should probably be captured
on the wiki - in the hopes that it will be resolved and respective changes
incorporated, and serve as documentation for those who would raise the same
issue in the future.

Thanks,

Tantek