Re: Getting more people able to cut releases for @uportal npm organization

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Getting more people able to cut releases for @uportal npm organization

Andrew Petro-3
+1

Steerers having admin might be important to ensure that the project retains effective control of the uPortal organization on NPM over time.

I'd interpret "be given publish access" in the Committers case as "be given publish access the first time they need it or sooner if that need seems likely". I wouldn't provision access that's unlikely to be exercised, even though I totally agree the Committer is welcome to that access the moment they need it to exercise the responsibilities of Committership. That pespective offered, if someone else provisions and navigates the tradeoffs differently, I'll have no objection.

-Andrew


On Tuesday, October 16, 2018 at 11:17:32 AM UTC-5, Christian Murphy wrote:
Hey all,

As web component driven portal development becomes more common.
It becomes more important that the community has the ability to create and manage components quickly and effectively.
To help empower folks to continue to build new and interesting interfaces, it would help to expand the number of people who can publish packages to the <a href="https://www.npmjs.com/org/uportal" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.npmjs.com%2Forg%2Fuportal\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHBGnSQGQJYPNACzSmnRg7pSLBMSw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.npmjs.com%2Forg%2Fuportal\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHBGnSQGQJYPNACzSmnRg7pSLBMSw&#39;;return true;">uPortal organization on NPM.

I propose that the uPortal steering committee be given admin access to the organization, and that the <a href="https://github.com/Jasig/uPortal/blob/master/docs/COMMITTERS.md" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FJasig%2FuPortal%2Fblob%2Fmaster%2Fdocs%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFoyOvU09149SgQMVvWb-Ut1dnq-g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FJasig%2FuPortal%2Fblob%2Fmaster%2Fdocs%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFoyOvU09149SgQMVvWb-Ut1dnq-g&#39;;return true;">uPortal, <a href="https://github.com/uPortal-Project/uportal-home/blob/master/committers.md" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-Project%2Fuportal-home%2Fblob%2Fmaster%2Fcommitters.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGl98gFG5_XNpUGxqTYgwFliANNEA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-Project%2Fuportal-home%2Fblob%2Fmaster%2Fcommitters.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGl98gFG5_XNpUGxqTYgwFliANNEA&#39;;return true;">uPortal-home, and <a href="https://github.com/uPortal-contrib/uPortal-web-components/blob/master/COMMITTERS.md" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-contrib%2FuPortal-web-components%2Fblob%2Fmaster%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF8tmPXiI9OWchGK_qeziJvr-iV4A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-contrib%2FuPortal-web-components%2Fblob%2Fmaster%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF8tmPXiI9OWchGK_qeziJvr-iV4A&#39;;return true;">uPortal-web-components committers be given publish access.

Best Regards,

Christian Murphy

--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.
Reply | Threaded
Open this post in threaded view
|

Re: Getting more people able to cut releases for @uportal npm organization

Julien Gribonvald

Hi !

I won't vote as I'm concerned by this need as I can't publish to @uPortal npm all new version of my components.

An alternative would be to have a server with a bot that will generate package and deploy it on npm each time a new tag is created on the git repo, but there is a server cost ! Expect if someone have a better idea ?

On my side I didn't find any other alternative. The only alternative is publishing on my own npm account/organization my components before to push them on uportal-contrib, finally I won't use my components from uPortal repo, so it's not encouraging sharing the work ....

- Julien


Le 19/10/2018 à 06:25, 'Andrew Petro' via uPortal Developers a écrit :
+1

Steerers having admin might be important to ensure that the project retains effective control of the uPortal organization on NPM over time.

I'd interpret "be given publish access" in the Committers case as "be given publish access the first time they need it or sooner if that need seems likely". I wouldn't provision access that's unlikely to be exercised, even though I totally agree the Committer is welcome to that access the moment they need it to exercise the responsibilities of Committership. That pespective offered, if someone else provisions and navigates the tradeoffs differently, I'll have no objection.

-Andrew


On Tuesday, October 16, 2018 at 11:17:32 AM UTC-5, Christian Murphy wrote:
Hey all,

