<div dir="auto">Very true Oliviee. Confluence always had the capability to merge multiple mailing list streams and categorize information from multiple sources. Maybe if we revisit these features, we may be able to bring out something. Other way is to use IFTTT and or Google alerts and drop these pulls into a single source, blog like environment.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 9 Jul 2019, 2:27 am Olivier MJ Crépin-Leblond, <<a href="mailto:ocl@gih.com">ocl@gih.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Dear colleagues,<br>
<br>
in Marrakesh, the Cross Community Engagement Group on Internet
Governance discussed its future with the Board Working Group on
Internet Governance. The decision was to use the Engagement Group as
a platform for sharing information about Internet Governance.<br>
We already do that using email. Unfortunately, there are an
increasing number of parallel tracks and we often drop the ball, or
lose a track altogether.<br>
<br>
My enquiry is as follows: the Engagement Group on Internet
Governance has a LOT of different tracks that are being followed,
from IGF, to CSTD, UN General Assembly, ITU, WTO, etc. etc. <br>
So many tracks, that sometimes the history of what is happening in
these global conferences is being lost - there are just too many
threads. <br>
We've tried putting the threads on WIKI pages, but we are faced with
two hurdles:<br>
1. many people in the working group are not versed in editing WIKIs.
<br>
2. staff does not have time to update WIKIs given the multiplication
of threads. We do not have a "curator" to make sense of the
avalanche of information that's coming our way.<br>
<br>
As a result, what I wanted to ask you is whether you can recommend
any tool that would help with our ability to track several threads
and make these easily accessible to participants, including
historical perspectives, without creating an undue amount of work
for ourselves. Our problem is basically one of Knowledge Management.<br>
<br>
Kindest regards,<br>
<br>
Olivier<br>
</div>
_______________________________________________<br>
ttf mailing list<br>
<a href="mailto:ttf@atlarge-lists.icann.org" target="_blank" rel="noreferrer">ttf@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ttf" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/ttf</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div>