[Portfolio] [Management] Deprecating reports and warehouse tools.

[Anthony Whyte]

I recommend that this issue be surfaced on sakai-dev and the production lists.  The developer/production community should have a chance to comment on the proposal.

Cheers,

Anthony


Begin forwarded message:

> From: Anthony Whyte <arwhyte at umich.edu>
> Date: March 10, 2010 11:24:03 AM GMT+02:00
> To: Michael Korcuska <mkorcuska at sakaifoundation.org>
> Cc: Alan Berg <qa.director.sakai at gmail.com>, Beth Kirschner <bkirschn at umich.edu>, lbrooks at stanford.edu, Noah Botimer <botimer at umich.edu>
> Subject: Re: Test plans for reports
> 
> I recommend that this issue be surfaced on sakai-dev so that others can have a chance to comment.  I also agree with MK's hesitation regarding the proposed criteria for deprecation/removal proposed by Alan; better to simply focus on the absence of community support rather than assert what is absolutely true but can't at this moment be backed up by procedural documentation.
> 
> As for the mechanics of deprecation I assume we would do the following:
> 
> 1) roll back the reports fix.  As a courtesy make sure reports at least starts up in Tomcat.
> 2) relocate reports and warehouse to contrib (strictly speaking this not absolutely necessary at the present time; we could do it when we have time)
> 3) either
> 	a.  stealth reports and warehouse in trunk/2.7.x (if the projects are moved we will have to repoint .externals to their contrib locations)
> 	b.  excise reports and warehouse from trunk/2.7.x builds (i.e., remove them from .externals)
> 
> Today I have the day off until 5 pm (GMT+2) when I head in to UCT to join in on the MT call.  Reports/warehouse are on our agenda.
> 
> Cheers,
> 
> Anthony
> 



On Mar 10, 2010, at 1:29 AM, Berg, Alan wrote:

> Hi Clay,
> 
> Good questions:
> 
> 1) The report tool did not start up in beta 3 or beta 4, this was due to remedial repairs that broke the tool in a difficult to diagnose way.
> 2) The warehouse tool has the same community support level as the reports tool, which at best is low.
> 3) External dependencies are not known to me and if exist are dangerous.
> 
> I think this is a good juncture for the OSP experts to cast their opinions.
> 
> Alan
> 
> Alan Berg
> Interim QA Director - The Sakai Foundation
> 
> Senior Developer / Quality Assurance
> Group Education and Research Services
> Central Computer Services
> University of Amsterdam
> 
> http://home.uva.nl/a.m.berg
> 
> 
> Alan
> 
> Alan Berg
> Interim QA Director - The Sakai Foundation
> 
> Senior Developer / Quality Assurance
> Group Education and Research Services
> Central Computer Services
> University of Amsterdam
> 
> http://home.uva.nl/a.m.berg
> 
> 
> 
> 
> -----Original Message-----
> From: khomotso at gmail.com on behalf of Clay Fenlason
> Sent: Wed 3/10/2010 0:20
> To: management at collab.sakaiproject.org; plumbers at sakaifoundation.org; portfolio
> Subject: Re: [Management] Deprecating reports and warehouse tools.
> 
> Copying the portfolio list on this, to cast the net for informed
> functional opinions a little wider.
> 
> No comments from me for the moment, I just want to ask an extra
> question or two. Can you explain more precisely what "does not work"
> means for the Reports tool?
> 
> What dependencies are there between the Reports and Warehouse tools
> and any other parts of osp? Or perhaps even outside the osp suite?
> 
> ~Clay
> 
> On Tue, Mar 9, 2010 at 5:50 PM, Berg, Alan <A.M.Berg at uva.nl> wrote:
> > Hi Product council and Maintenance team members,
> >
> > the MT are meeting Wednesday to discuss depreciation recommendations for the
> > PC as part of the Sakai 2.7 life cycle. This is good as the MT are the
> > experts who deal with operational reality on a daily basis.
> >
> > As Interim QA director I have the professional role to signal issues
> > clearly. The Reports tool does not work in the QA tag Sakai 2.7 beta 4 and
> > that the warehouse tool also appears to be unsupported. After discussion
> > with Noah and Beth I believe that the tools do not have sufficient community
> > support and are not being used widely enough to justify continued QA
> > effort. I therefore strongly recommend moving the tools from Enterprise core
> > status back into contrib before the beta 5 tag is released and thus giving
> > QA enough time to verify that removal was safe before 2.7 is tagged.
> >
> > Alan
> >
> > Alan Berg
> > Interim QA Director - The Sakai Foundation
> >
> > Senior Developer / Quality Assurance
> > Group Education and Research Services
> > Central Computer Services
> > University of Amsterdam
> >
> > http://home.uva.nl/a.m.berg
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > management mailing list
> > management at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/management
> >
> > TO UNSUBSCRIBE: send email to management-unsubscribe at collab.sakaiproject.org
> > with a subject of "unsubscribe"
> >
> 
> 
> 
> _______________________________________________
> management mailing list
> management at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/management
> 
> TO UNSUBSCRIBE: send email to management-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/portfolio/attachments/20100310/708f65ae/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2417 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/portfolio/attachments/20100310/708f65ae/attachment.bin