As web component driven portal development becomes more common.
It becomes more important that the community has the ability to create and manage components quickly and effectively.
To help empower folks to continue to build new and interesting interfaces, it would help to expand the number of people who can publish packages to the <a href="https://www.npmjs.com/org/uportal" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.npmjs.com%2Forg%2Fuportal\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHBGnSQGQJYPNACzSmnRg7pSLBMSw';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.npmjs.com%2Forg%2Fuportal\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHBGnSQGQJYPNACzSmnRg7pSLBMSw';return true;" moz-do-not-send="true">uPortal organization on NPM.

I propose that the uPortal steering committee be given admin access to the organization, and that the <a href="https://github.com/Jasig/uPortal/blob/master/docs/COMMITTERS.md" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FJasig%2FuPortal%2Fblob%2Fmaster%2Fdocs%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFoyOvU09149SgQMVvWb-Ut1dnq-g';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FJasig%2FuPortal%2Fblob%2Fmaster%2Fdocs%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFoyOvU09149SgQMVvWb-Ut1dnq-g';return true;" moz-do-not-send="true">uPortal, <a href="https://github.com/uPortal-Project/uportal-home/blob/master/committers.md" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-Project%2Fuportal-home%2Fblob%2Fmaster%2Fcommitters.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGl98gFG5_XNpUGxqTYgwFliANNEA';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-Project%2Fuportal-home%2Fblob%2Fmaster%2Fcommitters.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGl98gFG5_XNpUGxqTYgwFliANNEA';return true;" moz-do-not-send="true">uPortal-home, and <a href="https://github.com/uPortal-contrib/uPortal-web-components/blob/master/COMMITTERS.md" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-contrib%2FuPortal-web-components%2Fblob%2Fmaster%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF8tmPXiI9OWchGK_qeziJvr-iV4A';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-contrib%2FuPortal-web-components%2Fblob%2Fmaster%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF8tmPXiI9OWchGK_qeziJvr-iV4A';return true;" moz-do-not-send="true">uPortal-web-components committers be given publish access.

Best Regards,

Christian Murphy
--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.
--
Julien Gribonvald

--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.
Reply | Threaded
Open this post in threaded view
|

Re: Getting more people able to cut releases for @uportal npm organization

Andrew Petro-3
Julien,

Potential path forward:

2. You gain publish on the npm org.
3. You publish web components.

:)

On Friday, October 19, 2018 at 4:55:27 AM UTC-5, Julien Gribonvald wrote:

Hi !

I won't vote as I'm concerned by this need as I can't publish to @uPortal npm all new version of my components.

An alternative would be to have a server with a bot that will generate package and deploy it on npm each time a new tag is created on the git repo, but there is a server cost ! Expect if someone have a better idea ?

On my side I didn't find any other alternative. The only alternative is publishing on my own npm account/organization my components before to push them on uportal-contrib, finally I won't use my components from uPortal repo, so it's not encouraging sharing the work ....

- Julien


Le 19/10/2018 à 06:25, 'Andrew Petro' via uPortal Developers a écrit :
+1

Steerers having admin might be important to ensure that the project retains effective control of the uPortal organization on NPM over time.

I'd interpret "be given publish access" in the Committers case as "be given publish access the first time they need it or sooner if that need seems likely". I wouldn't provision access that's unlikely to be exercised, even though I totally agree the Committer is welcome to that access the moment they need it to exercise the responsibilities of Committership. That pespective offered, if someone else provisions and navigates the tradeoffs differently, I'll have no objection.

-Andrew


On Tuesday, October 16, 2018 at 11:17:32 AM UTC-5, Christian Murphy wrote:
Hey all,

As web component driven portal development becomes more common.
It becomes more important that the community has the ability to create and manage components quickly and effectively.
To help empower folks to continue to build new and interesting interfaces, it would help to expand the number of people who can publish packages to the <a href="https://www.npmjs.com/org/uportal" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.npmjs.com%2Forg%2Fuportal\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHBGnSQGQJYPNACzSmnRg7pSLBMSw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.npmjs.com%2Forg%2Fuportal\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHBGnSQGQJYPNACzSmnRg7pSLBMSw&#39;;return true;">uPortal organization on NPM.

