Elsewhere

Giving design feedback is hard, but with a few quick tips you do it like a pro.

The Design Feedback Sandwich.

The best way to keep designers happy and your project on track is to use what I call the Design Feedback Sandwich. Start by telling your designer a few things you like about the design. Next, tell the designer which pieces are problematic. Finish by telling them something positive thing about their work. Validating the positive ingredients keeps morale up and will create a healthy work relationship. Remember - people are more creative when they're in a good mood.

Frame Your Feedback Around the Goals

To become a true design feedback pro, frame all your feedback around the project goals. For instance, instead of saying "I don't like that blue," say "I don't think that blue effectively conveys a sense of excitement to our target teen audience." By framing your feedback within the goals you immediately win. You help keep the team on track and you remove your own personal bias. Go you! You are becoming a pro already!

When You Get Stuck, Test

When your team gets can't agree on the feedback, try testing. Using cheap and easy tools such as FiveSecondTest or UserTesting.com to bring in a fresh perspective to the conversation. Fresh eyes and new data can usually unblock creative gridlock.

Define Roles

As I learned from Paul Boag - It's the client's job to define the problem, and the designer's job to solve it. Keep this in mind when giving feedback. For instance, a common piece of feedback is "i think the page looks too busy. Lets add more padding." Try to remember to state the problem, not the solution. Instead, allow the designer to explore solutions to the problem. When you tell a designer how to do their job, you unknowingly limit their creativity. For example, adding more padding may make the page feel less busy, but so might reworking the copy, adjusting the type size, or reworking the layout. In short, trust your designer to find the best solution.

NOTE - many clients have fantastic suggestions and collaboration is key, but it's good to remember the roles to play to each others strengths.

R-E-S-P-E-C-T

Being both respectful to each other and validating each others efforts produces long term fruitful partnerships. When collaborators feel heard, moving forward becomes effortless.

This is my list. I'd love to hear yours. Design feedback can be a tricky business, so the more we share the better.

Normally Skype isn't mentioned by name on this blog, but today I'm making an exception.

When a new scandal broke out in the Australian Army today, one of the first questions asked was how does it compare to the Skype Scandal which had everybody talking (and blushing) in 2011. A concise military reply direct from the General:

"I'd say it's worse than the Skype matter"

(For those who are interested, the original Skype Scandal cadets are going on trial in six weeks)

Jedi Council brings cultural change in the Army: from Skype to email

Since the original scandal, there have been plenty of PR-orchestrated headlines about cultural change in the Army. Sadly, it seems that several ranking officers believed that was a cue to simply start using email instead of live feeds

Operating under the operational code name Jedi Council, they've apparently been swapping annotated images of female colleagues and members of the public service.

Usually such senior ranking officers have given many years of dedicated service to the country. They are widely respected and the vast majority of them are unlikely to be systematically involved in such games.

On the other hand, it's likely that all of them, including the bad apples, have top secret security clearances. After the revalation that Australia has a direct peering arrangement with the NSA, there are all kinds of questions about whether a couple of rogue officers have access to pursue their private projects using tools like PRISM and Boundless Informant. Maybe they even have direct access to images from those invasive airport body scanners - like these pictures that were not supposed to exist. Just like the British undercover cops stealing the identities of dead children and fully engaging impressionable young women from environment campaign groups, there is always a risk of things getting a little too naughty.

While this latest Army example involves private pursuits, it is not hard to imagine many other permutations: perhaps a couple of rogue Government employees making unauthorised use of a citizen's data for a commercial objective and gaining the upper hand on private sector competitors who have no such data feed.

100% trust?

In every organisation there will always be a few people bending the rules. It's human nature, if it wasn't that way, we'd all be robots. The Army and the Catholic Church tend to be hammered a lot more in the public eye when these transgressions are discovered although statistically their crime rates are no higher than average. The bottom line is that no organisation is perfect and people have to take some responisbility to object to the excessive growth of the security state and keep our data to ourselves as you just never know who you can trust.

