Re: Blog post "Introduction to the Apache(R) Ignite™ community structure"

[Dmitriy Pavlov <dp...@apache.org>]

Hi Ilya,

Thank you for the idea. Yes, probably I will re-post older blog on habr/en,
but, anyway, we've finished a new one:
https://habr.com/ru/company/sberbank/blog/444264/  it is now in Russian,
but I hope someday I will translate it to English and post it there.

Sincerely,
Dmitriy Pavlov

ср, 27 мар. 2019 г. в 18:17, Ilya Kasnacheev <il...@gmail.com>:

> Hello!
>
> There's an English version of Habr now, did you consider reposting there?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 21 мар. 2019 г. в 15:35, Dmitriy Pavlov <dp...@apache.org>:
>
>> Sorry for the late reply. Contributors are not ranked so weight is not
>> measured. The community always prefer to build consensus. If consensus is
>> not reached (this happens time-to-time), then feature or change should not
>> appear in the product.
>>
>> By the way, Apache PMCs may veto changes with a technical justification
>> explaining why change is bad.
>>
>> A final word in project development has PMC (it is a committee consisting
>> of all its members). Practically Apache Ignite Community prefers wider
>> consensus - from all contributors.
>>
>> In case something is going wrong, there is our last resort:
>> https://www.apache.org/board/escalation  But I don't remember any
>> escalations.
>>
>> Priority of implementing features is solved in another way: if someone
>> wants to implement something and the community does not reject it, so why
>> not? There is no single priority for all contributors.
>>
>> ср, 17 окт. 2018 г. в 12:09, zaleslaw <za...@gmail.com>:
>>
>>> [For discussion] It's interesting to know more about possible conflicts:
>>> when
>>> a few persons are involved in contribution as a commiters, for example,
>>> and
>>> they have different opinions about next steps in roadmap implementation
>>> or
>>> about certain feature. How to measure correctly their weights? One of
>>> them
>>> doing small bug fixes, another does large features. They are not ranked,
>>> except amount of commits or code lines in github. Who can say last word?
>>>
>>> Imagine, only they are both understand something in this feature and its
>>> priority. Votes couldn't help, right? How they should solve their
>>> conflict?
>>> Does you have any cases in your experience?
>>>
>>>
>>>
>>> --
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>
>>