Notes from our TitanPad:

Program Committee

January 9, 2013

Agenda:

Introductions

Theme

Tracks

Timeline

Next steps

Links:

2013 - https://wiki.jasig.org/display/JCON/2013+Conference+Planning

2012 - https://wiki.jasig.org/display/JCON/2012+Conference+Planning

Attendees:

Alan Regan, Pepperdine

Matt Herzog

Debbie Smith

Ian Dolphin

Patrick lynch

Drew Wills

Jenn Cummings

Neal Caidin

Amanda Cynkin

Kelly Geng

Patty Gertz

Benn Oshrin

Jim Helwig

Jason Smith

Tracks and theme from 2012 described here: https://wiki.jasig.org/x/vQURAw

THEME:

Ideas of capturing and promoting the feel of the new organization

Keywording around partnership

Open Solutions, Open Minds // Open Source, Open Minds

Increasing participation in the communities (costs/benefits/sustainability/knowledge/improvements locally by participating globally/community needs)

Open House for Open Source

Moving Forward...

Perhaps something reflecting the mission statement of Apereo???

“collaborate to foster, develop, and sustain open technologies and innovation to support learning, teaching, and research." (Mission statement from bylaws) More at http://www.apereo.org/governance/draftbylaws

Opening minds: Open solutions for an open world

Create context for Open Source? What does Open Source mean? Why it is important and, seemingly, inevitable (therefore needs to be embraced)

It would be nice to have a theme which will regularly appear in presentations

TRACKS - 2012

1 - Awareness and Advocacy - Open Source Software, as a movement, dates back to February 2, 1998 (2/3/98), yet even today, almost 15 years later, awareness and adoption are often hindered by assumptions, misconceptions and a general lack of knowledge regarding open source development, support and implementation. Significant resistance can arise across campuses from non-technical stakeholders, unfamiliar with the open source ecosystem. Presentations discussing non-technical issues around awareness and adoption of open source (as opposed to specific OS applications) are welcome. These presentations might include: the introduction of open source options to your campus; the procurement process for identifying and evaluating options (commercial and open); approaches for addressing common and unique concerns; lessons learned in the implementation, etc.

2 - Design and Development - Sharing is critical among communities creating open software. Please share development projects, design approaches, usability and accessibility improvement plans and projects. Topics may also include best practices in design and development approaches that could be incorporated into software in the future.

3 - Deployment and Integration - Presentations for people who need to make applications work on campus: developers, content providers, team leaders, and evangelists. In particular, we would like to highlight work that integrates community source projects within enterprise infrastructure, and with each other.

4 - Expanded Solutions - For most organizations open source software is one important component of a complex ecosystem of systems and tools supporting teaching, learning and research. Please share your experiences and successes integrating solutions to expand the benefit to your faculty and students.

I think 4 should be incorporated into 6. I Agree

5 - Getting Started - Sessions for newcomers: from faculty to developers, administrators to trainers, students to tech support. Learn the steps to evaluate, plan, deploy, promote, and support software on your campus.

6 - Leadership and Future Directions - Open software is an element within your broader strategy and goals. How are institutions using open software to achieve strategic goals? What changes and opportunities on the horizon should be influencing the direction of the community? What other trends, advances and challenges should become part of our community planning and dialogue?

7 - Teaching, Learning, Portfolios and Research - Technology to improve the quality of teaching, learning and research. Please share case studies of effective teaching, research and collaboration practices as well as new approaches to technology-enabled teaching and research.

I suspect we'll need to break this out a little; self paced learning has been mentioned - analytics still has a high profile. What's the MOOC experience out there?

I would love to see a balance between technical tracks and using tools either teaching and learning or other (product) open source tools - not sure how viable that is

8 - Technical Management - Deploying, supporting and managing open software is critical to its success. Please share your best practices and approaches in creating and maintaining open software successfully for your users.

Is this focussed on deployment like 3, or developing like 2 above or more an intent to think of support?

How to get people connected

pins/ribbons/stickers

BOF - that are a bit more organized

Lunch - break into 4 constitutent groups

Session Times

60 minues with 10 minutes inbetween

50 minutes with 10 minutes in between

45 minutes with 15 minutes in between

Speaker Instructions

Put together a sheet of dos and don'ts for speakers

Action Items

All: Work on Theme and Tracks

All: Send to Alan any presentation pointers

Alan: Give permission to those who don't have it on Wiki

Alan: Evaluations from last year to committee

CONCENTRA: Survey results from last year's survey on what do you want to hear

TIMELINE:

https://wiki.jasig.org/display/JCON/2013+Conference+Program+CFP+Deadlines+and+Timing

Rolling acceptance of papers

CHAT HISTORY:

January 9, 2013

