Leaderboard

@Bmon I'll try and address what I perceive to be the presented concerns: Lack of Transparency / Communication on the Git Hidden Dev Channels Slipping back into past bad practicies I'll give my 2 cents on this as someone who has served in most roles on the Dev team (excluding -headcoder & -balance team) as well as general staff leadership. This has little to do with the development team's commitment to being open and honest and everything to do with time and energy. Lack of Transparency / Communication Back in January/December, contributors were opening PRs at around 10-15 PRs A DAY, we had 2 active headcoders, 2 review team members, and 2 commit access members all with varying availability (some with almost none), it was impossible to keep up with the rate of these PRs and also provide the kind of communication you want, this rate of PRs decreased into the second semester of schooling for most of us but did not largely stop until late February; Furthermore, most people on the design team (such as myself) also serve in other roles and have to balance responsibilities. It is exhausting to keep up with it and I'm not always going to sacrifice 15 minutes of my day sometimes to leave reasoning behind a PR objection every time I have one (especially if I'm leaving 3-4 a week). It's not because I don't want to be transparent it's because I'm doing other important things like a) talking to my girlfriend b) doing my homework c) dealing with a dumpster fire in staffcoord as a HOS or d) simply doing code reviews / merges to get our PR count down. Making our dev-channel public will not fix this and will make it worse, it wont make me be more transparent, I will be less transparent and here's why: Hidden Dev Channels Players and contributors will likely never truly understand the perspective/experience/needs of the development team or staff team until they serve on them or a similar team. This isn't a jab at our contributors' empathy or behavior, it's just a simply a matter of having that collection of micro-experiences that changes the lens in which you look at things. The single hidden dev channel we have on the public discord is the only channel that is exclusive to development team members (it even excludes most GA's) minus a single headcoder-leadership channel we have on the staff discord. Why is this important? The obvious points have been covered, exploit discussion and GitHub disciplinary action discussion. Here's what's not necessarily been talked about I need a space where I can talk freely and privately with dev people I trust 100% It shields certain dev/staff politics from public view, all of us do not agree on everything and it can get to the point where we have fights behind closed doors. I do not want contributors or any player for that matter to be privy to what is said or to take it as an opportunity to butt in on a conversation they do not have a share in. Sometimes things that are said that are not necessarily true in the heat of the moment and has to be approached very cautiously and tenderly. This may even be the reason why certain controversial objections are not written out thoroughly, its a difficult choice for multiple dev team members to be openly in contradiction with each other on a PR because it reflects poorly on our collective vision and its invites all of us to participate in a potentially energy-draining drawn-out discussion, so we often work it out in this channel. Privacy is important to everyone, it's hard enough to find people who will invest the amount of time they do in our development team + are nearly completely in-line with leadership + we're able to work with them. I realize that we can look as if we're slipping back into bad past practices and its certainly always a concern that is on the back of my mind, I'm glad you bring this up because its always an important topic to revisit. I certainly don't think you have any bad intentions in mind either. More communication could always be better and our dev team needs to work on coming together to establish a central design vision. At this moment, most of our dev team is in the busiest moments of their year (school, works, life, etc) and have to balance it all with their responsibilites in a volunteer organization (i.g. paradise). We're going to be committed to being better about justifying objections in the future, however.

Yeah, this conversation is clearly going nowhere. Every point you make has a valid counterpoint but you don't even stop to consider it. Mira took time out of her day to provide us with a large-enough sample size for 2 months of data, and you do nothing but complain about it and provide strawman arguments while slinging vague accusations. Your PRs got closed, it sucks, but that doesn't mean everyone is out to get you and are silently plotting to smother your ideas. Could communication have been better? Yes, I think this has been established. You started a very reasonable discussion and pointed out, rightly, that there is always room for improvement. Don't ruin it and leave a sour taste in everyone's mouth by arguing for the sake of it. I am personally done with this thread because of your attitude. Let the cogs turn and the improvements that follow from this be set in motion.

Are there some players that think that armed and equipped cultists aren't armed and dangerous under Space Law? Seeing as the basic piece of equipment for a cultist is a magic stabby-boi even before they get extra stuff, this is a pretty strange take - especially when Space Law explicitly specifies flag-robed cultists as KOS-able: For all the ways cult balance could be improved, this isn't one. It's a very, very rare situation where sec aren't already covered to KOS cultists. KOS under Space Law != valid for most crew. If the argument is that cult should become valid earlier, then that holds more water.

