https://support.zoom.us/hc/en-us/articles/203806119-Will-Zoom-Work-Internati... For those that have computer issues, international call-in numbers: https://zoom.us/zoomconference On Nov 8, 2019, at 10:30 AM, Navarro, JP <navarro@mcs.anl.gov> wrote: On Tuesday we need to review Jens’ and Björn's feedback posted here: https://redmine.ogf.org/boards/43/topics/506?r=522 Jens’ feedback is in two parts, one from ~3 months ago and one from this week. The reviewed document appears in docx and pdf at the top of the above page. Regards, JP On Oct 17, 2019, at 11:19 AM, Navarro, JP <navarro@mcs.anl.gov<mailto:navarro@mcs.anl.gov>> wrote: Agenda: 1) Review GLUE v2.1 feedback 2) Next steps Regards, JP GLUE WG teleconference Scheduled: Nov 12, 2019 at 3:30 PM Central European Time; 8:30 AM to 10:00 AM US Central Location: https://zoom.us/j/164308301 Or iPhone one-tap : US: +16468769923,,164308301## or +16699006833,,164308301## Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 Meeting ID: 164 308 301 Alternate https://webconf.vc.dfn.de/ogf-glue-wg/ <iCal-20191017-111612.ics>

I vote to keep it simple and focus on getting 2.1 out the door. Converting to Markdown, git, or other editing and writing tools can be done as a separate future activity and is broader in scope that the 2.1 document. It applies to all the rendering documents and everything else we currently have hosted on ogf.org. Given the two online editing choices I think Google docs may be the easiest. JP

On Nov 12, 2019, at 11:04 AM, Baptiste Grenier <baptiste.grenier@egi.eu> wrote:

Hi, Thanks all for the feedback and the meeting.

I've been looking at changing the sharing of the glue2.1-specification file in Sharepoint but it requires to change the link (!!) so the old link was removed. I can invite people to use the new one but...

I've also enabled change tracking (via the Desktop version, no other choice (!!!)), but it's not very friendly, changes are not shown directly in the page it seems: https://support.office.com/en-us/article/can-i-use-track-changes-in-word-onl...

``` You can’t see tracked changes in Word for the web but they’re still there. When you open a document in Word for the web that has tracked changes, they’re preserved and any changes you make will also be tracked. You just won’t see them until you open the document in the Word desktop application. ```

That's a bit weird (to the least).

And there is no way to have a suggest mode like in Google doc.

So I'm not sure what is the best way to work on this, sending word files back and forth is a pain, and office online doesn't seem to help much, it's error prone and a pain to maintain a consolidated version. Unless you have a better alternative it seems moving to google doc could help working collaboratively on this. We can create this doc if you want. The big question mark is wrt to the formatting that is likely to have at least some issues.

So what should we do? Stay with the semi change tracking support of office online? Use a google doc? Have some github- and PR-based workflow? With regards to GitHub/PR usage Alan started a repo but it's from an outdated version and it's a big markdown file: https://github.com/OpenGridForum/OGF-GLUE

For me it would probably be the cleanest to have a GitHub repo with at least sections in dedicated markdown files, but output/rendering/theming have to be checked and things like tables will probably be problematic. And we need to have something usable quickly.

We are happy to sue whatever you think is appropriate but we need to agree ASAP.

We are Looking forward to hearing from you.

Best, Baptiste

Le 12/11/19 à 15:24, Navarro, JP téléscripta :

...

https://support.zoom.us/hc/en-us/articles/203806119-Will-Zoom-Work-Internati...

For those that have computer issues, international call-in numbers:

https://zoom.us/zoomconference

On Nov 8, 2019, at 10:30 AM, Navarro, JP <navarro@mcs.anl.gov> wrote:

On Tuesday we need to review Jens’ and Björn's feedback posted here: https://redmine.ogf.org/boards/43/topics/506?r=522

Jens’ feedback is in two parts, one from ~3 months ago and one from this week.

The reviewed document appears in docx and pdf at the top of the above page.

Regards,

JP

On Oct 17, 2019, at 11:19 AM, Navarro, JP <navarro@mcs.anl.gov<mailto:navarro@mcs.anl.gov>> wrote:

