sparcopen / open-action-kit Goto Github PK

Things to say:

• Ask for input ideas for actions/resources
• What do we already have, not having to reinvent the wheel.

(https://librariandesignshare.org/

August

Set of light-weight resources that help our audience identify the particular action/s they want to facilitate and move forward with planning, with an emphasis on partnering with local/institutional communities, aligning plans and messaging with institutional goals and interests, and taking your advocacy to the next level. Potential products include:

• Curated lists of existing resources. Leveraging @camillet idea of making existing resources easier to use and navigate.
• Inventorying your current environment, resources
• Talking points
• Live or blogged "show and tell" of specific types of actions, to inspire different models of local activities.
• Forum or blogged interviews on the subject of community engagement and institutional goals alignment.

Complete the Roadmap Exercise

September

Deliver and highlight existing templates for facilitating local messaging, and 2-3 profiles on actions community members are planning. The latter will highlight the what, why, and how and speak across the spectrum of experience we've discussed.

Open Action Kit team members please comment with the following info, so I can add this info to our website's team member page. All fields are optional of course.

• Name
• Position, Organization
• Link to your preferred head shot photo
• Contact info
• Twitter handle

Editable Google Doc

https://docs.google.com/document/d/1baTE7PvBbK9MANPRy6DVHa6NbzKDjHgyOd-vwHSCFEI/edit?usp=sharing

Coordinating Open Access Week activities and other kinds of open advocacy initiatives takes a lot of work, and you should be proud of what you’ve done -- and be prepared to share.

The work you do for open is part of your professional identity and accomplishments. Documenting your work and its outcomes, will help you take advantage of new opportunities when they arise and save you time!

We've collected samples of different kinds of event and outreach reports - read and borrow from them to tell your own story!

Do you want to share your reporting examples or strategies? Please comment on this issue and consider including the following information:

• Your name and preferred contact information (if you want to be attributed and/or are open to people reaching out with questions or ideas).
• The kind of action or event your report describes (e.g. panel discussion, upload-a-thon, social media campaign).
• The metrics you utilized to demonstrate your success and outcomes.
• Sample text or figures.

Thank you, we really appreciate your contribution. ❤️🎆⭐❤️🎆⭐ - The Open Action Kit Team

Starting a thread for folks to submit anything for our next meeting (not sure if this is helpful, if not just close).

cc: @sparcopen/ecl-team

Current state: The repository name is currently mixed case (ECL-OAWeek) and so are the URLs, e.g. https://sparcopen.github.io/ECL-OAWeek/

Desired state: Use all lowercase for all URLs and file names.

Reasoning: avoiding mixed case is not only more elegant (this is subjective, of course, YMMV) but it's also more practical. Why?

• Lowercase version of the first URL will work: https://github.com/sparcopen/ecl-oaweek -- the page opens fine
• Lowercase version of the second URL will fail: https://sparcopen.github.io/ecl-oaweek/ -- you'll see an error message

I would hate to dictate to someone the URL to https://sparcopen.github.io/ECL-OAWeek/ over the phone, along with proper cases for all the letters (ecl dash o a week with capital ecl, capital o, capital a, capital w and lowercase e e k). While you don't have to pronounce the URL often, sometimes you need to do that and doing so with mixed case makes it much harder.

And it's not just URLs, it's also file systems (this affects people who clone the repository to work on it). Some computers (or file systems) are case-sensitive and some aren't. So if you have the "OAWeek" repository on a Windows machine and look for "oaweek", you'll find it just fine. If you do the same on Linux, you will see nothing unless you search for the exact mixed-case string ("OAWeek"). And to make this even more fun, Mac can have it both ways, depending on how a particular disk was formatted.

So unless there is a very good reason to use mixed case, can we just be practical, make it easy for ourselves and use all-lowercase instead?

November

Resources that address strategies for building on and telling the story of your success via/to various forums and audiences (e.g. institutional peers, administrators, your CV).

@sparcopen/ecl-team brainstorm all the things in comments here. If you aren't sure how to comment speak to Joe.

First of all, thumbs up to @rchampieux on creating and updating CONTRIBUTING.md! Very useful and friendly, I like it. 👍

One idea: the current version does not seem to talk about the licensing of submissions. It may be an overkill to introduce CLAs from a practical perspective (although maybe not from the legal perspective) but perhaps it may be useful to at least include in CONTRIBUTING.md that any submissions to the project will be subject to the licensing terms in LICENSE.md?

IANAL, so having someone more experienced (a lawyer? or @txtbks?) put this in better language would help. This may still not be fully enforceable from a legal perspective anyway (at least in some jurisdictions) but I think it may be useful to mention the issue of licensing upfront.

Read-through existing contributions / notes from discussion to revise and complete the Canvas.

LICENCE.md says the license is "Attribution-ShareAlike 4.0 International" while README.md claims "Except where otherwise noted, this work is licensed under a Creative Commons Attribution 4.0 International License."

This should be made consistent.

Also, while we are at it, is it possible to also consider renaming LICENCE.md to LICENSE.md to make spelling consistent? U.S. version is standard, even this repository uses it (see README.md cited above), just not consistently.

October 🎆 🥇 🏁

Tricks & tips for addressing last minutes details; ideas and resources for sharing and connecting a local event with broader/international OA Week network; preparing for assessment and bragging 😸