Wait! March already? Where did December go?
Is it too late to wish you all a happy new year? Probably. Yes…
However, it’s not to later to deliver a Happy 2017!!
A lot of releases, right? Indeed. We have switched to releasing more often, and we try to deliver as many bug fixes as possible as quickly as possible. Thank you all for your bug reports, and as always thank you for including screenshots which make it easy for us to narrow down on the problem much quicker.
Now let’s not forget new features! 6.8.x was packed with new features and the recently released 6.9.0-beta adds another layer. 6.9.1 is also just around the corner with some more.
Here are a few of our favorite new features added in 6.8 and 6.9:
Next stop: 6.9.1! And that’s a loaded one! Stay tuned! ;)
Over the last few years, many of us have seen the need to evolve community governance. Up until now, we had to focus on other priorities, but now is the time to address our needs for community governance especially in light of recent community events.
Our project has matured greatly and participation has expanded from developers and site builders to also include more content editors, designers, and marketing managers who work not only as freelancers or at Drupal shops, but also for large digital agencies or system integrators. We want all community members to be included in these community discussions so the redefined community governance serves everyone. This is an exciting time to create an even healthier future for our ever-growing community.
The Drupal Association is committed to staying in a support role as the community determines how to best evolve community governance to support everyone’s needs. We started helping by hosting Community Discussions that were mediated by Whitney Hess. There were 7 sessions at DrupalCon Baltimore and 7 virtual sessions between April and May. You can find the meeting minutes here.
The Community Discussions surfaced several common needs and identified several strategies for addressing those needs.
The most commonly shared needs of the community are (in order of frequency):
Strategies to address those needs ranged from clarifying the responsibilities and boundaries of the leadership roles throughout the Drupal project, determining how and where to communicate community decisions, improving processes for community management, and providing easier access to documentation about leadership roles and clearly communicating what is expected of Drupal community members.
In terms of next steps, the participants were in agreement that we need to come together in a Governance Summit to start architecting improvements to today’s governance structure. However, the community did not define the best way to hold this meeting. It is still unclear when and where it should be, and who should participate and facilitate. We will send out a community survey next to get input from you to answer these questions.
We invite to you attend a webinar on July 6 at 11 am ET / 1600 BST / 8:30 pm IST hosted by Whitney Hess. Whitney will review the findings from our Community Discussions in more detail. We will record the video and share it with you afterwards, along with a written transcript.
Dial in details are below:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 589 988 397
International numbers available:
Thank you for your patience and participation as we tackle these big questions and move forward together as a stronger community.
Over the past months there has been a significant amount of people who have become more and more involved with e107. This is great news and highly appreciated!
In order to stimulate and facilitate collaboration among all volunteers, e107 tries to offer the best platforms given the restraints in resources such as time and money. As a first step, the organisation of the e107 translations has recently undergone some changes. More improvements to other areas will follow in due time.
Thanks to our volunteers in the community, great efforts have been made to publish language packs for the latest releases of e107. To further support and coordinate the development of language packs, a new Github organisation has been created: ‘e107translations’. This organisation houses the official translations of e107.
Translators are strongly encouraged to use this platform so all translations can be effectively managed and published. Each translation team has the freedom to decide how they would like to manage their specific translation and are not bound to use the Github organization for the development process. However, to be recognised as an official language pack, the final version of each language pack has to be uploaded to the Github repository.
To clarify, each translation team can choose how they want manage their own translation. This means that if you are using another way to create your language pack, you can continue to do so. Only the final version of a translation needs to be uploaded to the Github organisation.
In case you or your team are already using your own Github repository, it can be easily transferred directly into the e107translations organisation while maintaining all existing data as well as all ownership rights that you had previously. The change is purely meant to make sure all translations are stored in one place as this enhances coordination and facilitates collaboration among all translators and volunteers.
Using this platform has numerous advantages, including:
If you are currently translating e107 into a specific language and you already have translated previous versions, please get in touch with me (Moc). The best way to contact me is through Gitter but you can also send me an email on moc [at] e107.org. This way we can exchange the necessary information and provide you with the appropriate permissions for the Github repository to allow you to manage the translation in however way you want to.
If you are interested in contributing to a particular translation which is currently not available or not finished, please contact the coordinator for the specific language that is being translated into. A full list of the all the teams can be found on the organisation's team's page. If you cannot find the coordinator, please contact me. If the team is using Github repositories, you can easily contribute by submitting so-called pull requests. More info on those can be found through the links which are added at the end of this post.
Once again, thank you community for providing the currently available translation of e107. Being able to use e107 in your own language stimulates the growth of e107 across borders and should be highly valued.
Feedback on the changes that were made is greatly appreciated. Please join in our Gitter chatroom to have a chat. This is also the place to go to if you have any questions about the new translation organisation structure.
To learn more about how Github works and to find more information on the translation standards of e107, please check the following links:
Thanks again, and see you soon.
The Geeklog DokuWiki Plugin v1.9.0 is now available for download.
The DokuWiki Integration Plugin for Geeklog provides an integration with your Geeklog v2.1.1+ website. This plugin is based on DokuWiki 2016-06-26a "Elenor of Tsort", ” which is the latest release at the time of this writing.
If you find any bugs or wish to request a feature, please add them to our issues tracker.
Joomla! 3.7.2 is now available. This is a bug fix release for the 3.x series of Joomla. This release fixes some bugs in file mime checks, module page filtering as well as some other bugs and several other minor improvements.
This release only contains bug fixes that were inadvertently introduced in recent version and is focused on stabilising the 3.7 series by rectifying them.
Five Nights at Freddy's 4 is the fourth, and last (supposedly) release in the Five Nights at Freddy's saga. Developed and published by Scott Cawthon, this horror game has delighted all the fans of horror games, and has also raised the criticism from those that say that there are too many FNaF games. This time, you are not a security guard fighting for your life against creepy animatronics. Instead, you are a defenseless kid who struggles every night because of his terrifying nightmares (nightmares about creepy animatronics, of course).
Now, animatronics don't kill you, because they are just nightmares, but they can scare you as they have done since forever. Freddy, Bonnie, Chica, and Foxy have come back, and they have brought new nightmare friends with them. Also, the location is not an office anymore. It takes place in your own room, a room with a bed, two doors, and a dark closet. Each part of the room is dangerous since they are places where the animatronics can hide.
Moreover, the mechanics of the game have significantly changed compared to the previous tree installments in the saga. Now, you do not depend on your vision, or the cameras, because in this release, you don't have them. Now, you have to hear; you have to pay attention to every sound, breath, and laugh, because sound indicates where enemies will come from. It's recommended to play with earphones or with a very high volume. You are free to play with a regular sound volume, but you will not be able to hear your enemies.
As mentioned, the mechanics have changed. Now, you have nothing more than your senses and a flashlight to defend yourself. You have to control both doors, the closet, and the bed behind you. Animatronics can appear in any of the four places. What you have to do is walk bravely to the doors and the closet, listen carefully and if you hear something, close the door as fast as you can and hold it shut until the sound disappears. In case you don't hear anything, use the flashlight to prevent enemies from coming. The bed at your back has a little Freddy fluffy toy, but sometimes dreadful miniature Freddy's appear, followed by Nightmare Freddy himself. You have to shoo them with the flashlight unless you want Freddy to appear. It can seem easy, but the slightest mistake (using the flashlight when you hear a breath, or not closing the doors in time), will bring an end to the game.
Freddy, Bonnie, Chica, and Foxy have come back, and they have brought new nightmare friends with them
Talking about your friends the animatronics, when you download FNaF4, you will have to face six of them, eight if you take into account the "nonofficial" ones. You already know Freddy, Bonnie, Chica, and Foxy (nightmare version) but let me introduce you to Nightmare FredBear and Nightmare (plainly). All the animatronics in nightmare version are decrepit, broken, and especially scary. They have very long sharp teeth and glowing eyes, but Nightmare FredBear and Nightmare have even longer teeth, and they are very dangerous because they are unpredictable. This is especially true of Nightmare, since he is black and semi-transparent. They start appearing on nights 5 and 7, respectively.
In this version, you can check out the main features of Five Nights at Freddy's 4:
If you like this horror adventure, feel free to visit the developer's official website to discover all the features before you download it.
You can read here the minimum PC system requirements needed to download and play this game: