Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-ui-dev] Tip of the day

I'm sure you do not mean to disqualify Nebula [0] but let me defend her anyway.  

Nebula has had four releases since 1-6-2016 [1]. Here is the latest N&N [2].  We have a full cycle build which automatically runs any attached tests [3]. We are a Gerrit user since the beginning and have extensive documentation on how to contribute [4].  All widgets come with examples and most with snippets[5] and we have our own perspective where users can play with the widgets. 

Our stats are here [6].




On Mon, Jul 10, 2017 at 3:48 PM, Mickael Istria <mistria@xxxxxxxxxx> wrote:

On Mon, Jul 10, 2017 at 3:39 PM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
@mickael: I guess we can move it. Why do you ask?

The reason I have in mind is that Platform requires and uses more constraints than Nebula. Those constraints are the price to pay for sustainability of Platform (they can be API/version numbering, reproducible qualifiers, process to make sure doc is up-to-date accordingly, strict schedule and rules to include new features...). So adding a dependency from Platform to a project which doesn't enforce such constraints may be an issue to maintain the quality of Platform.
Hence why I think such component should be in Platform if we want to use it in Platform.

That said, I'm not sure that such tip of the day would fit best in Platform. Maybe it could be some EPP bundle, like the Marketplace Client; in which case, it's fine ot use Nebula components I believe.

It's a more a design decision between enforcing quality at the price of constraints (Platform) or choosing more agility at the price of lower internal quality requirement (Nebula/EPP).


platform-ui-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top