[sakai-pmc] Dashboard inclusion in trunk

Bryan Holladay holladay at longsight.com
Wed Jun 11 05:43:15 PDT 2014


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

Unless this has changed in a recent version, there really is no way to "run
dashboard in stealth".  All the hard word (event collection and
aggregation) is constantly running behind the scenes.  The only thing
stealthed is the tool interface to users, which is a simple lookup table.
 So in this case, running in production but not being exposed to the UI is
about 95% of the load.

-Bryan


On Wed, Jun 11, 2014 at 4:34 AM, Jean-Francois Leveque <
jean-francois.leveque at upmc.fr> wrote:

> I'm not blocking, just discussing, because I know I can be the minority
> in case of a vote.
>
> I'm not demanding that the contributing institution fix all JIRAs. Only
> critical issues and another issue previously mentioned were written
> about. Other members of the community can help the contributing
> institution before (or after) the inclusion and I've read UM was asking
> for such help.
>
> I'm only asking about the order of fixing and including.
>
> I won't comment about "outdated and unhelpful method of operating."
> because I don't know how it could be proven right or wrong.
>
> Le 10/06/2014 17:03, Sam Ottenhoff a écrit :
> > I agree 100% with John Bush.  This is an important piece of
> > functionality that needs to be in core Sakai to round out the product.
> >   Blocking the road and demanding that the contributing institution fix
> > all JIRAs and meet other criteria is an outdated and unhelpful method of
> > operating.  I believe there are enough of us that together believe in
> > pushing the product features forward and will collaborate over the
> > coming months on getting the remaining JIRAs resolved.
> >
> >
> > On Tue, Jun 10, 2014 at 10:57 AM, John Bush <jbush at anisakai.com
> > <mailto:jbush at anisakai.com>> wrote:
> >
> >     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
> >     <mailto: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
> >     <mailto: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
> >
> >
> >
> >     --
> >     John Bush
> >     602-490-0470
> >
> >     ** This message is neither private nor confidential in fact the US
> >     government is storing it in a warehouse located in Utah for future
> >     data mining use cases should they arise. **
> >     _______________________________________________
> >     sakai-pmc mailing list
> >     sakai-pmc at collab.sakaiproject.org
> >     <mailto:sakai-pmc at collab.sakaiproject.org>
> >     http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20140611/11775acc/attachment-0001.html 


More information about the sakai-pmc mailing list