Meeting minutes
Charles: explains to Susan how to scribe...
<Paul-B> Review wording of Ed TF purpose statement, adjust and finalize
Paul: first order to review wording of Ed TF purpose statement
Review wording of Ed TF purpose statement, adjust and finalize
Paul: This is the basic verbiage around the purpose statements, do we need any adjustments…
Google doc was posted for comments…
… we can finalize the doc and move on
<Paul-B> https://
Rick: Perhaps we need to narrow the focus of the first phrase to be format specific
Paul: The initial phrase is simple
Rick: What if people outside the group misunderstand our scope?
Paul: What about this phrase is vague our out of scope?…
Paul: we may have opportunities to narrow the scope as we move forward
Bill: We want to encourage a broader view, most of the publishers I talk to are most interested in subjects outside of the publishing activity…
including accessibility, ?
Bill: web content is getting more webby all the time with publishers putting more content on line. I like the open quality of the statement
Paul: There's nothing wrong with us passing along anything we discover to another wg like the css group
Bill: Something may come up that needs to be addressed, that is already being addressed elsewhere on the web. That may be part of what Rick is getting at.
Paul: I hope/expect we will find people looking for things that already to exist, and we can point them to it…
Wolfgang: "K-12" is typically American, and needs explanation to be country or continent neutral
Wolfgang: suggests "kindergarten" and "primary" and "secondary" though it is difficult to get precise terms since education systems are different among countries
Paul invites Wolfgang to edit this phrase
Charles: I would like to state that we are keeping accessibility in mind
Paul invites Charles to add that verbiage
Rick: I advocate against segmenting markets such as K 12, there are huge markets in Secondary and business learning
<Bill_Kasdorf> +1 to Rick
Paul: we can expand scope, though we don't want to make the scope too broad. Continuing ed, certification, are important aspects
Rick: We can define our scope with the use cases
Rick: K12 is different from higher ed, rather than list out all markets here, identify where we are starting rather than keep a comprehensive list
Paul: How do we capture that from a documentation standpoint?
Rick: the second paragraph actually captures that
Bill: The use case format starts with "I am an X" and I want to do "XYZ" The use cases should be specific
Rick: If the use case presents something not in the purpose statement, do we need to edit the purpose statement?
Rick: Scope would be educators, etc., but not the markets. The markets are not nee3ded
Bill: it is not needed
Paul: Do we not need the user profiles?
Rick: I think those come up in the use cases
Wolfgang: It would be helpful to have an overview, perhaps more refined than we have at the moment
Wolfgang: as a publisher, the more specifc the better, maybe drill down in the categories we have
Paul: This grew out of our desire to not be too narrow with our use cases
Paul: suggests adding ",included but not limited to, the following" after user profiles
correction: Bill: suggests adding "including but not limited to, the following"
Paul: we don't want to limit ourselves to the usual suspects
Paul: we don't need to document the process extensively but we should have a conversation about general scope and have a conversation about the sample use case
Paul: we can mirror that in a template
Paul: do we need a cover letter?
Bill: It could be an option to have a cover letter. I can make calls, but not everyone is the same.
Use Cases
<Paul-B> Sample Use Case
<Paul-B> https://
Gautier: I more or less translated the text we just discussed and will circulate it in French publishing contexts, and he will make the use case for them. This can make for more participation if it is in French …
I have tried to write one using the template, making a lot of paraphrases to fit into the template as it is.
Gautier: The template is complicated, I feel like it is repetitive
Gautier: maybe my use case is too simple
Paul: there will be a learning curve for all of us who are new to use cases and we don't have to be slaves to the format. The important thing is to get the information in there. No need to repeat yourself.
Charles: walks us through the document…
Charles: the main points include the title, the ## is the mark up so it will stand out in github. Write the details as prose…
Charles: make a proposal, after that we have any benefits based on the proposal above…
<CharlesL> https://
Charles: some user stories may have less, you don't have to have everything…
Paul: on github the mark down will make the use case clearer, and people will be able to comment
Bill: This provides a full picture of the situation. A contrasting approach, the use case only focuses on the problem and doesn't propose a solution…
Bill: Perhpas we should end at the use case
Charles: I agree, and not every use case needs a solution
Paul: when we are working with people building the use cases not everyone will have the technical depth to offer a solution…
<CharlesL> I will update my user store accordingly
<Bill_Kasdorf> s/ end at the use case or put subheads in: Problem (what the issue is); Proposed solution (the details) or put subheads in: Problem (what the issue is); Proposed solution (the details)
Paul: sounds like everyone is generally comfortable with the use case format
<CharlesL> https://
Paul: I'll make a version of this for people who don't want to use github when working through this
Susan: suggests using a release or other statement that makes clear the intent of the information being gathered, how information will be stored/used as we do interviews
Paul: no personal information is included in the use case, we may not need people to sign a document…
Paul: it is a fair point to make sure people understand what we are doing with this. The third paragraph states this, is that enough? It might depend who you are talking to
James: We should at least state that everything will be anonymised
Bill: Someone may be working on an idea that would be a competitive advantage, and they may not want to share
Paul: Susan can you paraphrase something short with key concepts: it will be anonymous, no information will be shared
Charles: we will take out any names that we come across and focus on the issue, maybe just general information but nothing that could be used to identify a student
@wolfgang can I correct my spelling? Not having any luck
Paul: this has been a successful meeting, our next meeting will be looking at the use cases that come in
Paul: thanks everyone! See you in a few weeks
<sue-neu> s/eveything/everything
<sue-neu> s/cirulate/circulate/
Charles Gives tips for Scribing
Charles: use s/misspeling/misspelling to correct, rssagent, draft minutes to draft the minutes (can be done multiple times)
you can add a topic with a hook, and put it into the minutes at the point of the hook
Charles: Paul you can send out the minutes using the URL
Paul: we may need to revisit distribution to be sure everyone gets the meeting info I will send the zoom link via email as well