*** ChanServ sets mode: +v T4 | 02:04 | |
*** martyone_ is now known as martyone__ | 05:49 | |
*** martyone__ is now known as martyone_ | 05:49 | |
*** martyone_ is now known as martyone | 05:52 | |
T4 | <neochapay> i reopened bug | 06:18 |
---|---|---|
T4 | <neochapay> [Edit] i reopened mr | 06:18 |
*** ChanServ sets mode: +v T4 | 08:07 | |
T4 | <akaWolf> @neochapay do you want issue? For what? | 10:05 |
T4 | <akaWolf> I already have solution, what is for opening new issue? | 10:05 |
T4 | <akaWolf> We can discuss the same way in MR as it would be in issue | 10:05 |
T4 | <akaWolf> Don't understand why issue is needed in the case when solution is simple and ready | 10:05 |
coderus | There is a workflow everyone should follow. | 13:27 |
T4 | <akaWolf> we can change workflow if it doesnt satisfy our requirements | 13:30 |
T4 | <akaWolf> dont see any reason to spend time for nothing | 13:30 |
coderus | So, go away and come back when you'll be able to understand things | 13:33 |
T4 | <akaWolf> what should I understand? | 13:33 |
T4 | <akaWolf> explain me please :) | 13:33 |
T4 | <akaWolf> each part of workflow should have goal for minimizing time costs | 13:35 |
T4 | <akaWolf> quite simple | 13:35 |
T4 | <akaWolf> [Edit] each part of workflow should have a goal for minimizing time costs | 13:35 |
T4 | <locusf> @akaWolf [we can change workflow if it doesnt satisfy ou …], our has to mean you in this case | 13:35 |
T4 | <locusf> since you are astoundingly against our current way of working | 13:36 |
T4 | <locusf> these rules are the same for everyone | 13:36 |
T4 | <akaWolf> I'm not against rules, I'm against stupid following of the rules | 13:36 |
T4 | <akaWolf> when it make sense, we should follow workflow | 13:37 |
T4 | <akaWolf> when in does not — why should we spend time? | 13:37 |
T4 | <akaWolf> I'm just not understand why creating issue is needed in my case | 13:37 |
T4 | <locusf> communication | 13:38 |
T4 | <akaWolf> we can communicate the same way in MR/PR | 13:38 |
T4 | <locusf> what do you want to solve here, why did you solve it this way | 13:38 |
T4 | <akaWolf> even more productive | 13:38 |
T4 | <akaWolf> since you are already see solution | 13:39 |
T4 | <akaWolf> when I dont know how to solve the task it make sense to create issue and discuss the proper way | 13:39 |
T4 | <akaWolf> when the solution is evident dont see any reason to create issue | 13:40 |
T4 | <faenil> An issue is an issue. An MR is not necessarily because of an issue. Having issues separated helps track the issues that have been found/investigated/fixed | 13:40 |
DylanVanAssche | akaWolf: Issues are used to keep track of what everyone is doing. You avoid this way that 2 people create a PR for the same problem. Even if the solution is so straight forward, an issue makes it easy to keep track which PR fixes a certain issue | 13:41 |
T4 | <faenil> +1 | 13:41 |
T4 | <akaWolf> why we can't use PR for that goal? | 13:41 |
T4 | <neochapay> In issue you say what the problem and why you think it's problem how you get it and etc | 13:42 |
DylanVanAssche | neochapay: +1 | 13:42 |
T4 | <neochapay> In mr you say how you whant resolve problem and in mr we talk about resolve not about problem | 13:42 |
T4 | <akaWolf> okay, so for fixing a bug when the package does not even compile it's necessary to create issue, right? | 13:42 |
T4 | <neochapay> One problem may have different resolves | 13:43 |
T4 | <akaWolf> for fixing one letter does it still necessary? | 13:43 |
DylanVanAssche | akaWolf: Yes, by using an issue we can see the problem you solved. If later something similar occurs, we can look it up in the issues in an easy way. | 13:43 |
T4 | <faenil> akaWolf: I am with you that we should spend time in the most efficient way, but I think we should avoid spending that time discussing problems that do no exist :) you're not spending most of your time creating issues, so I think the time we are spending discussing here would be more efficiently spent creating and fixing issues :) | 13:43 |
T4 | <faenil> do not* exist | 13:44 |
T4 | <akaWolf> discussing help to create an efficient workflow and save much more time in the future in the case of success | 13:44 |
T4 | <faenil> Then when it actually turns out to be a waste of your time, you can start a discussion and bring proof | 13:45 |
T4 | <akaWolf> [Edit] discussing helps to create an efficient workflow and save much more time in the future in the case of success | 13:45 |
T4 | <faenil> This project is not a newborn. So I'd find more appropriate discussing when problems arise, not just for the sake of discussing :) | 13:45 |
T4 | <faenil> Are you with me on that? | 13:46 |
T4 | <akaWolf> yep | 13:46 |
T4 | <faenil> Great :) | 13:46 |
T4 | <locusf> thanks @faenil :) you're much more diplomatic than me about this :) | 13:47 |
T4 | <faenil> Haha. Anytime | 13:47 |
T4 | <neochapay> (Sticker, 512x512) http://149.202.119.142:9090/A5n50JtNvO.png | 13:48 |
*** ChanServ sets mode: +v T4 | 14:22 | |
*** eekkelund_ is now known as eekkelund | 16:59 | |
*** ChanServ sets mode: +v T4 | 20:11 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!