Elsewhere

Open Source Training: Help Us Create Free Drupal 8 Training Videos

Planet Drupal - Tue, 14/04/2015 - 22:44

Drupal 8 is just around the corner, and the Drupal community is excited!

We want to make sure that as many people as possible can use Drupal 8. However, many new Drupal 8 users will need training, which can be expensive and difficult to find.

So, we started a Kickstarter project to create Drupal 8 training and give it away for free!

Sounds intriguing? Watch the video to find out more ...

Categories: Elsewhere

Mediacurrent: Top Drupal 7 Modules: Final Edition

Planet Drupal - Tue, 14/04/2015 - 22:22

If you have been to the Mediacurrent blog before you have probably seen my Top 50 modules lists for Drupal 6 and 7. This current list will be my final update for Drupal 7. My last blog from 2012 was in dire need of updating so I have gone through one last time to give our readers my a good list of modules to start with for their next Drupal 7 site.

If you have visited Drupal.org recently you will notice that there are literally thousands of modules available to download. This can be very intimidating for new users who are just getting started building Drupal sites. The secret for newbies to know is that most developers continually use a few dozen of the same modules on almost every project.

As a 9 year veteran of Drupal I like to share my list of modules that I personally use on almost every site I build. If you are just getting started, this is a good list to begin with. If you are an intermediate or even an expert developer it can be helpful to skim the list to see if there are any modules that can help you on your next project.

Categories: Elsewhere

Mark Brown: Flashing an AT91SAM9G20-EK from bare metal

Planet Debian - Tue, 14/04/2015 - 20:04

Since I just had cause to do this and it was harder than it needed to be due to bitrot in the public documentation I could find I thought I’d write up how to get a modern bootloader onto older Atmel boards. These instructions are written for the AT91SAM9G20-EK though they should also apply to other Atmel boards of a similar generation.

These instructions are for booting from NAND since it’s the default thing for the board, for this J34 should be fitted to enable the chip select and J33 disconnected to disable the dataflash. If there is something broken programmed into flash then booting while holding down BP4 should cause the second stage bootloader to trash itself and ensure the ROM bootloader puts itself into recovery mode, or just removing both J33 and J34 during power on will also ensure no second stage bootloader is found.

There is a ROM bootloader but it just loads a small region from the boot media and jumps into it which isn’t enough for u-boot so there is a second stage bootloader called AT91Bootstrap. Download sources for current versions from github. If it (or a more sensibly written equivalent) is not yet merged upstream you’ll need to apply this patch to get it to build with a modern compiler, or you could use an old toolchain (which you’ll need in the next step anyway):

diff --git a/board/at91sam9g20ek/board.mk b/board/at91sam9g20ek/board.mk index 45f59b1822a6..b8251ca2fbad 100644 --- a/board/at91sam9g20ek/board.mk +++ b/board/at91sam9g20ek/board.mk @@ -1,7 +1,7 @@ CPPFLAGS += \ -DCONFIG_AT91SAM9G20EK \ - -mcpu=arm926ej-s + -mcpu=arm926ej-s -mfloat-abi=soft ASFLAGS += \ -DCONFIG_AT91SAM9G20EK \ - -mcpu=arm926ej-s + -mcpu=arm926ej-s -mfloat-abi=soft

Once that’s done you can build with:

make at91sam9g20eknf_uboot_defconfig make CROSS_COMPILE=arm-linux-gnueabihf-

producing binaries/at91sam9g20ek-nandflashboot-uboot-${VERSION}.bin. This configuration will look for u-boot at 0x40000 in the flash so we need a u-boot binary. Unfortunately modern compilers seem to produce binaries that fail with no output. This is normally a sign that they need the ABI specifying more clearly as above but I got fed up trying to spot what was missing so I used an old CodeSourcery 2013.05 release instead, hopefully future versions of u-boot will be able to build for this target with older toolchains. Grab a recent release (I used 2015.01) and build with:

cd ${UBOOT} make at91sam9g20ek_nandflash_defconfig make CROSS_COMPILE=arm-linux-gnueabihf-

to get u-boot.bin.

