<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Uh oh, looks like I'll have to fork this thread and turn it into a cross-mailing list one!</div><div><br></div><div class="-x-evo-paragraph -x-evo-top-signature-spacer"><br></div><div>Le jeudi 12 mai 2016 à 12:59 -0700, Adelia Rahim a écrit :</div><blockquote type="cite">Hi everyone,<div class=""><br class=""></div><div class="">It has taken a while, but finally we have the bulk of the articles ready for review;</div><div class=""><br class=""></div><div class="">1) <a href="https://wiki.gnome.org/Engagement/AnnualReport/2015/Hackfests">Hackfests</a></div><div class="">2) <a href="https://wiki.gnome.org/Engagement/AnnualReport/2015/Releases">Releases</a></div><div class="">3) <a href="https://wiki.gnome.org/Engagement/AnnualReport/2015/Conferences">Conferences</a></div><div class="">4) <a href="https://wiki.gnome.org/Engagement/AnnualReport/2015/Feature">Feature article on Xdg-app and Builder</a></div><div class="">5) <a href="https://wiki.gnome.org/Engagement/AnnualReport/2015/Outreach">Outreach</a></div><div class="">6) <a href="https://wiki.gnome.org/Engagement/AnnualReport/2015/Accessibility">Accessibility</a></div><div class=""><br class=""></div><div class="">For the reviewers, focus first on content for accuracy and also clarity. I need your assistance to complete the review <u class=""><font color="#5e30eb" class="">by Friday, 20 May 2016</font>.</u> (an article a day helps defray the workload :) )</div><div class=""><br class=""></div><div class="">I’m not expecting major comments on structure and style, as (most of) the writers involved have written for the annual report before. However, if there are any major areas for improvement, please highlight. </div><div class=""><br class=""></div><div class="">As you go along, also look out for spelling, punctuation, capitalisation and consistencies in words and terminologies.</div><div class=""><br class=""></div><div class="">Those on the mailing list, you can also provide feedback at this phase :)</div><div class=""><br class=""></div><div class="">Let’s do this!</div><div class=""><br class=""></div><div class="">best,</div><div class="">adelia</div><div class=""><br class=""></div><div class=""><font size="1" class=""><b style="font-family: arial, sans-serif;" class="">Main Initiative Page: </b><a href="https://wiki.gnome.org/Engagement/AnnualReport/2015">https://wiki.gnome.org/Engagement/AnnualReport/2015</a></font></div><pre>_______________________________________________
engagement-list mailing list
</pre></blockquote><div><br></div><div><br></div><div><br></div><div>Well, I have a question regarding the "<a href="https://wiki.gnome.org/Engagement/AnnualReport/2015/Feature">Feature article on Xdg-app and Builder</a>" currently being drafted for the GNOME Annual Report... XDG-App has often been written as "xdg-app", "Xdg-App" or some other variants. It seems it was not used in a standardized way so far. For example:</div><div><div><br></div><div><a href="https://wiki.gnome.org/Projects/SandboxedApps">https://wiki.gnome.org/Projects/SandboxedApps</a> ("Xdg-App")</div><div><a href="https://en.wikipedia.org/wiki/Xdg-app">https://en.wikipedia.org/wiki/Xdg-app</a> ("xdg-app")</div><div><a href="https://www.freedesktop.org/wiki/Software/xdg-app/">https://www.freedesktop.org/wiki/Software/xdg-app/</a> ("xdg-app")</div><div><br></div><div>To me, the current name makes more sense to be capitalized as "XDG-App", or "XDG App" (as far as I know, XDG is an acronym for "X Desktop Group")… But! It so happens that there was a larger discussion two months ago about the problematic branding of the project, in the thread "The xdg-app story", at <a href="https://lists.freedesktop.org/archives/xdg-app/2016-March/thread.html">https://lists.freedesktop.org/archives/xdg-app/2016-March/thread.html</a> — that discussion had quite a bit of traction, and alternative project names were proposed. It ended with "almost a decision", but no clear announcement on what was decided after all. At that time there was, as Alexander said, "no super hurry".</div><div><br></div><div>…well, that's until I come in and mess with your plans, folks ;)</div><div><br></div><div>Indeed, the annual report makes settling this a bit more urgent, in my view. It would be great if we could get the naming nailed down before the words are etched forever on dead trees—it would hurt the visibility of the project's new identity if we were to publish a brand new article using the old naming.</div><div><br></div><div>According to the Annual Report's wiki page, the plan is to get it off the printing press by the end of June... so time is of the essence.</div></div></body></html>