> Please avoid singling out individuals
How can I not refer to you after you're the one locking the threads? Am I
not allowed to point out you have personally and systematically misused
your power as an administrator?
> progress has been made by @jasp00 and myself
Seems to me like you are personally closing the issue you're not interested
in and allowing the one you're personally involved in to keep going. Maybe
you can do that but then don't lock and close other issues claiming "ad
hominen" accusations, making it about yourself and not about technical
issues. Be transparent (if that's indeed the case)
> #3558 thread is not locked, but rather closed. Simon or any other
interested parties will have access to answer his/her progress there if
he/she chooses to do so.
Are you literally telling me that we should continue to work on a cosed
issue? That's completely devoid of any logic.
> The decision to lock #2556 was done after several warnings.
Warnings that I did my best to heed and respect and which were baseless
since I never attacked you personally. I'll add the link here again so
anyone interested can verify for themselves if my last comment was
personally offensive at all to merit a thread being shutdown
https://github.com/LMMS/lmms/issues/2556#issuecomment-301805379
I am more than willing to accept an apology from you to make things right.
On 16 May 2017 at 15:04, Tres Finocchiaro <tres.finocchi...@gmail.com>
wrote:
> > I don't know who Tres is and frankly, I don't even care or want to know.
>
>
> Please avoid singling out individuals as it can quickly become toxic.
> This is the third request to avoid ad hominem style responses.
>
> > (@tukkek) and Simon (@probonopd), who were the only users there making
>> progress towards resolving the issue
>
>
> On the contrary, progress has been made by @jasp00 and myself
> towards #2932, which has redundancies with the AppImage effort. This was
> explained in #2556.
>
> > opened [#3558] and pinged Simon to try and continue to work on a pull
>> request
>
>
> #3558 thread is not locked, but rather closed. Simon or any other
> interested parties will have access to answer his/her progress there if
> he/she chooses to do so. The open status of #3558 is redundant with
> #2556 so it will remain closed unless the tasks are split.
>
> The decision to lock #2556 was done after several warnings.
>
> Best regards,
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