These can then be flashed using the Atmel flashing tool SAM-BA. Start it and connect to the target (there is a Linux version, though it appears to rely on old versions of TCL/TK so if you get trouble starting it the easiest thing is to use the sacrificial Windows laptop you’ve obtained in order to run the “entertaining” flashing tools companies sometimes provide without risking a real system, or in my case your shiny new laptop that you’ve not yet installed Linux on). Start it then:

  1. Connect SAM-BA to the device following the dialog on start.
  2. Make sure you’ve selected “NandFlash” in the memory type tabs in the center of the window.
  3. Run the “Enable NandFlash” script.
  4. Run the “Erase All” script.
  5. Run the “Send Boot File” script and provide the at91bootstrap binary.
  6. Set “Send File Name” to be the u-boot binary you built earlier and “Address” to be 0x40000.
  7. Click “Send File”
  8. Press the reset button

which should result in at91bootstrap output followed by u-boot output on the serial console. A similar process works for the AT91SAM9263, there the jumper you need is J19 (sadly u-boot does not flash pictures of cute animals or forested shorelines on the screen as the default “Basic LCD Project 1.4″ firmware does, I’m not sure this “full operating system” thing is really delivering improved functionality).

Categories: Elsewhere

Red Crackle: Working With The Drupal Google Analytics Module

Planet Drupal - Tue, 14/04/2015 - 20:00
This article helps you install the Drupal Google Analytics module. Go through the accompanying screenshots to enable and configure the module for your Drupal 7 site. We will show you how to deploy the Tracking ID for your site. We will be going through the different options you will come across while enabling this module. At the end of the article, we will show how Drupal Google Analytics works with real-time examples. We hope this article lays the foundation for your site to generate valuable insights day in, day out.
Categories: Elsewhere

Drupal Watchdog: Ready To Learn

Planet Drupal - Tue, 14/04/2015 - 18:32
Feature

Drupal 8 is right around the corner; it's time to start brushing off your old textbooks, taking notes, asking questions, and preparing for all the awesomeness coming your way.

For most of us, Drupal 8 represents a departure from what we've come to know about how to create with Drupal. In short, we've got a learning curve we're going to have to overcome before we can be proficient with Drupal 8. But I'm here to tell you: it’s okay, we're in this together, and, given the proper learning environment and a little bit of guidance, you'll be Drupal 8 ready in no time.

In the glorious words of Douglas Adams, “Don't panic!”

While most of us have a tendency to want to jump right into the documentation and start poring over code samples, this is a good opportunity to take a step back and make sure we're ready to learn before we dive in. So let’s take a minute to think about education theory and the environment we put ourselves in when preparing to learn a new technology. How do we remove blockers from the learning process and set ourselves up for success?

Consider:

  • What is my motivation for learning this?
  • Where can I practice what I'm learning?
  • How will I know if I have learned the right thing?

How motivated are you?

Are you learning for fun, or for work?

Because you want to, or because you have to?

Our motivation – and our understanding of it – allows us to decide whether it is worth the investment in time and energy necessary to learn something new today – right now – which we may not use until tomorrow.

One of the best ways to assess whether or not you've learned something is to teach it to someone else. Lucky for you, you're not the only one embarking on the quest to learn Drupal 8; there are plenty of opportunities to share your new knowledge with others. Local user groups, co-workers – even friends on IRC – all represent great teaching opportunities. Moreover, these interactions often turn into discussions, and discussions are one of the best ways to get beyond the how and into the why.

Categories: Elsewhere

Drupal Association News: Announcing Our New Drupal Co-Marketing Initiative

Planet Drupal - Tue, 14/04/2015 - 17:35

Marketing is a key factor to growing Drupal adoption and spreading the goodness of Drupal. One way to do that is by exhibiting at key industry events. The CMS Garden team has done a great job getting Drupal included in some key events in Europe and now the Drupal Association will take on a parallel effort.

The initiative will be an experimental “co-marketing” campaign to promote Drupal in the European marketplace. It is called a “co-marketing” campaign because it will be crowdfunded by a group of Drupal businesses (if you would like to find out how your Drupal business can get involved, keep reading). This is a pilot program that will allow us to experiment with the best ways to promote Drupal in the global marketplace and reach the CMS evaluator audience.

