ODP Wiki pages on Github

Description

MVP Definition / Acceptance Criteria

  • Program participants can login read, write, edit and comment wiki pages

Assumptions

  • Banks can access Github

Tasks

  • Test (and validate) project activity site hosting with GitHub Wiki (+ODP‌-17+)

  • Create (chat and/or email) bot to write, edit and comment site pages (+ODP‌-3+)

Next steps
1. Finalise ODP Wiki migration to GitHub (2-3 days)

2. Document (as a Wiki sub-pages) (2 days)

  • How to edit content (for project participants)

  • How to contribute (for anyone else)

  • Confluence-to-GitHub migration and how to setup GitHub Wiki from scratch

3. Send out notification to other PMCs (1 day)

Acceptance Criteria

None

Activity

Maurizio Pillitu 
August 12, 2019 at 2:19 PM

Feedback from Voice PMC, while working on https://github.com/finos/voice-metadata-standard/wiki

1- You can only attach images or other type of attachments through git commit - there is no tool to attach files on GH Wiki. You can add images with valid URL's but this requires that the user have a valid URL of the image.
2 - No comments on GH wiki - This was used in the meeting notes in our group. My suggestion here is to recommend to people to always create issues or use maillist instead of commenting on meeting notes.
3 - Need HTML for multiline cells on meeting notes - It's not easy to write multiline notes on markdown table cells, user need to use HTML tags for that(AFAIK). I've changed from tables to list of items in the migration.

See https://groups.google.com/a/finos.org/forum/#!topic/voice-pmc/pmGDBPpL-tQ

Maurizio Pillitu 
July 9, 2019 at 10:29 AM

Apart from the socialization bit, this task is complete, you can find the results on https://github.com/finos-fdx/odp-test/wiki

Gabriele Columbro 
June 19, 2019 at 6:55 PM
(edited)

Moving this on top of the backlog for discussion per my conversation with today, given similar topics came up during the ODP WG.

This should not be assigned to me given you folks can work directly with each other. The issue require scope review / more info so leaving unassigned because it can’t be actioned yet by .

Maurizio Pillitu 
February 27, 2019 at 5:59 PM

Reminder: involve Will Quan (JPMC) and George Grant (GS)

Gabriele Columbro 
February 12, 2019 at 12:58 AM

I think this issue requires a bit more thinking through and plan of attack in terms of:

  • Documentation (this is another standard functionality offered by ODP, should be documented alongside with ODP‌-67 Document Foundation-provided standards release and docs process) and training material ( do you have some wiki best practices here from projects out there?)

  • Socialization / comms plan: we need to make it very clear to the Community that this is a standard option on announce@. And do maybe a blog post. given we a moving to GH, would be worth for you to write a short blog post to announce this?

  • Estimation: can you add your best guess of story points you think it will take.

Regardless, moving up in the backlog.

Unresolved

Details

Assignee

Reporter

Story Points

Priority

Fix versions

Created August 28, 2018 at 4:34 PM
Updated August 12, 2019 at 2:19 PM