Talk:Goals

From html4all

Jump to: navigation, search

liacelalcnaa

Contents

[edit]

What are Goals?

These goals are statements describing what html4all hopes to accomplish. Goal statements answer the question "What?" What are we going to do? They list what actions we intend to take. They refer to things we need to undertake to achieve the Mission of html4all. (In contrast the mission statement answers the question "Why?" Visit the mission statement talk page for details.)

[edit]

Adding Objectives to the Goals?

We might want to think about adding Objectives to the Goals or having a separate Objectives page.

An objective is a specific result, consistent with a goal and the mission. Objectives break the goal down into smaller parts that provide specific, measurable actions by which the goal can be accomplished.

  • Goals are broad; objectives are narrow.
  • Goals are general intentions; objectives are precise.
  • Goals are abstract; objectives are concrete.

For instance for the "Investigate and document issues" goal consider adding 4 objectives like:

  • Investigate and document issues, through research, testing, and analysis.
  1. Flag issues that bear looking into by the WAI's Protocols and Formats Working Group (PFWG).
  2. Follow the process that Judy Brewer outlined in her May 24, 2007 email: RE: WAI mandate to work with other WGs.
  3. Present documentation to PFWG and the HTML 5 WG.
  4. Ask PFWG for an official response.

We may also what to consider using SMART objectives:

  • Specific
  • Measurable
  • Achievable
  • Relevant
  • Time-bound

Notes on social context section

I added most of Josh's social context discussion to the mission statement. Social context is more about the why that the what. ~Laura

[edit]

First Draft Mockup

[edit]

In an open, honest, collaborative, and respectful way html4all will:

  • Foster constructive feedback for the HTML Working Group.
  • Exchange information and educational materials.
  • Keep one another apprised of activities (particularly in regards the Wiki, user testing, research, and construction of test suites and sample pages).
  • Discuss strategies for superior solutions to outstanding problems.
  • Investigate and document issues.
[edit]

First Draft Feedback and Suggestions

  • First Draft Survey Results
    • Keeping Apprised Point
      • Patrick: "in regards the" change to "regarding the"
    • Discussing Strategies Point
      • Patrick: drop "superior" from "superior solutions"
    • Investigating Issues
      • Gregory: add "in a complimentary effort to that being undertaken by the HTML WG in W3C space"
    • Additional Goals
      • Leif: add a goal about being diverse and differ in opinions.
      • Added a draft Objectives Wiki Page for items that are more concrete with specific results.

I began incorporating the feedback from first draft into the second draft mockup - LauraCarlson 06:45, 15 October 2007 (PDT)

[edit]

Second Draft Mockup

[edit]

In an open, honest, collaborative, and respectful way html4all will:

  • Foster constructive feedback for the HTML Working Group.
  • Exchange information and educational materials.
  • Keep one another apprised of activities (particularly regarding the Wiki, user testing, research, and construction of test suites and sample pages).
  • Discuss strategies for solutions to outstanding problems.
  • Investigate and document issues, in a complimentary effort to that being undertaken by the HTML WG in W3C space.
  • Always be mindful of diverse and differing opinions.
[edit]

Second Draft Mockup Discussion

Please share your second draft thoughts and comments. Thanks! - LauraCarlson 06:09, 19 October 2007 (PDT)

[edit]

Third Draft Mockup

[edit]

In an open, honest, collaborative, and respectful way html4all will:

  • Foster constructive feedback for the HTML Working Group.
  • Investigate and document issues, in a complimentary effort to that being undertaken by the HTML WG in W3C space.
  • Collaborate via the html4all mailing list and Wiki.
  • Be considerate of diverse and differing opinions.
[edit]

Third Draft Mockup Discussion

I combined the three "Exchange information", "Keep one another apprised", and "Discuss strategies" goals into one simple "Communicate Via the html4all Mailing List and Wiki" goal and moved those specfic details of how we will communicate to the Objectives document. The Objectives are more of a "how we are going to reach these goals" document. Is this an improvement or not?

Please share your third draft thoughts and comments. Thanks! - LauraCarlson 13:03, 21 October 2007 (PDT)

Zara: Hi Laura. Great work once again. Here are my general comments. I have read both the "Goals" and "Objectives" proposals and after thinking about it more clearly, I am a bit perplexed. I think that, in English perhaps, goals and objectives generally amount to the same thing though I understand that goals can be broader and objectives more specific. When reading the "Objectives" document however, I feel that they seem more like "Means" to me (in French, we would say "moyens"), that is, how we intend to achieve our goals. To me, objectives are not hows but more specific whats. So, in that perspective, I think I preferred mock-up number 2. But you know, I could be completely wrong.

And in light of what I have written above, I feel that item 4, "Always be mindful of diverse and differing opinions" (and notwithstanding that I am not completely sure what being mindful signifies but am guessing it is like taking something into consideration?), is not a goal but rather a means of being "open, honest, collaborative and respectful" and since we have already stated that in the title, I feel this is redundant. When I look at the "objectives" listed for this item, it reads more like a code of conduct than objectives and I wonder if this is really necessary at this point. I understand that we have all had bad experiences in this whole adventure but I also think we should not try to over-do it. In short, we already have hit on this idea in several places (Mission Statement, List Guidelines and Moderation Policy and Goals Statement) so I respectfully think we need to relax. Just my opinion of course. These are general comments, I feel unable to really contribute anything more specific, such as editing, at the moment but I hope it helps regardless.

From Laura: Hi Cathrine,

Thanks for the helpful comments. It is wonderful to have someone to bounce ideas off.