Agenda:

1) Review GLUE v2.1 feedback 2) Next steps

Regards,

JP

GLUE WG teleconference Scheduled: Nov 12, 2019 at 3:30 PM Central European Time; 8:30 AM to 10:00 AM US Central Location: https://zoom.us/j/164308301 Or iPhone one-tap :

US: +16468769923,,164308301## or +16699006833,,164308301##

Or Telephone:

Dial(for higher quality, dial a number based on your current location):

US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968

Meeting ID: 164 308 301

Alternate https://webconf.vc.dfn.de/ogf-glue-wg/ <iCal-20191017-111612.ics>

-- Baptiste Grenier | Senior Operations Officer | baptiste.grenier@egi.eu EGI Foundation (Amsterdam, The Netherlands) Phone: +31 (0) 627 860 852 | Keybase: gwarf | Skype: baptiste.grenier.egi | @baptgrenier

EGI: Advanced Computing for Research The EGI Foundation is ISO 9001:2015 and ISO/IEC 20000-1:2011 certified

I think we should start creating the entire OGF-GLUE githug directory structure, identify all the documents we will need to convert, and even put placeholders in GitHub. I’m willing to help out and work on it in parallel to GLUE 2.1 as long as we don’t make the conversion a pre-requisite to releasing 2.1. JP On Nov 12, 2019, at 11:17 AM, Sill, Alan <alan.sill@ttu.edu<mailto:alan.sill@ttu.edu>> wrote: This would be fine also, but can I suggest that a document be started to begin the conversion process so that we can start any future revisions from Markdown? Alan On Nov 12, 2019, at 11:14 AM, Navarro, JP <navarro@mcs.anl.gov<mailto:navarro@mcs.anl.gov>> wrote: I vote to keep it simple and focus on getting 2.1 out the door. Converting to Markdown, git, or other editing and writing tools can be done as a separate future activity and is broader in scope that the 2.1 document. It applies to all the rendering documents and everything else we currently have hosted on ogf.org<http://ogf.org/>. Given the two online editing choices I think Google docs may be the easiest. JP

Dear all, Please let me know if you can access the following document: https://drive.google.com/a/egi.eu/file/d/1RnFYmC1IGKJTQtOKz1s1HEOBmOOva2gc Document should be publicly available but it's expected to require authenticated access to be able to suggest changes that we will be able to review after. If needed I can also give straight write access, just let me know. Best regards, Baptiste Le 12/11/19 à 18:17, Sill, Alan téléscripta :

This would be fine also, but can I suggest that a document be started to begin the conversion process so that we can start any future revisions from Markdown?

Alan

On Nov 12, 2019, at 11:14 AM, Navarro, JP <navarro@mcs.anl.gov<mailto:navarro@mcs.anl.gov>> wrote:

I vote to keep it simple and focus on getting 2.1 out the door. Converting to Markdown, git, or other editing and writing tools can be done as a separate future activity and is broader in scope that the 2.1 document. It applies to all the rendering documents and everything else we currently have hosted on ogf.org<http://ogf.org/>.

Given the two online editing choices I think Google docs may be the easiest.

JP

-- Baptiste Grenier | Senior Operations Officer | baptiste.grenier@egi.eu EGI Foundation (Amsterdam, The Netherlands) Phone: +31 (0) 627 860 852 | Keybase: gwarf | Skype: baptiste.grenier.egi | @baptgrenier EGI: Advanced Computing for Research The EGI Foundation is ISO 9001:2015 and ISO/IEC 20000-1:2011 certified

