Recent Updates RSS Toggle Comment Threads | Keyboard Shortcuts

  • Jane Wells 12:00 pm on April 15, 2012 Permalink | Reply
    Tags: bbPress   

    Jtrip posted this over at the bbPress development blog, thought it worth mentioning here:

    Coming in the next few days, the bbPress Subversion repository is going to be slightly rearranged.

    • /trunk will be moved to /branches/1.1/
    • /branches/plugin will be moved to /trunk

    The 1.x stand-alone version of bbPress is considered legacy, and our own repository should reflect this. If you have a legacy installation running off of a Subversion check-out of /trunk, be sure to switch your checkout to use /branches/1.1/

     

    • banago 12:38 pm on April 15, 2012 Permalink | Reply

      It’s time to move to Git altogether I think.

    • Jon Brown 4:55 pm on April 15, 2012 Permalink | Reply

      Good move, having never touched the legacy version getting 2.1 checked out was a bit confusing to me.

  • Jane Wells 7:45 pm on April 5, 2012 Permalink | Reply
    Tags: community, ,   

    Organizing Our Contributor Groups 

    Hi there, core contributors (and those who follow them). One of the things I’ve been meaning to do in the contributor community for the last 3-4 years is organize it so that when we say “contributor” it doesn’t just mean core code and the different contributing groups can all be on the same page. You may have seen some surveys sent/posted to the forums/docs/theme review teams etc. Your turn!

    In order to create a closer relationship between all the contributor groups, ensure our policies and agendas don’t conflict, recognize outstanding contributors, and just generally level up, we need some organization. To wit:

    • I’d like to identify who the active contributors are in each group.
    • I’d like to appoint someone from each group (based on votes from the active group participants) as a group liaison to the rest of the WP project and any cross-team initiatives to improve communication.
    • I’d like to set up a central P2 for communicating project-wide things so that no contributor group ever has to hear important announcements after the fact and we can discuss any issues that come up that could use the help/attention of people from other groups (including core).
    • I’d like to try and set up a monthly IRC chat and/or Google hangout for the liaisons to have some real-time communication.
    • I’d like to organize an annual contributor summit. Similar to the core team meetup concept, but more inclusive.

    The core code contributor team is the most in the know right now, but I’d like to make things a little more equal. Even within core, sometimes I hear people saying they wish they had more of a voice. The way the survey is set up, first you’ll pick how many reps you think core needs to have in the game (just one for core, or a couple, with each representing a different level of experience/seniority to make sure more issues/concerns are heard?), then you’ll vote on who you think the rep(s) should be. Note that inclusion in the survey does not mean that person has agreed to be a rep… I just pulled from our credits list and teams page for 3.4. Once the votes are in, I’ll contact people to see if they’re up for it.

    The survey is at http://wordpressdotorg.polldaddy.com/s/core-contributors
    and is password protected to help reduce spam responses: core2012

    If you could fill it in before the weekend is over (or right now… it’s only a few multiple choice questions), that would be great.

    Thanks!

     

    • Pete Mall 7:53 pm on April 5, 2012 Permalink | Reply

      1. Didn’t need the password.
      2. I think the conditionals are screwed up. It seems to be asking me all questions no matter what I picked (1/2/3… reps).

      • George Stephanis 7:55 pm on April 5, 2012 Permalink | Reply

        Ditto.

        • Jane Wells 8:08 pm on April 5, 2012 Permalink

          Deleted your response so I could fix survey. Try again?

      • Jane Wells 7:57 pm on April 5, 2012 Permalink | Reply

        You are so right! Closing survey for a minute to check it/fix it. Thanks for the heads up.

      • Jane Wells 8:07 pm on April 5, 2012 Permalink | Reply

        Reopened, try now.

        • The Z Man 8:13 pm on April 5, 2012 Permalink

          Still didn’t need the password…

        • Helen Hou-Sandi 8:13 pm on April 5, 2012 Permalink

          Conditionals seems good now, but didn’t ask for a password.

        • Eric Mann 8:17 pm on April 5, 2012 Permalink

          Ditto to Helen’s response. Everything seems to be working except for the password.

        • The Z Man 8:18 pm on April 5, 2012 Permalink

          It asked for the password after I cleared my cache and all the conditionals worked great!

        • Aaron D. Campbell 8:21 pm on April 5, 2012 Permalink

          It asked me for the password, and the conditionals seemed fine.

        • Helen Hou-Sandi 8:24 pm on April 5, 2012 Permalink

          Yep, password seems fine now. Must have just caught it in the in-between :)

    • Jon Brown 8:34 pm on April 5, 2012 Permalink | Reply

      Took me a minute to figure out what you meant by Q.9. I’m assuming you mean representatives _at the core community summt_ mentioned in Q.7?

      Also do you really want “people that just follow core” to fill this out?

      • Jane Wells 8:57 pm on April 5, 2012 Permalink | Reply

        Realistically, only people who consider themselves contributors ought to submit a survey. That said, if some extra people fill it in, it’s not that big a deal. It asks for names, so I can double check status if it looks fishy.

    • Mert Yazıcıoğlu 9:05 pm on April 5, 2012 Permalink | Reply

      A little off topic but I think the “Core Contributor” term needs to be expanded a tiny little bit. Authors of accepted patches get the “props” (which is right) but people who report the bug itself do not. As far as I know, Core Contributors list is generated by a script that checks “props” in the commit messages and I think it is unfair because a person who reports 100 bugs gets no credit while a guy who submits a simple patch do get.

      Am I missing something?

      • Jane Wells 8:05 am on April 6, 2012 Permalink | Reply

        “Core contributor” has traditionally been shorthand for “core code contributor” or “core developer,” while testers have been another contributor group, though there is frequent overlap (much like forums + docs). I haven’t done the survey for testers yet, as I am making my way through the groups one by one.

      • Mark 8:37 am on April 6, 2012 Permalink | Reply

        If you wanted to widen this – someone who answers 1,000 or 10,000 forum questions to help the community at the http://wordpress.org/support forums gets zero acknowledgement while someone who contributes a 10 line patch gets a credit. WP is nothing without all these people.

        • Jane Wells 8:59 am on April 6, 2012 Permalink

          Which is the exact reason for doing these surveys to identify who’s being active where and get representation for each contributor group ‘at the table’ from now on.

        • Jane Wells 8:59 am on April 6, 2012 Permalink

          (Forums was the very first group that got one.)

        • Mika Epstein (Ipstenu) 1:14 pm on April 6, 2012 Permalink

          So … wait, Jane doesn’t send everyone those cyanide pills to swallow if we get caught by rampant trolls?

        • Mark 1:23 pm on April 6, 2012 Permalink

          That sounds great Jane :)

        • Mert Yazıcıoğlu 10:29 am on April 8, 2012 Permalink

          @Mark: Exactly! If there are credits being given, everyone who helps in some way deserves to get one.

  • Jane Wells 11:42 pm on April 4, 2012 Permalink | Reply  

    Image Post 

    20120404-194222.jpg

     

    • Jane Wells 11:51 pm on April 4, 2012 Permalink | Reply

      image posted from new ipad so @azaozz could see bug.

    • Andrew Ozz 2:56 am on April 5, 2012 Permalink | Reply

      Seems in Chrome 18 there are some strange artifacts on the headers of list tables too and the border-color controls their color. This may be related.

      • George Stephanis 7:57 pm on April 5, 2012 Permalink | Reply

        I couldn’t manage to duplicate this in the iPad 2, I’ll be testing on the 3 shortly. Personally, I blame the gremlins.

  • Jane Wells 5:24 pm on March 28, 2012 Permalink | Reply
    Tags: , ,   

    Dev Chat Plan 

    This week we wanted to declare beta. But things are still being committed that are not just bug fixes! And things with patches are still waiting for review! And half the core team is out of town today! What to do?!

    • Koop more or less wrapped up theme previewer last night.
    • Before we do another check on where our planned features stand, I’d like the queue of has-patch tickets to be cleared. Any/all commit-level developers in chat today should divvy up the tickets for the commit/punt roll call until there are no more patches waiting in the 3.4 milestone. Tomorrow we can do a check in of the planned features and punt the things that just didn’t make it in time despite valiant efforts. Maybe Friday we could call beta, or that could be Monday (not sure when Ryan gets back). Nacin is driving in dev chat today.
     

    • arena 9:03 pm on March 28, 2012 Permalink | Reply

      Dev (schit) plan
      ticket #18997 was opened 5 months ago, I posted a patch…. happy to contribute to this wonderful project called wordpress !
      And … has been arbitrarily postponed today for future release … with the following comment …

      A good idea, but too late for 3.4.

      are you looking for volonteers ?

      • Aaron D. Campbell 5:01 am on March 29, 2012 Permalink | Reply

        We’re always looking for volunteers! And we very much appreciate the feature request AND the patch. Unfortunately, in order to get versions out on time (and we’re already behind schedule on this one) we have to draw a line somewhere. Even with the patch already written, it needs to be reviewed, tested, checked for potential security issues, checked for backwards compatibility, etc.

        Additionally, this release is specifically focused on giving the site owner the ability to make their site look how they want (mostly theme enhancements). This doesn’t particularly fit with that and we need to try to stay focused so we can accomplish as much as possible. Your idea hasn’t been rejected, just postponed.

  • Andrew Nacin 2:47 am on March 27, 2012 Permalink | Reply  

    Phishing attempts for WordPress.org credentials 

    Recently there was a “phishing” email sent to several plugin authors designed to steal their login credentials. If you receive or have received any emails claiming to be from the plugin repository, please make sure to double check them. Emails regarding the repository are always sent from a wordpress.org email address. If in doubt please reply to the email asking for confirmation.

    Please always check the URL you are logging into, for any site. Be sure you are logging into “wordpress.org”, not “wordpress.some-evil-domain.info”.

    Here’s what many plugin authors have reported receiving:

    Example phishing email. That link doesn't go to wordpress.org, though! (And we don't have a my-plugins-status page.)

    If you have received a suspicious email and followed any links, please visit the real WordPress.org and change your password. If not, as a plugin author it’s a good idea to change your password regularly.

     

    • Lee 6:40 am on March 27, 2012 Permalink | Reply

      Last time plugin author accounts got compromised didn’t the repo start emailing authors on every commit? I just did some commits right now, but didn’t get any emails – has that broken/been turned off?

      [As an addendum, I didn't get an email to say that my latest repo had been approved either - so maybe I've stuffed up a setting somewhere?]

      • Andrew Nacin 6:43 am on March 27, 2012 Permalink | Reply

        I got an email for your commit [524175] (I receive all of them) so I would check your spam.

        • Lee 2:09 pm on March 27, 2012 Permalink

          Nope, nothing, nil, nada I’m afraid.

      • Alex Mills 4:46 am on March 28, 2012 Permalink | Reply

        I can confirm they’re working for the average Joe. I get e-mails for all my commits.

        • Lee 6:30 am on March 28, 2012 Permalink

          Hi Alex, thanks for confirming they’re working for you – must be something wonky with my personal setup – I’ll do a bit more digging. [Apologises to Andrew in advance for dummy commit messages!]

    • Charles 12:49 pm on March 28, 2012 Permalink | Reply

      I’m sorry for my account was hacked this time. I use iPhone check my email these days and Safari on iPhone has a too short address bar and I over looked the domain name. I noticed that you’ve fixed my plugin and prevented it from bothering more users. Thank you very much.

      Could you tell me something about how can I get back my account? Any help will be appreciated.

  • Jane Wells 9:42 pm on March 21, 2012 Permalink | Reply
    Tags: , dev chat summary   

    Dev chat summary:

    • Two more days of wrap-up on features
    • Weekend review by people with commit access
    • Major puntfest begins now, things that were thisclose can be targeted for early 3.5
    • Hoping for Beta 1 next Wednesday.

    For complete transcript including team-by-team updates, see the IRC transcript.

     

    • Mr. Roy Arellano 10:10 pm on March 21, 2012 Permalink | Reply

      Ok, stupid question, what is the definition of “puntfest.” Absolutely have never heard the word use in over 14 years of IT experience. LOL. Sorry.

      • Jane Wells 10:31 pm on March 21, 2012 Permalink | Reply

        A fest(ival) of punt(ing) tickets that didn’t get committed in time.

        • Chris Clayton 10:45 pm on March 21, 2012 Permalink

          Roy, Punting is the term they use to basically kick (punt) the ticket to a future release. (took me a while to figure that out despite hearing the word over and over again. lol)

        • Chris Clayton 10:47 pm on March 21, 2012 Permalink

          fail. by kick, i mean drop… “drop the ticket to a future release.”… i need sleep.

        • Jane Wells 10:47 pm on March 21, 2012 Permalink

          @Chris: you were right the first time. It’s definitely a kick, not a drop.

        • Chris Clayton 10:52 pm on March 21, 2012 Permalink

          lol, got myself confused after posting the first comment “wait, is kicking, or dropping the right word”. lol Anyways, in total english for thoes still not ‘up’ with development terms (since it is confusing unless you have been around for a while) is that every ticket that is not 100% ready is being kicked out of 3.4 and into 3.5.

        • Mr. Roy Arellano 10:56 am on March 22, 2012 Permalink

          ALCON,
          Thank you Ms. Wells and Mr. Clayton. I appreciate that. I’ve worked in IT for 14 years, to include 4 years in Software Development, 6 years in Project Management, and honestly I have never heard it used in this way, but after the explanations provided I understand. Thank you.
          :-)

  • Andrew Nacin 6:40 pm on March 20, 2012 Permalink | Reply
    Tags: ,   

    As Twenty Twelve is punted to 3.5, it is being removed from core. It can be found here for now, and will be brought back in for 3.5.

     

    • Cais 7:13 pm on March 20, 2012 Permalink | Reply

      I’m looking forward to its return, there looks to be a great deal of potential with the theme.

    • arena 2:59 am on March 21, 2012 Permalink | Reply

      Hope it will be released before Dec 21 ….

    • John Blackbourn 3:08 pm on March 21, 2012 Permalink | Reply

      I thought the plan was TwentyTwelve would be the headline feature of 3.4 that 3.3 lacked. Now that it won’t be, what will?

    • RozaniGhani 12:51 pm on March 22, 2012 Permalink | Reply

      It too bad to wait twenty twelve theme until the end of year 2012. It should be renamed as twenty thirteen because almost 2013 in that moment.
      So far, twenty twelve theme is far more better than toolbox theme.

      • Mert Yazicioglu 10:12 pm on March 23, 2012 Permalink | Reply

        Agreed. 3.3 was the best release to call it Twenty Twelve and 3.4 would still be nice but 3.5 sounds a bit too late. On the other hand, assuming that 3.5 will be released by the end of the summer or beginning of the fall, it would be too early to call it Twenty Thirteen.

        Doesn’t really matter what it’s called though, it’s a great theme and I’m sure people will love it :)

  • Andrew Nacin 5:25 pm on March 19, 2012 Permalink | Reply
    Tags:   

    r20212 introduced new methods for registering custom headers and custom backgrounds. Everything now wraps add_theme_support(), and the various HEADER_ and BACKGROUND_ constants are gone.

    This is ideally backwards compatible (I am cautiously optimistic), but because of the many factors at play here — child theme inheritance, constants, and theme support — it is very difficult to test.

    I am going to come up with some sort of a testing protocol in the hope that we can crowd-source testing the WP.com themes that implement custom headers or backgrounds. For now at least, if you are running a theme with custom header or background support, please test and make sure functionality did not change.

     

  • Jane Wells 6:16 pm on March 16, 2012 Permalink | Reply
    Tags:   

    No GSoC 2012 

    WordPress was rejected as a mentoring organization from GSoC for this summer. This is unexpected, as I spent some time during the application period talking with Carol (Smith, the GSoC administrator) about our proposed approach of building a release cycle around GSoC and making it a mentorship-focused release and she seemed to approve the idea.

    We can still do a summer mentorship-focused release for 3.5 if we want to, though. We could pimp it as independent study for credit for college students and put more focus on non-student potential contributors, such as from the plugin/theme ranks. If nothing else, it would avoid the inevitable couple of students who are only in it for the $$. We’ll need to decide if we still want to do something along these lines, or if we don’t.

    Why did we get rejected? We don’t know yet. I used last year’s successful application as a template. There will be a feedback meeting in a week or so, and Carol says to attend that when it is announced and we can find out why during that meeting.

     

    • Daniel Chatfield 6:20 pm on March 16, 2012 Permalink | Reply

      That is very unexpected. I’m a student and would love to get involved :)

    • Brian Layman 6:20 pm on March 16, 2012 Permalink | Reply

      Well that’s unexpected… If we are going to get feedback from that meeting, it probably won’t pay to spend time speculating on the reason right now…

    • Aaron D. Campbell 6:22 pm on March 16, 2012 Permalink | Reply

      Mentorship-focused doesn’t sound that far from the teams setup we used for 3.4. The other advantage is that we can mentor any age, rather than restricting it to college students.

      • Jane Wells 6:26 pm on March 16, 2012 Permalink | Reply

        Was planning to do that anyway. The GSoC part would have been a good push on external deadlines, though.

      • Kyriakos 8:45 pm on March 16, 2012 Permalink | Reply

        Sounds like a good idea Aaron. There is a wider audience than college students that will like to participate and need the guide from a WordPress Guru.

    • drecodeam 6:26 pm on March 16, 2012 Permalink | Reply

      This is seriously unexpected, but yet for us students the idea of the mentorship focused release is a nice option now, i would still love to get involved for this summers. One of the major advantages of GSoC program was the structured approach it puts the students in. If you can still chalk out such a plan, a lot of good work can still be done from the students who are deeply interested.

    • George 6:37 pm on March 16, 2012 Permalink | Reply

      I think students who wanted to work with WordPress would contribute anyway. Will WordPress team still provide mentorship?

      • Stas Sușcov 7:22 pm on March 16, 2012 Permalink | Reply

        This is debatable. WordPress is solid enough (probably that’s the reason why Google thought it doesn’t need help) to get a SoC or some sprints like it happened during 3.5 cycle.

        I remember http://rubysoc.org and it’s a great example. I would help crowd-sourcing/mentor/contribute to some projects like bbPress/BuddyPress or why not Coursewa.re.
        And many would do the same.

        • George 7:26 pm on March 16, 2012 Permalink

          That would be great. I wanted too ask about BBs mentorship. You did a great job with Courseware, I’ve idea similar to Courseware, but not sure can it be done on top of your project. Maybe when you have time we can chat and discuss this.

        • Stas Sușcov 7:30 pm on March 16, 2012 Permalink

          Thanks, sure, anytime.

    • George Stephanis 6:40 pm on March 16, 2012 Permalink | Reply

      Still planning on keeping it to core contributions only, or possibly opening it up to plugins as well? The latter could get a bit messy paperwork-wise without a more consistent oversight if done for credits.

    • mitcho (Michael 芳貴 Erlewine) 6:44 pm on March 16, 2012 Permalink | Reply

      I feel surprised and saddened by GSoC’s decision, but I agree that having a program to get new contributors more involved through some mentorship is a powerful thing that could continue outside of the purview of the GSoC program. I hope that does indeed happen.

    • Mert Yazicioglu 6:52 pm on March 16, 2012 Permalink | Reply

      I wasn’t expecting that just like the others but I’m sure there are many people out there (like me) that would love to take part in a mentorship-focused release. Most of us students have more time than the core developers during the summer so I’m sure we can make great contributions.

      This is certainly sad news but not a show-stopper in my opinion.

    • Kyriakos 7:05 pm on March 16, 2012 Permalink | Reply

      Why unexpected? WordPress should see this coming. Is obvious that Google at some point would stop supporting competitors to its own products like WordPress is for Blogger and soon other organizations will follow. (Firefox>Chrome, ChromeOS competitors etc.)

    • Jane Wells 7:17 pm on March 16, 2012 Permalink | Reply

      Now that the list has been released, we are in good company… Drupal, Mozilla, and other big projects are out, also. There are only 54 organizations listed (vs 150+ in past years) and most look to be smaller ones.

      • Tunilame 7:42 pm on March 16, 2012 Permalink | Reply

        But the list is getting longer with minutes (180 participating organizations marked, but only 73 shown ’till now), is that normal?

      • Jane Wells 7:51 pm on March 16, 2012 Permalink | Reply

        My bad. Not all the orgs are listed yet, because they only show up on the list ( http://www.google-melange.com/gsoc/program/accepted_orgs/google/gsoc2012 ) after they have filled in a post-acceptance profile. For all we know, Drupal, Mozilla, etc may have been acepted and we just weren’t. Will find out for sure at next week’s meeting.

        • Rafael Poveda - RaveN 11:14 am on March 17, 2012 Permalink

          I think WordPress have enough support by companies to begin with your own WordPress Summer of Code without funding problems. As said before, it can be an excellent opportunity to allow more projects –not just students projects– and to focus in company-related issues too.

      • Egill Erlendsson 8:20 pm on March 20, 2012 Permalink | Reply

        Drupal, Joomla, Mozilla, Wikimedia, Django are on the list of accepted organizations, which makes the decision even more interesting.

    • Kyriakos 7:21 pm on March 16, 2012 Permalink | Reply

      Mozilla products are direct competitors to android (b2go) and chrome (firefox) etc This day was about to come Jane, Is quite anorthodox for a company to pay competitors to grow bigger stronger better.

      • Jane Wells 7:27 pm on March 16, 2012 Permalink | Reply

        Leaving multiple comments with the same content is a good way to get marked as spam. We got it the first time. And completely disagree.

        • Kyriakos 7:38 pm on March 16, 2012 Permalink

          And what is the reason for this kind of move from Google Jane according to your opinion?

        • Jane Wells 7:54 pm on March 16, 2012 Permalink

          We will have to wait until the meeting next week to find out. We have participated for 5 years though, and are not exactly in need of the helping hand that GSoC offers.

      • Mert Yazicioglu 10:09 am on March 17, 2012 Permalink | Reply

        Having a stronger competitor is a good thing, it motivates you to do greater things. GSoC is to get students more involved in Open Source and not Google or its products. Google is just trying to contribute to the growth of the Open Source ecosystem, that’s all.

        And by the way, Mozilla is accepted so your argument is invalid in every possible way.

    • rhh 12:48 am on March 17, 2012 Permalink | Reply

      GSoC rejection does not matter at all. In fact WP can have its own summer of code for all open source stuff, maybe in some other name. WP needs independent and unique branding, which it has but needs to be MORE. For example, Facebook have no mention of WP, neither Google in the form of small icons, logos, or the “like it” buttons, so WHY does WP needs that in its various properties/web estates?

      First step towards shaking the unhealthy dominance by G,FB, Apple – be UNIQUE dear WP!

    • DrewAPicture 8:32 am on March 17, 2012 Permalink | Reply

      It was probably all the jokes about Melange finally getting fixed.

    • Thorsten 10:39 am on March 17, 2012 Permalink | Reply

      Bummer, nevertheless I would be happy to mentor any student who wants to do something “WordPress” during the summer.

    • Frederick Townes 12:51 pm on March 17, 2012 Permalink | Reply

      This is a bit of a surprise for me, but what I can say is that there’s still an opportunity to drive innovation for WP. Whether it’s as transparent as it could be or not, there’s quite a bit of mentorship permeating this community and I agree with some of the prior commentors that this community has the means to “institutionalize” that mentorship in least in terms of manifesting those values in the form of it’s own program. As usual, it would set the bar in terms of culture for other open source groups as well, which is definitely not a bad thing (nor a small feat). So I’m all for an “internal” mentorship program (which can have quite few different possible legs).

    • Shibu Lijack 4:28 am on March 19, 2012 Permalink | Reply

      I am extremely disappointed! Being a college student, I was eagerly waiting for GSOC’12. I thought for sure WP would be one of the mentoring organisations. So I started preparing months ago.. Developed quite a few plugins and themes. But how unfortunate! All my hopes and dreams shattered. I still wish WP could somehow get accepted into GSOC’12.

      • Jane Wells 3:57 pm on March 19, 2012 Permalink | Reply

        There may not be a $5000 paycheck attached, but new contributors to core are always welcome. :)

    • Stas Sușcov 4:13 pm on March 19, 2012 Permalink | Reply

      For students looking for WordPress GSoC projects, last two years Creative Commons were looking for a WordPress developer. I checked again and it looks like their WordPress RDFa plugin is still on their ToDo list:
      http://wiki.creativecommons.org/RDFa_Plugin_for_WordPress

      if you really-really want to help CC, I could be a lamb and even help you with my last year proposal draft (just to help you dig into what they were looking for) :)

      Good luck!

  • Andrew Nacin 8:01 pm on March 14, 2012 Permalink | Reply
    Tags: ,   

    Starting next week, the dev chat is moving to 20:00 UTC to follow the schedule of daylight saving in the U.S. Since we forgot about daylight savings, and every person on the core team is either traveling or busy at some point over the next two hours, we’re going to be in a working session (see earlier post) — triaging teams, tasks, and tickets on the road to 3.4 Beta 1. See y’all in IRC.

    I’ve updated the sidebar to reflect the new time starting next week.

     

    • Aaron D. Campbell 5:37 pm on March 19, 2012 Permalink | Reply

      Back from vacation today and I saw this. It’s a bad time for me now (my son gets out of school right in the middle of the dev chat), but assuming it’s good for everyone else I’ll make it work.

← Older posts

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Follow

Get every new post delivered to your Inbox.

Join 1,015 other followers