Yes, goals are broader. Objectives more specific. Objectives break the goal down into smaller parts that provide specific actions by which the goal can be accomplished. We could rename the objectives, "tasks" instead if you think that is better. Would calling them "tasks" be clearer? We may also want to consider using SMART objectives. They are Specific, Measurable, Achievable, Relevant, and Time-bound.

Yes, mindful means "considerate of"; "aware of"; "attentive to". "Considerate of" might be clearer. I'll change it.

In the goals survey Leif suggested the goal about being diverse and differ in opinions. It may be a bit redundant but it can't hurt putting it in again.

Nevertheless you are absolutely right, after rereading the objectives for that goal, they do seem like a code of conduct or a mediation guide. I think what is needed is different objectives/tasks that can help that goal along. Perhaps a person or several people to take turns as list moderator/mediator(s), to jump in and extinguish fires and keep things on track. "Apply the list guidelines and moderation policy" might be a better objective/task to help accomplish that goal. And then have some of the founders volunteer to help out with it. I'll change it.

Since you prefer mock-up number 2 of the goals, do you also prefer the companion mock-up number 1 of the objectives? It seemed redundant to me to repeat Communicate "via html4all Mailing List", "html4all Wiki", "html4all Wiki Talk Pages" as objectives/tasks for the "Exchange...", "Keep apprised...", and "Discuss..." goals. Those three goals, all seemed to be saying the same thing. They are ways of communicating or collaborating with the same associated objectives/tasks. This became more apparent when I couldn't figure out distinctive tasks for each one of them. Do you foresee differing tasks for them besides using the list and Wiki?

To me mock-up number 2 of the objectives seems to break the goals down into distinctive, specific tasks better so they can be accomplished.

Thoughts? - LauraCarlson 08:39, 29 October 2007 (PDT)

[edit]

Fourth Draft Mockup

In an open, honest, collaborative, and respectful way html4all will:

[edit]

Foster constructive feedback for the HTML Working Group.

  1. Flagging issues that bear looking into by the WAI's Protocols and Formats Working Group (PFWG).
  2. Following the process that Judy Brewer outlined in her May 24, 2007 email: RE: WAI mandate to work with other WGs
  3. Presenting documentation to PFWG and the HTML 5 WG.
  4. Asking PFWG for an official response.
[edit]

Investigate and document issues, in a complimentary effort to that being undertaken by the HTML WG in W3C space.

  • Experiment, create techniques, test, demonstrate, and present code using the Sandbox space inside the Wiki. (Leif, Gez, others?)
  • Examine how XHTML or related specifications could help solve HTML5 Issues. (Jason, others?)
  • Work directly with AT vendors (Debi, others?)
  • Survey users, developers, designers, authors on issues. (Volunteers?)
  • Track issues on the Open Issues Wiki page (Steve, others?)
[edit]

Collaborate via the html4all mailing list and Wiki.

  • Discuss strategies for solutions to outstanding problems and issues. (Any volunteers for discussion leaders?)
  • Exchange information and educational materials and keep one another apprised of activities through periodic reports and documentation. (Everyone)
[edit]

Be considerate of others.

  • Enforce guidelines and policy. (Josh, Catherine, Laura - list monitors/mediators; Rob - List Admin)
  • Patrol and moderate the Wiki (Laura, others? - Wiki Gardeners; Rob, Laura - sysop)
[edit]

Fourth Draft Feedback and Suggestions

From Laura: I've tried to eliminated redundancy and combined similar goals where appropriate.

I've begun to add objectives (the bullet points under each goal) in an attempt to break them down into smaller parts where we can start providing specific, measurable actions and tasks by which the goal can be accomplished. The objectives should be an explicit direction for the action to take and a specific quality of work to be accomplished. The relationship between a goal and supporting objectives is that if we accomplish our objectives we have theoretically achieved our goal.

In order to be able to determine whether we have accomplished our objectives, we might try to include three key components in each objective: measure, level and time. We may also what to consider making them SMART objectives

Thoughts and ideas?

Please add your ideas and comments below. Thanks, - Laura 03:37, 1 November 2007 (PDT)

From Gez: I think the tasks you have are very good. html4all's role is to work alongside the HTML WG to ensure universality isn't overlooked, so I can't think of any more specific tasks than the ones you already have. The tasks need to be quite generic, as the role will require being dynamic in response to what happens within the main group. I would be happy to help create techniques, and help with testing,

From Jason: I would encourage members of this group to review the drafts for the purpose of submitting public comments.

From Laura: I added an objective about submitting public comments to the foster goal. Many thanks to Jason. Also added an objective about face-to-face meetings. Laura 01:42, 18 November 2007 (PST)

From Jason: Comment about added an objective "Examine how XHTML or related specifications could help solve HTML5 Issues."

From Laura: I added an objective "Examine how XHTML..." to the investigate goal. Laura 09:30, 19 November 2007 (PST)

From Laura: Even though I support Jason's request, upon further reflection, this is a departure from what everyone has bought into, so am hesitant to bolt it on the document after this vote. I previously proposed the following process for amendments [1]. If a founder would like to formally amend a previously approved document they should:

  1. Make a motion for an amendment.
  2. Supply the proposed amended text.
  3. Lead discussions of the proposal
  4. Adjust the proposal if needed according to feedback.
  5. Create a survey on the proposed amendment.
  6. Call for a founders vote.
  7. Amend the original document if voting results indicate a critical mass of support.

Jason, I am more than happy to help with getting things into the Wiki and creating the survey. Laura 19:43, 22 November 2007 (PST)

Retrieved from "http://html4all.org/wiki/index.php/Talk:Goals"
Personal tools