[All] Is it time to move on from StoryBoard? (Was: [All][StoryBoard] Angular.js Alternatives)

Stephen Finucane stephenfin at redhat.com
Wed Jan 27 10:17:38 UTC 2021


On Tue, 2021-01-26 at 12:51 -0800, Kendall Nelson wrote:
> For better or for worse, we are a pretty small team and don't need to poll
> since we can all attend a meeting and agree there. 
> 
> Calling for outside opinions was also a half hearted plea for help :) 

Is this an indication that we finally have to settle on another bug tracker?
This has been discussed previously but I can't find any conclusions from those
past discussions, hence I'm asking again. I do not intend to dismiss the hard
work of those people working on StoryBoard in the slightest, but it does seem
like StoryBoard as a project has never really taken off outside OpenStack and is
having a hard time surviving, let alone growing, likely because of that along
with the widespread use of forge-style tools (GitHub, GitLab) and more
comprehensive project management tools (sigh, JIRA). I recall fungi (?) raising
the idea of enabling the more forge'y features, including the issue tracker, of
Gitea in the past, but there are also separate tools like (heaven forbid)
Bugzilla, Trac, Mantis, etc. that we could use. Heck, Launchpad is still around
and is still open source (though I recall there being other issues with that?).
We've already made a tough decision recently, with the sunsetting of ask.o.o,
and with the impending deprecation of Angular.js, perhaps this is as good a time
as any to do the same with StoryBoard?

/me goes back to logging in for the zillionth time while trying to triage OSC
bugs :)

Cheers,
Stephen

> -Kendall (diablo_rojo)
> 
> On Fri, Jan 22, 2021 at 1:28 AM Radosław Piliszek
> <radoslaw.piliszek at gmail.com> wrote:
> > On Thu, Jan 21, 2021 at 10:24 PM Kendall Nelson <kennelson11 at gmail.com>
> > wrote:
> > > 
> > > Hello Everyone!
> > > 
> > > The StoryBoard team is looking at alternatives to Angular.js since its
> > going end of life. After some research, we've boiled all the options down to
> > two possibilities:
> > > 
> > > Vue.js
> > > 
> > > or
> > > 
> > > React.js
> > 
> > Hello, Kendall!
> > 
> > This is likely the toughest question in the frontend universe at the moment.
> > Both solutions are very well thought out and have solid ecosystems.
> > Based on observed productivity both are good choices.
> > Personally, I have done more Vue than React.
> > I have added a few points in the etherpad.
> > Angular is not a bad choice either but it involves much stronger
> > bonding with the final product.
> > The others leave more freedom of choice.
> > 
> > As for the verdict, I am afraid the best solution would be to run
> > voting for parties interested in Storyboard development and just stick
> > to the poll winner.
> > 
> > -yoctozepto
> > 
> > > I am diving more deeply into researching those two options this week, but
> > any opinions or feedback on your experiences with either of them would be
> > helpful!
> > > 
> > > Here is the etherpad with our research so far[3].
> > > 
> > > Feel free to add opinions there or in response to this thread!
> > > 
> > > -Kendall Nelson (diablo_rojo) & The StoryBoard Team
> > > 
> > > [1] https://vuejs.org/
> > > [2] https://reactjs.org/
> > > [3] https://etherpad.opendev.org/p/replace-angularjs-storyboard-research





More information about the openstack-discuss mailing list