[DG: Teaching & Learning] [Building Sakai] New joinable site settings, which should be on by default? (SAK-24423)

Mon Feb 3 09:03:35 PST 2014

For testing purposes, I am turning on the following properties on Sakai 
Experimental:

sitemanage.join.joinerGroup.enabled=true
sitemanage.join.notification.enabled=true
sitebrowser.join.enabled=true

They should be available on Tuesday, February 4 at 
http://nightly2.sakaiproject.org:8085/portal

Hopefully this will help folks to see how these different properties 
behave so we can come towards a consensus. It seems like everyone is 
comfortable with the notification property, but not 100% about those 
other two.

Thanks,
Neal

> Ward, Lynn E. <mailto:leward at iu.edu>
> January 31, 2014 at 2:31 PM
>
> I'm confused.  I just looked around for this feature on trunk and 
> couldn't find the new features.  I do see an option under Manage 
> Groups to Create New Joinable Set, but I don't think that is related 
> to the features being implemented under Manage Access.  Can someone 
> tell me where I can see this live.  I agree that option 2 should be on 
> by default.  I need to see how 1 is implemented before voting yay or 
> nay on that one.  I agree the others should be off by default.
>
> Lynn
>
> *From:*pedagogy-bounces at collab.sakaiproject.org 
> [mailto:pedagogy-bounces at collab.sakaiproject.org] *On Behalf Of *Jeff 
> Ziegler
> *Sent:* Friday, January 31, 2014 10:04 AM
> *To:* Neal Caidin
> *Cc:* pedagogy at collab.sakaiproject.org
> *Subject:* Re: [DG: Teaching & Learning] [Building Sakai] New joinable 
> site settings, which should be on by default? (SAK-24423)
>
> Update:
>
> I looked around a bit more and found these features implemented under 
> Manage Groups (I was looking under Manage Access) and was able to 
> understand the workflow.  I had thought it would be part of the make 
> Joinable workflow but I now see that making a Joiner group is a 
> completely independent workflow so I'm revising my earlier feedback. 
>  I agree that features 1 & 2 should be on by default.  Sorry for my 
> confusion.
>
> J
>
> On Jan 31, 2014, at 9:45 AM, Jeff Ziegler <ziegler at umich.edu 
> <mailto:ziegler at umich.edu>> wrote:
>
>
>
> "New != better.  Different != better.  Only better == better."
>
> ---------------------------------------------------------------
>
> Jeff Ziegler
>
> CTools Service Manager
>
> ITS Teaching and Learning Group
> University of Michigan
>
> ---------------------------------------------------------------
>
> Jeff Ziegler <mailto:ziegler at umich.edu>
> January 31, 2014 at 10:04 AM
> Update:
>
> I looked around a bit more and found these features implemented under 
> Manage Groups (I was looking under Manage Access) and was able to 
> understand the workflow.  I had thought it would be part of the make 
> Joinable workflow but I now see that making a Joiner group is a 
> completely independent workflow so I'm revising my earlier feedback. 
>  I agree that features 1 & 2 should be on by default.  Sorry for my 
> confusion.
>
> J
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> "New != better.  Different != better.  Only better == better."
>
> ---------------------------------------------------------------
> Jeff Ziegler
> CTools Service Manager
> ITS Teaching and Learning Group
> University of Michigan
>
> ---------------------------------------------------------------
>
> Jeff Ziegler <mailto:ziegler at umich.edu>
> January 31, 2014 at 9:45 AM
> My 2¢.
>
> Only setting two should be on by default.  Based on years of feedback 
> and user requests I think our users will find functions 1, 2, and 
> especially 3 very useful.  However, in my experience, many site 
> maintainers are unaware that Group functionality exists.  So to have a 
> default that (seems) to require them to create a group before making 
> their site Joinable would be a confusion point and lead to a user 
> support request.
>
> It's possible I'm misunderstanding how the Joiner Group function works 
> in practice; I generally prefer to do a hands-on run-through of new 
> functionality before making suggestions, but I don't think it should 
> be on by default.  It is a nice feature, tho.
>
> Jeff
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> "New != better.  Different != better.  Only better == better."
>
> ---------------------------------------------------------------
> Jeff Ziegler
> CTools Service Manager
> ITS Teaching and Learning Group
> University of Michigan
>
> ---------------------------------------------------------------
>
> Neal Caidin <mailto:neal.caidin at apereo.org>
> January 30, 2014 at 4:51 PM
> Hi Pedagogy group,
>
> This could be a good one to chime into. It is new behavior in Sakai 10 
> and we might want to recommend default behaviors. See Brian's email 
> below. Also, his recommendation in the last paragraph seems pretty 
> reasonable to me.
>
> Thanks,
> Neal
>
>
>> *From:* Brian Jones <bjones86 at uwo.ca>
>> *Date:* January 30, 2014 at 1:44 PM
>> *To:* 'dev sakai' <sakai-dev at collab.sakaiproject.org>
>> *Subject:* [Building Sakai] New joinable site settings, which should 
>> be on by default? (SAK-24423)
>> Hi,
>>
>> SAK-24423 introduces several new settings available for use with joinable
>> sites. I would like to gauge the community as to what people think 
>> are good
>> candidates for being turned ON by default. These settings are 
>> available (if
>> enabled) on the 'Manage Access' page of the 'Site Info' tool. The new
>> settings are:
>>
>> 1) Joiner group - this setting allows maintainers of a site to select a
>> group that joiners will be placed into automatically.
>>
>> 2) Join notification - when enabled for a site, this will send email
>> notifications to maintainers of the site when a user joins the site.
>>
>> 3) Exclude from public list - when enabled for a site, users will not see
>> this site in the 'Joinable Sites' interface of the 'Membership' tool.
>>
>> 4) Limit by account type(s) - this setting allows maintainers to specify
>> exactly what user account types are allowed to join the site.
>>
>> 5) Join from 'Site Browser' tool - this is a global setting (not per 
>> site),
>> and enables people to join a site directly from the 'Site Browser' on the
>> gateway.
>>
>> My recommendation so far has been to enable 1) and 2) by default, however
>> I'm not sure if other institutions may find some of the other settings
>> useful to be enabled by default as well.
>>
>> Please join the conversation and let us know what you think! The more 
>> input
>> the better. Also, if you'd like more information/clarification on any of
>> these settings, just let me know.
>>
>> Cheers,
>>
>> Brian Jones
>> Programmer/Analyst
>> Information Technology Services
>> Support Services Building, Room 4326
>> Western University
>> (519) 661-2111 x86969
>> bjones86 at uwo.ca
>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to 
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of 
>> "unsubscribe"
> Brian Jones <mailto:bjones86 at uwo.ca>
> January 30, 2014 at 1:44 PM
> Hi,
>
> SAK-24423 introduces several new settings available for use with joinable
> sites. I would like to gauge the community as to what people think are 
> good
> candidates for being turned ON by default. These settings are 
> available (if
> enabled) on the 'Manage Access' page of the 'Site Info' tool. The new
> settings are:
>
> 1) Joiner group - this setting allows maintainers of a site to select a
> group that joiners will be placed into automatically.
>
> 2) Join notification - when enabled for a site, this will send email
> notifications to maintainers of the site when a user joins the site.
>
> 3) Exclude from public list - when enabled for a site, users will not see
> this site in the 'Joinable Sites' interface of the 'Membership' tool.
>
> 4) Limit by account type(s) - this setting allows maintainers to specify
> exactly what user account types are allowed to join the site.
>
> 5) Join from 'Site Browser' tool - this is a global setting (not per 
> site),
> and enables people to join a site directly from the 'Site Browser' on the
> gateway.
>
> My recommendation so far has been to enable 1) and 2) by default, however
> I'm not sure if other institutions may find some of the other settings
> useful to be enabled by default as well.
>
> Please join the conversation and let us know what you think! The more 
> input
> the better. Also, if you'd like more information/clarification on any of
> these settings, just let me know.
>
> Cheers,
>
> Brian Jones
> Programmer/Analyst
> Information Technology Services
> Support Services Building, Room 4326
> Western University
> (519) 661-2111 x86969
> bjones86 at uwo.ca
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to 
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of 
> "unsubscribe"

-- 
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/pedagogy/attachments/20140203/1eac4570/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/pedagogy/attachments/20140203/1eac4570/attachment-0001.jpg 