10:06 Jenn Cummings: If someone is outside (windy?) can you mute yourself?

10:06 Deb Smith: Can folks put their phones on mute until they need to talk

10:07 Patrick Lynch: manage excellently

10:09 unnamed: I don't think I have a log in to the wiki?

10:09 Neal Caidin: me - Neal

10:09 Neal Caidin: never mind

10:09 Neal Caidin: I see the sign up

10:15 Amanda Cynkin: My suggestion would be to include a separate track for self-paced courses, or to insert that into an existent track, so we can ask for proposals for this audience as well.

10:16 Amanda Cynkin: yes, trying to speak. my skype is not working well.

10:17 Amanda Cynkin: I'm not sure where to suggest this, but I and my coworkers last year also felt that there was a lot for professors on how to develop courses, and for developers, but not for actual practical usage of tools.

10:18 Patty Gertz: I have a silly question...are we gearing the presentations towards CLE 2.9 or OAE?

10:18 Kelly Geng: interesting question, but not from me :-)

10:19 Neal Caidin: Yeah, that is an interesting question

10:20 Patty Gertz: which question? The OAE CLE one?

10:20 Matt Hertzog: this chat is interesting. i didn't type anything until now.

10:20 Neal Caidin: To me/ OAE - CLE is interesting

10:20 Neal Caidin: imagining a balance of some sort, but don't know

10:21 Matt Hertzog: Hahah I'm the one that asked the CLE/OAE one...some reason said I was Patty...

10:21 Neal Caidin: plus it is a moving or unknown quantity to some extent

10:22 Ian Dolphin: Don't feel we should "gear" to any particular software

10:23 Jim Helwig: I'm here now

10:30 Neal Caidin: Sakai CLE developer community would like to know about local development efforts

10:30 Neal Caidin: so that they can advise/guide/evaluate for the core tool

10:33 Neal Caidin: Also there might be interest in a "User Focus group" (from a Sakai CLE working perspective)

10:36 Matt Hertzog: I agree with Amanda

10:38 Neal Caidin: bless you

10:38 Patrick Lynch: . mute to sneeze!

10:40 Neal Caidin: people will appreciate an option for early entry

10:40 Neal Caidin: for planning and budget

10:41 Neal Caidin: (not including the procrastinators, which is probably a lot!)

10:52 Neal Caidin: +1 to fill the gaps comment!

10:56 Patrick Lynch: abstracts do not inform us of the quality of the presentation

10:57 Patrick Lynch: +1 pointers

10:57 Neal Caidin: +1 pointers

11:00 Ian Dolphin: I have another call on the hour... thanks to everyone for participating and great suggestions!

11:01 Neal Caidin: bye Ian

11:02 Drew Wills: +1 60 min sessions

11:02 Amanda Cynkin: +1 60 mins

11:05 Jim Helwig: Drew is one of those long winded people. ;-)

11:05 Drew Wills: lol

11:05 Jim Helwig: I'm suprised he didn't vote for 90

11:05 Patrick Lynch: there are different session types, Q&A doesn't make sense for some

11:05 Neal Caidin: I agree, no hard line for Q&A

11:05 Neal Caidin: though often nice to have

11:06 Drew Wills: from my perspective, 45 or 50 or 60 makes little difference... the big question is whether we'll offer sessions of different lengths, and i feel we shouldn't

11:06 Amanda Cynkin: no hard line, but the option is nice. some sessions i wished would go longer, some shorter. however, standardizing is useful for scheduling

11:06 Amanda Cynkin: unless you want to say 45 mins in the mornings, 30 in the afternoon, etc

11:06 Patrick Lynch: back to pointers I suggest

11:06 Neal Caidin: Interesting idea to have shorter sessions in afternoon

11:06 Jim Helwig: Interesting point about scheduling different lengths at different times

11:06 Neal Caidin: folks usually have shorter attention span as day goes on

11:07 Amanda Cynkin: that would be me...

11:07 Patrick Lynch: i do

11:07 Neal Caidin: Attendees are the main focus

11:07 Neal Caidin: not presenters!

11:07 Neal Caidin: (imo)

11:07 Amanda Cynkin: i was talking about attendees

11:07 Neal Caidin: I know

11:07 Neal Caidin: agreeing with you

11:07 Amanda Cynkin: the nvm

11:07 Amanda Cynkin: then*

11:08 Neal Caidin: :-)

11:09 Patrick Lynch: good call - thanks Alan

11:09 Matt Hertzog: Good meeting...hope you feel better Alan

11:09 Neal Caidin: +1 thanks Alan

11:10 Alan Regan: Thanks, all!

11:10 Kelly Geng: feel beter.

11:10 Kelly Geng: better

Browser not supported