The unofficial third party repository Debian Multimedia stopped using the domain debian-multimedia.org some months ago. The domain expired and it is now registered again by someone unknown to Debian. (If we're wrong on this point, please sent us an email so we can take over the domain! ;) )

This means that the repository is no longer safe to use, and you should remove the related entries from your source.list file.

After all, the need of an external repository for multimedia related packages has been greatly reduced with the release of Wheezy, which features many new and updated codecs and multimedia players.

Not sure if you're using the debian-multimedia repository? You can easily check it by running:

grep debian-multimedia.org /etc/apt/sources.list /etc/apt/sources.list.d/*

If you can see debian-multimedia.org line in output, you should remove all the lines including it.

Eight days after Confab 2013, and I have finally come down from my conference high. The conference was insightful to say the least - it is by far the best industry conference I have ever attended. This past week, I have sifted through notes, read recommended articles and reports, replayed in my mind all the thought-provoking presenter one-liners, and had many a conversation about the value of things like content “chunking” versus “blobbing”...the usual things you do when you come back from a conference feeling equipped with the knowledge you need to change the world.

I had a moment, as I sat down to write this post, where I asked myself “why does any of this matter?” There seemed to be something missing in all my thoughts and ideas after Confab. It all seemed very...tactical. I felt like I was missing a larger theme that timed all of these topics together.

It came to me as I read an interview with Paul Adams of Facebook in Fast Company. “People!” The theme that tied all of the Confab sessions together was the focusing on the needs of people consuming content.

Michael Brenner of SAP defined content strategy best:

“Content strategy is about delivering the content your audience needs, in all places they go.”

Content strategy is about meeting the needs of people. We often get lost in conversations about content, asking questions like:

1. What CMS should we use?

2. How do we create a great editorial calendar?

3. What keywords will get us ranked highest in search?

None of that matters. Not unless you are making a connection with what is at the other end of your content. People.

Each presentation I attended at Confab made that point within the wealth of knowledge shared that, at the center of all the planning, and wireframing, and building, is the need of a person. All the strategizing, and designing, and production, is all done with the intention of building a relationship with a person by helping to meet their needs. Where I think Paul Adams’ views on social design come into play, as many of us know about content strategy, is that investing in content is a long-term strategy that will take many, light-touch interactions with people over time before a relationship is really established.

Let’s get a little bit more practical with this concept. Here are some tips I pulled from different sessions I attended at Confab that will help you develop a content strategy centered around building relationships with people:

Content Modelling by Rachel Lovinger

Content modelling is essentially the process by which we as define content types, their attributes (fields, assets, metadata), and the relationships between types of content. It is foundational to any content strategy.

People are now engaging with brands across multiple platforms, on many different devices, often times all at once. As an example, a person attending an your event is reading information about your organization on their mobile phone, while they are following people’s tweets about the event on their laptop or tablet. One interaction, three touch points.

To address the needs of our users wanting content across various platforms and channels, we need to model content for portability.

Some recommendations that came out of this session all content strategists should keep in mind:

Think of your content separate from presentation. The root of this concept is in the content chunking versus blobbing debate. Most content management systems are designed with a Title field and a Body field where the content editor designs their content. That is dangerous because editors shouldn’t have to, and often are not good at, content design. By focusing on content structure over presentation, we can more granularly model our content with all the fields that need to be presented, allowing content editors to focus on entering content that needs to be served without having to do formating.

Content should be adaptive, not responsive. A related concept is adaptive content. The general idea is that content can, and probably should, look differently depending on how and where it is served. That ultimately is a design issue, not a content issue. When modelling content, we need to think of content types as having granular attributes (i.e. if a press release has an intro and a body, then have separate fields for each). Editors should focus on creating content, and designers focus on how it is presented on various platforms. As content strategist, we need to ensure our content is structured in a way that allows an editor to easily publish a piece of content in it’s entirety, and designers can then present content chunks, or collections of content attributes, in different ways on different platforms.  

Content models should be CMS agnostic. Technology should not inform your editorial strategy, your editorial strategy should define what content management system you use. Develop content models that map to the content needs of your audience and editors, then select the technology solution that will best support those.

Content Strategy for a Customer Journey by Kevin NIchols

Customer/user engagement happens across multiple channels and multiple platforms. Customers expect that they will have the same experience with a brand no matter where they interact with you - your website, via a mobile app, etc. Designing a consistent experience for a consumer regardless of channel or platform , referred to as omni-channel retailing, is driven by content and can be adopted by all industries.

The key to this strategy is personalization. Understanding who your user is, their needs, and where and how they meet those needs is critical to determining what content to serve along the user journey. If you know that Ann is a mother in Chicago that likes to cook casserole for her children, you can serve her a coupon on her mobile phone when she visits the recipe section of your mobile app or website.

There are many different ways to personalize your content strategy. You can build a recommendation engine into your website that serves a user content based on their defined interests. You can inform how you segment content on social media, email marketing, or direct mail based on your understanding of user personas. The approach you take should be specific to your organization, but remember the key is to focus on meeting the user need at every touchpoint in your user journey.

Well This IS Interesting by Melissa Rach

People need interests to live. We are “information foragers” - we seek information the same way we seek food. The more we learn, the more information we seek.

Content is about feeding people’s natural desire for information that is interesting to them. Our goal is to find the intersection between a person’s interest and our desire for them to take some type of action.

While interests are many things to us as humans, they are most importantly social. We build relationships through shared interests. The same thing goes for people building relationships with people as with people building relationships with brands. To establishing a relationship with a person, we need to produce content that aligns with both of our interests.

Our interests are enticed by emotion. Whether content is goal-, entertainment-, or action-oriented, we choose to engage with a brand based on how a piece of content makes us feel. Write copy that will evoke a desired emotion in your reader - joy, anger, intrigue. If you can evoke an emotional reaction from the reader, the greater the likelihood they will remember and be interested in your content in the future.

Some things to keep in mind when writing copy or designing content:

• Make sure you know the topic you are talking about and can provide helpful information

• Focus on meeting the needs of the content consumer - it is all about them

• Produce content that fills the gaps between what the user needs and what you have to offer them

• Encourage people to have a conversation with you

The Poetry of SEO by Mike King

Search engine optimization for years was a very prescriptive process circa 2000-2008. You optimized pages with metadata - meta titles, meta descriptions, and meta keywords - that helped search engines better understand what content was on a page. You made sure your pages were marked up in a way that allowed search engines to understand the structure of your page. Then  you worked on building cross links between your website and more reputable website. Voila! High ranking website.

Since the proliferation of social media, the game has changed. Major search engines now take into account social interaction with content and content consumed by your social graph in determining what to display to you in search results. People are spending more time on social media websites and discovering more content in their newsfeed than ever before. While keywords are still critical to search placement, the new driver of content discovery is social media.

Keyword optimization within content and meta titles is still important, but not as important as writing copy for people. You should write content with an eye towards getting people to share it with their friends.  Meta descriptions that appear in search results should connect with a reader, just like a tweet or an ad.

Social media can also be one of your best research tools because it shows you what people actually think and say about topics and brands. Use Facebook ad data and Google Adwords keyword tool to get demographic information about people who are searching for and talking about specific topics and use that data when building personas and your keyword strategy.

Did you attend Confab? What were some of the insights you gleamed from various sessions?

First, some background. My name is Aaron Winborn, and I am a developer for Drupal, which is an open source content management system, used to make web sites. I also the father of two young girls, who bring much joy into my life, and married to a beautiful woman. You may have heard of her, her name is Wonder Woman.

Just over two years ago, I was diagnosed with ALS, also known as Lou Gehrig's Disease. In short, that means that my mind will increasingly become trapped in my body as the motor neurons continue to die, and the muscles atrophy and waste away, until my diaphragm dies, bringing me with it.

My hands and arms are already completely paralyzed, and I'm confined to a power wheelchair. My diaphragm strength is largely diminished, and I am using breathing assistance 24/7, and I am at imminent risk for respiratory failure.

Even if I am fortunate enough to survive another year, which is only likely if I opt for a tracheostomy, my chances of surviving much longer become increasingly unlikely, as pneumonia becomes a specter haunting the late stages of ALS. There is no cure for this awful disease. My family gets to take care of all my needs and wipe the drool off my face, until I die, and leave them to pick up the pieces.

But yes, there is a silver lining to this all, such as it is. Kim Suozzi made a similar plea to the Internet a year ago today, and came up with the brilliant idea of freezing her body in the hopes of a distant advanced technology being able to revive her someday. Her body now rests at liquid nitrogen temperatures. http://www.reddit.com/r/AskReddit/comments/uvaqe/today_is_my_23rd_birthd...

I approached the organization responsible for raising the funds to help her out, the Society for Venturism, last November, and they agreed to take on my case as well. http://venturist.info/aaron-winborn-charity.html

But I am actually telling you all this in order to come up with a sort of reverse bucket list.

I've had a full life, with no regrets. I've done some travel, have lived in some cool places, like the Netherlands and London. I've made lots of good friends, and continue to do so. I've contributed to my debt to society, working hard throughout my life, as a teacher, a waiter, an open source software developer. I've worked with a few interesting characters, like Elisabeth Kubler-Ross, and even lived in a Buddhist monastery before I met the woman of my dreams.

But I'm not ready to hang up my jacket quite yet.

When I was ten, I came up with three things that I wanted to be when I grew up: a teacher, a writer, and an astronaut. I've been two of the things, which is not bad. As an aside, I once told that to some people, and was asked, "Oh, what did you write?" To which I replied, "I didn't say I've written anything."

Joking aside, I'm looking for some grandiose ideas of things to do after I've died, and have hopefully been revived. And by that, I mean the sky's the limit. Don't worry about whether something seems technically feasible. This is your opportunity to think big. Like, go skinny dipping in the methane oceans of Neptune.

I want to do so much more with my life, but it's not in the cards this go around. I've become a spectator in life, living vicariously through my daughters, and relegated to typing with my eyes at fifteen words per minute on a good day.

But I'm not complaining. I awaken each morning as I always have, excited to take on the day. This is just a way to do some more brainstorming, to come up with a list of things to do during the next century, should we be so fortunate.

Stay strong,

Aaron

PS This question was originally banned from the Internet at http://www.reddit.com/r/AskReddit/comments/1g7h69/anything_awesome_i_sho...

read more

Before doing any changes to your web site, the first thing to figure out are your goals. As a web development shop, we focus on building web sites that create measurable value for our customers, aligned with their goals.

Some common goals:

• Help me close more sales from people who I send to my web site (brochure/information)
• Bring me new customers (online marketing, SEO)
• Help me manage sales leads (CRM)
• Increase sales (e-commerce)

How you should revamp your site completely depends upon which of those goals (or whatever other goals you may have) are most important for your business at the current time.

Drupal PlanetGoalsData Visualization

Personal blog tags: DrupalCon Praguedrupalcon

The new Twitter 1.1 API kicked in recently, which meant a new cycle of maintenance for anyone consuming their data programmatically. My own Feeds + Views demo site streams #drupal, using Feeds and complementary modules. I had to make a few changes to adapt to the new API:

• Authorization using OAuth
• Parsing JSON instead of XML

OAuth authentication

The new Twitter 1.1 API requires OAuth authentication/authorization for every request.

read more

Dear lazyweb,

my Nexus 4 just ate a brick and the screen is so broken that the capacitative sensing stopped working completely. That sucks a bit, especially considering that you can't really replace the screen according to ifixit...

What sucks more is this: As my phone is both encrypted and passphrase-protected, I can't access my photos.

Yes, yes, I should have set up git-annex on it by now, but that's of no help now. So... How do I get my data off of that phone? Again, I don't really care about much other than my photos.

This series outlines our project process through the lens of our development of the new 4SiteStudios.com. In this post, we will discuss our process for architecting a content management solution for a client.

In the technical plan, we take the content plan, wireframes, and our documentation from the discovery phase, and begin to make decisions about how we're going to actually implement the site in Drupal. What content types do we need? What contrib modules do we need to install? Do all of those modules play nicely together? What custom modules do we need to write? What views do we need to build? How do we know when a feature is done, and how do we test to make sure?

The first thing we do is break all the main functionality of the site down into user stories. These are simple statements that describe tasks that different types of users should be able to perform. For example, "A visitor to the site can see a list of upcoming events," or "An authenticated user can register for an event." These are intentionally kept simple, so that we keep the focus on the problem we're trying to solve, rather than the way we're planning to solve it.

Next, we write a description for each user story. Descriptions are still simple and user-focused, but they go into a bit more detail. If the story is that the user should be able to fill out a form, the description tells us what form fields the user should see on the screen, and what she should see after she submits the form. These descriptions help guide us as we're designing solutions, but they also tell our developers (and more importantly, our QA testers) what "done" means. Occasionally as we're writing descriptions we'll discover additional use cases that weren't captured in the original wireframes, and we'll update the wireframes to match.

Finally, we briefly describe the solution we're proposing for each user story. Do we need to create a new content type? Build a view? Install a module? The solutions usually start fairly simply in the technical plan, but once we import the stories into our project tracking system, Pivotal Tracker, we'll start adding much more detail, including acceptance criteria and QA testing instructions. For any particular story, we usually write these detailed specs during the sprint before we actually start development on that story.

For the new 4SiteStudios.com site, most of our stories are pretty straightforward. We probably could have even built the site in Wordpress, but why would we want to do that? :) And since we're building the new site on top of our install profile, 4Site Hub, a lot of user stories (particularly stories for content editors and administrators) were already addressed in the tech plan for that project. As we go through the development phase, we'll test the 4Site Hub stories too, to make sure we haven't introduced any regressions.

The second tab of the technical plan outlines all of the content types we'll need on the site. We already started this work in the content plan, but the tech plan goes into much more detail. We capture all of the fields we need, the field type for each, whether it's required, and how it will be displayed. If the content type is based on one in 4Site Hub, we describe how we'll capture the changes—will we create a feature override, or just build a new feature? The third tab captures similar information for our taxonomy vocabularies. The final tab captures all of the modules, features, and third-party libraries we'll need for the project. For Hub-based projects, we always look for features and modules that are part of the standard installation that can be disabled.

Now that we have a plan for how we're going to proceed, we're ready to spin up a development environment and start building!

If you want to get a look at the tech plan for our new website, look below.

Technology Plan for new 4SiteStudios.com from 4sitestudios

It's the DrupalCon Portland Floor Show! I went around the exhibitors' area and through the halls of the Oregon Convention Center asking two vital questions to our community: What is your favorite thing about Drupal? Why should other people come to DrupalCon?

drupalcon_portland_floorshow_final.mp3

Let me preface this blog by stating the following facts about myself. I come from advertising. This was my first Drupalcon. I was attending on a severely sprained ankle and had left my fiancé (now wife) at home just two weeks before our wedding. Needless to say on my shaky flight to a city that is stuck with a perpetual rain cloud over it, my mind was not focused on Drupal.

A month or so ago the Drupalize.Me team started a discussion on how to start helping others learn Drupal 8. We knew Drupal 8 wasn't ready for our typical curriculum and video production process, but thought you would be interested to learn along with us about Drupal 8 as it continues to evolve. This blog post is the kick off to that series. As we stated in a recent podcast where we announced this idea, we need everyone to understand that the things we discuss are still in development and could change, or even be removed from D8 altogether.

read more

This series outlines our project process through the lens of our development of the new 4SiteStudios.com. In this post, we will discuss our process for developing a creative direction for a client.

I’m coming up with a design for the new 4Site website following the same process and with the same deliverables as our clients’ sites. That means starting out with some conversations with the decision-makers (“the boss” - aka Heming - in this case) to figure out what kind of personality the company has and what kind of customers/clients/visitors the site will have. Because I’m so close to 4Site, I see so many design possibilities that it can become overwhelming to choose just one! This is where the reviews and multi-stage deliverables come into play. Where they help clients decide what design direction they’d like, the 4Site design deliverables help me and my team discuss internally what works and what can be improved.

I start out with style tiles to reflect a few different ideas based off of my discussions with the team, then create a component style guide to reflect all the changes we want to see and get an idea of what some individual pieces of the site  will look like. This part is a narrowing-down of the style tile directions, but often I need to combine elements from several tiles, which poses a challenge to create balance and proper visual hierarchy, and can often take longer than the style tile stage.

With the 4Site redesign, I spoke with Heming initially to figure out how we’d like to portray ourselves as a company. We had just released our new logo, which is a minimalist version of our old logo, to be more modern and versatile. That now needs to be paired with the friendly, eclectic, historic feel of Columbia Heights, our neighborhood. Getting the clean, minimalist technology direction to mesh well with the artsy, hip aesthetic was definitely challenging. The first round of design (the style tiles) covered the gamut of ‘just clean,’ ‘clean and eclectic,’ and ‘just eclectic.’ Then, going into the component style guide after getting everyones thoughts and feedback, I had to come up with the real combo.  I’m pretty sure I had a few dreams about it, and every time I walked up 14th to the office I’d see something new to include in the design. It took a long time to come up with which elements should reflect which parts of our company, as well as showcase our work, but in the end we all were very happy with the results.

The component style guide wound up being a reflection of who we are as a company, and the type of work we do. We work primarily with non-profits and like to think of ourselves as “do-gooders,” so we have a lot of inviting textures. Our roots are as a design and creative services company, so we have some playful fonts here and there. And finally, because we’re pretty tech-savvy (geeky!), and are on the cutting-edge of web design and development, we have a clean, open, airy feel. A few Victorian accents add the Columbia Heights feel (since the modern elements are already covered with the other aesthetics). And... voila! There’s our concept for the new 4Site website theme.

Our style tiles and component style guide are working documents that inform our design mockups. Below is the component style guide for the new website. Let us know what you think!

New 4SiteStudios.com Component Style Guide from 4sitestudios

Thanks to everyone who stopped by the Commerce Village at DrupalCon Portland to drink, see demos, and meet the folks who make Drupal Commerce thrive. We had some great sessions, too, both in our Village Square and in the main conference.

If you couldn't make it, don't worry: we recorded all the sessions and have posted them to our site. And although there were some only-at-DrupalCon opportunities, home-schooled Drupalistas won't remain empty-handed! Read on....

View all Sessions

It takes a (Commerce) Village

First we once again want to thank our attending Service Providers for making DrupalCon — and Drupal Commerce itself — such a success. The feedback throughout the village from attendees was amazing. Everyone told us they learned a lot from each of our providers and they, in turn, got to meet so many of their userbase face-to-face... and introduce potential users to their solutions.

...and did you get to see Commerce Platform?

The big Commerce Guys news from the show was Commerce Platform, our new cloud-based hosting solution for smarter development.

You can see what's coming by checking out Damien and Robert's Commerce Platform demo and then request to be part of the private beta. Platform's unique architecture gives site-builders unprecedented flexibility to create and control their sites. (Believe us, you'll want to watch the demo.)

… and did you talk to us about our *New* Delivery Partner Program?

There are lots of opportunities for creating and running Drupal Commerce sites, and we need your help!

Mike O'Connor talked about our Drupal Commerce Delivery Partner Program, and we had a chance to speak to many of you. But if you're an experienced Drupal development company and have an interest in growing your eCommerce practice... and you're not yet on our list, Get in Touch with us to start getting the leads, co-marketing, and support you need to expand into this fast-growing field.

There's always something exciting happening at Commerce Guys. As always, stay in touch with us through Twitter, Facebook, or join our mailing list. See you in Prague in September... and in Austin for DrupalCon 2014

Tags: drupalcon portlandcommerce villagePlanet Drupal

Topic: Drupal

Drupal Developer Days is a great tradition in Europe to provide space for developers and site builders to get together in the summer. After such prior locations as Barcelona and Brussels, the Drupal Developer Days is coming to Dublin this year!

The conference program includes great sessions on security, project management, automation, multilingual, mapping, REST, continuous integration and so on! Lots of opportunities to learn about Drupal and the entry ticket is only €25.

The event is also ideally timed to coincide with the last days before Drupal 8's API freeze. There is a whole weeklong sprint included for those who want to work on solving major and critical issues as well as any patches still viable before API freeze. If you are still to take your first steps to contribute, the Community Tools Workshop is for you to delve into giving back.

There will be a recruitment event there too, so when you register make sure to say that you're looking for a job. Acquia will be there so come talk with us about the work we do if you are interested in joining!

To revert all features ..

drush fra -y drush cc all

To revert a specific feature..

drush fr -y feature drush cc all

If a feature has been overridden, it can be reverted. This means that the version in the database is destroyed and the version defined in code, in your feature, is used.

If you're deploying code to one of you servers you would ..

git pull drush fra -y drush cc all

To update your feature ..

drush fu -y feature drush cc all

Updating an overridden feature will ensure that the version of the feature defined in code is made to match the version stored in the database.

A feature is overridden when a user uses the UI to make configuration changes. These changes are stored in the database, and override what is stored in code.

Tags: featuredrushdrupalplanet Tweet

Weblate is now year and half old, has quite many users and almost all features I wanted it to have. Now it's time to push it further to fit also other projects.

Therefore I've decided to try crowdfunding on Catincan to see which of requested features are actually wanted most. Yes, you can vote with your money :-).

The first set of features to fund is:

• Federated login using Facebook, Google, GitHub etc.
• Source strings tracking to improve experience for developers with source strings changes or prioritization
• Voting for suggestions to better support larger translation teams

This is my first experiment with crowdfunding, so I'm looking forward to it's results.

Filed under: English Weblate | 0 comments | Flattr this!

Another maintenance release of inline is now on CRAN and in already included in Debian. This release was triggered by a change in the development version of R which removed an argument to package.skeleton(). The complete NEWS entry is below. Changes in inline version 0.3.12 (2013-06-12)

• Align package.skeleton with the R-devel version of the function which no longer has a NAMESPACE argument.

• Remove copy of LGPL in source archive as R CMD check now complains about it. License status continues to be specified in file DESCRIPTION.

Courtesy of CRANberries, there is also a diffstat report for the most recent release. A few more details are available at the R-Forge page.

Completed Drupal site or project URL:  http://Georgia.gov