Shared Problems at DU:
Where They Come From, What They Mean, and Why They Matter
Intro
-
How do we make DU work?
-
UB, a strong organization vs. a project host/umbrella
-
Different perspectives
Possible outcome of seminar
-
Shared understanding of current situation
-
Ideas how to rebalance projects vs. shared resources/infrastructure
-
Concrete plans for development at DU
Focus groups
-
Gets us talking! But...
-
Currently a space for the discussion of shared topics/plans/problems etc.
-
Mainly ad-hoc discussion based on individual initiative
-
Weak agreement on longterm plans
Problem
-
Planning is usually project based
-
Everything "not-project"-based is (more or less) unorganised
-
Non-project infrastructure could enable more efficient project
-
They could already be essential for projects!
-
Discussion: the current situation
- What does or does not work for you?
- What are the daily or recurring painpoints?
- What makes a good day at work?
Shared objectives?
-
What do we mean by “shared”?
-
Shared responsibility?
-
Keeping track of development and maintenance?
-
Active support?
-
-
Essentials vs. Nice-to-have
Shared infrastructure?
-
Search cluster
-
Goobi?
-
API-layer + services
-
Lemmatization
-
Glossary service
-
-
Ansible roles, images etc?
-
Accessibility resources/testing etc.
-
Monorepo
-
Framework for user feedback
-
Utilities (e.g. NPM packages, XML-lib)
Shared organizational objectives?
-
How can we support shared resources?
-
Responsibility?
-
Dev cycles?
-
Testing?
-
-
Shared resources should be in shared, tidy spaces
-
Relationship between developers and project members
-
Define relationship with IT, what services can they provide? Sometimes unclear and even unstable
-
How to make better use of the meetings and standups
Next steps
-
What do we prioritize?
-
Search cluster: what is the timeline?
-
Production ready
-
Test run with SDG dataset
-
Which projects will use the cluster?
-
-
API-layer
-
Framework discussion/decision
-
Development setup vs deployment setup
-
API design
-
How do we follow up on this?
deck
By Tarje Lavik
deck
- 40