> On 26 Mar 2019, at 18:52, Esteban Lorenzano <[email protected]> wrote:
>
> Hi,
>
> I am sorry you feel frustrated but this is an important change that is going
> on and we need to tackle it, not revert it.
> Yes, probably last two weeks there has not been much movement, but reason is
> we are working on make PharoDays possible.
>
> Now, as Stef said… Pharo 8 is alpha.
> I will add VERY alpha.
> Each release has some moments where there is something severely broken. From
> my part I’m happy that this happens now and now (as usual) in august when we
> are preparing for release :)
And NOT (as usual)… etc. (errare humanum est :P)
>
> Please, do a step back and and rephrase your mail. You are the advocate of
> non-violent communication. I’m afraid do tell you that the tone of the mail
> was very violent.
>
> In the positive lecture of things: yes, we are having problems with rubric.
> But once we fix it, you will be happier with it, I’m sure :)
>
> Esteban
>
>> On 26 Mar 2019, at 18:39, Stephan Eggermont <[email protected]> wrote:
>>
>> ducasse <[email protected]> wrote:
>>> Hi stephan
>>>
>>>> Unless someone is working on fixing it today, I want this PR reverted.
>>>> Issues 2865, 2963, 2964, 2980, 3013
>>>>
>>>> Stephan
>>>
>>> Nobody is working on Pharo this is well known.
>>
>> I am feeling angry and ignored. I am trying to contribute and am frustrated
>> in doing so. I am asked to go through fogbugz and make sure that important
>> issues are reopened on github. I do so and get comments that bugs don’t
>> solve themselves, on the one where I notice that Rubric is not ready. I
>> find and fix important other bugs and try to integrate them and notice that
>> a lot of things don’t work as they should. CI has been systematically red.
>> The first thing I notice is that an in-image test is red, with a trivial to
>> fix issue. Then I run into all kinds of other problems with Rubric not
>> implementing something. And I’m not the only one, looking at the issue
>> tracker. So I look back trough github and see no signs of improvements in
>> the past 14 days. I collected the relevant issues and reached out on github
>> and discord first, without getting a useful reaction. This is not the
>> development process we are using, as I understand it.
>>
>> Please revert the PR. I have been working on FFI, Taskbar and CI bugs and I
>> want to be able to commit, integrate PRs and make Pharo better. Pharo is
>> mine.
>>
>>>
>>> Sorry but I did not like the ton of your email, especially because there
>>> are
>>> lot of information that you do not know.
>>
>> I’m up to date with the github commits, issues and PRs, Discord and the
>> mailing lists. If you feel contributors need more information, please make
>> sure we get it
>>
>>> Now if you want to help, add the issue to the projects so that I can work
>>> on them with Alain
>>> and others. Else I will do it.
>>
>> Projects don’t work yet.
>>
>> If you want time to focus on Rubric only and don’t want other contributions
>> to Pharo 8 at the moment, then please announce so. Or use a branch. Don’t
>> integrate a PR that breaks CI and then don’t fix the issues for two weeks.
>>
>> Stephan
>>
>>
>>
>>
>>
>
