[sakai2-tcc] TCC - CLECC, Wednesday, May 1, 10 am Eastern Daylight/ 2 pm GMT

Tue Apr 30 09:17:30 PDT 2013

Fwiw, I like the integration of Jira and Confluence. The automatic cross referencing is pretty awesome. 

However, 

2 cents.

-- Neal

On Apr 30, 2013, at 11:45 AM, David Adams <da1 at vt.edu> wrote:

> I think it would be wise to have an entirely separate site for official documentation as the challenge at present is that it's impossible to find anything because of the duplication of outdated content in multiple spaces. Strongly consider using something entirely different than Confluence as well. Some static website generation tool is probably the right solution, with the doc sources kept in source control, and matched up to the appropriate Sakai version. Put it at github to make it easily branchable/mergeable and to encourage community contributions. In fact, if you use Github, they can automatically generate and host the site using Jekyll. I think a clean break is the best strategy. Put a banner on all the current docs to say they're out of date, and start moving to something new.
> 
> David Adams
> Director, Systems Integration and Support
> Virginia Tech Learning Technologies
> 
> 
> On Tue, Apr 30, 2013 at 9:28 AM, Noah Botimer <botimer at umich.edu> wrote:
> I'm curious... Isn't what we suffer the usual documentation death by wiki and diluted/convoluted responsibility?
> 
> Don't get me wrong -- I love wikis and am always in favor of an open contribution model. But I'm skeptical after years of watching our (and others') grab bag spaces that this is the place for "official" documentation. Perhaps the tool is fine, perhaps not, but without a clear demarcation, it's hard for even the most diligent to find and update the information.
> 
> So, I might shade this proposal with a slight variation. This is partly incited by the memory of large archival/deletion efforts in the past, which I'm not sure hit the mark. I don't think the proposal is bad or off in its intention -- just offering some adjustments for consideration:
> 
> 1. Leave everything in place and mark it with a "community/development space" header.
> 
> 2. Make a *simple* document inventory that lists what we think always needs to remain current and what should be locked to a release as "official" documentation, finding the existing pages that have this essential and relevant information.
> 
> 3. Set up a new Confluence space (maybe another domain) and move/copy pages in #2 according to the doc set.
> 
> 4. Create a small group with a practical schedule of dates for reviewing inventory and keeping it as a public punch list (and ideally working to make updates or do the housekeeping, but at the least identifying the needs on a defined rhythm and in a known spot and announcing them).
> 
> 
> The variation here is intended to meet the same goals (as I see them):
> 
> 1. Identify the items that we (as experienced practitioners) wish were well maintained and findable.
> 
> 2. Segregate the old/unknown stuff from the much smaller, maintained corpus, partitioned by release.
> 
> 3. Support information seekers by reducing the ambiguity and improving search results.
> 
> 4. Support information maintainers by itemizing expectations we think the community reasonably has and regularizing expectations on maintainers.
> 
> Thanks,
> -Noah
> 
> On Apr 30, 2013, at 9:30 AM, Beth Kirschner wrote:
> 
> > I'd like to add an agenda item regarding what to do about the Sakai Confluence documentation. This continues to be a source of confusion, wasted time and a barrier to adoption. We've talked about this at previous Sakai conferences, but it hasn't gained any traction to my knowledge. I'd like to restart the conversation prior to this years conference and work on a proposal:
> >
> > 1) Scrap the current Confluence - move to a "legacy" space
> > 2) Rebuild a new Confluence, pulling relevant pages from the legacy space
> > 3) Create a policy to keep these pages up-to-date
> >
> > I hope that many would be willing to contribute to this effort (myself included), if we had a good point person. Neal would be willing to be this point person if others are willing to split up the effort and collaboratively work on a new space that meets the needs of the community.
> >
> > Thoughts?
> > - Beth
> >
> > On Apr 30, 2013, at 8:49 AM, Neal Caidin <nealcaidin at sakaifoundation.org> wrote:
> >
> >> Open meeting - non-TCC welcome to attend
> >>
> >> When: Wednesday, May 1 (tomorrow), 10 am Eastern Daylight/ 2 pm GMT
> >>
> >> Proposed Agenda:
> >>
> >> * CLE 2.9.2 status
> >> * Acknowledgements (Institutional) for conference. Status and how to move forward (level of detail/granularity; challenges of time [conference almost here]; identifying quantity / quality, etc).  Trying to simplify Acknowledgements so we can be ready for the conference. Still would be good to identify special key contributions.
> >> * Tools survey - time permitting. See below.
> >> * Jira management - ongoing feedback requested on how CLECC can best contribute to cleaning up/managing Jira.
> >>
> >>
> >> TCC, any agenda ideas?
> >>
> >>
> >> Teleconference information (Calliflower)
> >> ---------------------------------------------------------
> >>
> >> Default Dial-in Number:+1-323-375-2185
> >>
> >> Your Conference Code: 8600146
> >>
> >> Join Online:
> >> http://www.calliflower.com
> >>
> >> 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.
> >>
> >>
> >> Tools Survey idea
> >> ---------------------------------
> >>
> >> Tools Survey idea
> >>
> >> Potential goals of a tools survey:
> >>
> >> * Highlight tools that are available in Sakai CLE but which many in the community might not be as aware of. For example, LTI.
> >> * Get a sense of the impact of stealthing or removing the rWiki tool
> >> * Identify potential institutions or individuals who have an interest in helping maintain various tools (like rWiki, but could be other tools that need attention as well)
> >> * Make clear the status of the Gradebook 2 tool (my understanding is that it is built on technology with incompatible licensing with CLE?)
> >> * Make visible the requirements of the Assignments vs Assignments 2 tools.
> >> * Get a sense of the use of Contrib tools. Again with the idea that out of this might come some additional resources for development, as well as helping to identify needs
> >> * Get a sense of implicit, explicit or emerging requirements and needs overall
> >>
> >> Or, as Steve Swinsburg says, maybe a simple survey will work for rWiki:
> >>
> >> "A simple survey would do here:
> >> 1. Do you use the wiki (y/n)
> >> 2. What so you use it for (options)
> >> 3. If the wiki went away, how sad would you be (really sad, a bit sad, meh, I'd just use another tool, I hate the wiki)"
> >>
> >> CLECC goal is to generate conversation and strategies for information that would be helpful input to the TCC in decision making processes wrt tool needs, and to get input from the community.
> >>
> >> 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
> >
> > _______________________________________________
> > 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
> 
> _______________________________________________
> 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/20130430/c21b6cc5/attachment.html 