Skip to content

Commit

Permalink
Synchronized build
Browse files Browse the repository at this point in the history
  • Loading branch information
@lektor-bot
lektor-bot committed May 1, 2024
1 parent af62239 commit 3dd1969
Show file tree
Hide file tree
Showing 22 changed files with 2,751 additions and 504 deletions.
Binary file added ...024-04-25-project-meeting-actions/20_workgroup_structure_governance_image01.jpg
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
505 changes: 505 additions & 0 deletions blog/2024-04-25-project-meeting-actions/index.html
View file

Large diffs are not rendered by default.

272 changes: 218 additions & 54 deletions blog/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -137,9 +137,224 @@ <h1>Invenio Blog</h1>
<header class="blog-top-header">
<h2>

<a href="/blog/2024-04-23-april-project-meeting-update/">InvenioRDM Partner Meeting Summary, March 2024</a>
<a href="/blog/2024-04-25-project-meeting-actions/">InvenioRDM Partner Meeting / Developer Workshop: Action Items</a>

</h2>
<p class="blog-list-item-meta">
<i class='fa fa-user text-muted'></i>
<span class="author">

Sarah Wiechers

</span>
<i class='fa fa-calendar text-muted'></i>
<span>Apr 24, 2024</span>
<i class='fa fa-users text-muted'></i>
<span class="label invenio-team"><a class="team-url" href="">InvenioRDM</a></span>
</p>
</header>
<div class="blog-list-item-content">
<p><img src="/blog/2024-04-25-project-meeting-actions/20_workgroup_structure_governance_image01.jpg" alt=""></p>
<p>From March 18 - 22 the InvenioRDM partner community met in Münster, Germany, to discuss current challenges and plans for the future of the project. While many smaller questions and issues were addressed immediately on-site, e.g. during one of the “merge parties” or in work sessions resulting from and building upon previous discussions, many sessions ended with clear lists of planned actions for the coming weeks and months.</p>
<p>To showcase the kinds of actions we decided on, and to have something to measure our success by at the next developer workshop, we're sharing here our full list of action items. In the fall, approximately at the half-way-point between the last and the next workshop, the community will meet at a themed Telecon to evaluate this list and see what the status on these plans is.</p>
<p>In the following you can find a list of all sessions and the actions decided upon by the participants. Some of the plans mentioned were already set into action - a huge thank you goes to the motivated community members working on all these actions!</p>
<h2><strong>Community engagement and handling pull requests</strong></h2>
<ul>
<li>document this process in invenio-docs (curator role, responsibilities, templates, schedule, reviewer guide)</li>
<li>make PR checklist more extensive (criticality, bug/feature, packages impacted, target release (old, current, new brach))</li>
<li>merge party this afternoon and on a regular basis</li>
<li>dream parties (form pitch to architecture proposal, mockups)</li>
<li>demo parties</li>
<li>public documentation of people to talk to for packages and features (e.g. list of module maintainers)</li>
<li>dedicated role for community contribution management</li>
<li>identify people involved from the community and their involvement (e.g. searchable expertise board)</li>
</ul>
<h2><strong>Translations / i18n, i10n</strong></h2>
<ul>
<li>test if yaml-files can have four letter codes</li>
<li>group tests Münster approach way of overwriting python strings, java-script</li>
<li>Zack and David try to implement the Münster approach into the official cookiecutter so its easier to use and has a global storage of frontend translations</li>
</ul>
<h2><strong>Large file management</strong></h2>
<ul>
<li><strong>Multipart uploader</strong><ul>
<li><a href="https://github.com/inveniosoftware/invenio-app-rdm/issues/2612">Issue 2612</a></li>
</ul>
</li>
<li><strong>File linking API</strong><ul>
<li><a href="https://github.com/inveniosoftware/invenio-app-rdm/issues/2613">Issue 2613</a></li>
</ul>
</li>
<li><strong>File metadata</strong><ul>
<li><a href="https://github.com/inveniosoftware/invenio-app-rdm/issues/2614">Issue 2614</a></li>
</ul>
</li>
</ul>
<h2><strong>Invenio RDM Version 12</strong></h2>
<ul>
<li>fix the blockers until end of April</li>
<li>document features</li>
<li>translate in May</li>
<li>going forward and release v12 before open repositories</li>
</ul>
<h2><strong>Invenio CRIS</strong></h2>
<ul>
<li>further call for interest in InvenioRDM visio conferences (presentation)</li>
<li>Created a GitHub Discussion to gather more use cases and interest from the community <a href="https://github.com/inveniosoftware/product-rdm/discussions/153">inveniosoftware/product-rdm#153</a></li>
<li>decide between specific in communities and more ambitious in a specific module based on traction</li>
<li>If invenio-communities is the way to go, try to put specific fields in community data model in a bucketed way</li>
<li>deepen code review</li>
</ul>
<h2><strong>Customising Schema</strong></h2>
<ul>
<li>Write a feature request for overlay config for required fields per instance / community.</li>
<li>Improve docs on Custom Fields - checklist on when they're useful, community examples.</li>
<li>Case studies / knowledge sharing of the 'hard way' customisations that have been achieved.</li>
</ul>
<h2><strong>Deployment</strong></h2>
<ul>
<li>do a Session on small one VM deployments</li>
<li>do a Session on Helm charts</li>
<li>update deployment documentation</li>
</ul>
<h2><strong>Digital Preservation</strong></h2>
<ul>
<li>Brush up Invenio-SIPStore (Max) Check out Invenio-Archivematica, or look at the AM Python client (Max) Check if an AM plugin for Invenio is needed (Panna?)</li>
</ul>
<h2><strong>Workflow to keep internal roadmap updated</strong></h2>
<ol>
<li><a href="https://github.com/inveniosoftware/product-rdm/discussions/new?category=ideas">GitHub Discussions</a> implemented for feature request forum </li>
<li>CERN will do quarterly cleaning &amp; updates of roadmap items (Jan, Apr, Jul, and Oct) and will host talks about issues at corresponding Telecons</li>
</ol>
<h2><strong>RDM Curation Workflow</strong></h2>
<ul>
<li>open question is if/how this could go into the core or if it should remain an extra package maintained by TU Graz</li>
<li>ensure possibility to configure aspects in order to meet discussed requirements, use cases, and user stories</li>
<li>upload package to GitHub for future collaboration</li>
<li>after follow-up discussion, one idea is to extend the functionality of the requests in the core and build the curation on top of these changes<ul>
<li><a href="https://codimd.web.cern.ch/_pB2IO2sTy2U6MB67ExW2w#">more details</a></li>
<li>Split approval and acceptance of requests</li>
<li>Requests can be extended with requirements/checks. These have to be fulfilled before a request can be accepted.<ul>
<li>Can be specified per request type</li>
<li>Repository wide requirements are applied to all request types</li>
</ul>
</li>
</ul>
</li>
</ul>
<h2><strong>Harvesting vocabularies</strong></h2>
<ul>
<li>Start a coordinated sprint in May (CERN and Uni Münster).</li>
</ul>
<h2><strong>Creating a place to collect Invenio modules etc.</strong></h2>
<ul>
<li><a href="https://inveniosoftware.github.io/awesome-invenio/">Awesome Invenio</a> - links to the actual GitHub Repository where everyone with a GitHub account can add their or other projects and create a PR for it. It's mainly curated by @egabancho for the time being.</li>
</ul>
<h2><strong>Community workflow improvements</strong></h2>
<ul>
<li>Pitch governance documentation update</li>
<li>Propose group structure (InvenioRDM Interest and Task Groups)</li>
<li>Propose new/additional way of subscribing to the list-serv</li>
<li>Pin and list welcome message and resource list to the welcome channel in Discord</li>
</ul>
<h2><strong>Developing with Devbox</strong></h2>
<ul>
<li>share repository with all used scripts with community</li>
</ul>
<h2>Repeatable installs</h2>
<ul>
<li>always copy <code>package-lock.json</code> from <code>../var/instance/assets/</code> to <code>my-site/</code>. Make sure that <code>git</code> ignores the creation/modification file dates if the file content didn't change</li>
<li>have an extra CLI param in <code>invenio-cli</code> that will:<ul>
<li>copy the <code>package-lock.json</code> from <code>my-site</code> to <code>../var/instance/assets/</code></li>
<li>if the <code>my-site/pipfile.lock</code> is newer than <code>my-site/package-lock.json</code>, then overwrite or fail (some python deps might have changed)</li>
<li>run <code>npm ci</code> instead of <code>npm install</code></li>
</ul>
</li>
<li>the development workflow with linked editable (watched) modules should be tested, to ensure nothing breaks</li>
<li>when in <code>NODE_ENV=production</code>, the above should always happen. When in <code>NODE_ENV=dev</code>, then I can use a new param <code>invenio-cli install --keep-deps</code></li>
<li>New issue tracked here: <a href="https://github.com/inveniosoftware/product-rdm/issues/179">inveniosoftware/product-rdm#179</a></li>
</ul>
<h2><strong>One VM Deployment</strong></h2>
<ul>
<li>improve documentation with the deployment<ul>
<li><a href="https://pad.gwdg.de/hEje65dOTIWuejjf2r30RA#">Docu PR work in progress</a></li>
</ul>
</li>
<li>cookiecutter issue: <a href="https://github.com/inveniosoftware/cookiecutter-invenio-rdm/issues/278">inveniosoftware/cookiecutter-invenio-rdm#278</a><ul>
<li>have a finished docker-compose without dev container</li>
<li>improve secrets by default</li>
</ul>
</li>
</ul>
<h2><strong>Preservation of workshop outcomes</strong></h2>
<ul>
<li>Create a Google form for filling in session information (→ Steve)</li>
<li>Process information from the Google form entries (→ Markus)</li>
<li>Create a repo in the inveniosoftware namespace (→ someone from CERN)</li>
</ul>
<h2><strong>Kubernetes Helm-charts requirements</strong></h2>
<ul>
<li>Issues on the <code>[helm-invenio</code> Github repo](<a href="https://github.com/inveniosoftware/helm-invenio/issues">https://github.com/inveniosoftware/helm-invenio/issues</a>)<ul>
<li><a href="https://github.com/inveniosoftware/helm-invenio/issues/109">Configurable resources for deployments</a></li>
<li><a href="https://github.com/inveniosoftware/helm-invenio/issues/110">Configurable {liveness,readiness,startup}Probes</a></li>
<li><a href="https://github.com/inveniosoftware/helm-invenio/issues/111">Init and Sidecar containers config for web/worker deployments</a></li>
<li><a href="https://github.com/inveniosoftware/helm-invenio/issues/112">Granular env-based solution for "connection string"-like config</a></li>
</ul>
</li>
<li>Share of current community charts:<ul>
<li>University of Münster: <code>helm pull oci://harbor.uni-muenster.de/ulb/invenio --version 0.4.0</code></li>
</ul>
</li>
</ul>
<h2><strong>Workgroup structure - Governance</strong></h2>
<ul>
<li>please contact Lars if you know a good mailing list software! - in progress</li>
</ul>
<h2><strong>InvenioRDM feature request form</strong></h2>
<ul>
<li><a href="https://github.com/inveniosoftware/product-rdm/discussions/new?category=ideas">GitHub Discussions</a> feature request forum implemented </li>
</ul>
<h2><strong>Usage statistics</strong></h2>
<ul>
<li>Created discussions<ul>
<li><a href="https://github.com/inveniosoftware/product-rdm/discussions/181">inveniosoftware/product-rdm#181</a><a href="https://github.com/inveniosoftware/product-rdm/discussions/182">inveniosoftware/product-rdm#182</a></li>
</ul>
</li>
</ul>
<h2><strong>Evaluate proposed strategies for handling PRs</strong></h2>
<ul>
<li>regular merge parties right after Telecons (cut Telecons to 30 minutes) (Sara)</li>
<li>train more people as maintainers with merge rights (in on-site meetings) (CERN)</li>
<li>figure out a clear labeling system (Karolina)</li>
</ul>

</div>
<div class="blog-top-more-link">

<a href="/blog/2024-04-25-project-meeting-actions/">Read More</a>

</div>
</div>

</div>
</div>

<div class="row">
<div class="col-md-12 col-xs-12 block-center">
<div class="blog-post-list">




<div class="blog-list-item col-xs-12 col-md-4">

<div class="blog-list-item blog-list-item-frame">
<header class="blog-list-item-header">
<h3>

<a href="/blog/2024-04-23-april-project-meeting-update/">InvenioRDM Partner Meeting Summary, March 2024</a>

</h3>
<p class="blog-list-item-meta">
<i class='fa fa-user text-muted'></i>
<span class="author">
Expand All @@ -166,20 +381,14 @@ <h2>
</ul>

</div>
<div class="blog-top-more-link">
<div class="blog-list-item-more-link">

<a href="/blog/2024-04-23-april-project-meeting-update/">Read More</a>

</div>
</div>

</div>
</div>

<div class="row">
<div class="col-md-12 col-xs-12 block-center">
<div class="blog-post-list">

</div>



Expand Down Expand Up @@ -769,51 +978,6 @@ <h3>Just the start</h3>
</div>



<div class="blog-list-item col-xs-12 col-md-4">

<div class="blog-list-item blog-list-item-frame">
<header class="blog-list-item-header">
<h3>

<a href="/blog/2021-06-04-community-spotlight/">InvenioRDM Community Spotlight: Summer 2021</a>

</h3>
<p class="blog-list-item-meta">
<i class='fa fa-user text-muted'></i>
<span class="author">

Sara Gonzales

</span>
<i class='fa fa-calendar text-muted'></i>
<span>Jun 7, 2021</span>
<i class='fa fa-users text-muted'></i>
<span class="label invenio-team"><a class="team-url" href=""></a></span>
</p>
</header>
<div class="blog-list-item-content">
<p><img src="/blog/2021-06-04-community-spotlight/Summer.jpg" alt=""></p>
<p>Summer 2021 is an exciting time in the development of InvenioRDM, as the team works towards the Long-Term Support (LTS) version. Here are just a few updates we have to share about recent work:</p>
<h2>Contributions from the community</h2>
<p>InvenioRDM partners are not only local implementers, but frequently contribute their coding expertise to the project. Read <a href="https://www.tuwien.at/en/research/rti-support/research-data/news/news/tu-wien-contributes-to-inveniordm-development">this recent news item</a> about the efforts of TU Wien developer Maximilian Moser related to the share-by-link feature and the authentication modules.</p>
<h2>Usability testing</h2>
<p>One way that the entire community can contribute towards InvenioRDM development is to test the most recent version of the software either through your local implementation or at the <a href="https://inveniordm.web.cern.ch/">CERN sandbox site</a>. Report any bugs you find using this <a href="https://docs.google.com/forms/d/e/1FAIpQLSdExcCjDUMTkaXCU9JHCBqeFfDuCW2kFQGbuZFrr3t77qHOsw/viewform?usp=sf_link">form</a>. Timely and accurate bug reporting gives the entire project a boost!</p>
<h2>Getting the word out</h2>
<p>InvenioRDM will be featured in two sessions at <a href="https://or2021.openrepositories.org/">Open Repositories 2021, June 7-10</a>, “Poster Minute Madness” and the “Repository Rodeo”, both taking place on June 9. If you or someone you know would like an introduction to the software, encourage them to attend!</p>
<p>Are you presenting on InvenioRDM at an upcoming meeting? Please let us know using this <a href="https://docs.google.com/document/d/1HhGtd39TqxleUkK-b5qyPqMjSg8EBqacxSpoDtydmE8/edit?usp=sharing">form</a>.</p>

</div>
<div class="blog-list-item-more-link">

<a href="/blog/2021-06-04-community-spotlight/">Read More</a>

</div>
</div>

</div>


</div>
</div>
</div>
Expand Down
Loading

0 comments on commit 3dd1969

Please sign in to comment.