COmanage Developers List

[Benn Oshrin <>]

If you didn't already have an account with Spaces or JIRA, then yes you 
need to enroll with that COmanage instance. If you run into problems, I2 
tech support is pretty responsive, or let me know and I'll get in touch 
with them.

Thanks,

-Benn-

On 5/16/19 1:57 AM, Ioannis Igoumenos wrote:
> Hi Benn,
>
> thank you for your feedback.
>
> I am trying to create a Jira ticket but as soon as i press Create, only 
> the 'Grouper Security Vulnerability' project is available. I tried to 
> login, which led to an enrollment flow through COManage. Now i am 
> waiting for a confirmation from the side of support. Should i follow a 
> different path?
>
>
> Thank you,
>
> Ioannis
>
>
> On 15/5/19 6:12 μ.μ., Benn Oshrin wrote:
> > Hey Ioannis,
> >
> > Your timing here is very good, as the dev group just had a similar 
> > conversation about increasing the use of the COmanage CO for platform 
> > configuration. (See notes in https://todos.internet2.edu/browse/CO-1481)
> >
> > Originally, the thought was that platform localization could happen 
> > via the lang.php file (see also CO-1168), but in practice updating 
> > that file is a bit of a pain, and obviously requires VM level access. 
> > So I agree your proposal makes sense.
> >
> > One consideration is that this is technically a breaking change, and 
> > therefore would need to be scheduled for v4.0.0. While I expect very 
> > few deployments are doing so, any current deployments that have 
> > localized text in the COmanage CO would need to do some form of 
> > reconfiguration, otherwise those texts would become platform wide 
> > after upgrading.
> >
> > So if we want to move ahead with this, I think the steps are
> >
> > 1. Open a new JIRA issue, linked to CO-1168 and CO-1481
> > 2. Create a new develop-4.0.0 branch (or something) and ultimately 
> > submit the PR against that branch.
> > 3. Merge develop-4 into develop later this year, depending on the 
> > project release cycle.
> >
> > Thanks,
> >
> > -Benn-
> >
> > On 5/14/19 4:28 AM, Ioannis Igoumenos wrote:
> > > Hi Benn,
> > >
> > > while trying to set a couple of *global* localization variables in 
> > > COManage, i understood that i could not do it.
> > >
> > > What i mean is that we added some localization variables in the 
> > > COManage default CO and we expected to see this variables everywhere. 
> > > Nevertheless, this did not happen.
> > >
> > > For us it would make sense if the localization variables created in 
> > > comanage default CO, were global even for home(display) page. 
> > > Continuously, if a user creates a new localization variable in a 
> > > specific CO, then this variable would
> > >
> > > overwrite all the previous. Something like the custom Theme 
> > > functionality.
> > >
> > >
> > > Does this make sense to you?
> > >
> > >
> > > Thank you in advance,
> > >
> > > Ioannis
> > >
> > > --
> > > Ioannis Igoumenos
> > > Research Engineer
> > > GRNET - Greek Research and Technology Network
> > > 7, Kifisias Av., 115 23, Athens, Greece
> > > t: +30 210 7471130 ext: 442
> > > f: +30 210 7474490
> > >
> > > Follow us:www.grnet.gr
> > > Twitter: @grnet_gr | Facebook: @grnet.gr
> > > LinkedIn: grnet | YouTube: GRNET EDET