Last day of the month, and I finally got my PR done. Sorry I’m so late!

@dindu-nuffin

…you used http://contributor-covenant.org , a site that has been used and pushed by insane SJWs.

Yup, I’ve seen this too often. The Node community, the Ruby community… yeah. There’s a little more to it than that, though.

Since the maintainers put the second line in the code of conduct…

You’re referring to the following, right?

Part of this problem lies with the very structure of some projects: the use of insensitive language, thoughtless use of pronouns, assumptions of gender, and even sexualized or culturally insensitive names.

While I agree with the sentiment you got from that paragraph, it’s not actually in our version of the CoC - and I don’t think it’s in the “official” version explicitly. You can check here for the latest version of what we’re using.

Use welcoming and inclusive language. - that can be anyone’s opinion.

Subjective, yes, to a point. I think that may be intentional, though - not just to target the perspective of the “victim”, but also to make it easier to apply to the situation of each individual project. I think a lot of this comes down to enforcement - and yes, I have seen projects pressured into over-enforcing this clause.

That said, that’s specifically listed as an example of behavior that contributes to creating a positive environment - deliberately subjective because, in my opinion, it makes people think of the best things that they could say in the situation, rather than some idea of what we require from them.

Be respectful of differing viewpoints and experiences. - again totally subjective

I wouldn’t say this is subjective. A lot of people assume this means that you can’t challenge viewpoints or discuss them, but there are ways to do that respectfully. For example, instead of being confrontational and proclaiming that xyz viewpoint is wrong, you could ask Why do you believe xyz? - and if you don’t agree with them, just say something along the lines of I disagree with you, but I respect your right to believe that.

That said, we aren’t really about general discussion. It’s going to pop up, as it does with every community, but we prefer to focus on discussion that’s specifically related to the project, so we don’t anticipate having to moderate situations like that very often.

Show empathy towards other community members. - Totally un-needed, and also is subjective.

Empathy is a little subjective, yeah, but it’s not hard to give empathy. If someone is in a bad situation, and you are involved in the conversation, you can simply say something along the lines of Yeah, that sucks or Sorry to hear that or something similar - or if not, you don’t have to engage at all. Up to you!

This code of conduct also doesn’t take into account how speech can mean one thing in one context, and completely another in a different. The code of conduct could be used to spin the speech and kick a member off the team.

Interesting point. See the next section.

---

I take a lot of these points as they come - I see them raised a lot, and some of them are issues that I have also had with this exact CoC. That said, I think a lot of this comes down to enforcement.

A CoC is only half of the story - If you have a project which has people with malicious intentions, people that are ignorant of problems with a CoC like this, or just people that don’t care about the community, things can go bad quickly because the CoC is so open-ended. Sometimes, politically-motivated people may try to pressure staff to achieve the outcome that they want - a great example of all of this is the infamous eggplant controversy in the Node community.

I just want to make sure that you (and everyone else) are aware that we know about these issues. We are not interested in censoring certain types of speech, and we’re not interested in pushing our political views on others. What we are interested in is keeping things productive and friendly, which will allow everyone involved to further the project.

---

Some other misc stuff that has come up in discussion:

• It’s worth noting that the current CoC is a draft, we haven’t put it in place yet. As I mentioned earlier, we realize that there are problems with the contributor covenant, and our version is pretty heavily modified. I linked it earlier - why not take a read?
• Are there any specific suggestions that you have? If you could help with drafting new language that still does not allow stuff like this issue while bettering the code of conduct in your view, please feel free to suggest improved language for our community rules.
• You may say that it is a choice to be offended, but sometimes things are so obviously out of line, like calling a maintainer stupid or flaming new contributors. That type of language isn’t helpful to our project. It wastes our time, and it also discourages new contributors.
• Like all laws, there can be some abuse from those who enforce those rules. It will be important to include some balances for those who enforce laws, most likely involving the community, just to provide some oversight for maintainers with their new responsibilities when this new code of conduct takes effect.
• @mastercoms said the enforcement starting date was the end of this month, but since you bring up some good points, we can accept releasing it later so we can get it right.

I hope that helps, and I hope it wasn’t too long. :P

I had similar concerns, to be honest. That said, I’m happy that @mastercoms has modified it enough and have grilled her about how it would be enforced and such.

If you have any actual questions about it, ask away - that’s what we’re here for. However, as a moderate myself, I can’t say that a code of conduct is inherently bad. We do need something to refer to on expected behavior, after all.

Sorry, I haven’t gotten around to it yet. I’m sure I’ll remember soon :v

I think this covers most of what we need. It doesn’t read very well, mostly due to punctuation and lack of Markdown formatting where appropriate - can I reformat it?

Interesting idea! Just to note that there’s an issue on your server - I connect, die immediately, and are stuck in a block. Wew! Also, I can’t seem to turn my view. Browser is Vivaldi.

Most of our organic traffic comes from GitHub, and not the site. That said, I would be fine with putting that info on there - it’s a question that comes up every so often.

EDIT: I have raised this on Discord.

---

Glowstone is a small project. We are “all hands on deck”, but “all hands” is two people at the moment. There are four people on the core team - @mastercoms as the project head and lead developer, me as a sysadmin and PR guy, @momothereal as a prolific contributor and talented developer, and @kamcio96, who is currently busy with other things.

---

As it stands, any “pure” bukkit, spigot or paperspigot plugin (which is to say, one that only uses the Bukkit/Spigot/PaperSpigot API and no internals) should be compatible at this point, barring the features we don’t have implemented yet. The plugins that don’t work are not strictly Bukkit plugins, and are instead have an intimate association with the server software they’re developed for.

Some developers have decided to add specific support for Glowstone, and others have decided to write plugins with Glowstone as their primary target, but we are a small project at the moment and we don’t have the infrastructure to maintain a big database of plugins - although that is coming.

We also have the Linkstone project, which attempts to add an emulation of the net.minecraft.server package, so that plugins which rely on it will be able to work with Glowstone - but that project is currently stalled as we do not have the manpower to dedicate to it right now. Perhaps you know someone or are a developer yourself?

---

EDIT: I’m going to bed now, but feel free to drop by the Discord if you feel so inclined.

Specific issues are best left to GitHub, but I can sum up the response nicely.

These things are simply not yet implemented. Glowstone is beta-level software at the moment, and it is not yet feature-complete.

This month, the team is working on AI and mobs, so hopefully those (and related things) will be working by May.

Wow, this is… pretty neat. I had a quick play with it, and I’m pretty impressed.

Small suggestion: How about the ability to disable editing the map in the config?

EDIT: It has been done. Woo!

Nothing wrong with providing an answer!

That’s pretty interesting. When did you test it? We’ve come a long way in a short time recently.