[sakai-pmc] Dashboard inclusion in trunk

[Berg, Alan]

Hi all,

The dashboard add's value. By default, we should let developers get at the code.  I therefore think it's important to get the dashboard into trunk. 

Regards,
           Alan


Alan Berg

Innovation working group
On the use of ICT in Education & Research
University of Amsterdam
Postbus 1025 / 1000 BA Amsterdam
Weesperzijde 190 / 1097 DZ Amsterdam

________________________________________
From: sakai-pmc-bounces at collab.sakaiproject.org [sakai-pmc-bounces at collab.sakaiproject.org] on behalf of Jean-Francois Leveque [jean-francois.leveque at upmc.fr]
Sent: 11 June 2014 10:27
To: sakai-pmc at collab.sakaiproject.org
Subject: Re: [sakai-pmc] Dashboard inclusion in trunk

It's not about where the code comes from. Schools that were known and
trusted in the past left us with issues to solve. Look at the number of
components that have "Core Team" as lead!

I won't judge the usefulness of dashboard.

I don't think running stealthed is completely running in production.

I do think postponing fixing issues in dashboard after its inclusion in
trunk is dangerous.

About known issues in JIRA, with the few issues I've mentioned, I've
only scratched the surface of 29 open issues and 10 that still have to
be verified.

I don't think you understood my point either, but writing we don't
understand each other won't get us far. :(

Le 10/06/2014 16:57, John Bush a écrit :
> I don't think you understood my point.   Inclusion in trunk doesn't
> necessarily mean something is 100% production ready and stable, or
> that its passed detailed QA.  Putting it in trunk does actually help
> get more eyes and more QA on things, because more people will be
> running it everyday.  If there is translation work that needs to
> happen, getting it in trunk will help move that faster as well.
>
> If you were bringing up a bunch of issues that break the build, or
> otherwise cause day to day work to be affected, then you would have a
> valid reason for not including in trunk.
>
> The dashboard IMHO, makes Sakai a much better product, much more
> useful, and valuable.  The technology stack is no different than other
> things we support.  It was built by a school we all know and trust.
> Its been running in production.  Those are the types of criteria I
> think are important to something getting in trunk or not.
>
> On Tue, Jun 10, 2014 at 7:39 AM, Jean-Francois Leveque
> <jean-francois.leveque at upmc.fr> wrote:
>> 10 being expected to be released within a few weeks and is therefore today's
>> release.
>>
>> Putting Dashboard in trunk shows intent to put it into 11 which is
>> tomorrow's release.
>>
>> Doesn't seem to me in a good enough state for that, AFAICT. I would like to
>> be as confident as you are, but I need more information for that.
>>
>> Le 10/06/2014 16:28, John Bush a écrit :
>>
>>> We aren't talking about putting it in a release tomorrow, we are talking
>>> about putting it in trunk for 11.
>>>
>>> Seems to me it's in a good enough state for that.
>>>
>>> Sent from my iPhone
>>>
>>>> On Jun 10, 2014, at 7:11 AM, Jean-Francois Leveque
>>>> <jean-francois.leveque at upmc.fr> wrote:
>>>>
>>>> I wasn't able to attend at Miami and am therefore learning about this
>>>> discussion now.
>>>>
>>>> Is dashboard currently used in another language than English?
>>>>
>>>> About the general state of Dashboard I've just checked JIRA quickly and
>>>> found the following.
>>>>
>>>> DASH-242 is shown as Critical and DASH-310 as Major.
>>>>
>>>> Apart from the issues mentioned by Beth, there are also the following
>>>> Critical issues:
>>>> DASH-308
>>>> DASH-292
>>>>
>>>> I think it would be a good idea to get Dashboard in good state before
>>>> its inclusion.
>>>>
>>>> Cheers,
>>>>
>>>> J-F
>>>>
>>>> Le 10/06/2014 15:46, Anthony Whyte a écrit :
>>>>>
>>>>> Following up on our discussion in Miami regarding moving the Dashboard
>>>>> project from contrib to core before the anticipated migration of Sakai
>>>>> trunk to Github, I pinged Beth for a status update.  Her reply is below:
>>>>>
>>>>> "Feel free to let people know that we've been running Dashboard in
>>>>> production (stealthed) for several months without incident, and we plan
>>>>> to unstealth it in the Fall. There are still bugs related to
>>>>> functionality we could use some help on (e.g. DASH-242, DASH-310), but
>>>>> we feel the software itself is robust and production ready."
>>>>>
>>>>> Given this assessment, I'm prepared to draft a proposal that would have
>>>>> us move Dashboard to trunk for Sakai 11, unless someone objects to the
>>>>> idea.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Anthony

_______________________________________________
sakai-pmc mailing list
sakai-pmc at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc