[developers] Infrastructure updates
olzama at uw.edu
Fri Jan 15 19:55:29 UTC 2021
Alexandre and I met a couple of weeks ago to continue the discussion on
updating the current DELPH-IN infrastructure (started by Stephan earlier).
Below are the notes from our meeting. Any comments welcome!
DELPH-IN Infrastructure meeting
December 29, 2020, 10--11 am Pacific Time
Present: Alexandre Rademaker, Olga Zamaraeva
*Platforms:* We briefly discussed various platforms, but since we both
agree that GitHub is a competitive solution, we focused mostly on
discussing GitHub. Another possibility mentioned by Emily M. Bender via
email is MediaWiki. Alexandre points out that MediaWiki is more challenging
to serialize in a standard format, which is very important for posterity.
In the end, the top priority is to have a solution that adopts open and
standard formats and the use of cloud-based systems where we do not have to
deal with low-level issues like hardware issues, OS maintenance,
packages/libraries updates, etc.
Considering the use of the GitHub infrastructure, we still have two
alternatives to evaluate:
An off-the-shelf wiki in a particular repository, e.g., doc, under the
A static site generated website hosted by http://pages.github.com
service, possible using the address http://delph-in.github.io. Many
tools, such as http://jekyllrb.com, can produce static sites. They are
easy to maintain, and we can facilitate contributions using the online
GitHub file editor and an automatically building script. See the header of
the Universal Dependencies pages, such as
So far, our impression is that a static site generated website may be
better for maintenance/posterity! But a wiki solution is more comfortable
to start with.
Notifying about recent changes
Having each entry as a page/file
Linking to other pages within the same wiki
Seeing which pages are linked to the given page (reverse links)
Linking to things outside the wiki
Access to/ease of editing/contributing
Access to different versions of a page
Deleted pages: what should be known/done about those?
Rigid vs. flat/free/absent organization
creating groups with privileges (MoinMoin unique feature called ACL)
More we can learn from other experiences:
Is it possible to assume some people will serve as admins? E.g., to
approve changes or modify wiki structure.
How to deal with the pages of our current wiki with ACL restrictions?
Attached materials such as pdfs, videos, etc.? How to better host them?
What is the ideal balance between 'easy to use tools' vs. its 'careless
content creation' consequence?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the developers