Date: Thu, 28 Mar 2024 14:59:04 -0400 (EDT)
Message-ID: <817951226.28686.1711652344725@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_28685_567469481.1711652344725"
------=_Part_28685_567469481.1711652344725
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Unavailable:
The :yellow-star:<=
/span> represents who will be taking notes for a given meeting. <=
/p>
Meeting Details
Background
Discussion items
Item |
Who |
Not=
es |
DSpace Communication Plan=
Draft A draft document for capturing the audiences, types of com=
munication, and communication channels for DSpace information. This is a dr=
aft for committee reaction and for anyone to add content. |
Jenn, Meg, Pascal |
- Jenn walked the group through the document, reviewed the categories and=
audiences.
- Send a recognition message to actively contributing developers
- What communications would got to other developers who are not as active=
but want to keep up with DSpace.
- Should there be a newsletter, that nightlights features each month?
- List and define the audiences: new adopters, potential adopters, person=
s who know IRs vs those who are completely new to IRs., library school stud=
ents and faculty awareness,
- leadership: if you go too high in the leadership can be too high. =
- Organizations in the ecosystem: CrossRef, ORCID, other groups. Perhaps =
a section on the website or communications once per year. DSpace partners.&=
nbsp;
- Developers who are not core committers could be aspiring committers, co=
uld be starting to be interested in contributing. Could aim information at =
those who might be interested in making their first commit. There are somet=
imes people who are overlooked and who should be nominated as committers.&n=
bsp;
- Rename core committers to active contributors. Separate from developers=
. But all developers are aspiring committers.
- People who are getting actively involved in the project. Want to thank =
them, keep them motivated.
- Can revisit the list and see if we are too granular, merge groups toget=
her
- Could look at position in organization, role in community, level of und=
erstanding of technical detail.
- Repository managers are shaping the individual repository content, not =
the code base.
- Release of major versions, minor versions x.x, security patch, patches =
for older versions: do we communicate about these, or amplify them?, module=
s, testathon for testing and for documentation, requests for community feed=
back or input.
|
Strategic approach to communica=
tions going forward Marketing goals: DSpace 7 Marketing Goals |
Heather, all |
- Need to think about communication as a whole, and these five goals are =
essential. Need to get the community upgraded and onto the new stack. A lot=
riding on doing that communication correctly.
- An agenda item for next month, what do we need to have ready for encour=
aging adoption of DSpace 7? What materials do we create, who has time, what=
do we need to be prepared for the push to move to DSpace 7?
- Who can take action on these goals in the next three months?
|
Wiki translation project update=
|
Mic |
|
Lyrasis event plans that involve p=
romotion of DSpace |
Bram |
DLF November 2020 - August 17 C=
FP Deadline https://forum2020.diglib.org/c=
all-for-proposals/ Northeast IR Day Dec 3rd https://escholarship.umassmed.edu/neirug/2020/ ...
Others on: http://oad.simmons.edu/oadwiki/Events<=
/p>
- Would like to see DSpace featured prominently at LYR events. That doesn=
't always happen. This year just did short topical leadership forums that w=
ere an hour long. Planning virtual member summit for October. A key piece o=
f that will be talking about and showcase use cases from the community supp=
orted programs.
- We have a number of DSpace 7 early adopters who we can share at an even=
t like this. And members are doing really exciting things right now, many o=
f them would be happy to share what they are doing. Can discuss this =
at the next meeting, discuss options for DSpace highlights in events. =
|
Other business, news to share&n=
bsp; |
All |
|
Action items
Item |
Who |
=
td>
| =
td>
|
=
td>
| =
td>
|
=
td>
| =
td>
|
=
td>
| =
td>
|
=
td>
| =
td>
|
------=_Part_28685_567469481.1711652344725--