Why Europe? Data from our DrupalCon surveys show that relative to DrupalCon North America, DrupalCon Europe has a higher percentage of developer attendees but a lower percentage of CMS “evaluator” attendees. From that standpoint, it makes sense to target Europe evaluators in this pilot program. The evaluators we are targeting in the pilot program are digital marketers who have significant sway over CMS selection.

So what’s the plan?

This year, Drupal Association will secure exhibit space at two European digital marketing industry events (dmexco in Germany and Festival of Marketing in the UK). We will exhibit as Drupal and together with representatives from the anchor sponsors who have already signed on (including Wunderkraut (Germany), Wunder (UK) and Deeson (UK), we will promote Drupal and the sponsoring companies’ expertise and successes with Digital Marketing and Drupal. Leads generated from the exhibit presence will go to the sponsoring companies. We are offering first right of refusal to sponsor the effort to Drupal Premium Supporting Partners, followed by other Supporters.

Why these two events? There are many events in Europe that target the audiences we want to reach. After researching attendee types, costs and other factors, we determined the abovementioned events make the most sense for this pilot project.

If you would like to learn more about how your business can participate in this exciting initiative, please contact Johanna Bergmann. johanna@association.drupal.org.

Categories: Elsewhere

Blink Reaction: Free as in Training. Blink Launches Free Drupal Training Initiative

Planet Drupal - Tue, 14/04/2015 - 16:43

Blink Reaction has announced it has begun to offer free live public Drupal training online, in NYC and in other major markets.The free classes will focus on Drupal 8 adoption and will include Site Building classes formerly offered at $799.

Announcing the decision to offer free Drupal training, Blink CEO Nancy Stango explained the decision.

Building a robust Drupal ecosystem requires attention to all the things. We can’t just build great software. For many people formal training is the best way to learn and we need to lower obstacles to Drupal adoption everywhere. Providing this training free of charge on a regular schedule is part of our contribution back to the community.

Included in each free class listing is an appeal to support the Drupal Association by becoming a paid member.

Why is this class free?

Providing this class free of charge is one of the many ways we give back to the open source community. 

Blink is highly committed to helping organizations and individuals adopt Drupal successfully. At Blink we believe great training helps create great, results-oriented websites. That's a win-win-win for you, Drupal and Blink.

Please consider supporting the Drupal Association instead. Individual membership is only $15.

And if you’re interested in Developing for Drupal 8 register for our Drupalcon LA class, ‘Introduction to Symfony/Getting Ready for Drupal 8.’ Half of all proceeds goes to support the Drupal Association.

Blink has been delivering paid public training since 2011 through the Blink Institute and has offered free training during Global Drupal Training days since the start of the program. 

Visit our training pages for more information and to register for a free training.

If you’re interested in Developing for Drupal 8 register for our Drupalcon LA class, ‘Introduction to Symfony/Getting Ready for Drupal 8.’ Half of all proceeds goes to support the Drupal Association.

 

DrupalDrupal PlanetDrupal TrainingPost tags: Trainingdrupal 8
Categories: Elsewhere

Blink Reaction: Introduction to Symfony/Getting Ready for Drupal 8 Training at Drupalcon LA

Planet Drupal - Tue, 14/04/2015 - 16:19

After making it’s first Drupalcon appearance to a sold out crowd in Austin, I’m really excited to be offering an updated version of our class in LA. 

Since Austin we’ve offered the class in Drupalcon Amsterdam and Drupalcon Bogota. Each time it has been filled to capacity and tickets are already going fast for Drupalcon LA.

This year we’ve focused even more on the Symfony components that are most important for developing in Drupal 8.  We’re spending additional time in Drupal 8 too since we are oh so close to a release. 

The class will be led by Blink Drupal 8 Solutions Engineer Jesus Olivas, lead contributor on the Drupal Console project supported by Blink. Jesus will also share some of the latest new features he's built in the Console project. No fewer than eight Blink developers will be supporting Jesus so that we can give each and every participant a hands on experience.

Register for the class now on the Drupalcon LA site.

DrupalDrupal PlanetDrupal TrainingPost tags: drupal 8symfonyTraining
Categories: Elsewhere

Tag1 Consulting: Drupal Changed My Life - Will You Take My Drupal Commit Challenge

Planet Drupal - Tue, 14/04/2015 - 16:00

I want to share two stories with you.

read more

Categories: Elsewhere

Drupal Watchdog: VIDEO: DrupalCon Amsterdam Interview: Holly Ross

Planet Drupal - Tue, 14/04/2015 - 15:58

On a beautiful summerlike day at DrupalCon Amsterdam, we stop at the Drupal Association table, where we are introduced to DA Staff Members JOE SAYLOR, LEIGH CARVER, and RUDY GRIGAR. Then it’s on to HOLLY ROSS (Executive Director, Drupal Association). Erudite cameraman BOB WILLIAMS (Financial Manager, Tag1 Consulting) works the GoPro.

HOLLY ROSS: Yep, so we had a BoF for people who like to knit and are at DrupalCon and it was really great because we all worked on our projects, and we all talked about how we learned to knit. And what I love the most about the fact that there are so many knitters in Drupal is that – I love the relationship between knitting and coding – right? -- like pattern discernment and building – and all the things we talk about that we love about Drupal – it’s all there in knitting, too.

This one is really interesting to me because – well first of all, I’ll just share that we have 2,300 people here – 500 more than Prague. That’s a lot bigger.

What I am reading right now actually is a book called The Last Ship. I don’t recommend it – I hate it – it’s taking me months to read. I’m also concurrently reading a couple of Cory Doctorow books, because I was getting ready to come here and see Cory speak, so I’m reading Little Brother, which is a young adult novel he wrote, which is really really good. And I’m also reading right now, the uh – oh, what’s it called when all the people go to heaven except the bad people that are left on Earth?

RR: Left behind?

BOB WILLIAMS: The Rapture.

HR: The Rapture of the Nerds, that’s it, The Rapture of the Nerds, yeah.

Tags:  DrupalCon DrupalCon Amsterdam Video Video: 
Categories: Elsewhere

Neil Williams: Extending an existing ARMMP initramfs

Planet Debian - Tue, 14/04/2015 - 14:27

The actual use of this extension is still in development and the log files are not currently publicly visible, but it may still be useful for people to know the what and why …

The Debian ARMMP kernel can be used for multiple devices, just changing the DTB. I’ve already done tests with this for Cubietruck and Beaglebone-Black, iMX.53 was one of the original test devices too. Whilst these tests can deploy a full image (there are examples of building such images in the vmdebootstrap package), it is a lot quicker to do simple tests of a kernel using a ramdisk. The default Debian initramfs has a focused objective but still forms a useful base for extension. In particular, I want to be able to test one initramfs on multiple boards (so multiple dtbs) with the same kernel image. I then want to be able, on selected boards, to mount a SATA drive or write an image to eMMC or a USB stick or whatever. LAVA (via the ongoing refactoring, not necessarily in the current dispatcher code) can automate such tests, e.g. to allow me to boot a Cubietruck into a standard Debian ARMMP armhf install on the SATA drive but using a modified (or updated) ARMMP kernel over TFTP without needing to install it on the device itself. That same kernel image can then be tested on multiple boards to see if the changes have benefitted one board at the expense of another. Automating all of that could be of a lot of benefit to the ARM kernel developers in Debian and outside Debian.

So, the start point. Install Debian onto a Cubietruck – in my case, with a SATA drive attached. All well and good so far, standard Debian Jessie ARMMP. (Cubietruck uses the LPAE kernel flavour but that won’t matter for the initramfs.)

Rather than building the initramfs manually, this provides a shortcut – at some point I may investigate how to do this in QEMU but for now, it’s just as quick to SSH onto the Cubietruck and update.

I’ve already written a little script to download the relevant linux-image package for ARMMP, unpack it and pull out the vmlinuz, the dtbs and a selected list of modules. The list is selective because TFTP has a 32Mb download limit and there are more modules than that. So I borrowed a snippet from the Xen folks (already shown previously here). The script is in a support repository for LAVA but can be used anywhere. (You’ll need to edit the package name in the script to choose between ARMMP and ARMMP LPAE.

Steps
  1. Get a working initramfs from an installed device running Debian ARMMP and copy some files for use later. Note: use the name of the symlink in the copy so that the file in /tmp/ is the actual file, using the name of the symlink as the filename. This is important later as it saves a step of having to make the (unnecessary) symlink inside the initramfs. Also, mkinitramfs, which built this initrd.img file in the first place, uses the same shared libraries as the main system, so copying these into the initramfs still works. (This is really useful when you get your ramdisk to support the attached secondary storage, allowing you to simply mount the original Debian install and fixup the initramfs by copying files off the main Debian install.) The relevant files are to support DNS lookup inside the initramfs which then allows a test to download a new image to put onto the attached media before rebooting into it. cp /boot/initrd.img-3.16.0-4-armmp-lpae /tmp/ cp /lib/arm-linux-gnueabihf/libresolv.so.2 /tmp/ cp /mnt/lib/arm-linux-gnueabihf/libnss_dns.so.2 /tmp/

    Copy these off the device for local adjustment:

    scp IP_ADDR:/tmp/FILE .
  2. Decompress the initrd.img: cp initrd.img-3.16.0-4-armmp-lpae initrd.img-3.16.0-4-armmp-lpae.gzip gunzip initrd.img-3.16.0-4-armmp-lpae.gzip
  3. Make a new empty directory mkdir initramfs cd initramfs
  4. Unpack: sudo cpio -id < initrd.img-3.16.0-4-armmp-lpae
  5. Remove the old modules (LAVA can add these later, allowing tests to use an updated build with updated modules): sudo rm -rf ./lib/modules/*
  6. Start to customise - need a script for udhcpc and two of the libraries from the installed system to allow the initramfs to do DNS lookups successfully. cp ../libresolv.so.2 ./lib/arm-linux-gnueabihf/ cp ../libnss_dns.so.2 ./lib/arm-linux-gnueabihf/
  7. Copy the udhcpc default script into place: mkdir ./etc/udhcpc/ sudo cp ../udhcpc.d ./etc/udhcpc/default.script sudo chmod 0755 ./etc/udhcpc/default.script
  8. Rebuild the cpio archive: find . | cpio -H newc -o > ../initrd.img-armmp.cpio
  9. Recompress: cd .. gzip initrd.img-armmp.cpio
  10. If using u-boot, add the UBoot header: mkimage -A arm -T ramdisk -C none -d initrd.img-armmp.cpio.gz initrd.img-armmp.cpio.gz.u-boot
  11. Checksum the final file so that you can check that against the LAVA logs. md5sum initrd.img-armmp.cpio.gz.u-boot

Each type of device will need a set of modules modprobed before tests can start. With the refactoring code, I can use an inline YAML and use dmesg -n 5 to reduce the kernel message noise. The actual module names here are just those for the Cubietruck but by having these only in the job submission, it makes it easier to test particular combinations and requirements.

- dmesg -n 5 - lava-test-case udevadm --shell udevadm hwdb --update - lava-test-case depmod --shell depmod -a - lava-test-case sata-mod --shell modprobe -a stmmac ahci_sunxi sd_mod sg ext4 - lava-test-case ifconfig --shell ifconfig eth0 up - lava-test-case udhcpc --shell udhcpc - dmesg -n 7

In due course, this will be added to the main LAVA documentation to allow others to keep the initramfs up to date and to support further test development.

Categories: Elsewhere

ERPAL: 3 things to consider when creating project specifications

Planet Drupal - Tue, 14/04/2015 - 12:45

In the last part of our series, we talked about "Agile work at a fixed price". We realized that detailed requirements in terms of a project specification are the key to agile management of fixed-price projects. Today, we’ll deal with those project specifications.

A “specification” describes the results or certain milestones of a project. Thus, it defines what we have to measure in order to find out whether the project is finished, that is: either the requirements are fulfilled – or they’re not. This point harbors the greatest potential for conflict! Neither restrictive contracts nor other contractual pieces of art can help here. Only when both parties know exactly what has to have been implemented by the end of the project, can you:

  • Show, prove, demonstrate and understand that everything that should have been done has actually been done
  • Check whether a new request is indeed new during the project
  • Find out whether changes have negatively affected the software (change management and risk management)

Using some negative examples of a specification, I’ll try to demonstrate what to avoid during a project.

1) Avoid ambiguous wording in your specifications

"We integrate social media functions." What does that really mean? The developer may understand this to include a Facebook Like button, a Google +1 button and a Tweet this button. In fact, what the customer would like is to have a portal for his Facebook app. It’s purely a matter of interpretation what social media functions really are and how they should be integrated. Always check that your requirements are clear and without ambiguous wordings.

2) Avoid comparisons

"We implement web pages with the same functions as those of awesome-competitor.com." No one knows exactly which functions the competitor’s websites possess in detail. Here again, two different expectations would collide at the end of the project. As provider, you don’t know for sure what features are implemented in the backend. However, if you agree to the statement above, then you must provide these functions. Arguing after the fact with statements like "But I didn’t know that..." doesn’t suffice. The extra costs can be enormous! So, avoid comparisons with other systems in your specification. This might save time in the beginning, but at the end of the project one of the parties could have over twice the expected expenses, which would no longer be controllable.

3) Write clear definitions

"We import the current data of the previous software." The data format for new software is usually not the same as for the previous version. Here, it’s important to clarify how the import should take place. Which old fields should be mapped to which new fields? Which validations should be processed, and, most importantly, what does the data format of the previous version look like, exactly, and how can you get this data and map it to the new structure? Clarify these points up front in order to avoid explosive increases in the effort required. In this case, it’s hard to argue using experience from past projects, because it implies that imports in previous projects are similar to the case at hand, which may be true – but usually isn’t. "We implement ... according to the usual ..." What’s usual here and who defines what’s normal? Make absolutely clear that both parties are talking about the same thing. Otherwise, two worlds will again clash over their differing expectations, which can be difficult to reconcile. Instead, refer to or quote the text that clearly defines "... the usual ..." and the requirements. Then everyone involved knows what the wording means.

There are countless other formulations that you should avoid. However, the above are the most common. A detailed engineering of requirements is always a good investment for both project parties to provide a solid basis for project success. Additionally, relevant user stories with related acceptance criteria can help to clarify the project deliverables.

Incorrect specification happens!

Specifications are wrong if they don’t serve the overall project goal. A short example: the sales manager of a company orders an app to support the sales team. The software is developed according to his requirements. However, it can’t be imported because no one involved the sales team and asked them for their requirements. Take the conditions of each case into account: nothing is more dissatisfying for both sides than fully-developed software that can’t be used because it doesn't deliver value to the users or the company as a whole. You should pay attention to these conditions right at the start of the project, both as a supplier and as a customer. During the analysis of requirements, involve all the stakeholders. Finally, the specification also serves to keep the documentation effort low, because it has already described what the final product looks like. It also provides for good planning and systematic change management to ensure that the software is stable. Imagine you’re building a house and want to combine the kitchen and the living room. For this, you only need to remove one wall. However, if this is a load-bearing wall, the floor above will collapse onto your head as the whole house caves in. This should be prevented at all costs, so be attentive and take all the challenges listed into account!

In the next part in our series, we examine responsibilities and communication in projects.

Other blog posts of this series:

These 3 questions help you to ensure satisfactory project results

Setting objectives in projects with these 3 rules

Agile projects for a fixed price? Yes you can!

Categories: Elsewhere

Steindom LLC: Sorting a view by a list field's allowed values

Planet Drupal - Tue, 14/04/2015 - 11:52

There's a neat feature in MySQL which lets you sort a result set by arbitrary field values. It's the ORDER BY FIELD() function. Here's how to leverage this in your Drupal views.

Let's say you have a field in your Article content type called Status, and it has the following allowed values:

Draft
Pending Approval
Published
Postponed
Canceled

It can be very helpful to sort the articles by status. You could key your allowed values with alphabetical prefixes, numbers, etc. But let's say you didn't. Or don't want to.

With bare MySQL, the query would look something like this (not an actual Drupal query, but used to illustrate how FIELD() works):

SELECT *
FROM articles
ORDER BY FIELD(status, 'Draft', 'Pending Approval', 'Published', 'Postponed', 'Canceled')

This is now possible in Drupal & Views with the Views List Sort module, which creates a sort handler that populates the FIELD() sort with the allowed values of a given "List (text)" field.

To use it is easy, just add the "List (text)" field to your sort criteria, and set "Sort by allowed values" to "yes".

Submitted by Joel Stein on April 14, 2015.Tags: Drupal, Drupal 7, Drupal Planet
Categories: Elsewhere

J-P Stacey: Safe, performant generation of a unique Drupal username

Planet Drupal - Tue, 14/04/2015 - 10:53

There are examples out there for generating a unique Drupal username. The usual technique is to continue incrementing a numeric suffix until an unused name is found. There's also a project to automatically generate usernames for new users. All of this makes sense and works, but compared to the existing solutions, I wanted one that focussed on encapsulation and stability; by which I mean it should:

Read more of "Safe, performant generation of a unique Drupal username"

Categories: Elsewhere

Rapha&#235;l Hertzog: Freexian’s report about Debian Long Term Support, March 2015

Planet Debian - Tue, 14/04/2015 - 10:37

Like each month, here comes a report about the work of paid contributors to Debian LTS.

Individual reports

In February, 61 work hours have been equally split among 4 paid contributors. Their reports are available:

The remaining hours of Ben and Holger have been redispatched to other contributors for April (during which Mike Gabriel joins the set of paid contributors). BTW, if you want to join the team of paid contributors, read this and apply!

Evolution of the situation

April has seen no change in terms of sponsored hours but we have two new sponsors in the pipe and May should hopefully have a few more sponsored hours.

For the need of a LTS presentation I gave during the Mini-DebConf Lyon I prepared a small graph showing the evolution of the hours sponsored through Freexian:

The growth is rather slow and it will take years to reach our goal of funding the equivalent a full time position (176 hours per month). Even the intermediary goal of funding the equivalent of a halt-time position (88h/month) is more than 6 months away given the current growth rate. But the perspective of Wheezy-LTS should help us to convince more organizations and hopefully we will reach that goal sooner. If you want to sponsor the project, check out this page.

In terms of security updates waiting to be handled, the situation looks similar to last month: the dla-needed.txt file lists 40 packages awaiting an update (exactly like last month), the list of open vulnerabilities in Squeeze shows about 56 affected packages in total (2 less than last month).

Thanks to our sponsors

The new sponsors of the month are in bold (none this month).

No comment | Liked this article? Click here. | My blog is Flattr-enabled.

Categories: Elsewhere

Mario Lang: Bjarne Stoustrup talking about organisations that can raise expectations

Planet Debian - Tue, 14/04/2015 - 10:13

At time index 22:35, Bjarne Stroustrup explains in this video what he thinks is very special about organisatrions like Cambridge or Bell Labs. When I just heard him explain this, I couldn't help but think of Debian. This is exactly how I felt (and actually still do) when I joined Debian as a Developer in 2002. This is, what makes Debian, amongst other things, very special to me.

If you don't want to watch the video, here is the excerpt I am talking about:

One of the things that Cambridge could do, and later Bell Labs could do, is somehow raise peoples expectations of themselves. Raise the level that is considered acceptable. You walk in and you see what people are doing, you see how people are doing, you see how apparently easily they do it, and you see how nice they are while doing it, and you realize, I better sharpen up my game. This is something where you have to, you just have to get better. Because, what is acceptable has changed. And some organisations can do that, and well, most can't, to that extent. And I am very very lucky to be in a couple places that actually can increase your level of ambition, in some sense, level of what is a good standard.
Categories: Elsewhere

Michal &#268;iha&#345;: Hacking Gammu

Planet Debian - Tue, 14/04/2015 - 08:30

I've spent first day of SUSE Hackweek on Gammu. There are quite many tasks to be done and I wanted to complete at least some of them.

First I started with the website. I did not really like the old layout and aggressive colors and while touching it's code it's good idea to make the website work well in mobile devices. I've started with conversion to Bootstrap and It turned out to be quite easy task. The next step was making the pages simpler as in many places there was too much information hidden in sidebar. While doing content cleanup, I've removed some features which really don't make much sense these days (such as mirror selection). Anyway read more in the news entry on the site itself.

Second big task was to add support for Python 3 in python-gammu. It seems that world is finally slowly moving towards Python 3 and people started to request python-gammu to be available there as well. The porting itself took quite some time, but I've mostly completed it before Hackweek. Yesterday, there was just some time spent on polishing and releasing standalone python-gammu and Gammu without python bindings. Now you can build python-gammu using distutils or install it using pip install python-gammu.

Filed under: English Gammu python-gammu SUSE Wammu | 0 comments

Categories: Elsewhere

Pages

Subscribe to jfhovinne aggregator - Elsewhere