Hello! I've tried to provide Code of Conduct based on Arch Linux CoC,
pasted here: https://paste.kde.org/pzdmvyi3t
Will try to send it to codereview later, feel free to do it instead of me
if it will be easier for you,
I'm going to spend some time to learn how to do it correctly
пн, 29 окт. 2018
community
with current details, but I guess it could be helpful for future
comparition.
пн, 29 окт. 2018 г. в 18:40, Thiago Macieira :
> On Monday, 29 October 2018 00:52:49 PDT Alexey Andreyev wrote:
> > Talking about CC and KDE's CoC, it's not obvious for me how to perform
> > poli
> I think we have two camps:
> We want a CoC as a feel-good statement of inclusion and tolerance (I
think everyone is > committed to this)
> AND
> 1) We want to use existing situation of laws/self-policing OR
> 2) We want a CoC that contains a framework that can get people banned or
more
Hello,
to step back.
I do not want to look like annoying person, just wanted to help with
controversial subjects.
I have no doubts about Qt people professionalism and happy do be a part of
the community.
пн, 29 окт. 2018 г. в 7:08, Thiago Macieira :
> On Sunday, 28 October 2018 17:20:04 PDT Al
Thank you, Lydia and everyone!
I hope I'm not upsetting anyone. I could accept I'm taking too much
attention to the subject.
Qt project is very valuable for me as a user and a developer.
пн, 29 окт. 2018 г. в 2:53, Lydia Pintscher :
> On Sun, Oct 28, 2018 at 10:45 PM Thiago Macieira
> wrote:
hy.
пн, 29 окт. 2018 г. в 0:44, Thiago Macieira :
> On Sunday, 28 October 2018 13:18:02 PDT Alexey Andreyev wrote:
> > > The text is clear - actions will be taken to stop the discrimination.
> > > That involves technical means (kick / ban) but also more social means
> >
ouldn't find any
> > > controversial sentences. Could you elaborate? Which points shall be
> > > discussed?
> > >
> > > > The controversial discrimination protection sentences at least
> should be carefully discussed. It's not some thing that we could
nubmer of the conflicts at Qt project before,
anything like that.
Nobody tried to predict the consequences after accepting current CoC.
We just trying to provide some rules and to treat something blindly
without even specifying the problem.
вс, 28 окт. 2018 г. в 17:35, Elvis Stansvik :
> Den
my arguments be adressed to someone personally, and I'm not
saying there's some conspiracy here.
I just want to help to save and develop the community for the future.
I agree we need rules. My problem is not any rules are healthy.
вс, 28 окт. 2018 г. в 14:37, Elvis Stansvik :
> D
I agree with you, Konstantin
вс, 28 окт. 2018 г. в 13:36, Konstantin Shegunov :
>
>
> On Sun, Oct 28, 2018 at 10:43 AM Martin Smith wrote:
>
>> >Oh, it is going to end in A resolution, it may not end the way the
>> offended party
>> >may feel just, but that's true also for the proposed text.
>>
Hello, Tomasz! :)
Thank you for the question!
Current draft based on CoC:
> Our Pledge
> ==
> In the interest of fostering an open and welcoming environment, we
> as contributors to and maintainers of the Qt Project pledge to make
> participation in our project and our community a
t those of us empowered, under a CoC, to
> resolve cases of abuse, would suddenly lose their ability to resolve abuse
> problems and would instead use the CoC to abuse alleged abusers.
>
> That's what it looks like to me.
>
> ____
> From: Alexe
I agree not interacting is probably not a solution and your contribution
without other details is not an excuse.
But I think existing CoC have problems.
There are statements everywhere about discrimination protection for example
which are very controversial.
The problem with that in other
thers.
I agree about reusing some working CoC is good idea. Not sure that there's
one yet.
сб, 27 окт. 2018 г. в 0:35, Thiago Macieira :
> On Friday, 26 October 2018 12:28:42 PDT Alexey Andreyev wrote:
> > > I personally think those situations explain why we need a CoC in the
> I personally think those situations explain why we need a CoC in the
first place and why the judgment on such situations is very subjective,
best left to humans, not to a script. And the deliberations should not be
in a public forum, like a GitHub issue.
If mentioned situations best left to
Hello! :)
The CoC is a lie. From my point of view, some of the current intentions at
least.
I'm hesitating a bit, that I'm so loud. I'm doing this to prevent problems
at the community, trying to find bottlenecks and provide better solution
for us.
> The rest should be in the CoC text itself and
there's any chances to minimize conflicts
more with CoC? Where is professional scientific research that Qt community
or Linux or KDE is slowly dying without CoC? I'm afraid that research could
probably show the opposite.
чт, 25 окт. 2018 г. в 20:48, Alexey Andreyev :
> > Don't define it bec
> Don't define it because you already know what it is. Just explain the
complaint process and create the committee to deal with each complaint on a
case by case basis.
It could make sense, but then we should made a plan how the committee could
work and how many resources could it take.
Should it
ld Trump, we all know what is bad behavior in this context.
>
> ____
> From: Alexey Andreyev
> Sent: Thursday, October 25, 2018 3:56:18 PM
> To: Martin Smith
> Cc: Ulf Hermann; Qt development mailing list
> Subject: Re: [Development
> I suspect that most if not all of the commenters here who object to the
CoC object to the attempt to define unacceptable behavior. It really has to
be decided on a case by case basis, so remove the examples of unacceptable
behavior, and don't attempt to define it at all.
I'm okay to develop the
I guess NIkolai point was not about the trust and some personal details.
I guess everyone could agree that conflicts are possible.
The question was is proposed CoC helping to solve them, or is it making
things worse? Are there any objective metrics?
P.S.: as I said, I personally not against any
Hello! Young Qt fanboy, who worried about the future of the project:
What problems are CoC trying to solve?
Abusive behaviour?
People are not social angels at all.
But how many situations of problematic behaviour at the Qt project do
we have with current terms?
When it's ruined some tasks we
may have
> with regards to implementing a Controls 2 style, but I don’t think I can
> put aside enough time to be a mentor for this.
>
>
>
> Cheers.
>
>
>
> *From:* Alexey Andreyev [mailto:yetanotherandre...@gmail.com]
> *Sent:* Tuesday, 3 April 2018 2:14 PM
> *To:
he controls don't end up in qtquickcontrols2, please at least
> consider putting them in qpm (https://www.qpm.io/) so that other people
> can benefit from them easily :)
> >
> > ---
> > Jean-Michaël Celerier
> > http://www.jcelerier.name
> >
> > On
y
> nice; a good candidate for “non-native” cross-platform apps.
> >
> > Universal - relevant in terms of Windows market share.
> >
> > As mentioned, I do think the Silica controls look nice, but that’s the
> only justification I could think of for including them in
> qt
Thank you Mitch for the feedback!
I've also tried to record current controls on a real device:
https://youtu.be/T-qUZMuTGqw (hope not only 360p will be available soon)
2018-03-23 21:55 GMT+03:00 Alexey Andreyev <yetanotherandre...@gmail.com>:
> Silica cheat sheet:
> https://sailf
enshots of it? I read that entire page and the Silica
> docs but couldn’t see anything.
>
>
>
> Cheers.
>
>
>
> *From:* Development [mailto:development-bounces+mitch.curtis=
> qt...@qt-project.org] *On Behalf Of *Alexey Andreyev
> *Sent:* Friday, 23 March 2018
Hello!
My name is Alexey, what do you think about Silica Style for QQC2 as a gsoc
project?
I have some notes here: http://aa13q.ru/qqc2-silica-style-en/
and want to create a proposal.
___
Development mailing list
Development@qt-project.org
28 matches
Mail list logo
