[Building Sakai] Roster2 changes

Fri Nov 28 07:02:08 PST 2014

Whether we target for 10.4 or 11, I'm curious if this would be easy to
apply to Site Info? Seems like that would be a natural thing to do.

Btw, I plan to move Roster, and a few other remaining Jira projects into
SAK before the end of the year. I just plan on leaving Kernel, Samigo, and
Lessons separate for now.

Thanks!
Neal

On Fri, Nov 28, 2014 at 9:58 AM, Matthew Jones <matthew at longsight.com>
wrote:

> I wouldn't say it's necessary to wait until 11, but at least until 10.3 is
> released, expected in 2-3 weeks by the week of December 15th, and possibly
> target for 10.4. (Which would likely be in late February at our schedule)
>
> On Fri, Nov 28, 2014 at 9:02 AM, JUAN JOSé MEROñO SáNCHEZ <jjmerono at um.es>
> wrote:
>
>>
>> Sounds reasonable to wait to 11 to get this out, there are some remaining
>> jiras that could improve this new look&feel also.
>> Thanks !!
>>
>> El 28/11/2014 14:52, Neal Caidin escribió:
>>
>> Please do not merge these changes into 10.x.
>>
>>  Being a new feature this needs time to shake the interface out a bit in
>> trunk, imho. While it looks really really cool, there are a couple of
>> interface elements that seem confusing to me.
>>
>>  We are trying to get 10.3 out the door and I worry that this would add
>> significant risk. Plus, it should be subject to the Maintenance Branch
>> Merge Policy [1].
>>
>>  [1]
>> https://confluence.sakaiproject.org/display/TCC/Maintenance+Branch+Merge+Policy
>>
>>  Thanks!
>> Neal
>>
>>
>> On Thu, Nov 27, 2014 at 11:49 AM, Adrian Fish <adrian.r.fish at gmail.com>
>> wrote:
>>
>>> I've just fixed the permissions one. I think you've put the tickets
>>> against the wrong project, though. Roster 2's now a component in the Sakai
>>> project, so we've got tickets split between. It got me as well. Just leave
>>> them where they are this time, unless we really need to move them in the
>>> Sakai project.
>>>
>>>  If anybody on the list wants to create a Roster2 ticket, they should
>>> be in the Sakai project, under the Roster2 component , like this one
>>> https://jira.sakaiproject.org/browse/SAK-27501. Is that right, Sam?
>>>
>>>  Cheers,
>>> Adrian.
>>>
>>> On 27 November 2014 at 13:39, JUAN JOSé MEROñO SáNCHEZ <jjmerono at um.es>
>>> wrote:
>>>
>>>>  Hi Adrian,
>>>>
>>>>     I've been testing roster2 now in trunk and it is great !!
>>>>     Thank you for all the suggestions you've added to the branch before
>>>> merging into trunk...
>>>>
>>>>     I've created a set of jiras so that we don't forget other
>>>> suggestions that could improve this new UI.
>>>>
>>>>
>>>> https://jira.sakaiproject.org/issues/?jql=key%20in%20(RSTR-73%2CRSTR-74%2CRSTR-75%2CRSTR-76%2CRSTR-77)
>>>> <https://jira.sakaiproject.org/issues/?jql=key%20in%20%28RSTR-73%2CRSTR-74%2CRSTR-75%2CRSTR-76%2CRSTR-77%29>
>>>>
>>>>     But there is one thing that we solved in 10.x that is broken now in
>>>> trunk:
>>>>
>>>>         https://jira.sakaiproject.org/browse/SAK-27501
>>>>
>>>>     I don't know if it will be too disruptive to merge this new UI into
>>>> 10.x, any concerns/opinions?
>>>>
>>>> Thanks !!
>>>>
>>>> El 21/11/2014 22:53, Sam Ottenhoff escribió:
>>>>
>>>> Great job Adrian.  The infinite scroll worked really well for me and
>>>> was fast in a huge testing site.
>>>>
>>>>  My only major confusion was the new Groups dropdown when viewing
>>>> users. I was unclear if I was assigning the user to a group or limiting my
>>>> view to that one group only.
>>>>
>>>>  I would drop the pain of the separate branch and move your code into
>>>> trunk quickly!
>>>>
>>>> On Fri, Nov 21, 2014 at 5:42 AM, Adrian Fish <adrian.r.fish at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>>  I've done some significant work on making Roster2 scale successfully
>>>>> to thousands of site members. Juanjo's suggestion of using an infinite
>>>>> scroll technique seems to have paid off and works well in the 5000 member
>>>>> site I've set up for testing.
>>>>>
>>>>>  I've done all the work in a branch at ...
>>>>>
>>>>>  https://source.sakaiproject.org/svn/roster2/branches/SAK-28028
>>>>>
>>>>>  ... and I'd like people who are interested to do a bit of testing
>>>>> when they get a chance. I'm particularly interested in people in the know
>>>>> testing the security. Most of the old server side code has been reused, so
>>>>> I expect that things are okay on the security front, but still ...
>>>>>
>>>>>  I'll leave it a week and then, if there have been no concerns or
>>>>> objections, I'll merge it into the trunk.
>>>>>
>>>>>  Cheers,
>>>>> Adrian.
>>>>>
>>>>> _______________________________________________
>>>>> 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"
>>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> sakai-dev mailing listsakai-dev at collab.sakaiproject.orghttp://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>
>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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"
>>>
>>
>>
>>
>> _______________________________________________
>> 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"
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20141128/e3054076/attachment.html 