Could we install the co authors plus plugin…

Could we install the co-authors plus plugin?


@otto42 @iandunn posted a plugin on trac for…

@otto42: @iandunn posted a plugin on trac for the /community team site 5 weeks ago. Could that get added, or if it’s not ready could you tell him what he needs to change? It’s a bottleneck for some stuff we want to do on our team site to make it easier for groups working on separate projects. Thanks!

#community, #make, #plugin

Time Shortcode for Make P2s

A couple of weeks ago, Siobhan pointed out to me the difficulties in talking about times for IRC meetups on the various P2 blogs. She suggested a shortcode to make it easier to specify times.

So I wrote a first draft of a shortcode to make this a bit easier. It’s not perfect, but I figured to go ahead and tell people now, so that you all could go ahead and start banging on it and telling me what the problems are.

Usage: [time] some-time-format-here [/time]

By “some-time-format-here”, I’m being a bit generous. You can use pretty much any time format you can think of and it will attempt to figure it out. With extra emphasis on “attempt”.

Stuff like this all works:

  • March 30, 2013 1pm UTC
  • April 4th at 1pm
  • April 4th around 1pm
  • April 4th 2012 1pm
  • next monday 1pm CDT
  • 1pm UTC

Now, a few important points:

  • If you don’t specify a timezone, you’ll probably get UTC. This is just for now, until I work out a better way.
  • If it can’t figure it out, you’ll notice no change in your text. Hopefully.
  • If it gets really confused, it’ll probably say January 1st, 1970. 🙂
  • “Absolute” times are more likely to work than “relative” ones. Give a date, and year, and time, and timezone, and you’ll probably be good.
  • Timezones matter in terms of daylight savings. GMT is not the same as BST (British Summer Time).

So, what’s the point? Well, if it can figure out what time you meant, then it’ll encode that and a bit of Javascript will then localize that time to the viewer of the make P2 in question on load, assuming their browser knows what timezone they’re in.

So when I post “April 3rd, 2013 6:30pm CDT” (my current time) in the time shortcode, it’ll show this instead: April 3rd, 2013 6:30pm CDT. What you see there depends on where you live.

Hopefully this will make it somewhat easier to schedule IRC meetups and such. Let me know when (not if) you break it. Happy to iterate.

#make, #plugin

Welcome to Meta (with a feature!)

During the WordPress Community Summit pre-planning sessions, it became obvious that there’s not a lot of good communication about what we do, plan, and code for the website itself. So, after a bit of chatter, Make-Meta was born. This is where we plan on talking about changes to the site, as well soliciting feedback for feature ideas. Consider it a community site; we don’t always know what the best way to make the website work is, so feedback is not just welcome, but encouraged.

In order to kick things off properly, I figured I’d announce a new feature: Reviews!

After a lot of discussion, it became clear that a “plugin review” concept was very much desired by the community in general. So we implemented reviews, but didn’t bother to limit it to just plugins. So now, plugins and themes can have reviews.

In order to keep things straight, reviews are tied to ratings. In order to rate a plugin, you must write a review as well. All the old ratings are still there and won’t be going away (we use those, after all), but if you want to change your rating in the future, well, explain it. Tell your side of the story. What’s broken? What works? What’s the best and the worst of the code? How can the plugin or theme author improve it?

Communication is important, and “support” is only half of the equation. Feedback is critical, and hopefully, the new Reviews system will go a long way to improving communication between the many millions of users of code we host on and the many thousands of contributors who write the themes and plugins that we all use every day. And all reviews go into our forums and can be commented on by everybody, just in case somebody needs some extra help.

(Note to Plugin/Theme authors: You can subscribe to your reviews alone via RSS feed, but the email subscription is cross-tied to the support-forum email subscriptions. If you’re subscribed to those, you will get review emails as well.)

There won’t be a lot of reviews at first, but hey, that’s where you come in! Just to get everybody started, I went ahead and wrote a couple of reviews to kick things off. So if you want to see it in action immediately, you can see them here:

These are accessible for any plugin or theme through the “Reviews” tab. Alternately, try to rate a plugin or theme and you’ll be sent to the review form as well.

Note that this is “iteration 1” of the feature. I expect to make many visual and stylistic changes over the next couple of weeks, and perhaps add a few new features. If you have a great idea for a feature or enhancement, feel free to comment and let me know. (Don’t bother me with the visual-only stuff yet, I know the CSS needs some love. Also, reviews don’t really display all that well on profiles yet; I know, working on it.)

BTW, the majority of the code to power the reviews came from our own Scott Reilly, who is, frankly, a genius. Give him mega props. 🙂

#make, #meta, #plugin, #reviews