Dear Michael,
Thanks for sending the revised list here – very helpful indeed. I have a few questions here related to the list, as I know we have several other items listed on the
https://github.com/MichaelKambenga/ihfr_curation/issues?q=is%3Aissue+is%3Aopen that are listed as open issues still – and I think we want to continue to use Github to track open issues so the whole team has visibility into the open issues etc.
(1) One of these is related to the username that is logged in the collection for the requested changes – has this been updated to reflect the actual user who made the request instead of the administrator user?
(2) The second is related to release management of these bug fixes to the production site, and testing of these. We had talked about putting together a brief release management series of steps, identifying users who could test the revised code on the staging server, and then notifying users that new code is being released, and having some notification to all users of the changes that have been made and what issues were fixed.
(3) The third one is related to changing the hierarchy with the revised council list. Scott and I are ready to create these councils that were missing, but we need to do this in an organized manner, so that we can take the curation tool offline for users, while we make the changes, and then also find a way to see which users are impacted, so we can make sure they have access to the right councils.
How can we coordinate on item 2 and 3 here, so that we have a standardized process in place that UCC can lead here, and take over so that any additional councils changes can be made down the road by UCC?
It would probably be really useful to have a call to discuss this so please let me know when you have time here.
Thanks! Niamh
--
You received this message because you are subscribed to the Google Groups "hfr-tz" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
hfr-tz+un...@googlegroups.com.
To post to this group, send email to hfr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Michael,
That sounds great to have a call here. I spoke with Scott also, as we need his assistance here in 2 of these items I think. We are free anytime Tue, Wed or Thu, from 3.30 pm onwards TZ time to chat technically about these items? Please let us know if any of these times would work?
Thanks, Niamh
From: hfr...@googlegroups.com [mailto:hfr...@googlegroups.com] On Behalf Of Michael Kambenga
Sent: Monday, September 29, 2014 3:51 AM
To: hfr...@googlegroups.com
Thanks Ilomo for this feedback, and thanks for supporting the users here. It sounds like you were able to help them log in which is great.
Niamh
Thanks Michael,
Can we meet tomorrow morning US time, 7.30 wed, which is 14.30 Tanzania time.
Thanks, Niamh
I have a conflict tomorrow at 16.00 TZ time. So, could we make it instead at 15.00 Tanzania time? Niamh
Hello Michael/UCC,
Is it possible on UCC side to trace on the authentication logs to study what is happening?
1. Could it be possible users do forget their passwords/usernames,
2. Or could it be possible that there could be a communication timeout between AAA server(s) and curation tool (if they sit in different locations)
3. What about uptime of both servers AAA and curation?
Could there also be regular communication to users to remind them on what to do in case passwords are forgotten. This could be through emails and if possible phone.
We need to know
Denis.
From: hfr...@googlegroups.com [mailto:hfr...@googlegroups.com] On Behalf Of ilomosilvanus
Sent: Monday, September 29, 2014 5:56 PM
To: hfr-tz@googlegroups com
Here is the link for the call.
https://plus.google.com/hangouts/_/g53em32ymf6oxgx3sfl2a4tpoea
Please join in!