3:19 p.m.
Hey everyone,
On 16 January 2018 at 16:00, Ioannis Kakavas <ikakavas at protonmail.com> wrote:
We touched upon adding more people (Leif) as owners
for the pysaml2-dev and
satosa-dev channels on Slack too
That's what we discussed, iirc.
pysaml2-dev.slack.com
satosa-dev.slack.com
Since Leif wasn't a member in either of those, I made Ivan an owner for now.
Thanks for that.
I've been on those channels for some time now, and they are both quiet
enough. I would propose to have a single slack channel (idpy.slack.com
maybe?) and have separate channels for each project (that want to have
a channel) - plus the "random" channel for slacking :) , one for
github integration (broadcasting code changes, commits, testing
results), and another for announcements (new releases).
I would also propose to have an idpy-announcements mailing-list, with
only announcements of new project releases, or changes in the
organisation (additions or removals of projects and people) -- that is
strictly announcements, not discussions -- ideally replies should be
ignored by the list.
This would make management and coordination easier across the
different projects and project-communities. It will give an easier
overview of what's happening and will allow external people to
subscribe to only the vital parts that they may care for (project
announcement).
Usually announcements can be posted on a blog or twitter as
yet-another communication channel. This is a process that should be
automated and a trigger will post to all those channels at the same
time.
To close this, this is definitely not a high-priority thing. If we
agree on that, I think we can steadily start moving to that direction.
But, lets discuss it first. Are people comfortable using a single
slack channel? How do project maintainers feel about that? And if we
go forward, can we merge message histories? Should we contact slack
for help with something like that?
Cheers,
--
Ivan c00kiemon5ter Kanakarakis >:3
3:32 p.m.
New subject: Communication channels. Was: Re: Notes: idpy dev meeting, 9 January 2018
Huge +1 for the Single workspace for idpy (with per project channels) and +1 for the
announce list.
can we merge message histories? Should we contact
slack for help with something like that?
Not sure anything of value will be lost in the history..
-------- Original Message --------
Subject: Communication channels. Was: Re: [Idpy-discuss] Notes: idpy dev meeting, 9
January 2018
Local Time: January 16, 2018 5:19 PM
UTC Time: January 16, 2018 3:19 PM
From: ivan.kanak at gmail.com
To: Ioannis Kakavas <ikakavas at protonmail.com>
discuss at idpy.org <discuss at idpy.org>
Hey everyone,
On 16 January 2018 at 16:00, Ioannis Kakavas ikakavas at protonmail.com wrote:
We touched upon adding more people (Leif) as
owners for the pysaml2-dev and
satosa-dev channels on Slack too
That's what we discussed, iirc.
pysaml2-dev.slack.com
satosa-dev.slack.com
Since Leif wasn't a member in either of those, I made Ivan an owner for now.
Thanks for that.
I've been on those channels for some time now, and they are both quiet
enough. I would propose to have a single slack channel (idpy.slack.com
maybe?) and have separate channels for each project (that want to have
a channel) - plus the "random" channel for slacking :) , one for
github integration (broadcasting code changes, commits, testing
results), and another for announcements (new releases).
I would also propose to have an idpy-announcements mailing-list, with
only announcements of new project releases, or changes in the
organisation (additions or removals of projects and people) -- that is
strictly announcements, not discussions -- ideally replies should be
ignored by the list.
This would make management and coordination easier across the
different projects and project-communities. It will give an easier
overview of what's happening and will allow external people to
subscribe to only the vital parts that they may care for (project
announcement).
Usually announcements can be posted on a blog or twitter as
yet-another communication channel. This is a process that should be
automated and a trigger will post to all those channels at the same
time.
To close this, this is definitely not a high-priority thing. If we
agree on that, I think we can steadily start moving to that direction.
But, lets discuss it first. Are people comfortable using a single
slack channel? How do project maintainers feel about that? And if we
go forward, can we merge message histories? Should we contact slack
for help with something like that?
Cheers,
Ivan c00kiemon5ter Kanakarakis >:3 
2285
days inactive
2285
days old
2 comments
3 participants
participants (3)
-
ikakavas＠protonmail.com -
ivan.kanak＠gmail.com -
skoranda＠gmail.com