Even thought the idea of doing is interesting I do not see why it would make sense lore wise as constructs are very different from machines and suchs so it would need a extra step to be able to do so to make it lore wise sense and we do not redcon the world by accident.

I took 15 minutes to look at some data just to ensure we are not holding this discussion based on emotions and I-feel-likes, because this topic is leading to nowhere. Since 12 January, 300 PRs were handled of which 40 got closed. At maximum, 11 of those got rejected visibly on GitHub, of which 4 did not get a written reply as to why. This is a solid 100 PR / month with a little over 1 getting rejected without an explanation on GitHub (not counting the possible discussion between the PR opener and the maintainers on Discord). PR closed/abandoned by their author for personal/technical reasons or they made an alternative PR (28): https://github.com/ParadiseSS13/Paradise/pull/20417 https://github.com/ParadiseSS13/Paradise/pull/20400 https://github.com/ParadiseSS13/Paradise/pull/20378 https://github.com/ParadiseSS13/Paradise/pull/20377 https://github.com/ParadiseSS13/Paradise/pull/20374 https://github.com/ParadiseSS13/Paradise/pull/20373 https://github.com/ParadiseSS13/Paradise/pull/20365 https://github.com/ParadiseSS13/Paradise/pull/20364 https://github.com/ParadiseSS13/Paradise/pull/20358 https://github.com/ParadiseSS13/Paradise/pull/20355 https://github.com/ParadiseSS13/Paradise/pull/20338 https://github.com/ParadiseSS13/Paradise/pull/20318 https://github.com/ParadiseSS13/Paradise/pull/20317 https://github.com/ParadiseSS13/Paradise/pull/20316 https://github.com/ParadiseSS13/Paradise/pull/20296 https://github.com/ParadiseSS13/Paradise/pull/20292 https://github.com/ParadiseSS13/Paradise/pull/20647 https://github.com/ParadiseSS13/Paradise/pull/20633 https://github.com/ParadiseSS13/Paradise/pull/20624 https://github.com/ParadiseSS13/Paradise/pull/20557 https://github.com/ParadiseSS13/Paradise/pull/20555 https://github.com/ParadiseSS13/Paradise/pull/20510 https://github.com/ParadiseSS13/Paradise/pull/20475 https://github.com/ParadiseSS13/Paradise/pull/20446 https://github.com/ParadiseSS13/Paradise/pull/20269 https://github.com/ParadiseSS13/Paradise/pull/20212 https://github.com/ParadiseSS13/Paradise/pull/20210 https://github.com/ParadiseSS13/Paradise/pull/20186 PR closed by maintainers stating the reason on the PR (5): https://github.com/ParadiseSS13/Paradise/pull/20406 https://github.com/ParadiseSS13/Paradise/pull/20357 https://github.com/ParadiseSS13/Paradise/pull/20272 https://github.com/ParadiseSS13/Paradise/pull/20235 https://github.com/ParadiseSS13/Paradise/pull/20202 PR closed by maintainers without stating a reason on the PR (4): https://github.com/ParadiseSS13/Paradise/pull/20396 https://github.com/ParadiseSS13/Paradise/pull/20386 https://github.com/ParadiseSS13/Paradise/pull/20382 https://github.com/ParadiseSS13/Paradise/pull/20205 Either dev objection on Discord or personal, could not decide (1): https://github.com/ParadiseSS13/Paradise/pull/20370 Dev objection on Discord, not stated on the PR (2): https://github.com/ParadiseSS13/Paradise/pull/20509 https://github.com/ParadiseSS13/Paradise/pull/20178

Me and Marm relishing in our crate organization skills.

Jack Rheiner the seccie

The idea behind this, came when turbine was used to heat the plasma for the hot loop, but cause it went through space, it got very cooled, so the next round, we walled it up. Now a funny quirk we noticed is that the hot loop output has really cold gas, which was used for the cold loop, making the hot loop cool the cold loop, and as you can see, it peaked at 40million watts, even if the hot loop for SOME reason was not even hot enough to boil water, a warm drink would be considered lukewarm at best at that temp.

Atez breaking lyrics of country road before suddenly producing an armblade and killing the poor second vocalist south of him. Truly inspiring performance. Never enough plasmeme Back and forth she went, plagued by the admemery to the side Insert Skyrim joke here

Reserved- Cult Balance