OERu/Planning/Technology working group/Inaugural meeting

From WikiEducator
Jump to: navigation, search

When: 23 May 2014, 12:00PM NZST (Click on link for local time.)
Where: Google hangout

Agenda

  1. Welcome and aims of the meeting
  2. Review and determination of the aims and objectives of the working group
  3. OERu course site design project
  4. OERu course theming examples using the Snapshot approach
  5. OERu course site design project: Request for quotation
  6. Responsive design demonstration for OER1001 - Tim McCallum USQ
  7. Google summer of code: Peer evaluation
  8. Canvas OERu community for code, in-kind or financial contributions?
  9. Syndication/embed code ie on UBC Wiki?
  10. Date of the next meeting

Resource links and proposed aims and objectives of the working group

Links

  1. Jim's blog post summarising theming prototypes - The Course Snapshot approach will guide the RFP for OERu Course Site Design.
  2. Peer evaluation links: Full proposal | Peer evaluation concept design | Consultation feedback

Proposed aims of the working group

  • accommodate the needs and desires of the course development workgroup
  • maintain scalable, secure, cost-effective infrastructure for collaborative course authoring and delivery
  • interoperate with partner institution legacy systems, ideally federating similar systems
  • share open data formats, sources, and services to the greatest extent possible
  • deliver content in a variety of formats, including mobile (maintain separation between content and rendering)
  • implement solutions for customised local branding and theming of shared content resources
  • adapt to the increased importance of audio and video

Proposed objectives of the working group

Currently no proposed objectives - Note that in OER draft strategic plan "to build an OERu partner community source model for technology innovation and infrastructure support."

-- Short term objective: to define what a "community source model" would actually look like on the ground, what people could expect from it.


-- Immediate needs

    • Perceived failings with MediaWiki

-- MediaWiki strong as an authoring environment, not so much as a publishing one

-- worth exploring extensions that might address some of them -- maybe set up a space to catalog and assess them?

      • Simple development platform akin to consumer-grade tools and workflows
      • Need for convivial platform to bring non-techie discussants into the mix
    • SEO... find a search term that works. Not too general, but broad enough to

Minutes and decisions

Currently no proposed objectives - Note that in OER draft strategic plan "to build an OERu partner community source model for technology innovation and infrastructure support."

-- Short term objective: to define what a "community source model" would actually look like on the ground, what people could expect from it.


-- Immediate needs

    • Perceived failings with MediaWiki

-- MediaWiki strong as an authoring environment, not so much as a publishing one

-- worth exploring extensions that might address some of them -- maybe set up a space to catalog and assess them?

      • Simple development platform akin to consumer-grade tools and workflows
      • Need for convivial platform to bring non-techie discussants into the mix
    • SEO... find a search term that works. Not too general, but broad enough to
    • do "we now have to consider a designed environment, rather than continually grafting more (an complicated) hacks onto MediaWiki as baseline Swiss-Army knife?"

Interim step

Google Summer of Code project under way as of this week (Peer evaluation)... if this might work. Action item for next week's model, requires compressed feedback ASAP. A very compressed schedule

    • David P. prepared to test the peer evaluation work product with a UBC ETEC class when it's ready.


  • There is resistance to authoring in MediaWiki, but the ability to syndicate or manage content when it is there is very powerful
  • "there may be multiple valid pathways to authoring. We need to get a better handle on delivery look, feel, and consistency with regard to learner experience. "


WORKFLOW WORKFLOW WORKFLOW (Comment.gif: Do we need a task to start drafting ideas for an OERu workflow? For now have added this as an action item --Mackiwg 01:02, 24 May 2014 (UTC))







Icon key points.gif
Key points
Core items to report to the OERuMC
  • Reviewed and approved aims of the group
  • Considered recent developments in progress with theming of website pages.
  • overview of content authoring / publishing layer considerations
  • need for feedback on Google Summer of Code
  • solicit contributions for the community source objective - code, in-kind, or $$$


Attendance: David Porter, Jim Tittsler, Sarah Lambert, Tim McCallum, Tim Klapdoor, Wayne Mackintosh, Brian Lamb

Agreed for time being to meet weekly for medium term: same day and time, starting a half-hour later


Action items

  1. Transfer objective regarding community source model to working group homepage. - Done --Mackiwg 01:36, 24 May 2014 (UTC)
  2. Establish wiki page to define what a "community source model" would actually look like on the ground, what people could expect incorporating project needs and gaps we need to fill.
  3. Schedule weekly meetings of the technology group - Done --Mackiwg 01:05, 24 May 2014 (UTC)
  4. Establish wiki page for defining OERu workflow (possible integration / collaboration with the partners manual working group?)
Retrieved from "https://wikieducator.org/index.php?title=OERu/Planning/Technology_working_group/Inaugural_meeting&oldid=924591"