[Building Sakai] sakai-dev Digest, Vol 36, Issue 16
Naim Syed
nsyed at ccsnh.edu
Mon Feb 27 16:38:42 PST 2012
Hello, Is the URL of images are stored in a database table and if so, what table is it? For example I have an image with the following link, we are changing our servers but the image still reference the old location. The link below is the example of the file location, we want to change this link to our new server on a different domain.
http://sakai.ouroldserver.org:8080/access/content/group/be8bb47d-9735-4fec-82dc-73c86cb830a0/Template%205/Clip%20Art/grade%204%20-%20chalkboard.jpg
Thanks
Nick
________________________________________
From: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] on behalf of sakai-dev-request at collab.sakaiproject.org [sakai-dev-request at collab.sakaiproject.org]
Sent: Thursday, February 16, 2012 3:00 PM
To: sakai-dev at collab.sakaiproject.org
Subject: sakai-dev Digest, Vol 36, Issue 16
Send sakai-dev mailing list submissions to
sakai-dev at collab.sakaiproject.org
To subscribe or unsubscribe via the World Wide Web, visit
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
or, via email, send a message with subject or body 'help' to
sakai-dev-request at collab.sakaiproject.org
You can reach the person managing the list at
sakai-dev-owner at collab.sakaiproject.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of sakai-dev digest..."
Today's Topics:
1. Windows Users: Need help testing SAK-18655 (Thomas, Gregory J)
2. Re: How to set tool wise permission? (Steve Swinsburg)
3. External help questions - links within pages and image
references (Walters, Cynthia (cmw6s))
4. why ? (Baynaa_sk)
5. Messages count (DAVID ROLDAN MARTINEZ)
6. Problems exporting and importing assessments (Raul Sanchez Vegas)
7. BasicLTI trunk on 2.8.x (Adrian Fish)
8. Assignment2 on sakai 2.9.x (Jon Higham)
9. Re: Assignment2 on sakai 2.9.x (Steve Swinsburg)
10. Re: Messages count (John Leasia)
11. Re: How to set tool wise permission? (Shahid Pathan)
12. Re: OAE: problems with hybrid configuration (Michael Dunlap)
13. Assignment2 2012 edition (Sobieralski, Damian Michael)
14. Sakai CLE, log4j, and Tomcat logs (Seth Theriault)
15. Re: Sakai-ItunesU (Adam Marshall)
16. Re: Commit messages - a humble little plea (D. Stuart Freeman)
17. Re: [Deploying Sakai] Sakai CLE, log4j, and Tomcat logs
(Mike De Simone)
18. Re: Sakai-ItunesU (Zhen Qian)
19. Re: Sakai-ItunesU (Adam Marshall)
20. Re: Commit messages - a humble little plea (Zhen Qian)
21. Re: Sakai-ItunesU (Zhen Qian)
22. Re: Problems exporting and importing assessments (Karen Tsao)
23. Re: Commit messages - a humble little plea (Matthew Jones)
24. Re: Commit messages - a humble little plea (D. Stuart Freeman)
----------------------------------------------------------------------
Message: 1
Date: Wed, 15 Feb 2012 20:15:54 +0000
From: "Thomas, Gregory J" <gjthomas at iupui.edu>
Subject: [Building Sakai] Windows Users: Need help testing SAK-18655
To: "sakai-dev at collab.sakaiproject.org"
<sakai-dev at collab.sakaiproject.org>
Message-ID: <CB617CA9.CD17%gjthomas at iupui.edu>
Content-Type: text/plain; charset="us-ascii"
Hi all,
We need some Windows users to help confirm that https://jira.sakaiproject.org/browse/SAK-18655 works correctly when using the mvn -Ppack-demo install command. If we can confirm that this works ok on various Windows OS's, we can merge this in for 2.9 (and maybe others). Any help with this is greatly appreciated!
Thanks!
Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120215/e4789dce/attachment-0001.html
------------------------------
Message: 2
Date: Thu, 16 Feb 2012 08:05:06 +1100
From: Steve Swinsburg <steve.swinsburg at gmail.com>
Subject: Re: [Building Sakai] How to set tool wise permission?
To: Shahid Pathan <spathan at platys.in>
Cc: sakai-dev at collab.sakaiproject.org
Message-ID: <D12E0285-6B0E-4E03-AB35-D8CE9A8DC2E6 at gmail.com>
Content-Type: text/plain; charset=iso-8859-1
Hi,
Does your tool register the permissions? Can you post the code? They are just binary permissions (on or off) so once you register them they should show up and you can start assigning them to roles.
Have a look at the code for how other tools mange the 'permissions' page within the tool itself, IIRC there is a helper.
cheers.
Steve
On 16/02/2012, at 6:18 AM, Shahid Pathan wrote:
> Hi All,
>
> I have created 3 different module (employee, adaptive test, summetive test) and deployed in sakai.
>
> After that I have created one course site (let say Math-2012) and added above tool for this.
> Now I want to assign permission for this 3 different user. For that I am trying to create 3 different role as follows
>
> 1>empuser :- who can access only employee tool not other in Math-2012 site
> 2>adpuser :- who can access only adaptive tool not other in Math-2012 site
> 3>sumuser :- who can access only summetive tool not other in Math-2012 site.
>
> but I found that while creating role we have to select Function form the list of Function (for example alias.add, alias.del)
> and I am unable to find such function for my newly created modules (there are some other function let say employee.read.hidden and employee.write.any) but its not working as expected.
>
> Can any point me what am i missing?
> Do we have other approach to set permission on each tools?
>
> One strange thing i noticed, for existing tool we have link "Permission" present in each tools home page thorough with administrator can set different permission for each role
> that link is not visible for my newly created tool. If I want to add such link in my tools home page what need to done in JSF page.
>
> Thanks
> Shahid Pathan
>
> _______________________________________________
> 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"
------------------------------
Message: 3
Date: Thu, 16 Feb 2012 03:03:59 +0000
From: "Walters, Cynthia (cmw6s)" <cmw6s at eservices.virginia.edu>
Subject: [Building Sakai] External help questions - links within pages
and image references
To: "sakai-dev at collab.sakaiproject.org"
<sakai-dev at collab.sakaiproject.org>
Message-ID:
<3A29F35913A33441B60443B6253D71C0019D18FB at KENNEDY.eservices.virginia.edu>
Content-Type: text/plain; charset="iso-8859-1"
Hello:
UVa recently changed to Sakai external help pages through sakai properties help.location and help.welcomepage.
We need brief help on two remaining issues, especially that help page links referring to other help pages are now broken.
In making this change, we copied the help (html) pages for the various Sakai tools to a web server,
but have not yet edited anchor hrefs within those copied help pages.
These have the relative url, e.g., ../TOCDisplay/content.hlp?docId=amax and are now broken links.
Again, they are the same in before- and after- versions of the help files, and work before and fail after our change.
The apparent fix is to change the href to the url of the copied document on the web server, so to the relative url, e.g.,
../sakai_permissions/arax.html
This works.
However, before doing that work, we want to make sure that this is the approach intended for help migration editing.
(That is, it's not instead that content.hlp is supposed to continue filtering the external help content
and that we should instead solve what here becomes a basehref problem with the content.htp href.)
Also, as concerns images referenced by the external help files, we have in the past used public Resource storage from our Sakai instance
and may simply continue to do this. But we may decide to move this to simple web storage.
There appears to be no specific configuration for a location of images referenced by the external help files.
There is no apparent Sakai configuration setting and so we're free to position this storage as we wish in the new help page storage. Right?
It would be good to have that confirmed.
Thanks for your help on these matters.
Cindy @ UVa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/962382f1/attachment-0001.html
------------------------------
Message: 4
Date: Wed, 15 Feb 2012 19:11:00 -0800 (PST)
From: Baynaa_sk <baynaa.sk at gmail.com>
Subject: [Building Sakai] why ?
To: sakai-dev at collab.sakaiproject.org
Message-ID: <33333506.post at talk.nabble.com>
Content-Type: text/plain; charset=us-ascii
my sakai source is trunk /downloaded 2012-02-14/
database mysql 5.1
tomcat 5.5.35
http://old.nabble.com/file/p33333506/Untitled.jpg Untitled.jpg
--
View this message in context: http://old.nabble.com/why---tp33333506p33333506.html
Sent from the Sakai - Development mailing list archive at Nabble.com.
------------------------------
Message: 5
Date: Thu, 16 Feb 2012 09:14:28 +0100
From: DAVID ROLDAN MARTINEZ <darolmar at upvnet.upv.es>
Subject: [Building Sakai] Messages count
To: "sakai-dev at collab.sakaiproject.org"
<sakai-dev at collab.sakaiproject.org>
Message-ID:
<EB18E136DB92D44688CDBF688DAACDD9205EF2D7 at agenda2.upvnet.upv.es>
Content-Type: text/plain; charset="iso-8859-1"
Hi all,
Does anybody know how to query Message Center tables to get number of messages on a per topic (received, sent, deleted), user and site basis? I've been looking at hbm.xml files to see if there was a named query to help me but I haven't found any.
Any help will be too much appreciated.
Thank you very much in advance.
Cheers,
David Rold?n Mart?nez
[cid:image001.gif at 01CCEBEE.203CC8A0]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/94b866d4/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 8132 bytes
Desc: image001.gif
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/94b866d4/attachment-0001.gif
------------------------------
Message: 6
Date: Thu, 16 Feb 2012 11:59:45 +0100
From: Raul Sanchez Vegas <raulsv at um.es>
Subject: [Building Sakai] Problems exporting and importing assessments
To: sakai-dev <sakai-dev at collab.sakaiproject.org>
Message-ID: <4F3CE1A1.6040600 at um.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi all
We have found out two bugs:
First bug:
- The instructor creates a new assessment.
- The instructor creates the first assessment's question which text has
an image reference.
- The instructor exports the assessment using the "content package" option.
- The instructor try to import this assessment but it doesn't work and
it is shown this message
"There was an error importing this assignment. Ensure that the file is
correctly formatted IMS QTI."
We have found out that it doesn't work because the importing action try
to find the image of the question's text inside the zip file but it
isn't there.
If the export is made using the QTI option then the import doesn't fail.
Second bug:
- The instructor creates a new assessment.
- The instructor creates the first assessment's question with an attachment.
- The instructor exports the assessment using the QTI option.
- The instructor imports the assessment and it works fine but the
assessment's question doesn't have its attachment. The question has lost
its attachment.
We are usingo Sakai 2.7.2 and Samigo 2.7.5.
Has anyone had the same problems?
Thanks in advance,
Ra?l
------------------------------
Message: 7
Date: Thu, 16 Feb 2012 11:23:48 +0000
From: Adrian Fish <a.fish at lancaster.ac.uk>
Subject: [Building Sakai] BasicLTI trunk on 2.8.x
To: Sakai Dev <sakai-dev at collab.sakaiproject.org>
Message-ID: <4F3CE744.2010802 at lancaster.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I'm trying to build the trunk against our 2.8.x using the sakai-2.8
maven profile. It breaks with this message:
"Non-resolvable parent POM: Could not find artifact
org.sakaiproject:master:pom:2.10-SNAPSHOT and 'parent.relativePath'
points at wrong local POM"
Does BasicLTI trunk need to bind against the 2.10 master pom? Is there
anything specific in 2.10 that basiclti trunk uses?
Cheers,
Adrian.
--
==================================
Adrian Fish
Software Engineer
B66 Management School
Lancaster University
Lancaster
LA1 4YW
http://www.sakaiproject.org
http://confluence.sakaiproject.org/display/YAFT/Yaft
http://confluence.sakaiproject.org/display/CLOG/Home
http://confluence.sakaiproject.org/display/BBB/Home
------------------------------
Message: 8
Date: Thu, 16 Feb 2012 12:03:59 -0000
From: "Jon Higham" <J.Higham at hull.ac.uk>
Subject: [Building Sakai] Assignment2 on sakai 2.9.x
To: "sakai-dev" <sakai-dev at collab.sakaiproject.org>
Message-ID:
<EE007AF7077B7749B57FD9B55A757095073A4CA0 at EXCL1VS1.adir.hull.ac.uk>
Content-Type: text/plain; charset="us-ascii"
Hi everyone
I'm running sakai 2.9.x on tomcat 7.0.21. I've managed to get
Assignment2 from trunk to build, but only after having to add a
dependency to sakai-assignment2-api in assignment2/pack/pom.xml.
However, on startup I get the errors below, and when I access
Assignment2 I get "Unable to find registered context for tool with ID
sakai.assignment" error
Thanks
Jon Higham
ICT Department
University of Hull
2012-02-16 10:05:23,474 ERROR Thread-44
org.springframework.web.context.ContextLoader - Context initialization
failed
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'TLABPostProcessorLoader' defined in class path resource
[conf/rsf-config .xml]: Invocation of init method failed; nested
exception is org.springframework .beans.factory.BeanCreationException:
Error creating bean with name 'viewParamsInterceptorParent$child#0'
defined in ServletContext resource [/WEB-INF/applicationContext.xml]:
Cannot resolve reference to bean 'Assignment2ViewParamsInterceptor'
while setting bean property 'value'; nested exception is
org.springframework .beans.factory.BeanCreationException: Error creating
bean with name 'Assignment2ViewParamsInterceptor' defined in
ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot
resolve reference to bean 'LocalPermissionLogic' while setting bean
property 'localPermissionLogic'; nested exception is org.springframework
.beans.factory.BeanCreationException: Error creating bean with name
'LocalPermissionLogic' defined in ServletContext resource
[/WEB-INF/applicationContext.xml]: Initialization of bean failed; nested
exception is org.springframework.beans.TypeMismatchException: Failed to
convert property value of type
[org.sakaiproject.assignment2.logic.impl.AssignmentPermissionLogicImpl]
to required type
[org.sakaiproject.assignment2.logic.AssignmentPermissionLogic] for
property 'permissionLogic'; nested exception is
java.lang.IllegalArgumentException: Cannot convert value of type
[org.sakaiproject.assignment2.1ogic.impl.AssignmentPermissionLogicImpl]
to required type
[org.sakaiproject.assignment2.logic.AssignmentPermissionLogic] for
property 'permissionLogic': no matching editors or conversion strategy
found
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1338)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObjec
t(AbstractBeanFactory.java:264)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.g
etSingleton(DefaultSingletonBeanRegistry.java:222)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(
AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:164)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.get
BeansOfType(DefaultListableBeanFactory.java:308)
at
org.springframework.context.support.AbstractApplicationContext.getBeansO
fType(AbstractApplicationContext.java:947)
at
org.springframework.context.support.AbstractApplicationContext.registerL
isteners(AbstractApplicationContext.java:701)
at org.springframework.context.support.AbstractApplicationContext.refres
I (AbstractApplicationContext.java:377)
at
org.springframework.web.context.ContextLoader.createWebApplicationContex
t(ContextLoader.java:255)
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(
ContextLoader.java:199)
at
org.sakaiproject.component.impl.ContextLoader.initWebApplicationContext(
ContextLoader.java:64)
at
org.springframework.web.context.ContextLoaderListener.contextInitialised
(ContextLoaderListener.java:45)
at org.sakaiproject.util.ContextLoaderListener.contextInitialized(Contex
LoaderListener.java:56)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContex
.java:4723)
at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:
.226)
at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
.221)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/5ad960ca/attachment-0001.html
-------------- next part --------------
**************************************************
To view the terms under which this email is
distributed, please go to
http://www2.hull.ac.uk/legal/disclaimer.aspx
**************************************************
------------------------------
Message: 9
Date: Thu, 16 Feb 2012 23:09:36 +1100
From: Steve Swinsburg <steve.swinsburg at gmail.com>
Subject: Re: [Building Sakai] Assignment2 on sakai 2.9.x
To: "Jon Higham" <J.Higham at hull.ac.uk>
Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
Message-ID: <0A8A8AA8-8224-414B-AF50-7C2587B01445 at gmail.com>
Content-Type: text/plain; charset="windows-1252"
Ho Jon,
There is a strange typo in there:
org.sakaiproject.assignment2.1ogic.impl.AssignmentPermissionLogicImpl
Check the xml config to see if that is actually incorrect.
cheers,
Steve
On 16/02/2012, at 11:03 PM, Jon Higham wrote:
> Hi everyone
>
> I?m running sakai 2.9.x on tomcat 7.0.21. I?ve managed to get Assignment2 from trunk to build, but only after having to add a dependency to sakai-assignment2-api in assignment2/pack/pom.xml.
>
> However, on startup I get the errors below, and when I access Assignment2 I get ?Unable to find registered context for tool with ID sakai.assignment? error
>
> Thanks
>
> Jon Higham
> ICT Department
> University of Hull
>
> 2012-02-16 10:05:23,474 ERROR Thread-44 org.springframework.web.context.ContextLoader - Context initialization failed
> org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'TLABPostProcessorLoader' defined in class path resource [conf/rsf-config .xml]: Invocation of init method failed; nested exception is org.springframework .beans.factory.BeanCreationException: Error creating bean with name ?viewParamsInterceptorParent$child#0' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'Assignment2ViewParamsInterceptor' while setting bean property 'value'; nested exception is org.springframework .beans.factory.BeanCreationException: Error creating bean with name 'Assignment2ViewParamsInterceptor' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'LocalPermissionLogic' while setting bean property 'localPermissionLogic'; nested exception is org.springframework .beans.factory.BeanCreationException: Error creating bean with name 'LocalPermissionLogic' defined in Se
rvletContext resource [/WEB-INF/applicationContext.xml]: Initialization of bean failed; nested exception is org.springframework.beans.TypeMismatchException: Failed to convert property value of type [org.sakaiproject.assignment2.logic.impl.AssignmentPermissionLogicImpl] to required type [org.sakaiproject.assignment2.logic.AssignmentPermissionLogic] for property 'permissionLogic?; nested exception is java.lang.IllegalArgumentException: Cannot convert value of type [org.sakaiproject.assignment2.1ogic.impl.AssignmentPermissionLogicImpl] to required type [org.sakaiproject.assignment2.logic.AssignmentPermissionLogic] for property 'permissionLogic': no matching editors or conversion strategy found
> at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1338)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory$1.run(AbstractAutowireCapableBeanFactory.java:409)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.createBean(AbstractAutowireCapableBeanFactory.java:380)
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:185)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:164)
> at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:308)
> at org.springframework.context.support.AbstractApplicationContext.getBeansOfType(AbstractApplicationContext.java:947)
> at org.springframework.context.support.AbstractApplicationContext.registerListeners(AbstractApplicationContext.java:701)
> at org.springframework.context.support.AbstractApplicationContext.refres I (AbstractApplicationContext.java:377)
> at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
> at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
> at org.sakaiproject.component.impl.ContextLoader.initWebApplicationContext(ContextLoader.java:64)
> at org.springframework.web.context.ContextLoaderListener.contextInitialised(ContextLoaderListener.java:45)
> at org.sakaiproject.util.ContextLoaderListener.contextInitialized(Contex LoaderListener.java:56)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContex .java:4723)
> at org.apache.catalina.core.StandardContext$1.call(StandardContext.java: .226)
> at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> .221)
> **************************************************
> To view the terms under which this email is
> distributed, please go to
> http://www2.hull.ac.uk/legal/disclaimer.aspx
> **************************************************_______________________________________________
> 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/20120216/110d8f12/attachment-0001.html
------------------------------
Message: 10
Date: Thu, 16 Feb 2012 07:41:03 -0500
From: John Leasia <jleasia at umich.edu>
Subject: Re: [Building Sakai] Messages count
To: DAVID ROLDAN MARTINEZ <darolmar at upvnet.upv.es>
Cc: "sakai-dev at collab.sakaiproject.org"
<sakai-dev at collab.sakaiproject.org>
Message-ID: <4F3CF95F.8020902 at umich.edu>
Content-Type: text/plain; charset="iso-8859-1"
Haven't done this in a while, here is something that I pulled from my
bookmarks. Used it on Oracle. Might work for you or give you a start.
You could change it to remove the mfr_area_t.context_id like in the
where so that it considers all sites
(change
where mfr_area_t.context_id like '83ef2c1f-e77b-473f-00be-ddebb90517bc'
and mfr_area_t.id=mfr_open_forum_t.surrogatekey
to
where mfr_area_t.id=mfr_open_forum_t.surrogatekey )
-- count messages per topic per forum for a site
select count(mmt.id) as num_messages, MFR_OPEN_FORUM_T.title as Forum,
mfr_topic_t.title as Topic
from MFR_OPEN_FORUM_T, mfr_topic_t, mfr_area_t, mfr_message_t mmt
where mfr_area_t.context_id like '83ef2c1f-e77b-473f-00be-ddebb90517bc'
and mfr_area_t.id=mfr_open_forum_t.surrogatekey
and mfr_open_forum_t.id =mfr_topic_t.of_surrogatekey
and mmt.surrogatekey(+)=mfr_topic_t.id
group by MFR_OPEN_FORUM_T.title, mfr_topic_t.title
order by MFR_OPEN_FORUM_T.title
DAVID ROLDAN MARTINEZ wrote:
>
> Hi all,
>
> Does anybody know how to query Message Center tables to get number of
> messages on a per topic (received, sent, deleted), user and site
> basis? I've been looking at hbm.xml files to see if there was a named
> query to help me but I haven't found any.
>
> Any help will be too much appreciated.
>
> Thank you very much in advance.
>
> Cheers,
>
> David Rold?n Mart?nez
>
> Descripci?n: Descripci?n: I love touch
>
>
>
> _______________________________________________
> 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/20120216/cb20bd46/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 8132 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/cb20bd46/attachment-0001.gif
------------------------------
Message: 11
Date: Thu, 16 Feb 2012 20:17:55 +0530
From: Shahid Pathan <spathan at platys.in>
Subject: Re: [Building Sakai] How to set tool wise permission?
To: Steve Swinsburg <steve.swinsburg at gmail.com>
Cc: sakai-dev at collab.sakaiproject.org
Message-ID:
<CAM61mu0e+7f3JPOCadj=p=gS_78FVJRdgfYHhMMVD2__C3-CtQ at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Steve,
Thanks for your suggestion. Now I am going through the
https://confluence.sakaiproject.org/display/BOOT/Using+the+FunctionManager+Serviceto
understand how to register tool with permission and let you know. I
have
attached my code. Please have a look.
I did not understand the " IIRC there is a helper". Where do I find this?
Thanks
Shahid
On Thu, Feb 16, 2012 at 2:35 AM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:
> Hi,
>
> Does your tool register the permissions? Can you post the code? They are
> just binary permissions (on or off) so once you register them they should
> show up and you can start assigning them to roles.
>
> Have a look at the code for how other tools mange the 'permissions' page
> within the tool itself, IIRC there is a helper.
>
> cheers.
> Steve
>
>
> On 16/02/2012, at 6:18 AM, Shahid Pathan wrote:
>
> > Hi All,
> >
> > I have created 3 different module (employee, adaptive test, summetive
> test) and deployed in sakai.
> >
> > After that I have created one course site (let say Math-2012) and added
> above tool for this.
> > Now I want to assign permission for this 3 different user. For that I am
> trying to create 3 different role as follows
> >
> > 1>empuser :- who can access only employee tool not other in Math-2012
> site
> > 2>adpuser :- who can access only adaptive tool not other in Math-2012
> site
> > 3>sumuser :- who can access only summetive tool not other in Math-2012
> site.
> >
> > but I found that while creating role we have to select Function form the
> list of Function (for example alias.add, alias.del)
> > and I am unable to find such function for my newly created modules
> (there are some other function let say employee.read.hidden and
> employee.write.any) but its not working as expected.
> >
> > Can any point me what am i missing?
> > Do we have other approach to set permission on each tools?
> >
> > One strange thing i noticed, for existing tool we have link "Permission"
> present in each tools home page thorough with administrator can set
> different permission for each role
> > that link is not visible for my newly created tool. If I want to add
> such link in my tools home page what need to done in JSF page.
> >
> > Thanks
> > Shahid Pathan
> >
> > _______________________________________________
> > 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/20120216/990c1d95/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: employee.zip
Type: application/zip
Size: 58694 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/990c1d95/attachment-0001.zip
------------------------------
Message: 12
Date: Thu, 16 Feb 2012 09:54:32 -0500
From: Michael Dunlap <michael.dunlap at yale.edu>
Subject: Re: [Building Sakai] OAE: problems with hybrid configuration
To: sakai-dev at collab.sakaiproject.org
Message-ID: <4F3D18A8.8050909 at yale.edu>
Content-Type: text/plain; charset=ISO-8859-1
Has anyone on this list had success in adding a Sakai 2 widget in OAE?
I find that I also cannot add and Basic LTI widgets either.
Michael
On 02/14/2012 03:56 PM, Michael Dunlap wrote:
> I'm following the documentation here:
>
> https://confluence.sakaiproject.org/display/KERNDOC/Building+and+Configuring+a+Hybrid+Deployment#BuildingandConfiguringaHybridDeployment-SakaiOAE
>
> And am running up against a wall. Down in the troubleshooting section,
> I'm trying to verify #6. Though I've set the personalportal variable to
> true, I don't see any "My Sakai 2 favourites" in the add widgets dialog.
> Anyone have a tip here? I think I've done everything the doco suggests.
>
> Michael
--
Michael Dunlap UNIX Systems Administrator
michael.dunlap at yale.edu Production Systems, ITS
(203) 436-2539 Yale University
GPG Public Key: http://pantheon.yale.edu/~mrd25/gpg_work_key.pub
------------------------------
Message: 13
Date: Thu, 16 Feb 2012 15:59:23 +0000
From: "Sobieralski, Damian Michael" <dsobiera at indiana.edu>
Subject: [Building Sakai] Assignment2 2012 edition
To: "sakai-dev at collab.sakaiproject.org"
<sakai-dev at collab.sakaiproject.org>
Message-ID:
<6DE804C72159524ABF0DAE7A78BC5B5713F1BAB9 at IU-MSSG-MBX101.ads.iu.edu>
Content-Type: text/plain; charset="us-ascii"
Here's a quick note to let you know that next on my radar is addressing the Assignment 2 build/run issues. I am currently working on something else (not A2 related) but my hope is to be done with that other project by March 2nd.
After I fix the A2 building issues I will then go through the A2 JIRAs and try to prioritize them so that I can make an effort to start working on them. A2 will be getting some love soon. W/ all the recent activity on the list regarding A2 I felt that I needed to post this to let the community know next month will ramp up some A2 work.
- Damian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/739d618c/attachment-0001.html
------------------------------
Message: 14
Date: Thu, 16 Feb 2012 11:06:05 -0500 (EST)
From: Seth Theriault <slt at columbia.edu>
Subject: [Building Sakai] Sakai CLE, log4j, and Tomcat logs
To: production at collab.sakaiproject.org,
sakai-dev at collab.sakaiproject.org
Message-ID:
<alpine.OSX.2.02.1202161041040.67746 at mirth.cc.columbia.edu>
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Hello,
[pardon the cross-posting]
The short question(s): How are you dealing with your production
Tomcat logs? Are you overriding the default log4j.properties with
different appenders or the like? Do you ever "lose" Tomcat logs?
Locally on Sakai 2.8, we override the default log4j.properties to
send our Tomcat logs to a logs directory on each app server:
[...]
# Use "daily" instead of "Sakai"
log4j.rootLogger=INFO,daily
# Configuration for a daily rolling log file
log4j.appender.daily=org.apache.log4j.DailyRollingFileAppender
log4j.appender.daily.DatePattern='.'yyyy-MM-dd
log4j.appender.daily.File=/var/log/sakai.log
log4j.appender.daily.layout=org.apache.log4j.PatternLayout
log4j.appender.daily.layout.ConversionPattern=%d %-5p [%t] [%c]: %m%n
log4j.appender.daily.Encoding=UTF-8
[...]
This config works fine for the first 24 hours after Sakai is
started, but soon after the first log rotation, it becomes
unclear which log file (sakai.log or a sakai.log.yyy-MM-dd) Sakai
is actually logging to. After a few days, it doesn't appear to
be logging to any file at all. A quick "lsof -p <sakaipid>" often
shows multiple log files open.
Obviously, this is frustrating. I have thought about sending
everything over syslog to a different server, but that's not
really practical in my environment.
One option that I have been toying with most recently is
replacing Sakai's log4j back-end with Logback, its successor:
http://logback.qos.ch/
Logback relies on SLF4J, a widely used logging abstraction layer,
that we already using via its legacy API bridges:
http://www.slf4j.org/legacy.html
in the kernel and some of the Wicket-based tools.
This requires a bit of work (and the licensing needs to be
checked into), so I'd be interested in hearing what everyone else
does first.
Seth
------------------------------
Message: 15
Date: Thu, 16 Feb 2012 16:54:45 +0000
From: Adam Marshall <adam.marshall at oucs.ox.ac.uk>
Subject: Re: [Building Sakai] Sakai-ItunesU
To: DAVID ROLDAN MARTINEZ <darolmar at upvnet.upv.es>,
"sakai-dev at collab.sakaiproject.org"
<sakai-dev at collab.sakaiproject.org>
Message-ID:
<DF192BAB00144C48B1B41464F3347A204416371088 at EXMBX05.ad.oak.ox.ac.uk>
Content-Type: text/plain; charset="us-ascii"
ITunesU doesn't have any sort of web services interface though does it?
adam
From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of DAVID ROLDAN MARTINEZ
Sent: 13 February 2012 18:42
To: sakai-dev at collab.sakaiproject.org
Subject: [Building Sakai] Sakai-ItunesU
Hi all,
We are exploring the possibilities of replicating the index, content and/or resources of a Sakai course in an ItunesU course in an automated way. Has someone done anything related to this?
Thank you very much in advance.
Best,
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/1c982808/attachment-0001.html
------------------------------
Message: 16
Date: Thu, 16 Feb 2012 11:54:50 -0500
From: "D. Stuart Freeman" <stuart.freeman at et.gatech.edu>
Subject: Re: [Building Sakai] Commit messages - a humble little plea
To: Zhen Qian <zqian at umich.edu>
Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
Message-ID: <20120216165450.GF17318 at cetel-004-xx6.admin.gatech.edu>
Content-Type: text/plain; charset="us-ascii"
On Wed, Feb 15, 2012 at 10:11:37AM -0500, Zhen Qian wrote:
> I agree with the plea and I will remember to include more context and change info into the commit log.
>
> However, I think there is another exception to this, the security jiras. I think the succinct text like just the jira number is enough for those, since the log text is public.
So is the changeset though, so if it's obvious that it's a security issue
an attacker can presumably work out the attack based on the new logic.
>
> Thanks,
>
> - zhen
>
> On Feb 14, 2012, at 5:51 PM, Steve Swinsburg wrote:
>
> > I agree with this, trunk commits should include info about what the commit is doing. However there is one exception, branch merging.
> >
> > These have historically been of the form:
> >
> > SAK-123 merge trunk r12345
> >
> > If it merges cleanly, otherwise it would be:
> >
> > SAK-123 manually merge trunk r12345 (and any other notes required).
> >
> > You can then reference the original trunk commit and jira.
> >
> > cheers,
> > Steve
> >
> >
> > On 15/02/2012, at 4:25 AM, DAVID ROLDAN MARTINEZ wrote:
> >
> >> I absolutely agree. In fact, my commit messages are so brief (just the ticket number) because I thought that was the standard way of doing this. :D
> >>
> >> -----Mensaje original-----
> >> De: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] En nombre de Aaron Zeckoski
> >> Enviado el: martes, 14 de febrero de 2012 18:14
> >> Para: Noah Botimer
> >> CC: sakai-dev
> >> Asunto: Re: [Building Sakai] Commit messages - a humble little plea
> >>
> >> Definitely agree with this. And as much as possible, try to include the intent/reason behind the commit rather than just repeating the title which is probably something weird like "Tool X instructions are confusing". A better message would be "Updated the tool X instructions with more details about using a mouse in a web browser".
> >>
> >> -AZ
> >>
> >>
> >> On Tue, Feb 14, 2012 at 11:56 AM, Noah Botimer <botimer at umich.edu> wrote:
> >>> Hello folks,
> >>>
> >>> A trend I've noticed is the shortening of commit messages, to the
> >>> point of simply being a JIRA issue number. There is an up-side here: I
> >>> don't remember the last real commit I saw without a JIRA ticket
> >>> referenced. However, the downside is significant in assuming that this is sufficient.
> >>>
> >>> Take, for example, examining the history of a couple of branches to
> >>> find when something was introduced. Common cases of this are
> >>> cherry-picking a feature and porting a bug fix. I won't belabor all of
> >>> the hassle, but mention a few points:
> >>>
> >>> First, each JIRA ticket must be called up individually to see what the
> >>> intent was (set aside the topic of issue titles, which could be better
> >>> generally). Second, there are often multiple commits against a ticket,
> >>> sometimes interleaved with others, so the task often includes closely
> >>> analyzing multiple diffs just to divine the intent. Third, there are
> >>> occasionally errors in the reference or multiple issues combined in a
> >>> commit, making it very difficult to track in either direction (from
> >>> JIRA or Subversion).
> >>>
> >>>
> >>> So, my simple request follows:
> >>>
> >>> Could we please try to include a brief summary of what action is being
> >>> taken with each commit? If the change is non-trivial, please also
> >>> include some details of what was introduced, changed, or removed.
> >>>
> >>>
> >>> JIRA is great, but the one real truth is the source revision history.
> >>> If you are committing something, please tell the historical record
> >>> what you were doing.
> >>>
> >>> Although it has some Git specifics, this is a very nice
> >>> guideline:
> >>> http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
> >>>
> >>> Thanks,
> >>> -Noah
> >>>
> >>>
> >>> _______________________________________________
> >>> 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"
> >>
> >>
> >>
> >> --
> >> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile _______________________________________________
> >> 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"
> >
> > _______________________________________________
> > 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"
--
D. Stuart Freeman
Georgia Institute of Technology
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/74270814/attachment-0001.bin
------------------------------
Message: 17
Date: Thu, 16 Feb 2012 10:08:40 -0700
From: Mike De Simone <michael.desimone at rsmart.com>
Subject: Re: [Building Sakai] [Deploying Sakai] Sakai CLE, log4j, and
Tomcat logs
To: Seth Theriault <slt at columbia.edu>
Cc: production at collab.sakaiproject.org,
sakai-dev at collab.sakaiproject.org
Message-ID:
<CAHYrFKujJuLQ9hFCCEZSP6pGwQH=m_jogYCV1jJDZcuME3kkeQ at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Seth,
For our installations, I've put in place a manual log rotate script for
catalina.out. The main reason was that if tomcat is running and the
logfile file handle is lost, logging will cease until tomcat is restarted.
That might be what's happening here.
Basically, I wrote a simple bash script to copy catalina.out to a new file,
then 'cat /dev/null > catalina.out' to empty the file but preserve the file
handle. Then we remove files older than a certain # of days.
Caveat: on a very busy server, you could lose a few seconds of logging.
This timeframe could be lessened by rotating daily instead of weekly, for
example, allowing the copy to run a little faster.
I've attached the script in case it proves a useful approach for you.
Thanks,
-------------------------------
Mike DeSimone
Lead Systems Engineer
*r**Smart* | 602-490-0473
On Thu, Feb 16, 2012 at 09:06, Seth Theriault <slt at columbia.edu> wrote:
> Hello,
>
> [pardon the cross-posting]
>
> The short question(s): How are you dealing with your production
> Tomcat logs? Are you overriding the default log4j.properties with
> different appenders or the like? Do you ever "lose" Tomcat logs?
>
> Locally on Sakai 2.8, we override the default log4j.properties to
> send our Tomcat logs to a logs directory on each app server:
>
> [...]
> # Use "daily" instead of "Sakai"
> log4j.rootLogger=INFO,daily
>
> # Configuration for a daily rolling log file
> log4j.appender.daily=org.apache.log4j.DailyRollingFileAppender
> log4j.appender.daily.DatePattern='.'yyyy-MM-dd
> log4j.appender.daily.File=/var/log/sakai.log
> log4j.appender.daily.layout=org.apache.log4j.PatternLayout
> log4j.appender.daily.layout.ConversionPattern=%d %-5p [%t] [%c]: %m%n
> log4j.appender.daily.Encoding=UTF-8
> [...]
>
> This config works fine for the first 24 hours after Sakai is
> started, but soon after the first log rotation, it becomes
> unclear which log file (sakai.log or a sakai.log.yyy-MM-dd) Sakai
> is actually logging to. After a few days, it doesn't appear to
> be logging to any file at all. A quick "lsof -p <sakaipid>" often
> shows multiple log files open.
>
> Obviously, this is frustrating. I have thought about sending
> everything over syslog to a different server, but that's not
> really practical in my environment.
>
> One option that I have been toying with most recently is
> replacing Sakai's log4j back-end with Logback, its successor:
>
> http://logback.qos.ch/
>
> Logback relies on SLF4J, a widely used logging abstraction layer,
> that we already using via its legacy API bridges:
>
> http://www.slf4j.org/legacy.html
>
> in the kernel and some of the Wicket-based tools.
>
> This requires a bit of work (and the licensing needs to be
> checked into), so I'd be interested in hearing what everyone else
> does first.
>
> Seth
>
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
>
> TO UNSUBSCRIBE: send email to
> production-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/20120216/dd77908e/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tomcat_logrotate
Type: application/octet-stream
Size: 1123 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/dd77908e/attachment-0001.obj
------------------------------
Message: 18
Date: Thu, 16 Feb 2012 12:15:53 -0500
From: Zhen Qian <zqian at umich.edu>
Subject: Re: [Building Sakai] Sakai-ItunesU
To: Adam Marshall <adam.marshall at oucs.ox.ac.uk>
Cc: "sakai-dev at collab.sakaiproject.org"
<sakai-dev at collab.sakaiproject.org>
Message-ID: <90AF612E-E039-490E-823D-3504313E6B6D at umich.edu>
Content-Type: text/plain; charset="windows-1252"
Please checkout this: https://source.sakaiproject.org/contrib/itunesu/trunk/itunesu-scripts/
UofM have established a yearly routine to prune itunesu content because of the 500G storage limit.
HTH,
- Zhen
On Feb 16, 2012, at 11:54 AM, Adam Marshall wrote:
> ITunesU doesn?t have any sort of web services interface though does it?
>
> adam
>
> From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of DAVID ROLDAN MARTINEZ
> Sent: 13 February 2012 18:42
> To: sakai-dev at collab.sakaiproject.org
> Subject: [Building Sakai] Sakai-ItunesU
>
> Hi all,
>
> We are exploring the possibilities of replicating the index, content and/or resources of a Sakai course in an ItunesU course in an automated way. Has someone done anything related to this?
>
> Thank you very much in advance.
>
> Best,
> David
> _______________________________________________
> 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/20120216/b365e1ad/attachment-0001.html
------------------------------
Message: 19
Date: Thu, 16 Feb 2012 17:15:02 +0000
From: Adam Marshall <adam.marshall at oucs.ox.ac.uk>
Subject: Re: [Building Sakai] Sakai-ItunesU
To: Zhen Qian <zqian at umich.edu>
Cc: "sakai-dev at collab.sakaiproject.org"
<sakai-dev at collab.sakaiproject.org>
Message-ID:
<DF192BAB00144C48B1B41464F3347A20441637109C at EXMBX05.ad.oak.ox.ac.uk>
Content-Type: text/plain; charset="us-ascii"
Is this the same as the newly announced itunesU course thing? I was assuming that was what was being referredto by David.
adam
From: Zhen Qian [mailto:zqian at umich.edu]
Sent: 16 February 2012 17:16
To: Adam Marshall
Cc: DAVID ROLDAN MARTINEZ; sakai-dev at collab.sakaiproject.org
Subject: Re: [Building Sakai] Sakai-ItunesU
Please checkout this: https://source.sakaiproject.org/contrib/itunesu/trunk/itunesu-scripts/
UofM have established a yearly routine to prune itunesu content because of the 500G storage limit.
HTH,
- Zhen
On Feb 16, 2012, at 11:54 AM, Adam Marshall wrote:
ITunesU doesn't have any sort of web services interface though does it?
adam
From: sakai-dev-bounces at collab.sakaiproject.org<mailto:sakai-dev-bounces at collab.sakaiproject.org> [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of DAVID ROLDAN MARTINEZ
Sent: 13 February 2012 18:42
To: sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
Subject: [Building Sakai] Sakai-ItunesU
Hi all,
We are exploring the possibilities of replicating the index, content and/or resources of a Sakai course in an ItunesU course in an automated way. Has someone done anything related to this?
Thank you very much in advance.
Best,
David
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto: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/20120216/714d57f8/attachment-0001.html
------------------------------
Message: 20
Date: Thu, 16 Feb 2012 12:21:00 -0500
From: Zhen Qian <zqian at umich.edu>
Subject: Re: [Building Sakai] Commit messages - a humble little plea
To: "D. Stuart Freeman" <stuart.freeman at et.gatech.edu>
Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
Message-ID: <69CD4708-2B48-4D18-997D-CF8FD34E9CE4 at umich.edu>
Content-Type: text/plain; charset=us-ascii
Ahh, I guess that's the beauty of opensource then :)
svn is designed to never lose information. I don't know whether svn is capable to hide content diff or log message, aka "confidential checkin", based on security settings.
How about git? Just curious.
Tanks,
- Zhen
On Feb 16, 2012, at 11:54 AM, D. Stuart Freeman wrote:
> On Wed, Feb 15, 2012 at 10:11:37AM -0500, Zhen Qian wrote:
>> I agree with the plea and I will remember to include more context and change info into the commit log.
>>
>> However, I think there is another exception to this, the security jiras. I think the succinct text like just the jira number is enough for those, since the log text is public.
>
> So is the changeset though, so if it's obvious that it's a security issue
> an attacker can presumably work out the attack based on the new logic.
>
>>
>> Thanks,
>>
>> - zhen
>>
>> On Feb 14, 2012, at 5:51 PM, Steve Swinsburg wrote:
>>
>>> I agree with this, trunk commits should include info about what the commit is doing. However there is one exception, branch merging.
>>>
>>> These have historically been of the form:
>>>
>>> SAK-123 merge trunk r12345
>>>
>>> If it merges cleanly, otherwise it would be:
>>>
>>> SAK-123 manually merge trunk r12345 (and any other notes required).
>>>
>>> You can then reference the original trunk commit and jira.
>>>
>>> cheers,
>>> Steve
>>>
>>>
>>> On 15/02/2012, at 4:25 AM, DAVID ROLDAN MARTINEZ wrote:
>>>
>>>> I absolutely agree. In fact, my commit messages are so brief (just the ticket number) because I thought that was the standard way of doing this. :D
>>>>
>>>> -----Mensaje original-----
>>>> De: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] En nombre de Aaron Zeckoski
>>>> Enviado el: martes, 14 de febrero de 2012 18:14
>>>> Para: Noah Botimer
>>>> CC: sakai-dev
>>>> Asunto: Re: [Building Sakai] Commit messages - a humble little plea
>>>>
>>>> Definitely agree with this. And as much as possible, try to include the intent/reason behind the commit rather than just repeating the title which is probably something weird like "Tool X instructions are confusing". A better message would be "Updated the tool X instructions with more details about using a mouse in a web browser".
>>>>
>>>> -AZ
>>>>
>>>>
>>>> On Tue, Feb 14, 2012 at 11:56 AM, Noah Botimer <botimer at umich.edu> wrote:
>>>>> Hello folks,
>>>>>
>>>>> A trend I've noticed is the shortening of commit messages, to the
>>>>> point of simply being a JIRA issue number. There is an up-side here: I
>>>>> don't remember the last real commit I saw without a JIRA ticket
>>>>> referenced. However, the downside is significant in assuming that this is sufficient.
>>>>>
>>>>> Take, for example, examining the history of a couple of branches to
>>>>> find when something was introduced. Common cases of this are
>>>>> cherry-picking a feature and porting a bug fix. I won't belabor all of
>>>>> the hassle, but mention a few points:
>>>>>
>>>>> First, each JIRA ticket must be called up individually to see what the
>>>>> intent was (set aside the topic of issue titles, which could be better
>>>>> generally). Second, there are often multiple commits against a ticket,
>>>>> sometimes interleaved with others, so the task often includes closely
>>>>> analyzing multiple diffs just to divine the intent. Third, there are
>>>>> occasionally errors in the reference or multiple issues combined in a
>>>>> commit, making it very difficult to track in either direction (from
>>>>> JIRA or Subversion).
>>>>>
>>>>>
>>>>> So, my simple request follows:
>>>>>
>>>>> Could we please try to include a brief summary of what action is being
>>>>> taken with each commit? If the change is non-trivial, please also
>>>>> include some details of what was introduced, changed, or removed.
>>>>>
>>>>>
>>>>> JIRA is great, but the one real truth is the source revision history.
>>>>> If you are committing something, please tell the historical record
>>>>> what you were doing.
>>>>>
>>>>> Although it has some Git specifics, this is a very nice
>>>>> guideline:
>>>>> http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
>>>>>
>>>>> Thanks,
>>>>> -Noah
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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"
>>>>
>>>>
>>>>
>>>> --
>>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile _______________________________________________
>>>> 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"
>>>
>>> _______________________________________________
>>> 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"
>
> --
> D. Stuart Freeman
> Georgia Institute of Technology
------------------------------
Message: 21
Date: Thu, 16 Feb 2012 12:27:49 -0500
From: Zhen Qian <zqian at umich.edu>
Subject: Re: [Building Sakai] Sakai-ItunesU
To: Adam Marshall <adam.marshall at oucs.ox.ac.uk>
Cc: "sakai-dev at collab.sakaiproject.org"
<sakai-dev at collab.sakaiproject.org>
Message-ID: <2488B9AA-108D-480D-B335-5B10A56FA319 at umich.edu>
Content-Type: text/plain; charset="windows-1252"
My mistake then.
So is this link correct? itunesu app for iPhone and iPad: http://itunes.apple.com/us/app/id490217893?mt=8
I have an impression that the app only host open content. Please correct me if I am totally wrong here...
- Zhen
On Feb 16, 2012, at 12:15 PM, Adam Marshall wrote:
> Is this the same as the newly announced itunesU course thing? I was assuming that was what was being referredto by David.
>
> adam
>
> From: Zhen Qian [mailto:zqian at umich.edu]
> Sent: 16 February 2012 17:16
> To: Adam Marshall
> Cc: DAVID ROLDAN MARTINEZ; sakai-dev at collab.sakaiproject.org
> Subject: Re: [Building Sakai] Sakai-ItunesU
>
> Please checkout this: https://source.sakaiproject.org/contrib/itunesu/trunk/itunesu-scripts/
>
> UofM have established a yearly routine to prune itunesu content because of the 500G storage limit.
>
> HTH,
>
> - Zhen
>
> On Feb 16, 2012, at 11:54 AM, Adam Marshall wrote:
>
>
> ITunesU doesn?t have any sort of web services interface though does it?
>
> adam
>
> From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of DAVID ROLDAN MARTINEZ
> Sent: 13 February 2012 18:42
> To: sakai-dev at collab.sakaiproject.org
> Subject: [Building Sakai] Sakai-ItunesU
>
> Hi all,
>
> We are exploring the possibilities of replicating the index, content and/or resources of a Sakai course in an ItunesU course in an automated way. Has someone done anything related to this?
>
> Thank you very much in advance.
>
> Best,
> David
> _______________________________________________
> 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/20120216/12644e37/attachment-0001.html
------------------------------
Message: 22
Date: Thu, 16 Feb 2012 09:27:27 -0800
From: Karen Tsao <ktsao at stanford.edu>
Subject: Re: [Building Sakai] Problems exporting and importing
assessments
To: Raul Sanchez Vegas <raulsv at um.es>
Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
Message-ID:
<CAC29pTLBnQG9x88BEv_XwBrXxfFGOboKfZWQ_P5nMM+Uqxp06Q at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Raul,
Please see my comments below:
> First bug:
>
> - The instructor creates a new assessment.
> - The instructor creates the first assessment's question which text has
> an image reference.
> - The instructor exports the assessment using the "content package" option.
> - The instructor try to import this assessment but it doesn't work and
> it is shown this message
> "There was an error importing this assignment. Ensure that the file is
> correctly formatted IMS QTI."
>
> We have found out that it doesn't work because the importing action try
> to find the image of the question's text inside the zip file but it
> isn't there.
>
> If the export is made using the QTI option then the import doesn't fail.
>
I cannot reproduce this issue. Can you please give me an example of your
text?
>
> Second bug:
>
> - The instructor creates a new assessment.
> - The instructor creates the first assessment's question with an
> attachment.
> - The instructor exports the assessment using the QTI option.
> - The instructor imports the assessment and it works fine but the
> assessment's question doesn't have its attachment. The question has lost
> its attachment.
>
>
This is the expected behavior. If your assessment contains attachments,
please use Content Package. If you think the instruction is not clear
enough, please feel free to log a JIRA and we will see if we can add more
instruction.
Thanks,
Karen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/84e6a784/attachment-0001.html
------------------------------
Message: 23
Date: Thu, 16 Feb 2012 12:34:24 -0500
From: Matthew Jones <matthew at longsight.com>
Subject: Re: [Building Sakai] Commit messages - a humble little plea
To: Zhen Qian <zqian at umich.edu>
Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
Message-ID:
<CACz7-HRTq1LLToxQ29yF_KrnpUq0d9gHZ=Sx_eNDz31j_RTtkQ at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
If we ever had a change that was so high security that we couldn't even
make the fix public until the public, then no public version control system
would work. We'd have to just pass around a patch on the security list (or
in jira), release a binary (just the class file) and not commit it until
enough time had passed. It wouldn't matter what version control system we
used. I don't think this has happened yet though.
The bigger problem with subversion is accidently committing something you
didn't want to (like passwords or copyrighted data). It can be difficult to
remove it as it involves rebuilding the entire archive by the
administrator. Something that's not super likely to happen except in
extreme cases. Removing sensitive style data isn't even that easy on git
either. (http://help.github.com/remove-sensitive-data/)
In any version control system even if you could flag something as
'confidential' a smart user could still notice something out of the
ordinary in the change history, even if it might be more difficult.
I think git might obscure these better with the guids, but the system still
does keep track of the order or the changes.
On Thu, Feb 16, 2012 at 12:21 PM, Zhen Qian <zqian at umich.edu> wrote:
> Ahh, I guess that's the beauty of opensource then :)
>
> svn is designed to never lose information. I don't know whether svn is
> capable to hide content diff or log message, aka "confidential checkin",
> based on security settings.
>
> How about git? Just curious.
>
> Tanks,
> - Zhen
> On Feb 16, 2012, at 11:54 AM, D. Stuart Freeman wrote:
>
> > On Wed, Feb 15, 2012 at 10:11:37AM -0500, Zhen Qian wrote:
> >> I agree with the plea and I will remember to include more context and
> change info into the commit log.
> >>
> >> However, I think there is another exception to this, the security
> jiras. I think the succinct text like just the jira number is enough for
> those, since the log text is public.
> >
> > So is the changeset though, so if it's obvious that it's a security issue
> > an attacker can presumably work out the attack based on the new logic.
> >
> >>
> >> Thanks,
> >>
> >> - zhen
> >>
> >> On Feb 14, 2012, at 5:51 PM, Steve Swinsburg wrote:
> >>
> >>> I agree with this, trunk commits should include info about what the
> commit is doing. However there is one exception, branch merging.
> >>>
> >>> These have historically been of the form:
> >>>
> >>> SAK-123 merge trunk r12345
> >>>
> >>> If it merges cleanly, otherwise it would be:
> >>>
> >>> SAK-123 manually merge trunk r12345 (and any other notes required).
> >>>
> >>> You can then reference the original trunk commit and jira.
> >>>
> >>> cheers,
> >>> Steve
> >>>
> >>>
> >>> On 15/02/2012, at 4:25 AM, DAVID ROLDAN MARTINEZ wrote:
> >>>
> >>>> I absolutely agree. In fact, my commit messages are so brief (just
> the ticket number) because I thought that was the standard way of doing
> this. :D
> >>>>
> >>>> -----Mensaje original-----
> >>>> De: sakai-dev-bounces at collab.sakaiproject.org [mailto:
> sakai-dev-bounces at collab.sakaiproject.org] En nombre de Aaron Zeckoski
> >>>> Enviado el: martes, 14 de febrero de 2012 18:14
> >>>> Para: Noah Botimer
> >>>> CC: sakai-dev
> >>>> Asunto: Re: [Building Sakai] Commit messages - a humble little plea
> >>>>
> >>>> Definitely agree with this. And as much as possible, try to include
> the intent/reason behind the commit rather than just repeating the title
> which is probably something weird like "Tool X instructions are confusing".
> A better message would be "Updated the tool X instructions with more
> details about using a mouse in a web browser".
> >>>>
> >>>> -AZ
> >>>>
> >>>>
> >>>> On Tue, Feb 14, 2012 at 11:56 AM, Noah Botimer <botimer at umich.edu>
> wrote:
> >>>>> Hello folks,
> >>>>>
> >>>>> A trend I've noticed is the shortening of commit messages, to the
> >>>>> point of simply being a JIRA issue number. There is an up-side here:
> I
> >>>>> don't remember the last real commit I saw without a JIRA ticket
> >>>>> referenced. However, the downside is significant in assuming that
> this is sufficient.
> >>>>>
> >>>>> Take, for example, examining the history of a couple of branches to
> >>>>> find when something was introduced. Common cases of this are
> >>>>> cherry-picking a feature and porting a bug fix. I won't belabor all
> of
> >>>>> the hassle, but mention a few points:
> >>>>>
> >>>>> First, each JIRA ticket must be called up individually to see what
> the
> >>>>> intent was (set aside the topic of issue titles, which could be
> better
> >>>>> generally). Second, there are often multiple commits against a
> ticket,
> >>>>> sometimes interleaved with others, so the task often includes closely
> >>>>> analyzing multiple diffs just to divine the intent. Third, there are
> >>>>> occasionally errors in the reference or multiple issues combined in a
> >>>>> commit, making it very difficult to track in either direction (from
> >>>>> JIRA or Subversion).
> >>>>>
> >>>>>
> >>>>> So, my simple request follows:
> >>>>>
> >>>>> Could we please try to include a brief summary of what action is
> being
> >>>>> taken with each commit? If the change is non-trivial, please also
> >>>>> include some details of what was introduced, changed, or removed.
> >>>>>
> >>>>>
> >>>>> JIRA is great, but the one real truth is the source revision history.
> >>>>> If you are committing something, please tell the historical record
> >>>>> what you were doing.
> >>>>>
> >>>>> Although it has some Git specifics, this is a very nice
> >>>>> guideline:
> >>>>> http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
> >>>>>
> >>>>> Thanks,
> >>>>> -Noah
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> 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"
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile_______________________________________________
> >>>> 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"
> >>>
> >>> _______________________________________________
> >>> 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"
> >
> > --
> > D. Stuart Freeman
> > Georgia Institute of Technology
>
> _______________________________________________
> 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/20120216/a3ae82fe/attachment-0001.html
------------------------------
Message: 24
Date: Thu, 16 Feb 2012 12:39:15 -0500
From: "D. Stuart Freeman" <stuart.freeman at et.gatech.edu>
Subject: Re: [Building Sakai] Commit messages - a humble little plea
To: Zhen Qian <zqian at umich.edu>
Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
Message-ID: <20120216173915.GG17318 at cetel-004-xx6.admin.gatech.edu>
Content-Type: text/plain; charset="us-ascii"
On Thu, Feb 16, 2012 at 12:21:00PM -0500, Zhen Qian wrote:
> Ahh, I guess that's the beauty of opensource then :)
>
> svn is designed to never lose information. I don't know whether svn is capable to hide content diff or log message, aka "confidential checkin", based on security settings.
>
> How about git? Just curious.
With git you could do something like have a private repo that only the
security team could look at. You could then push security bug fixes only
to that repo until they're vetted, at which point you merge them into the
public repo and they become visible to everyone. I don't know that this
is the best idea/policy for getting good solutions to security issues in
a timely manner, but it's technically feasible.
I'm often of the opinion that if the good guys know about it, the bad guys
do too, or can figure it out. So, IMHO the best course of action is to
accuratly describe the risks to deployers and get them a patch as fast as
possible.
>
> Tanks,
> - Zhen
> On Feb 16, 2012, at 11:54 AM, D. Stuart Freeman wrote:
>
> > On Wed, Feb 15, 2012 at 10:11:37AM -0500, Zhen Qian wrote:
> >> I agree with the plea and I will remember to include more context and change info into the commit log.
> >>
> >> However, I think there is another exception to this, the security jiras. I think the succinct text like just the jira number is enough for those, since the log text is public.
> >
> > So is the changeset though, so if it's obvious that it's a security issue
> > an attacker can presumably work out the attack based on the new logic.
> >
> >>
> >> Thanks,
> >>
> >> - zhen
> >>
> >> On Feb 14, 2012, at 5:51 PM, Steve Swinsburg wrote:
> >>
> >>> I agree with this, trunk commits should include info about what the commit is doing. However there is one exception, branch merging.
> >>>
> >>> These have historically been of the form:
> >>>
> >>> SAK-123 merge trunk r12345
> >>>
> >>> If it merges cleanly, otherwise it would be:
> >>>
> >>> SAK-123 manually merge trunk r12345 (and any other notes required).
> >>>
> >>> You can then reference the original trunk commit and jira.
> >>>
> >>> cheers,
> >>> Steve
> >>>
> >>>
> >>> On 15/02/2012, at 4:25 AM, DAVID ROLDAN MARTINEZ wrote:
> >>>
> >>>> I absolutely agree. In fact, my commit messages are so brief (just the ticket number) because I thought that was the standard way of doing this. :D
> >>>>
> >>>> -----Mensaje original-----
> >>>> De: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] En nombre de Aaron Zeckoski
> >>>> Enviado el: martes, 14 de febrero de 2012 18:14
> >>>> Para: Noah Botimer
> >>>> CC: sakai-dev
> >>>> Asunto: Re: [Building Sakai] Commit messages - a humble little plea
> >>>>
> >>>> Definitely agree with this. And as much as possible, try to include the intent/reason behind the commit rather than just repeating the title which is probably something weird like "Tool X instructions are confusing". A better message would be "Updated the tool X instructions with more details about using a mouse in a web browser".
> >>>>
> >>>> -AZ
> >>>>
> >>>>
> >>>> On Tue, Feb 14, 2012 at 11:56 AM, Noah Botimer <botimer at umich.edu> wrote:
> >>>>> Hello folks,
> >>>>>
> >>>>> A trend I've noticed is the shortening of commit messages, to the
> >>>>> point of simply being a JIRA issue number. There is an up-side here: I
> >>>>> don't remember the last real commit I saw without a JIRA ticket
> >>>>> referenced. However, the downside is significant in assuming that this is sufficient.
> >>>>>
> >>>>> Take, for example, examining the history of a couple of branches to
> >>>>> find when something was introduced. Common cases of this are
> >>>>> cherry-picking a feature and porting a bug fix. I won't belabor all of
> >>>>> the hassle, but mention a few points:
> >>>>>
> >>>>> First, each JIRA ticket must be called up individually to see what the
> >>>>> intent was (set aside the topic of issue titles, which could be better
> >>>>> generally). Second, there are often multiple commits against a ticket,
> >>>>> sometimes interleaved with others, so the task often includes closely
> >>>>> analyzing multiple diffs just to divine the intent. Third, there are
> >>>>> occasionally errors in the reference or multiple issues combined in a
> >>>>> commit, making it very difficult to track in either direction (from
> >>>>> JIRA or Subversion).
> >>>>>
> >>>>>
> >>>>> So, my simple request follows:
> >>>>>
> >>>>> Could we please try to include a brief summary of what action is being
> >>>>> taken with each commit? If the change is non-trivial, please also
> >>>>> include some details of what was introduced, changed, or removed.
> >>>>>
> >>>>>
> >>>>> JIRA is great, but the one real truth is the source revision history.
> >>>>> If you are committing something, please tell the historical record
> >>>>> what you were doing.
> >>>>>
> >>>>> Although it has some Git specifics, this is a very nice
> >>>>> guideline:
> >>>>> http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
> >>>>>
> >>>>> Thanks,
> >>>>> -Noah
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> 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"
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile _______________________________________________
> >>>> 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"
> >>>
> >>> _______________________________________________
> >>> 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"
> >
> > --
> > D. Stuart Freeman
> > Georgia Institute of Technology
>
--
D. Stuart Freeman
Georgia Institute of Technology
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120216/d1dd9cde/attachment-0001.bin
------------------------------
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
End of sakai-dev Digest, Vol 36, Issue 16
*****************************************
More information about the sakai-dev
mailing list