Inconsistency in referring images

[ritik-malik]

Hi,
I saw that the images in this repository are being referred differently in different markdown files.
A good example would be the directory : focus-areas/when
The following metric markdowns refer to images as:

• Activity Dates and Times : HTML style - <img src=...
• Burstiness : https://raw.githubusercontent.com/chaoss/wg-common/...
• Time to Close : images/abc.png
• Time to First Response : https://github.com/chaoss/wg-common/...

Since there is already an attempt to bring all WG in same structure (doc), can we start by deciding a common way for referring the images...

Also, there is an error in mapping the metric from README, I tried to fix that in PR #109

[GeorgLink]

Thank you for spotting this inconsistency.

We want to use Markdown with relative links, like seen in Time to Close:

![Average and median time to close an Issue from GrimoireLab](images/time-to-close.png)  

Absolute paths, full URLS, and HTML <img> tags should be converted

[sgoggins]

@klumb : Does using markdown relative references require a different set of actions from you than providing a full link to the http:// version of the visualization?

[germonprez]

Sounds like every WG should have an:

'images' folder within each Focus Area

[sgoggins]

@GeorgLink Indicates using markdown relative links does not affect web deployment, and we recommend this be adopted as the standard for image referral.

[klumb]

There is some inconsistency in how this has been done. Relative paths often break on the website, however, there are instances where they have worked in the past. I haven't looked specifically at what folder/file structure works on the website with relative path links.

Absolute paths always work on the website.

[GeorgLink]

Relative paths for images require to start with images/ and never with ./ -- if followed, this will work.

[GeorgLink]

The PR #112 was merged. Issue can be closed