HI all, I agree about the idea of switching to GitHub and Markdown. I tried as Baptiste said to convert an old version as an experiment from Word to Markdown with automated tools, but this produced only marginally satisfactory results. I think the best thing would be to start as suggested with a new set of organized separate Markdown files from scratch. Note this has the advantage once you have done it that all further changes to the document can be handled as pull requests. The online tools in GitHub make it easy to produce such pull request changes, even for beginners, with no further software tools required (although the usual set of git and GitHub tools work fine also for doing this). Of course, there are other ways to use a GitHub repository other than Markdown, but the effort that is there was intended to at least start the conversion process. It can be abandoned and replaced as desired. I can add anyone who wants to be included to the @OpenGridForum/OGF-GLUE GitHub team (https://github.com/orgs/OpenGridForum/teams/ogf-glue/members) and make the group leaders the maintainers, so that you can do this yourself moving on. We are trying to modernize OGF support for working groups and move to using GitHub for group support, so this would be very desirable from our point of view. Please let us know of anything we can do to make this option more workable for the group and attractive. Several of you may already have invitations pending to join this group, so please check your GitHub accounts. Others who want to join, please send me your GitHub account IDs to make it easier to find and add you. Alan On Nov 12, 2019, at 11:04 AM, Baptiste Grenier <baptiste.grenier@egi.eu<mailto:baptiste.grenier@egi.eu>> wrote: Hi, Thanks all for the feedback and the meeting. I've been looking at changing the sharing of the glue2.1-specification file in Sharepoint but it requires to change the link (!!) so the old link was removed. I can invite people to use the new one but... I've also enabled change tracking (via the Desktop version, no other choice (!!!)), but it's not very friendly, changes are not shown directly in the page it seems: https://support.office.com/en-us/article/can-i-use-track-changes-in-word-onl... ``` You can’t see tracked changes in Word for the web but they’re still there. When you open a document in Word for the web that has tracked changes, they’re preserved and any changes you make will also be tracked. You just won’t see them until you open the document in the Word desktop application. ``` That's a bit weird (to the least). And there is no way to have a suggest mode like in Google doc. So I'm not sure what is the best way to work on this, sending word files back and forth is a pain, and office online doesn't seem to help much, it's error prone and a pain to maintain a consolidated version. Unless you have a better alternative it seems moving to google doc could help working collaboratively on this. We can create this doc if you want. The big question mark is wrt to the formatting that is likely to have at least some issues. So what should we do? Stay with the semi change tracking support of office online? Use a google doc? Have some github- and PR-based workflow? With regards to GitHub/PR usage Alan started a repo but it's from an outdated version and it's a big markdown file: https://github.com/OpenGridForum/OGF-GLUE For me it would probably be the cleanest to have a GitHub repo with at least sections in dedicated markdown files, but output/rendering/theming have to be checked and things like tables will probably be problematic. And we need to have something usable quickly. We are happy to sue whatever you think is appropriate but we need to agree ASAP. We are Looking forward to hearing from you. Best, Baptiste Le 12/11/19 à 15:24, Navarro, JP téléscripta : https://support.zoom.us/hc/en-us/articles/203806119-Will-Zoom-Work-Internati... For those that have computer issues, international call-in numbers: https://zoom.us/zoomconference On Nov 8, 2019, at 10:30 AM, Navarro, JP <navarro@mcs.anl.gov> wrote: On Tuesday we need to review Jens’ and Björn's feedback posted here: https://redmine.ogf.org/boards/43/topics/506?r=522 Jens’ feedback is in two parts, one from ~3 months ago and one from this week. The reviewed document appears in docx and pdf at the top of the above page. Regards, JP On Oct 17, 2019, at 11:19 AM, Navarro, JP <navarro@mcs.anl.gov<mailto:navarro@mcs.anl.gov><mailto:navarro@mcs.anl.gov>> wrote: Agenda: 1) Review GLUE v2.1 feedback 2) Next steps Regards, JP GLUE WG teleconference Scheduled: Nov 12, 2019 at 3:30 PM Central European Time; 8:30 AM to 10:00 AM US Central Location: https://zoom.us/j/164308301 Or iPhone one-tap : US: +16468769923,,164308301## or +16699006833,,164308301## Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 Meeting ID: 164 308 301 Alternate https://webconf.vc.dfn.de/ogf-glue-wg/ <iCal-20191017-111612.ics> -- Baptiste Grenier | Senior Operations Officer | baptiste.grenier@egi.eu<mailto:baptiste.grenier@egi.eu> EGI Foundation (Amsterdam, The Netherlands) Phone: +31 (0) 627 860 852 | Keybase: gwarf | Skype: baptiste.grenier.egi | @baptgrenier EGI: Advanced Computing for Research The EGI Foundation is ISO 9001:2015 and ISO/IEC 20000-1:2011 certified