code logs -> 2021 -> Tue, 06 Jul 2021< code.20210705.log - code.20210707.log >
--- Log opened Tue Jul 06 00:00:21 2021
00:33 abudhabi_ [abudhabi@Nightstar-7u8og7.adsl.tpnet.pl] has joined #code
00:36 abudhabi [abudhabi@Nightstar-von9v3.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
01:28 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
02:51 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has quit [[NS] Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
02:51 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has joined #code
02:51 mode/#code [+o Reiv] by ChanServ
03:09 Degi [Degi@Nightstar-69457v.pool.telefonica.de] has quit [Operation timed out]
03:09 Degi [Degi@Nightstar-d6aghi.pool.telefonica.de] has joined #code
03:27 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has quit [[NS] Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
03:27 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has joined #code
03:27 mode/#code [+o Reiv] by ChanServ
03:41 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has quit [[NS] Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
03:48 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has joined #code
03:48 mode/#code [+o Reiv] by ChanServ
04:19 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has quit [[NS] Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
04:28 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has joined #code
04:28 mode/#code [+o Reiv] by ChanServ
05:01 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has quit [[NS] Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
05:11 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has joined #code
05:11 mode/#code [+o Reiv] by ChanServ
05:14 VirusJTG [VirusJTG@Nightstar-ggj.oti.104.208.IP] has quit [Connection closed]
05:15 VirusJTG [VirusJTG@Nightstar-ggj.oti.104.208.IP] has joined #code
05:15 mode/#code [+ao VirusJTG VirusJTG] by ChanServ
06:00 Vorntastic [uid293981@Nightstar-h2b233.irccloud.com] has joined #code
06:00 mode/#code [+qo Vorntastic Vorntastic] by ChanServ
06:08 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has quit [[NS] Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
06:15 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has joined #code
06:15 mode/#code [+o Reiv] by ChanServ
07:21 Kindamoody[zZz] is now known as Kindamoody
08:01 Netsplit Deepthought.Nightstar.Net <-> Krikkit.Nightstar.Net quits: @PinkFreud
08:02 Netsplit over, joins: @PinkFreud
12:18 catralyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [[NS] Quit: -a- Connection Timed Out]
12:18 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
12:20 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [[NS] Quit: -a- IRC for Android 2.1.59]
13:55 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
15:01 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
15:01 mode/#code [+qo Vornicus Vornicus] by ChanServ
15:04 Kindamoody is now known as Kindamoody|out
17:04 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has joined #code
17:29 Vorntastic [uid293981@Nightstar-h2b233.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
18:39 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Connection reset by peer]
18:39 catalyst_ [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
18:52 catalyst [catalyst@Nightstar-arqf2l.dab.02.net] has joined #code
18:54 catalyst_ [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Ping timeout: 121 seconds]
19:18 gnolam_ [lenin@Nightstar-j9ajs0.priv.bahnhof.se] has joined #code
19:20 gnolam [lenin@Nightstar-j9ajs0.priv.bahnhof.se] has quit [Ping timeout: 121 seconds]
19:38 catalyst_ [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
19:39 catalys82 [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
19:39 catalyst_ [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Connection reset by peer]
19:41 catalyst [catalyst@Nightstar-arqf2l.dab.02.net] has quit [Connection reset by peer]
20:03 gnolam_ [lenin@Nightstar-j9ajs0.priv.bahnhof.se] has quit [Ping timeout: 121 seconds]
20:10 gnolam [lenin@Nightstar-j9ajs0.priv.bahnhof.se] has joined #code
20:10 mode/#code [+o gnolam] by ChanServ
20:51 Kindamoody|out is now known as Kindamoody
22:10 gnolam_ [lenin@Nightstar-j9ajs0.priv.bahnhof.se] has joined #code
22:11 gnolam [lenin@Nightstar-j9ajs0.priv.bahnhof.se] has quit [Ping timeout: 121 seconds]
22:15 gnolam_ is now known as gnolam
22:15 mode/#code [+o gnolam] by ChanServ
22:17 Kindamoody is now known as Kindamoody[zZz]
22:33 abudhabi [abudhabi@Nightstar-ren0qg.adsl.tpnet.pl] has joined #code
22:36 abudhabi_ [abudhabi@Nightstar-7u8og7.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
23:07 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has quit [Ping timeout: 121 seconds]
23:20 * Reiver hunts about for Teams expertise, suspects this is Mahal
23:21
< Mahal>
Uhoh
23:21
<&Reiver>
This is 'brainstorming and wondering if Teams is the right place, and I sure hope it is'
23:21
<&Reiver>
If you're up for it?
23:22
< Mahal>
I'm in a meeting right now, but brainstorm away and I'll get to you shortly :P
23:22
<&Reiver>
cool cool
23:23
<&Reiver>
We have seven non-production environments. (I know, I know.) These get blagged by various projects for varying lengths of time, in which they then 'own' the server; being able to faff about with the data and schedule refreshes (restoring to latest version of Production data and config) and generally having First Say on what happens in the environment.
23:25
<&Reiver>
Sometimes someone will need a non-prod environment for an ancillary use real quick to test something, double check something, etc; Part of my job is looking at who is doing what in where, then having the folks often end up going to the present 'owner' to check it's cool that there's double-faff going on in the same environment etc
23:25
<&Reiver>
All to the good... except this is a wee tad challenging to keep track of Who is Where and for How Long
23:25
<&Reiver>
The old solution was an excel spreadsheet made to look like a calendar and printed on the wall. Obviously not perfect.
23:26
<&Reiver>
I am proposing we have a calendar, or possibly suite of calendars, to keep track of Who is Where and for How Long, and then the extra bonus with a Teams group thus meaning that it's easier to spam folks with "Is anyone using RUA at the moment that we're not aware of? We're planning to XYZ it next week unless someone speaks up" kind of games.
23:27
<&Reiver>
Is Teams a decent fit for this? I know little of the calendar functionality, but it seems a tad cleaner than just half a dozen Outlook group calendars and a bunch of email chains >_>
23:28
< Mahal>
In this context Teams = Sharepoint calendars, and yes, they work fine.
23:28
< Mahal>
pin the tabs to the Team of the assorted calendars and away you go.
23:32
<&Reiver>
So this would be one Team with 7 calendars attached to it? Or one calendar? or
23:32
<&Reiver>
I confess I know precisely squat about Sharepoint
23:32
< Mahal>
Hold this thought until I'm not actively meeting
23:32
<&Reiver>
np, no rush
23:36
< Mahal>
okay, so
23:41
< Mahal>
https://saranyansenthivel.medium.com/creating-a-shared-calendar-in-microsoft-teams-400ab556bfa3
23:43
< Mahal>
https://usercontent.irccloud-cdn.com/file/Ud3miFtV/image.png
23:44
< Mahal>
I can't find the actual image I'm looking for so I'm going to DIY my own
23:44
< Mahal>
hold the phone
23:49
< Mahal>
Anyway, once you have your Team, you can go to [whatever] channel you want to use for this
23:49
< Mahal>
add a tab
23:49
< Mahal>
https://usercontent.irccloud-cdn.com/file/eLaDjPH6/image.png
23:49
< Mahal>
select Channel Calendar https://usercontent.irccloud-cdn.com/file/ZcAjeYcp/image.png
23:50
< Mahal>
Or, you can set up a Sharepoint List, as a calendar, and insert that as a tab into Teams (and then you can also manage it thru Sharepoint)
23:51
<&Reiver>
A... Sharepoint List?
23:52
<&Reiver>
(apologies, I know very little about the system capabilities of this thing, I just use it to phone people at th emoment and am convinced we could leverage it for shinier stuff)
23:52
< Mahal>
:D
23:52
< Mahal>
Okay, here's the thing
23:52
< Mahal>
there's approximately a millionty ways to skin this cat
23:53
<&Reiver>
Yeah
23:53
< Mahal>
So, how do you need to manage this? MUST it be with Outlook? who needs access? are there four people or six hundred?
23:53
< Mahal>
if there's like fifteen of you managing it then fuck, just use a channel calendar in a Team and be done (nb: will NOT be manageable with Outlook, EVER)
23:53
< Mahal>
(*For now until Microsoft update that, le sigh)
23:55
< Mahal>
https://usercontent.irccloud-cdn.com/file/TowfsTh2/image.png
23:57
< Mahal>
https://usercontent.irccloud-cdn.com/file/sRwuXaUu/image.png
23:58
< Mahal>
(You see them in Outlook but you don't get to edit them :D )
23:58
< Mahal>
Anyway, Teams would work fine for this
23:58
< Mahal>
use a Channel calendar
23:58
< Mahal>
be done
23:59
< Mahal>
All the events you create in a channel calendar automatically invite everyone who's a member of the Channel.
23:59
< Mahal>
so that might not be ideal.
23:59
< Mahal>
maybe you want a Sharepoint list that's a webpart embedded in a Teams tab instead!
--- Log closed Wed Jul 07 00:00:23 2021
code logs -> 2021 -> Tue, 06 Jul 2021< code.20210705.log - code.20210707.log >

[ Latest log file ]