I propose that the uPortal steering committee be given admin access to the organization, and that the <a href="https://github.com/Jasig/uPortal/blob/master/docs/COMMITTERS.md" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FJasig%2FuPortal%2Fblob%2Fmaster%2Fdocs%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFoyOvU09149SgQMVvWb-Ut1dnq-g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FJasig%2FuPortal%2Fblob%2Fmaster%2Fdocs%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFoyOvU09149SgQMVvWb-Ut1dnq-g&#39;;return true;">uPortal, <a href="https://github.com/uPortal-Project/uportal-home/blob/master/committers.md" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-Project%2Fuportal-home%2Fblob%2Fmaster%2Fcommitters.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGl98gFG5_XNpUGxqTYgwFliANNEA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-Project%2Fuportal-home%2Fblob%2Fmaster%2Fcommitters.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGl98gFG5_XNpUGxqTYgwFliANNEA&#39;;return true;">uPortal-home, and <a href="https://github.com/uPortal-contrib/uPortal-web-components/blob/master/COMMITTERS.md" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-contrib%2FuPortal-web-components%2Fblob%2Fmaster%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF8tmPXiI9OWchGK_qeziJvr-iV4A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-contrib%2FuPortal-web-components%2Fblob%2Fmaster%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF8tmPXiI9OWchGK_qeziJvr-iV4A&#39;;return true;">uPortal-web-components committers be given publish access.

Best Regards,

Christian Murphy
--

--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.
Reply | Threaded
Open this post in threaded view
|

Re: Getting more people able to cut releases for @uportal npm organization

Drew Wills

And mine is drewwills -- thank you.

drew

On 10/24/18 1:27 AM, Julien Gribonvald wrote:

Thanks Andrew !

my npm account is jgribonvald ;)

Julien


Le 24/10/2018 à 00:55, 'Andrew Petro' via uPortal Developers a écrit :
Julien,

Potential path forward:

2. You gain publish on the npm org.
3. You publish web components.

:)

On Friday, October 19, 2018 at 4:55:27 AM UTC-5, Julien Gribonvald wrote:

Hi !

I won't vote as I'm concerned by this need as I can't publish to @uPortal npm all new version of my components.

An alternative would be to have a server with a bot that will generate package and deploy it on npm each time a new tag is created on the git repo, but there is a server cost ! Expect if someone have a better idea ?

On my side I didn't find any other alternative. The only alternative is publishing on my own npm account/organization my components before to push them on uportal-contrib, finally I won't use my components from uPortal repo, so it's not encouraging sharing the work ....

- Julien


Le 19/10/2018 à 06:25, 'Andrew Petro' via uPortal Developers a écrit :
+1

Steerers having admin might be important to ensure that the project retains effective control of the uPortal organization on NPM over time.

I'd interpret "be given publish access" in the Committers case as "be given publish access the first time they need it or sooner if that need seems likely". I wouldn't provision access that's unlikely to be exercised, even though I totally agree the Committer is welcome to that access the moment they need it to exercise the responsibilities of Committership. That pespective offered, if someone else provisions and navigates the tradeoffs differently, I'll have no objection.

-Andrew


On Tuesday, October 16, 2018 at 11:17:32 AM UTC-5, Christian Murphy wrote:
Hey all,

As web component driven portal development becomes more common.
It becomes more important that the community has the ability to create and manage components quickly and effectively.
To help empower folks to continue to build new and interesting interfaces, it would help to expand the number of people who can publish packages to the <a href="https://www.npmjs.com/org/uportal" rel="nofollow" target="_blank" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.npmjs.com%2Forg%2Fuportal\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHBGnSQGQJYPNACzSmnRg7pSLBMSw';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.npmjs.com%2Forg%2Fuportal\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHBGnSQGQJYPNACzSmnRg7pSLBMSw';return true;" moz-do-not-send="true">uPortal organization on NPM.

