Hi,
Responding here on individual capacity, and my team mates will surely
have different views on some items. I will try to address some of the
comments and criticisms of our proposal at once.
First of all, I think that we did not make it clear enough that this is
"where we want to go", as the su
A community team is a good thing. Just its apparent focus on the Code of
Conduct is unfortunate. The biggest modulators of how we interact among
ourselves and how much inviting we are perceived as a community imho
currently are (somewhat ordered):
* salsa
* blends
* debconfs
* sprints
*
On 09/10/19 at 22:26 +0100, Steve McIntyre wrote:
> * Proactively writing emails to those who habitually make the
>community a hostile place, informing them that their behavior is
>harmful to the community, that action may be taken in the future,
^^^
On Wed, Oct 09, 2019 at 10:26:39PM +0100, Steve McIntyre wrote:
> Hi folks,
>
> We've had a lot of conversations this year about where the
> Anti-Harassment (now *Community*) Team should be going: what we're
> trying to do, and the relationship we'd like to have with the rest of
> the project and
Hi there,
I am just emailing to ask if you would be interested in placing any guest
content on your site?
I represent ProPrivacy, an online resource dedicated to helping everyone
reclaim their online privacy and stay safe in the digital age. We're
looking to spread our message far and wide and I
[content summary: interpretation with delegation, role separation for
definition and enforcement of rules, distinction between guidance and
warning, timeliness.]
Hi Steve, Community team and everybody,
I think that the current changes in name and role of the A-H team go in
a good direction. Here
> "Enrico" == Enrico Zini writes:
Enrico> On Wed, Oct 09, 2019 at 10:26:39PM +0100, Steve McIntyre wrote:
Enrico> I join other respondents, with a risk of redundancy, with a
Enrico> few notes due to the decision of not having delegated powers
Enrico> and being an undelegated a
On October 10, 2019 9:00:43 AM UTC, Gerardo Ballabio
wrote:
>Steve McIntyre wrote:
>> Within the team, we've brainstormed about this and come up with the
>following to describe our role and responsibilities. We'd like to
>discuss it now with the rest of the project. Feedback welcome please!
>
I wrote:
> That isn't really different from the Community Team claiming ownership of
> interpreting the CoC simply because they were the first who started working
> on that.
Thinking again about it, maybe they should have filed an ITP bug?!?
Gerardo
Enrico Zini wrote:
>> * Remove blogs from community forums like Planet Debian
>
>This I think is something the team could actually do, just as any Debian
>Developer could do it, having commit access to the planet config.
While technically they have the ability to do that, they are not
allowed to
Steve McIntyre wrote:
> Within the team, we've brainstormed about this and come up with the following
> to describe our role and responsibilities. We'd like to discuss it now with
> the rest of the project. Feedback welcome please!
Hi Steve,
that looks good (I especially like the "Examples of th
On Wed, Oct 09, 2019 at 10:26:39PM +0100, Steve McIntyre wrote:
I join other respondents, with a risk of redundancy, with a few notes
due to the decision of not having delegated powers and being an
undelegated advisory group.
> The (CT) is the team responsible for interpreting the Code of Conduc
* Steve McIntyre: " Community Team - where we want to go" (Wed, 9 Oct 2019
22:26:39 +0100):
Hi!
> Within the team, we've brainstormed about this and come up with the
> following to describe our role and responsibilities. We'd like to
> discuss it now with the rest of the project. Feedback welco
13 matches
Mail list logo
