All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gunnar Mills <gmills@linux.vnet.ibm.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Moving the WebUI to Vue; Repo vs Branch
Date: Wed, 18 Dec 2019 10:00:38 -0600	[thread overview]
Message-ID: <60d44fed-74e2-70e3-e91f-ae1289d1700f@linux.vnet.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]

Hi All,

This is a follow on to previous discussions of moving the GUI away from 
AngularJS and to a new framework, Vue, that was discussed on the list 
and in the GUI design workgroup meeting.

See:
https://lists.ozlabs.org/pipermail/openbmc/2019-September/018299.html
https://github.com/openbmc/openbmc/wiki/GUI-Design-work-group

The team here had some questions about Vue and wanted to answer some of 
our and the community concerns about moving to Vue, so over the last few 
weeks, our team has spent time working on a Vue prototype. If you are 
interested, https://github.com/gtmills/phosphor-webui-vue

This prototype has a few working panels and builds with the current 
webui recipe, 
https://github.com/gtmills/openbmc/commit/de6e2daef54fa5ace473a42b9ff9014cc9cb02ba

IBM is committed to moving the WebUI to Vue.
Is anyone opposed to moving to Vue?

Should this work be done in a separate repo?

Or a separate branch in phosphor-webui, that would be merged into the 
master branch once this Vue rewrite becomes functionally equivalent to 
the current AngularJS application?

Would anyone stay on the current AngularJS application?

We plan to maintain the current AngularJS application until the Vue 
rewrite becomes functionally equivalent, would anyone maintain the 
AngularJS application after such a time?

Thanks,
Gunnar


[-- Attachment #2: Type: text/html, Size: 2344 bytes --]

             reply	other threads:[~2019-12-18 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18 16:00 Gunnar Mills [this message]
2020-01-08 21:48 ` Moving the WebUI to Vue; Repo vs Branch Gunnar Mills
2020-01-15 17:54   ` Gunnar Mills
2020-01-17 13:12     ` Brad Bishop
2020-01-17 17:47       ` Gunnar Mills

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60d44fed-74e2-70e3-e91f-ae1289d1700f@linux.vnet.ibm.com \
    --to=gmills@linux.vnet.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.