Planning for apidays Paris
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 5
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Having met with apidays we agreed to expand out involvement with apidays starting with the conference in Paris in December. There will be several action items created for this but let's start with collecting ideas around what we may do. In the call we discussed:
An education workshop. An instructor will use the education material OAI has created to take those who sign up through the basics of the specifications. What we learn on how to run an education workshop will be reused at future conferences as a regular offering. Separate discussion needed on if some sort of certification would be attempted in this first effort or just some notice of participation.
Some means of soliciting feedback from participants on their use of our specs and their ideas for improvements.
Do we work with apidays to have some data on who attended our sessions?
Do we at least offer newsletter signups on site or other actions that provide us a means to follow up later?
Do we offer participants a means to request ad hoc discussion topics?
Do we ask for financial support from sponsors? Just an example, a tool provider showing in a more hand on session how their product uses the spec. This idea has issues, just trying to promote some discussion.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or implementation entry points are identified in the issue. Start by breaking the conference discussion into scoped action items with clear owners and outcomes; the work is done when the Paris activities and follow-up decisions are defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100