Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community:pmc_meetings:minutes20220711
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| community:pmc_meetings:minutes20220711 [2022/07/11 15:05] – [3. Documentation] demiankatz | community:pmc_meetings:minutes20220711 [2022/07/11 15:23] – [7. Community Call Restructuring/Marketing] demiankatz | ||
|---|---|---|---|
| Line 42: | Line 42: | ||
| ===== 4. OLF Update ===== | ===== 4. OLF Update ===== | ||
| - | The vufind.org email domain is now fully functional. We can set up custom vufind.org email addresses as needed. Do we want an address for pmc? What about for code of conduct? Anything else? Does anyone else want to receive forwarded messages from info@vufind.org? | + | The vufind.org email domain is now fully functional. Some questions discussed. We can set up custom vufind.org email addresses as needed. Do we want an address for pmc? What about for code of conduct? Anything else? Does anyone else want to receive forwarded messages from info@vufind.org? |
| + | André asked about traffic levels at info@vufind.org -- currently very low is it has not been advertised yet. | ||
| + | |||
| + | Leila asked about how difficult it is to change forwarding; Demian explained that it's based in Gmail, so fairly straightforward (though we would need to coordinate credential sharing if there' | ||
| + | |||
| + | After discussion: Demian will set up info@vufind.org to forward to entire PMC, rather than create overhead by making multiple addresses. If traffic becomes too high, we can revisit/ | ||
| ===== 5. Release Planning ===== | ===== 5. Release Planning ===== | ||
| Line 57: | Line 62: | ||
| Next steps: | Next steps: | ||
| + | * Craig will finish designing form (checkbox conversion, add CAPTCHA) and will share CSS updates with Chris. | ||
| * Link to RSP agreement from support page and GitHub. | * Link to RSP agreement from support page and GitHub. | ||
| - | * Create | + | * Leila will work on drafting the RSP logo. |
| - | * Once submission form is ready, link it to main RSP page, then reach out to existing VuFind vendors to gauge interest and solicit feedback (this may also be a good time to discuss trademark compliance, which has been on the " | + | * Once submission form is ready, link it to main RSP page, then reach out to existing VuFind vendors to gauge interest and solicit feedback (this may also be a good time to discuss trademark compliance, which has been on the " |
| - | * Set up a dedicated vufind.org email address, forward that to PMC members, and make it the recipient of application form submissions. Should we use a generic pmc@vufind.org | + | * We will use info@vufind.org for RSP communication for now (as per earlier discussion) |
| ===== 7. Community Call Restructuring/ | ===== 7. Community Call Restructuring/ | ||
| Line 66: | Line 72: | ||
| Should we run a new survey about the content/ | Should we run a new survey about the content/ | ||
| + | Demian volunteered to draft a possible survey. Leila volunteered to help with implementation. | ||
| ===== 8. Possible Future Actions ===== | ===== 8. Possible Future Actions ===== | ||
community/pmc_meetings/minutes20220711.txt · Last modified: 2022/07/11 15:28 by demiankatz