[sakai2-tcc] Summary - Re: TCC - CLECC meeting, Wednesday 8 am Eastern - 1 pm GMT
Anthony Whyte
arwhyte at umich.edu
Wed Jan 23 10:04:59 PST 2013
Re: the survey. "Original scope" as in: first seven questions as originally worded or first seven questions as newly worded? If the former, at least modify the wording of the question regarding which "release" do you use so that it does not imply that using maintenance branch code is the same as using an official tag.
I also think it a mistake not to enquire about the frequency with which schools can/want to absorb official releases, whether .0 or maintenance. Such data could help us better calibrate our release cycles to actual community needs. We should ask the question now, not later.
In other words the survey at a minimum should ask
Who are you?
Email address?
What organization do you represent?
What CLE version are you currently running?
When are you planning your next upgrade?
Do you plan on utilizing an official CLE community release during your next upgrade?
How many upgrades of your CLE installation are you willing/able/permitted to perform in a given year?
I regard the last two questions as particularly important from a release team perspective. If, for example, we find that few schools use our tags and prefer instead to run off the maintenance branch--then we should rethink our release strategy at least insofar as maintenance releases are concened. If, for example, we find that schools would love to see 3-4 release cycles per year for a given branch then we should see if we can try and shorten our release cycles. Whatever the data reveals we should use it to align our output to Community demand.
Cheers,
Anth
On Jan 23, 2013, at 9:32 AM, Neal Caidin wrote:
>
> 2.9.1 - just a comment or two emerged which sounded to me like appreciation that we have good movement on the release (if I got this wrong, please feel free to correct).
>
> Survey - this was the bulk of the discussion. Would have been nice to transcribe the discussion, but here is the bottom line. I'm planning to release the survey with it's original scope, which I think is the first seven questions. And, plan to have one or two more surveys, spaced out from each other with clear purposes. As we discussed the Help documentation issue (see below), we recognized it would be good to have input from the community. So the thinking is to have multiple surveys, each with their own well-defined scope. Tool questions, Community connections, etc. Specifics TBD. There is not a consensus on this approach among TCC, that I can tell, but I'm planning on moving forward for now and we'll see what happens.
>
> Help documentation - general acknowledgement that there is no clear person/institution/group that has bandwidth to devote to this issue. The problem is a dependency on the IU knowledge base, which needs to be retired, and simplification of the process from a technical perspective while keeping the workflow a reasonable one to encourage the great efforts that the Documentation group has made to keep the information up to date. This connected back with the Survey question. Two major themes that emerged are 1) how about finding out if existing vendors/institutions have already solved this problem for themselves and get them to share ; 2) Query the community (survey) to see what the needs are (i.e. is the context sensitive help still an important feature?). Perhaps this is it's own survey or perhaps this is bundled with a survey on information desired about other tools. TBD. There was skepticism about #1, but still may be worth following up.
>
> CLECC Blurb - go with Megan's suggestion (official job description) as a starting point and add on a sentence to indicate that CLECC is the person to contact if you are not sure where to go to get your question answered (and if you haven't found the online contact forms, etc, I suppose).
>
> "The CLE Coordinator ensures the continued high quality and timeliness of Sakai CLE releases, on a schedule that is appropriate for institutions depending on the CLE worldwide. The CLE Coordinator is a communications prime within the community and facilitates communications." eh, not sure I'm so excited about that wording (second sentence). Suggestions welcome. I'll get final input from Ian D.
>
>
> Thanks,
> Neal
>
>
>
> Neal Caidin
>
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> Skype: nealkdin
> AIM: ncaidin at aol.com
>
>
>
>
>
> On Jan 23, 2013, at 8:21 AM, Anthony Whyte <arwhyte at umich.edu> wrote:
>
>> Tried out the survey as "Sakaiger University" using Chrome. After completing the survey and submitting it I was treated to a blank page that gives no indication of whether or not I completed the survey successfully. Otherwise, the survey reads ok.
>>
>> I don't recall seeing Turnitin or Roster2 included among the contrib tools listed. You might consider adding them as well as a textbox for people to list other "contrib" tools (some local) that they may use and others might find interesting.
>>
>> On the description: Agree with Megan regarding how to describe your role. On the specific text you've floated I favor use of the word "facilitates" over "ensures."
>>
>> Cheers,
>>
>> Anth
>>
>>
>>>> The CLE Coordinator ensures the continued high quality and timeliness of Sakai CLE releases, on a schedule that is appropriate for institutions
>>>> depending on the CLE worldwide.
>>
>>
>>
>>
>>
>>
>> On Jan 23, 2013, at 8:08 AM, Aaron Zeckoski wrote:
>>
>>> Agreed
>>> -AZ
>>>
>>>
>>> On Wed, Jan 23, 2013 at 8:06 AM, May, Megan Marie <mmmay at indiana.edu> wrote:
>>>> Survey looks good
>>>>
>>>>
>>>>
>>>> Description of CLE Coordinator: The high level goal setting is primarily
>>>> handled by the TCC. I’d suggest using the core responsibility listed in
>>>> the job description:
>>>>
>>>> The CLE Coordinator ensures the continued high quality and timeliness of
>>>> Sakai CLE releases, on a schedule that is appropriate for institutions
>>>> depending on the CLE worldwide.
>>>>
>>>>
>>>>
>>>> Megan
>>>>
>>>>
>>>>
>>>> From: sakai2-tcc-bounces at collab.sakaiproject.org
>>>> [mailto:sakai2-tcc-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin
>>>> Sent: Wednesday, January 23, 2013 7:26 AM
>>>> To: sakai2-tcc at collab.sakaiproject.org 2
>>>> Subject: [sakai2-tcc] Meeting in 30 minutes - Re: TCC - CLECC meeting,
>>>> Wednesday 8 am Eastern - 1 pm GMT
>>>>
>>>>
>>>>
>>>> Reminder
>>>>
>>>>
>>>>
>>>> On Jan 22, 2013, at 4:19 PM, Neal Caidin <nealcaidin at sakaifoundation.org>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> Hi TCC,
>>>>
>>>>
>>>>
>>>> Tommorow is the 4th meeting Wednesday of the month, which means an 8 am
>>>> Eastern / 1 pm GMT TCC - CLECC instead of a 10 am Eastern.
>>>>
>>>>
>>>>
>>>> Tentative Agenda
>>>>
>>>> -----------------------------
>>>>
>>>> * 2.9.1 status - if any additional comments or feedback on the new plan
>>>> (2.9.x moved to Longsight QA server for testing this Thurs/Fri. Hopefully
>>>> release next week.)
>>>>
>>>>
>>>>
>>>> * Community Survey - would like to get it out this week. This is what I've
>>>> got so far -
>>>>
>>>>
>>>>
>>>> http://svy.mk/VVN3qi
>>>>
>>>>
>>>>
>>>> * Blurb for my position on Sakai (Apereo I guess) website - this sound okay?
>>>>
>>>> "The CLE Community Coordinator sets goals for the releases of the Sakai
>>>> CLE, coordinates communication between various groups within the community
>>>> to insure a timely and quality Sakai CLE product."
>>>>
>>>>
>>>>
>>>> * Plans for Sakai CLE context sensitive help -
>>>>
>>>> Can we start the discussion? Summarizing Elizabeth Venstra:
>>>> Last summer she had understood that the decision of the group present was to
>>>> move forward with the "divorce" between Sakai help files and the IU KB. To
>>>> quote : "I've already told the IU support consultants who review our version
>>>> of the documents for accuracy that they no longer need to review them for
>>>> the next version of Sakai if we’re not using it. So, those documents that
>>>> are currently listed as Sakai 2.9 in the Sakai KB are accurate, but the rest
>>>> may or may not be. (That’s 93 out of approximately 350-400 that are already
>>>> updated for 2.9, by the way.) And the longer it takes to get another system
>>>> in place, the further away from reality all of the documents may drift. As
>>>> it happens, though, IU is planning to upgrade to 2.9 this summer (most
>>>> likely in May or June), so we may catch up somewhat as part of that process.
>>>> Still, overall, I think our recent experience with the 2.9 release on the
>>>> Sakai side demonstrated that the current system is not working well ." She
>>>> also points out that over time there may be some loss of momentum and energy
>>>> from those who have been volunteering to participate in the documentation
>>>> group.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Teleconference information (Calliflower)
>>>>
>>>> -------------------------------------------------------------
>>>>
>>>> Default Dial-in Number:+1-734-418-9028
>>>>
>>>>
>>>>
>>>> Your Conference Code: 8373263
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Join Online:
>>>>
>>>> https://apps.calliflower.com/myconference/8373263
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Find a Dial in number in your city:
>>>>
>>>> https://apps.calliflower.com/account/call_in_numbers?organizer=328940
>>>>
>>>>
>>>>
>>>> Skype:
>>>>
>>>>
>>>>
>>>> Add ‘calliflowerskype’ as a contact in Skype. You can then call Calliflower
>>>> directly from Skype.
>>>>
>>>>
>>>>
>>>> Cheers,
>>>>
>>>>
>>>>
>>>> Neal Caidin
>>>>
>>>>
>>>>
>>>> Sakai CLE Community Coordinator
>>>>
>>>> nealcaidin at sakaifoundation.org
>>>>
>>>> Skype: nealkdin
>>>>
>>>> AIM: ncaidin at aol.com
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> sakai2-tcc mailing list
>>>> sakai2-tcc at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>>>
>>>
>>>
>>>
>>> --
>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>>> _______________________________________________
>>> sakai2-tcc mailing list
>>> sakai2-tcc at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130123/ba324197/attachment-0001.html
More information about the sakai2-tcc
mailing list