Discussion incident removal blockpalettes
#2
I think removing a tigerw as a member from the repo is really harsh, but I agree with xoft that this shouldn't have been committed directly to master. If possible I'd like to make it impossible for anyone, even adminsitrators of the repo, to directly push to master.

EDIT:
To clarify, I don't think the code shouldn't have been committed directly because it was bad (I haven't really looked at the code yet) but because it prevents a process where the code could be reviewed. The overal architecture has been discussed in detail, and to just throw things away without informing the others is simply not-done.
Reply
Thanks given by:


Messages In This Thread
RE: Discussion incident removal blockpalettes - by NiLSPACE - 09-10-2020, 08:54 PM



Users browsing this thread: 8 Guest(s)