I propose that the uPortal steering committee be given admin access to the organization, and that the <a href="https://github.com/Jasig/uPortal/blob/master/docs/COMMITTERS.md" rel="nofollow" target="_blank" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FJasig%2FuPortal%2Fblob%2Fmaster%2Fdocs%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFoyOvU09149SgQMVvWb-Ut1dnq-g';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FJasig%2FuPortal%2Fblob%2Fmaster%2Fdocs%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFoyOvU09149SgQMVvWb-Ut1dnq-g';return true;" moz-do-not-send="true">uPortal, <a href="https://github.com/uPortal-Project/uportal-home/blob/master/committers.md" rel="nofollow" target="_blank" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-Project%2Fuportal-home%2Fblob%2Fmaster%2Fcommitters.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGl98gFG5_XNpUGxqTYgwFliANNEA';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-Project%2Fuportal-home%2Fblob%2Fmaster%2Fcommitters.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGl98gFG5_XNpUGxqTYgwFliANNEA';return true;" moz-do-not-send="true">uPortal-home, and <a href="https://github.com/uPortal-contrib/uPortal-web-components/blob/master/COMMITTERS.md" rel="nofollow" target="_blank" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-contrib%2FuPortal-web-components%2Fblob%2Fmaster%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF8tmPXiI9OWchGK_qeziJvr-iV4A';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FuPortal-contrib%2FuPortal-web-components%2Fblob%2Fmaster%2FCOMMITTERS.md\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF8tmPXiI9OWchGK_qeziJvr-iV4A';return true;" moz-do-not-send="true">uPortal-web-components committers be given publish access.

Best Regards,

Christian Murphy
--

--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.
--
Julien Gribonvald
--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.

--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.
Reply | Threaded
Open this post in threaded view
|

Re: Getting more people able to cut releases for @uportal npm organization

Christian Cousquer
And mine is cousquer -- thanks 🙏.

Le mer. 24 oct. 2018 à 21:01, Drew Wills <[hidden email]> a écrit :

And mine is drewwills -- thank you.


drew

On 10/24/18 1:27 AM, Julien Gribonvald wrote:

Thanks Andrew !

my npm account is jgribonvald ;)

Julien


Le 24/10/2018 à 00:55, 'Andrew Petro' via uPortal Developers a écrit :
Julien,

Potential path forward:

2. You gain publish on the npm org.
3. You publish web components.

:)

On Friday, October 19, 2018 at 4:55:27 AM UTC-5, Julien Gribonvald wrote:

Hi !

I won't vote as I'm concerned by this need as I can't publish to @uPortal npm all new version of my components.

An alternative would be to have a server with a bot that will generate package and deploy it on npm each time a new tag is created on the git repo, but there is a server cost ! Expect if someone have a better idea ?

On my side I didn't find any other alternative. The only alternative is publishing on my own npm account/organization my components before to push them on uportal-contrib, finally I won't use my components from uPortal repo, so it's not encouraging sharing the work ....

- Julien


Le 19/10/2018 à 06:25, 'Andrew Petro' via uPortal Developers a écrit :
+1

Steerers having admin might be important to ensure that the project retains effective control of the uPortal organization on NPM over time.

I'd interpret "be given publish access" in the Committers case as "be given publish access the first time they need it or sooner if that need seems likely". I wouldn't provision access that's unlikely to be exercised, even though I totally agree the Committer is welcome to that access the moment they need it to exercise the responsibilities of Committership. That pespective offered, if someone else provisions and navigates the tradeoffs differently, I'll have no objection.

-Andrew


On Tuesday, October 16, 2018 at 11:17:32 AM UTC-5, Christian Murphy wrote:
Hey all,

As web component driven portal development becomes more common.
It becomes more important that the community has the ability to create and manage components quickly and effectively.
To help empower folks to continue to build new and interesting interfaces, it would help to expand the number of people who can publish packages to the uPortal organization on NPM.

I propose that the uPortal steering committee be given admin access to the organization, and that the uPortal, uPortal-home, and uPortal-web-components committers be given publish access.

Best Regards,

Christian Murphy
--

--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.
--
Julien Gribonvald
--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.

--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.

--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/uportal-dev/.