Split comonent into Web UI and Web Rest

[Reto Bachmann-Gmür <re...@apache.org>]

Hi,

Looking to assign STANBOL-944 to the right component in jira I found
nothing suitable. "Web" would be appropriate, "REST" would be too but "Web
UI" seems clearly wrong as the "U" in "UI" is typically thought as a human
user.

One possibility would be to introduce a new component "REST infrastructure".

Cheers,
Reto

Re: Split comonent into Web UI and Web Rest

[Fabian Christ <ch...@googlemail.com>]

Hi,

okay - I did rename "Web UI" to "Web" in JIRA.

Best,
 - Fabian

2013/2/18 Reto Bachmann-Gmür <re...@apache.org>:
> On Mon, Feb 18, 2013 at 3:00 PM, Fabian Christ <christ.fabian@googlemail.com
>> wrote:
>
>> Hi,
>>
>> is the functionality implemented in commons?
>
> The resolution of STAANBOL-936 was in commons.web. Maybe the easiest would
> just be a rename from "Web UI" to "Web". As we don't intend to spend lot of
> effort in UI design I think having all in this component would be fine.
>
> Cheers,
> Reto
>
>
>
>
>> Then it would be commons
>> at the moment. The "Web UI" component is not really helpful and yes -
>> maybe we need some new structure.
>>
>> I tried to align the components in JIRA with the releases we have cut.
>> It was just an attempt to easily find out which issues can be closed
>> after a release. Otherwise it can be really time consuming to filter
>> issues and decide if they are reflected by a new release of some
>> component.
>>
>> For releases it is a mapping problem:
>> Release -> JIRA component -> physical artifacts -> code changes
>>
>> JIRA issues are described sometimes on the level of a JIRA component,
>> sometimes a physical artifact. Often it is the case that a single
>> issue addresses more than one JIRA component and/or artifacts.
>>
>> If a new component is introduced, like "REST infrastructure", it would
>> be good to find this component also in the SVN directory and that
>> there exists a reactor that builds just this component. That makes
>> release cutting easy.
>>
>> Best,
>>  - Fabian
>>
>> 2013/2/18 Reto Bachmann-Gmür <re...@apache.org>:
>> > Hi,
>> >
>> > Looking to assign STANBOL-944 to the right component in jira I found
>> > nothing suitable. "Web" would be appropriate, "REST" would be too but
>> "Web
>> > UI" seems clearly wrong as the "U" in "UI" is typically thought as a
>> human
>> > user.
>> >
>> > One possibility would be to introduce a new component "REST
>> infrastructure".
>> >
>> > Cheers,
>> > Reto
>>
>>
>>
>> --
>> Fabian
>> http://twitter.com/fctwitt
>>



--
Fabian
http://twitter.com/fctwitt

Re: Split comonent into Web UI and Web Rest

[Reto Bachmann-Gmür <re...@apache.org>]

On Mon, Feb 18, 2013 at 3:00 PM, Fabian Christ <christ.fabian@googlemail.com
> wrote:

> Hi,
>
> is the functionality implemented in commons?

The resolution of STAANBOL-936 was in commons.web. Maybe the easiest would
just be a rename from "Web UI" to "Web". As we don't intend to spend lot of
effort in UI design I think having all in this component would be fine.

Cheers,
Reto




> Then it would be commons
> at the moment. The "Web UI" component is not really helpful and yes -
> maybe we need some new structure.
>
> I tried to align the components in JIRA with the releases we have cut.
> It was just an attempt to easily find out which issues can be closed
> after a release. Otherwise it can be really time consuming to filter
> issues and decide if they are reflected by a new release of some
> component.
>
> For releases it is a mapping problem:
> Release -> JIRA component -> physical artifacts -> code changes
>
> JIRA issues are described sometimes on the level of a JIRA component,
> sometimes a physical artifact. Often it is the case that a single
> issue addresses more than one JIRA component and/or artifacts.
>
> If a new component is introduced, like "REST infrastructure", it would
> be good to find this component also in the SVN directory and that
> there exists a reactor that builds just this component. That makes
> release cutting easy.
>
> Best,
>  - Fabian
>
> 2013/2/18 Reto Bachmann-Gmür <re...@apache.org>:
> > Hi,
> >
> > Looking to assign STANBOL-944 to the right component in jira I found
> > nothing suitable. "Web" would be appropriate, "REST" would be too but
> "Web
> > UI" seems clearly wrong as the "U" in "UI" is typically thought as a
> human
> > user.
> >
> > One possibility would be to introduce a new component "REST
> infrastructure".
> >
> > Cheers,
> > Reto
>
>
>
> --
> Fabian
> http://twitter.com/fctwitt
>

Re: Split comonent into Web UI and Web Rest

[Fabian Christ <ch...@googlemail.com>]

Hi,

is the functionality implemented in commons? Then it would be commons
at the moment. The "Web UI" component is not really helpful and yes -
maybe we need some new structure.

I tried to align the components in JIRA with the releases we have cut.
It was just an attempt to easily find out which issues can be closed
after a release. Otherwise it can be really time consuming to filter
issues and decide if they are reflected by a new release of some
component.

For releases it is a mapping problem:
Release -> JIRA component -> physical artifacts -> code changes

JIRA issues are described sometimes on the level of a JIRA component,
sometimes a physical artifact. Often it is the case that a single
issue addresses more than one JIRA component and/or artifacts.

If a new component is introduced, like "REST infrastructure", it would
be good to find this component also in the SVN directory and that
there exists a reactor that builds just this component. That makes
release cutting easy.

Best,
 - Fabian

2013/2/18 Reto Bachmann-Gmür <re...@apache.org>:
> Hi,
>
> Looking to assign STANBOL-944 to the right component in jira I found
> nothing suitable. "Web" would be appropriate, "REST" would be too but "Web
> UI" seems clearly wrong as the "U" in "UI" is typically thought as a human
> user.
>
> One possibility would be to introduce a new component "REST infrastructure".
>
> Cheers,
> Reto



--
Fabian
http://twitter.com/fctwitt