If you need support, go to the forums. If you want to help make Support awesome, stay here.
If your comment is for support, it will be deleted. If it looks like spam, it will be deleted. Sorry, but there’s no other way to keep up with things.
Great article about the benefits that active support forums/channels bring to on-line communities:
Originally shared by @fabianapsimoes.
Due to the Thanksgiving holiday in the United States the #wordpress-sfd meetup for November 28th will be unstructured but not canceled.
What that means is please meetup if you want but be aware that participation from the U.S. will be limited and possibly nonexistent.
I will review the IRC log from the meetup on Friday and will provide an update for the Support portion if there is any. If there are any support topics please feel free to discuss them and we can follow up next week.
During todays support and docs chat on IRC we introduced a few new faces on the access lists of the WordPress channels there to help moderate and control the behavior of the users, much like you would on the forums.
As IRC does not work with a bozo list like the forums do, we have a few alternatives available for use in such situations as outlined below. This means we can not mark users for moderation, nor preview what they are trying to say before it is said, it’s all live, and it’s all public.
We want to maintain as much transparency as we can, this is a public medium and we keep public logs of most actions (at the moment the logging devices can not log kick/ban messages), but at the same time protecting the one performing the action from any negative retaliations which may or may not occur after action is taken.
We have three (four) ways of dealing with users who are having a bad day beyond just speaking to them and informing them that their behavior is unacceptable/a bit too much and asking them to calm down or get some fresh air;
Muting (or “Quieting”) a user (/mode #channel +q Nickname) requires you already have the Operator status, or can be done through network services (/msg ChanServ quite #channel Nickname) but keeps the user in the channel, he is merely silenced and can not speak in public, this is also what hlin does automatically if someone spams.
A kick can be done either by being an Operator (/kick #channel Nickname ) or anonymously through the services of the network (/msg ChanServ kick #channel Nickname ). A kicked user is removed from the room temporarily, but may return at any point.
A ban, like a kick, can be done as an Operator (/mode #channel +b Nickname) or through network services (/msg ChanServ ban #channel Nickname ). Worth noting is that using services will also kick the user, if not you will have to manually kick the user after banning them. A ban will not by default expire unless you physically remove it.
Now that we are familiar with the ways one can deal with a user, a general guideline for when to use the various actions will most definitely be needed. This will be handy both for the users of the channel to know when a moderator should step in so they can be pinged, but also so the moderators know what action should be taken when to ensure a fair ruling.
Feedback will most definitely be required here to iron these out, but I’ve taken the liberty to provide the following suggestions to get the ball rolling;
There are many other situations of course, but these are the ones you’ll most likely meet, not only in spoken words, but also as nicknames or messages sent to the channel when leaving it (a part message).
There was also mention of a way to log (beyond IRC logs) offenders to keep tabs on what is going on as everyone might not be on at the same time etc. Thoughts on how this could be achieved in a fair manner are appreciated as we don’t want to make any public shame list at all, we only want to make IRC a welcoming place for anyone to drop by and learn a thing or two during their stay. Possibly a list restricted to moderators on g-docs or similar is an idea?
Another thing that might come up is how to deal with disputes if a user is banned and feels it was unjust. Is there a place we’d prefer them to take their appeal, and if so, where and how?
That means we need to decide on the level of transparency we wish to have, do we wish to have full transparency with users issuing the actions, or anonymize it through network services.
@sams suggested that for transparency when issuing a kick/ban we should state why in the channel after the ban since the logger does not pick up kicks/bans and only shows peoples reactions to them, would this be an acceptable approach and how would we deal with that if services are used to act?
Oh and before I forget, the fourth reasoning mentioned is only if a user should retaliate, this is much like a DDoS on a website, and extremely rare to occur, and even rarer to have any impact as most networks have security to prevent or mitigate such things. Should a disgruntled user retaliate with proxy bots or any other kind of bots that cause spam and disruptions, and it’s to such an extent that a moderator can not deal with it, drop by the kind people in the FreeNode support channel and mention that there’s a botnet and they’ll take care of it. Not that vital as it’s extremely unlikely to ever occur, but good to know just in case.
A closing thought, as it was mentioned that not everyone may be too familiar with the workings of IRC or remember commands and such, I did mention a few of the commands with quick defaults in the post, but is this something that you would prefer a more extensive outlining of made available in some form or other?
All right ladies and gentlemen, the floor is open
A few days ago some behavior on the IRC #wordpress channel was brought to Siobhan McKeown’s attention. Take a moment and visit her post on that topic. After that visit Lindsey Kuper’s post on her experience in the #rust channel.
Please do not use language based on someone’s looks or gender. It’s wrong and can’t be tolerated.
I had some difficulty expressing this in IRC but thankfully Siobhan and Mika provided me with support and they explained it well. The reason for my difficulty was simple: this is important, this problem needs to be stamped out early and I wanted to get this right.
When someone joins the #wordpress channel or posts to the support forums it is important to remember that they are either seeking help or attempting to help others. This is a good thing and that participation makes WordPress successful.
It’s not easy for everyone to join or start a public conversation. A forum post or joining an IRC channel is exposing yourself and that’s a risk. For some that can become a painful experience.
When someone replies using language that diminishes, makes people feel uncomfortable or disparages others then that participation is lost.
If the tone of the conversation includes words that focus on people’s looks or gender then that’s it. The person who wanted to join doesn’t feel welcome. That phrase about first impressions is true and an opportunity is gone. People stop participating or they never take the chance and do not even start to contribute.
At that point it’s the WordPress community that loses out.
Unlike the forums IRC is a live medium. There’s no moderation or editing and it’s easy to say something off the cuff. Everyone has bad days and may say things that they regret. And we all have a sense of humor that can be crass sometimes.
But using language based on gender or looks is not tolerable and has to stop. It’s not enough to be aware of this behavior. What will make it stop is when everyone speaks up if they see that.
“That language is not welcome here. Please stop.”
That’s it. That’s all it takes.
That reply alone raises the expectations for the whole community. That’s not a confrontation, that’s an invitation for others to join a community that does welcome everyone.
Let’s all raise those expectations. Speak up. You’ll be encouraging other people to do the same.
Normally I do an OMGWTFBBQ post. Here’s everything in my current draft, ready for editing by everyone!
The first section is ‘Stuff we, as mods, should be aware of.’ The second is the post itself
* How to disable
* In order for Automatic Updates to be enabled, there are a few simple requirements:
* If the install uses FTP for updates (and prompts for credentials), automatic updates are disabled
* If the install is running as a SVN or GIT checkout, automatic updates are disabled
* If the constants DISALLOW_FILE_MODS or AUTOMATIC_UPDATER_DISABLED are defined, automatic updates are disabled
* If the constant WP_AUTO_UPDATE_CORE is defined as false, automatic updates are disabled
* Your WordPress install also needs to be able to contact WordPress.org over HTTPS connections, so your PHP install also needs OpenSSL installed and working
* Wp-Cron needs to be operational, if for some reason cron fails to work for your install, Automatic Updates will also be unavailable
* What gets updated?
* What changed. ONLY changed files!
* Only for minor releases (3.7 to 3.7.1 but NOT 3.7.1 to 3.8)
Less Major Changes
Under the Hood
For the post…. (More …)
My internship period is now over and I just wanted to take this chance to say a big thank you to everyone who supported me throughout. Special thanks go to my mentors @hanni and @ipstenu for their help and guidance, and to @jenmylo for organising WordPress’ involvement with GNOME’s OPW.
I was looking forward to meeting a few more of you in person at WordCamp Europe, however, unfortunately, due to personal circumstances, I will no longer be attending this weekend.
Getting more involved in the WordPress community has been wonderful, and I hope to continue contributing back to the community far beyond this internship. If you are, or if you know of a, woman interested in becoming more involved in open-source communities, please do consider the GNOME Outreach Program for Women: http://gnome.org/opw/. They are now accepting applicants for their next round, starting December 10th. Feel free to contact me if you want any more information on the application process.
Thank you again.
Hey all. Not long left of my internship now. Just a really, really quick update this week. I’ll mainly be spending my last two weeks helping @sabreuse with Troubleshooting documents. The outline for these can be found here: http://make.wordpress.org/community/troubleshooting-workshop-outline/. More to follow next week.
Hey everyone. This is the last week of the OPW internship period, however, as I took two weeks out for my backpacking trip, I’ll be hanging around a little longer than expected. In my two week make-up time (next week and the week after) I’ve been asked to create some tutorials/documentation on troubleshooting problems in order to help newcomers to the forums.
Last week, I submitted my first two patches to core. These were towards the 3.7 effort to add Inline-Docs to all the hooks in core (make.wordpress.org/core/2013/09/05/add-inline-docs-for-hooks/.) Special thanks go to @kpdesign for encouraging and helping me to submit my first patch, and also to @DrewAPicture and @tierra for their help via the #wordpress-sfd IRC channel. Everyone was really quick to offer their time and help, it really made me happy to be a part of the WP community, so thanks everyone.
I’m hoping to submit some more Inline-Doc patches this week, in addition to helping out as much as possible on the forums.
Hey everyone. So, it’s the second to last week of my internship. Time flies.
As always, I’ll be about on the forums this week and I am going to try to do some more theme reviews.
I’m currently getting my head around SVN, PHPDoc standards, and the how to’s of submitting patches. I’m hoping to submit my first patch in the next few days for the Inline-Doc effort (http://make.wordpress.org/core/2013/09/05/add-inline-docs-for-hooks/). If anyone’s got any tips or feedback on any (inevitable) mistakes I make with my first patch, they’d be much appreciated.
Hey everyone. So I’ve been backpacking around Europe for the past two weeks! Thank you to my mentors, @ipstenu and @hanni, for allowing me to take this time out of my internship. I really had the best experience. The plan for this week is to catch up and get back on track with everything. I’ll be back on the forums as well as trying to see where I can contribute towards 3.7 and 3.8. As always, any tips, advice, or suggestions are welcome.