| Time |
Nick |
Message |
| 01:06 |
|
m42uko_ joined #minetest-dev |
| 02:29 |
|
pmp-p joined #minetest-dev |
| 03:33 |
|
proller joined #minetest-dev |
| 03:38 |
|
Noisytoot joined #minetest-dev |
| 05:00 |
|
MTDiscord joined #minetest-dev |
| 06:52 |
|
Noisytoot joined #minetest-dev |
| 08:25 |
MTDiscord |
<Andrey01> Will #13020 and #12828 be ever reviewed? |
| 08:25 |
pgimeno |
https://github.com/minetest/minetest/pull/13020 -- 3d line rendering. by Andrey2470T |
| 08:25 |
pgimeno |
https://github.com/minetest/minetest/pull/12828 -- Add vector variation for ContentFeatures 'visual_scale' property. by Andrey2470T |
| 08:52 |
|
calcul0n joined #minetest-dev |
| 09:01 |
|
YuGiOhJCJ joined #minetest-dev |
| 09:22 |
|
Warr1024 joined #minetest-dev |
| 09:44 |
|
m42uko joined #minetest-dev |
| 11:06 |
Zughy[m] |
Kinda hard to say, development has slowed down again, both with sfan stating they've got less time for Minetest and with the tragic passing away of TurkeyMcMac |
| 11:18 |
MTDiscord |
<Andrey01> oh, that's sad |
| 14:22 |
MTDiscord |
<MisterE> Andrey, very likely they will be eventually, if you keep it updated. It might take a very long time, but its worth it. |
| 16:33 |
|
fluxionary joined #minetest-dev |
| 16:47 |
|
pmp-p_ joined #minetest-dev |
| 16:56 |
|
pmp-p joined #minetest-dev |
| 17:46 |
|
pmp-p joined #minetest-dev |
| 17:50 |
|
pmp-p joined #minetest-dev |
| 19:24 |
|
proller joined #minetest-dev |
| 19:41 |
Krock |
> Team Discussions will be deprecated on May 8th, 2023. |
| 19:44 |
Krock |
looks like meeting announcements will happen elsewhere in the future |
| 19:54 |
Zughy[m] |
if MT used some up-to-date technology like Matrix, it'd be easy to have a private channel just for meetings where staff members can react to the meeting message (let alone the other benefits of not developing on an obsolete technology, such as reachability) |
| 19:55 |
Zughy[m] |
why are we still on IRC exactly? I don't remember |
| 20:15 |
|
Baytuch_2 joined #minetest-dev |
| 20:46 |
caffblks |
What are the requirements to join the core dev team? |
| 20:49 |
HuguesRoss |
Permission, mostly |
| 20:50 |
HuguesRoss |
You need to ask c55, and have...iirc, 2? existing coredevs who are willing to vouch for you? Something like that? |
| 20:50 |
HuguesRoss |
Best way to that, of course, is by contributing to the project |
| 20:51 |
Krock |
I don't think there's any requirements mentioned anywhere. You can apply and try your luck. It's often discussed in team meetings |
| 20:53 |
Krock |
correction: there are in fact some requirements mentioned here: https://dev.minetest.net/Organisation#Assignment |
| 21:31 |
rubenwardy |
caffblks: you need to contribute to the Minetest engine.first and gain trust |
| 21:34 |
caffblks |
Yes, I asked c55 and got the run down. |
| 21:36 |
caffblks |
The problem is that I don't have much c++ experience despite proficiency in many other areas. |
| 21:38 |
Zughy[m] |
#13107 can be merged actually, the approval is from another core dev |
| 21:38 |
pgimeno |
https://github.com/minetest/minetest/issues/13107 -- Colorfacedir and Nodeboxes |
| 21:38 |
Zughy[m] |
sorry, #13017 |
| 21:38 |
pgimeno |
https://github.com/minetest/minetest/pull/13017 -- Implement `minetest.get_node` and `minetest.get_node_or_nil` with LuaJIT FFI by TurkeyMcMac |
| 21:49 |
Krock |
I've seen it multiple times but I am not convinced that the additional code (and hence maintenance) justifies the performance gain that is yet to be measured |
| 21:49 |
Krock |
(there is a benchmark, but that's a torture test and not very applicable to mods) |
| 22:10 |
|
vampirefrog joined #minetest-dev |
| 22:13 |
MTDiscord |
<GreenXenith> #13189 is simple and waiting for 1 more approval ;] |
| 22:13 |
pgimeno |
https://github.com/minetest/minetest/pull/13189 -- Add chat HUD flag by GreenXenith |
| 22:21 |
|
Pexin joined #minetest-dev |
| 23:06 |
caffblks |
I'm working on building a tool to monitor CPU/memory usage. Not sure if anyone has done the same? |
| 23:10 |
caffblks |
I think I've discovered a leak in Mesecons. Difficult to really say, though. All evidence is currently anecdotal. What concerns me is that though mesecons is purported to be sandboxed, others have said that only applies to e.g. the luacontroller component. Otherwise, with simple things, like blinky plants, pistons, lights, etc., seems not to be. I guess what I'm wondering is why the engine doesn't shut down / throttle mods that might |
| 23:10 |
caffblks |
crash the server. How difficult would this be to implement in the engine? |
| 23:21 |
caffblks |
And, also, are there any issues that would be beginner-friendly that maybe others don't want to bother with at this time? |
| 23:23 |
caffblks |
I see there are 1,016 open issues. Where would my attention be best focused with an entry-level c++ skillset? |
| 23:50 |
wsor |
krock: please read https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/ - just need to move it |
