archive-org.com » ORG » D » DRUPALBG.ORG

Total: 901

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Последни публикации | Drupal BG
    с продукти но да не е онлай магазин още Последни коментари JAVA SCRIPT FILE NAME може преди 2 седмици 4 дни Благодаря много за помощта и преди 2 седмици 6 дни Може да ползваш модула JS преди 2 седмици 6 дни Може да ползваш и модул Code преди 3 седмици 2 дни Препдолагам става дума за преди 3 седмици 2 дни Виж тези линкове първият е преди 4 седмици 2 дни Здравейте Изпратих следните преди 8 седмици 19 часа Здравейте Във връзка с преди 8 седмици 19 часа Здравей по добре пробвай с преди 11 седмици 5 дни Уважаеми dimitur90 бих преди 14 седмици 1 ден Кой е онлайн В момента са 0 потребители и 1 гост online Гласуване Колко тестови Друпал сайта имате 1 5 бр 56 5 10 бр 16 10 15 бр 9 15 20 бр 3 20 30 бр 3 30 40 бр 3 40 50 бр 3 над 50 бр 6 Общо гласове 32 2 коментара По стари анкети Разпространи Loading Начало Последни публикации Тип Публикация Автор Отговори Последно обновени Тема във форум как да впиша код в HEAD страницата Svetlio2009 5 преди 2 седмици 4 дни Тема във форум Тема или модул за сайт за Обяви zozi 1 преди 4 седмици 2 дни Тема във форум Превод на Друпал 8 mmomtcheva 0 преди 4 седмици 2 дни Тема във форум Commerce EPayBG sve 5 преди 8 седмици 19 часа Тема във форум Искам да направя сайт с продукти но да не е онлай магазин danits 0 преди 11 седмици 3 дни Тема във форум ПРОБЛЕМ с инсталирането на Drupal dimitur90 2 преди 11 седмици 5 дни Тема във форум epaybg wendi 88 0 преди 11 седмици 5 дни Тема във форум ubercart add product проблем wendi 88 0 преди 16 седмици 13 часа Тема

    Original URL path: http://www.drupalbg.org/tracker?destination=tracker (2016-02-15)
    Open archived version from archive

  • Демо | Drupal BG
    Добавяне на съдържание Добавяне на съдържание със картинки Задаване на резюме на съдържание Редактиране деактивиране на Primary links Създаване на ново меню URL псевдоними Настройка на категории Конфигуриране на сайта SEO checklisst Излязох от сайта и не мога да вляза Настройване на модула Nodewords Основно конфигуриране на сайта Главни настройки в Друпал 6 Как да даден администраторски права на други потребители Допълнително конфигуриране на сайта php ini за Drupal всички версии Категории с taxonomy и оптимизация с pahtauto от the end Други Основни термини в Drupal Как да качим превод на български в своята инсталация на Drupal Как да добавим PHP код в Друпал Фикс на анкетния блок от the end Форум как да си направим функционален Друпал 7 форум инсталиране и настройки на Advanced Forum and Author Pane Вход потребители Идентификация с OpenID Какво представлява OpenID Потребителско име Парола Идентификация с OpenID Отмени идентификацията с OpenID Създаване на нов акаунт Заявка за нова парола Активни теми във форума как да впиша код в HEAD страницата Тема или модул за сайт за Обяви Превод на Друпал 8 Commerce EPayBG Искам да направя сайт с продукти но да не е онлай магазин още Последни коментари JAVA SCRIPT FILE NAME може преди 2 седмици 4 дни Благодаря много за помощта и преди 2 седмици 6 дни Може да ползваш модула JS преди 2 седмици 6 дни Може да ползваш и модул Code преди 3 седмици 2 дни Препдолагам става дума за преди 3 седмици 2 дни Виж тези линкове първият е преди 4 седмици 2 дни Здравейте Изпратих следните преди 8 седмици 19 часа Здравейте Във връзка с преди 8 седмици 19 часа Здравей по добре пробвай с преди 11 седмици 5 дни Уважаеми dimitur90 бих преди 14 седмици 1 ден Кой е онлайн В момента са 0 потребители и 1 гост

    Original URL path: http://www.drupalbg.org/node/284?destination=node%2F284 (2016-02-15)
    Open archived version from archive

  • Planet Drupal | Drupal BG
    is more than one way to solve a particular problem by using contrib read more Категории Planet Drupal myDropWizard com What version of PHP does Drupal 6 need 12 Февруари 2016 17 36 The short answer is Drupal 6 officially supports only PHP 5 2 but you should use the highest version of PHP that doesn t break your site For the longer answer PHP 5 2 17 is the latest version of PHP in the 5 2 x branch of the popular programming language While there are several newer versions it s a safe bet that legacy code will operate under 5 2 17 However there are potential security holes with earlier versions of PHP Drupal 6 core should safely work on PHP 5 3 5 4 and 5 5 but you may have difficulties with modules that have not been kept active This is especially true of legacy Drupal 6 custom modules The right thing to do is to start with PHP 5 5 and work backwards until you hit a version that works with your needed modules Rarely should ever need to go as far back to PHP 5 2 In general newer versions offer better security The 5 2 x branch was end of lifed on the 6th of January 2011 That s more than 5 years ago at this writing Even though efforts on PHP 5 3 x and PHP 5 4 x are also discontinued development didn t halt until August 2014 and September 2015 respectively There have been Drupal security vulnerabilities that only exist when running Drupal on older versions of PHP With Drupal 6 nearing EOL there s no need to stack the deck against yourself if you are trying to attempt modernizing Also we recommend using Pressflow a fork of Drupal 6 core that has improved performance and better support for newer PHP versions Some brief notes on your PHP configuration Категории Planet Drupal Drupal core announcements Reminder Drupal 6 7 and 8 core security release window moved to February 24 12 Февруари 2016 16 28 This is an early reminder that this month s security release window for Drupal core which would normally be on the third Wednesday of the month is being moved to February 24 to avoid conflicting with DrupalCon Asia February 24 is also the end of life date for Drupal 6 so this will be the last security release window for Drupal 6 Категории Planet Drupal blog studio gd Drupal 8 Views Plugins Part 2 The display extender plugin 12 Февруари 2016 13 06 Let s see how and why to use a views display extender plugin Категории Planet Drupal Lullabot Drupal 8 Contrib Module Development with Dave Reid Juampy NR Andrew Berry 12 Февруари 2016 00 00 Matt Mike discuss Drupal 8 module development with Dave Reid Juampy NR and Andrew Berry onsite at the Lullabot retreat in Palm Springs CA Категории Planet Drupal Drupal core announcements 8 1 0 will be released April 20 beta begins March 2 11 Февруари 2016 23 58 Drupal 8 1 0 the next planned minor release of Drupal 8 is scheduled for Wednesday April 20 2016 Minor releases include new features usability improvements and backwards compatible API improvements Here s what this means for core patches Drupal 8 1 0 beta1 will be released March 2 In preparation for the minor release Drupal 8 1 x will enter a beta phase on March 2 Developers and site owners can begin testing the beta The 8 2 x branch of core will be created and future feature and API additions will be targeted against that branch instead of 8 1 x All outstanding issues filed against 8 1 x will be automatically migrated to 8 2 x once it is opened During the beta phase core issues will be committed according to the following policy Issues that are allowed for patch releases will be committed to all three minor branches 8 0 x 8 1 x and 8 2 x Issues specific to added 8 1 x functionality or disruptive changes that have a positive impact outweighing their disruption will be committed to both 8 1 x and 8 2 x Such issues can be moved back to the 8 1 x branch after the automatic migration Most issues that are only allowed in minor releases will be committed to 8 2 x only Drupal 8 1 0 rc1 will be released April 6 The release candidate phase for the minor release begins on April 6 and starting on that date the 8 1 x branch will be subject to release candidate restrictions with only critical fixes and certain other limited changes allowed April 6 is also the final scheduled patch release window for 8 0 x and it will not receive further development or support after that date aside from its final security release window on April 20 All outstanding issues filed against 8 0 x will be automatically migrated to 8 1 x after the final 8 0 x patch release Future bug reports should be targeted against the 8 1 x branch Minor versions may include changes to user interfaces translatable strings themes internal APIs like render arrays and controllers etc See the Drupal 8 backwards compatibility and internal API policy for details Developers and site owners should test the release candidate to prepare for these changes 8 2 x will remain open for new development during the 8 1 x release candidate phase See the Drupal core release cycle overview Allowed changes during the Drupal 8 release cycle and Drupal 8 backwards compatibility and internal API policy for more information As a reminder we have until the start of the beta to add great new features to Drupal 8 1 x and migrate usability and bugfixes are all priorities for 8 1 0 Категории Planet Drupal HollyIT Windows Vagrant WinNFSD Without File Update Problems 11 Февруари 2016 21 07 Categories Drupal Planet Drupal I have

    Original URL path: http://www.drupalbg.org/aggregator/sources/4 (2016-02-15)
    Open archived version from archive

  • Planet Drupal | Drupal BG
    more Категории Planet Drupal myDropWizard com What version of PHP does Drupal 6 need Planet Drupal 12 Февруари 2016 17 36 The short answer is Drupal 6 officially supports only PHP 5 2 but you should use the highest version of PHP that doesn t break your site For the longer answer PHP 5 2 17 is the latest version of PHP in the 5 2 x branch of the popular programming language While there are several newer versions it s a safe bet that legacy code will operate under 5 2 17 However there are potential security holes with earlier versions of PHP Drupal 6 core should safely work on PHP 5 3 5 4 and 5 5 but you may have difficulties with modules that have not been kept active This is especially true of legacy Drupal 6 custom modules The right thing to do is to start with PHP 5 5 and work backwards until you hit a version that works with your needed modules Rarely should ever need to go as far back to PHP 5 2 In general newer versions offer better security The 5 2 x branch was end of lifed on the 6th of January 2011 That s more than 5 years ago at this writing Even though efforts on PHP 5 3 x and PHP 5 4 x are also discontinued development didn t halt until August 2014 and September 2015 respectively There have been Drupal security vulnerabilities that only exist when running Drupal on older versions of PHP With Drupal 6 nearing EOL there s no need to stack the deck against yourself if you are trying to attempt modernizing Also we recommend using Pressflow a fork of Drupal 6 core that has improved performance and better support for newer PHP versions Some brief notes on your PHP configuration Категории Planet Drupal Drupal core announcements Reminder Drupal 6 7 and 8 core security release window moved to February 24 Planet Drupal 12 Февруари 2016 16 28 This is an early reminder that this month s security release window for Drupal core which would normally be on the third Wednesday of the month is being moved to February 24 to avoid conflicting with DrupalCon Asia February 24 is also the end of life date for Drupal 6 so this will be the last security release window for Drupal 6 Категории Planet Drupal blog studio gd Drupal 8 Views Plugins Part 2 The display extender plugin Planet Drupal 12 Февруари 2016 13 06 Let s see how and why to use a views display extender plugin Категории Planet Drupal Lullabot Drupal 8 Contrib Module Development with Dave Reid Juampy NR Andrew Berry Planet Drupal 12 Февруари 2016 00 00 Matt Mike discuss Drupal 8 module development with Dave Reid Juampy NR and Andrew Berry onsite at the Lullabot retreat in Palm Springs CA Категории Planet Drupal Drupal core announcements 8 1 0 will be released April 20 beta begins March 2 Planet Drupal 11 Февруари 2016 23 58 Drupal 8 1 0 the next planned minor release of Drupal 8 is scheduled for Wednesday April 20 2016 Minor releases include new features usability improvements and backwards compatible API improvements Here s what this means for core patches Drupal 8 1 0 beta1 will be released March 2 In preparation for the minor release Drupal 8 1 x will enter a beta phase on March 2 Developers and site owners can begin testing the beta The 8 2 x branch of core will be created and future feature and API additions will be targeted against that branch instead of 8 1 x All outstanding issues filed against 8 1 x will be automatically migrated to 8 2 x once it is opened During the beta phase core issues will be committed according to the following policy Issues that are allowed for patch releases will be committed to all three minor branches 8 0 x 8 1 x and 8 2 x Issues specific to added 8 1 x functionality or disruptive changes that have a positive impact outweighing their disruption will be committed to both 8 1 x and 8 2 x Such issues can be moved back to the 8 1 x branch after the automatic migration Most issues that are only allowed in minor releases will be committed to 8 2 x only Drupal 8 1 0 rc1 will be released April 6 The release candidate phase for the minor release begins on April 6 and starting on that date the 8 1 x branch will be subject to release candidate restrictions with only critical fixes and certain other limited changes allowed April 6 is also the final scheduled patch release window for 8 0 x and it will not receive further development or support after that date aside from its final security release window on April 20 All outstanding issues filed against 8 0 x will be automatically migrated to 8 1 x after the final 8 0 x patch release Future bug reports should be targeted against the 8 1 x branch Minor versions may include changes to user interfaces translatable strings themes internal APIs like render arrays and controllers etc See the Drupal 8 backwards compatibility and internal API policy for details Developers and site owners should test the release candidate to prepare for these changes 8 2 x will remain open for new development during the 8 1 x release candidate phase See the Drupal core release cycle overview Allowed changes during the Drupal 8 release cycle and Drupal 8 backwards compatibility and internal API policy for more information As a reminder we have until the start of the beta to add great new features to Drupal 8 1 x and migrate usability and bugfixes are all priorities for 8 1 0 Категории Planet Drupal HollyIT Windows Vagrant WinNFSD Without File Update Problems Planet Drupal 11 Февруари 2016 21 07 Categories Drupal Planet Drupal I have used Windows

    Original URL path: http://www.drupalbg.org/aggregator/categories/4 (2016-02-15)
    Open archived version from archive

  • Drupal News | Drupal BG
    record of community volunteers helping to improve Drupal org just a few examples from the last year include u mlhess and u nnewton helping with infrastructure to u michelle helping to clean up spam to u dddave and others in the webmasters queue or u mshmsh5000 who helped with Drupal Jobs feature development If you have expertise and not just in code and are ready for guidance from the Drupal Association engineering team as to how you can help you can offer your assistance as a volunteer Learn about Volunteering I should also note we strongly encourage most volunteers to first consider giving back to the Drupal project itself but we are certainly happy for help with Drupal org The second way to influence the Drupal org roadmap is to develop a community initiative If you and perhaps a small team of others in the community have some expertise in a particular area and have a particular initiative in mind that you would like to work on you can propose a community initiative View Community Initiatives Community initiatives come in all shapes in sizes from documentation audits with the help of u dead arm to adding two factor authentication to Drupal org with u coltrane to a much larger task like building and deploying DrupalCI with the help of u jthorson u nickscuch u ricardoamaro u bastianwidmer and several others Some initiatives affect a subset of the community project maintainers for example whereas others may affect almost every user Why this new process The hard lesson we ve learned over the course of the past year is that we need to be involved early Even in cases where the community volunteers driving an initiative forward are experts in their area if Association staff are not involved early in the architectural and planning decisions then what should be a positive collaborative effort is often slowed down by architectural refactoring and design decision backtracks That is not fun for anybody and our immense respect for our community collaborators requires that we set them up for success by getting involved early As such our new community initiatives process has several steps Community members plan their contribution in an issue and identify who if anyone is able to volunteer some time to make the contribution The community members propose their initiative to the Association so that we can evaluate it for inclusion on our roadmap This may include a call with the community members proposing the initiative to talk it through in greater detail Association staff evaluate the initiative prioritize it into the roadmap postpone it or if necessary reject initiatives that are not a good fit Prioritized community initiatives are rolled into the larger Drupal org roadmap and monthly or bi monthly community initiative meetings are scheduled to ensure the work moves forward A liaison from the Association engineering team is assigned to help coordinate architectural decisions to provide support and access as needed and to coordinate with the larger team when it is time for the work to be reviewed This process is time intensive and so in general we expect to be able to run only one or maybe two community initiatives at a time in parallel with our other work We realize this may be frustrating but the last year has shown that our most successful initiatives required this close coordination This process is new and will evolve Finding a good process for working closely with such a diverse and passionate community is not easy and we aren t assuming that this new process will be perfect We re going to trial this new community initiative process in 2016 with the goal of increasing the transparency of how we prioritize our work and how the community can help us build a better Drupal org We are committed to making this process better Категории Drupal News 2016 Nominations Open for Drupal Association At Large Director 1 Февруари 2016 18 56 Overview It s a great time to be part of the Drupal Association We ve done some amazing work in the last few years and we re in a great position to work with the community to continue to improve and grow fully into our mission As a Drupal Association At Large Director you d be in the center of the action The At large Director position is specifically designed to ensure community representation on the Drupal Association board and we strongly encourage anyone with an interest to nominate themselves today Nominate Yourself Today The Board of Directors of the Drupal Association are responsible for financial oversight and setting the strategic direction of the Drupal Association New board members will contribute to the strategic direction of the Drupal Association Board members are advised of but not responsible for matters related to the day to day operations of the Drupal Association including program execution staffing etc You can learn more about what s expected of a board member in this post and presentation Directors are expected to contribute around five hours per month and attend two in person meetings per year financial assistance is available if required All board members agree to meet the minimum requirements documented in the board member agreement Today we are opening the self nomination form that allows you to throw your hat in the ring We re looking to elect one candidate this year to serve a two year term How to Nominate Yourself To nominate yourself you should be prepared to answer a few questions About Me Tell us about yourself Your background how you got into Drupal etc Motivation Why are you applying for a board position What initiatives do you hope to help drive or what perspectives are you going to try and represent Experience What Drupal community contributions have you taken part in code camps etc Do you have experience in financial oversight developing business strategies or organization governance Availability I am able to travel to three in person board meetings per year either self funded or with financial sponsorship IRC Handle Twitter Handle We ve also made a few changes to the process based on community feedback from the 2015 election We now display your username not your given name on your candidate profile to address privacy concerns that had been raised Nominees should note that given names are required on legal documentation such as our 990 IRS filings but we will do our best to preserve your privacy where we can Updated sidebar block has more information about the elections making it easier to the information you need When you nominate yourself we will ask if you would like to opt in to share your election results data Last year was the first time we published full results from the vote data Candidates that opt in will have their name displayed next to their vote counts as in this example from 2015 We will also need to know that you are available for the next step in the process meet the candidate sessions We are hosting 3 sessions Meet the Candidate Web Conferences Session One Tue 23 Feb 2016 at 16 00 UTC 7 AM PST Tue 23 Feb US and Canada 10 AM EST Tue 23 Feb US and Canada 1 PM Tue 23 Feb Sao Paulo Brasil 3 PM Tue 23 Feb London 11 PM Tue 23 Feb Beijing Session Two Wed 24 Feb 2016 at 21 00 UTC 12 PM PST Wed 24 Feb US and Canada 3 PM EST Wed 24 Feb US and Canada 5 PM Wed 24 Feb Sao Paulo Brasil 8 PM Wed 24 Feb London 4 AM Thu 26 Feb Beijing 7 AM Thu 26 Feb Sydney Australia Session Three Thu 25 Feb 2016 at 01 00 UTC 4 00 PM PST Thu 25 Feb US and Canada 7 00 PM EST Thu 25 Feb US and Canada 9 00 PM Thu 25 Feb Sau Paulo Brasil 12 00 AM Fri 26 Feb London 8 00 AM Fri 26 Feb Beijing 11 00 AM Fri 26 Feb Sydney Australia The nomination form will be open February 1 2016 through February 20 2016 at midnight UTC For a thorough review of the process please see the elections home page If you have any questions please contact Holly Ross Drupal Association Executive Director For the sake of keeping conversational threads in one place the comments on this news item have been closed Please comment on the original post on the Drupal Association website Front page news Drupal News Категории Drupal News Predictions for 2016 19 Януари 2016 00 02 Without a doubt 2015 was one of the Drupal community s best years We continued to grow and change from being on an island to more of a peninsula We also released the best Drupal version ever If you look back at our predictions for 2015 the Drupal 8 release was one of the most predicted events for the year Now the question is what we will be doing in 2016 Will we have a decoupled Drupal Will Drupal 9 be released Will we see a Drupal 6 Legacy Support program It is that time of year when you yes you can predict the future of Drupal take a look at your crystal ball and describe what you see Share your deepest thoughts on what will happen for us as a community what will happen to our code and the difference our work might make Категории Drupal News Drupal 15 years old and still gaining momentum 15 Януари 2016 19 57 Republished from buytaert net On December 29 2000 I made a code commit that would change my life it is in this commit that I called my project Drupal and added the GPL license to it The commit where I dubbed my website project Drupal and added the GPL license A couple weeks later on January 15 2001 exactly 15 years ago from today I released Drupal 1 0 0 into the world The early decisions to open source Drupal and use the GPL license set the cornerstone principles for how our community shares with one another and builds upon each other s achievements to this day Drupal is now 15 years old In internet terms that is an eternity In 2001 only 7 percent of the world s population had internet access The mobile internet had not entered the picture less than 50 of the people in the United States had a mobile phone and AT T had just introduced text messaging People searched the web with Lycos Infoseek AltaVista and Hot Bot Google launched in 1998 as a Stanford University research project was still a small private company just beginning its rise to prominence Google AdWords now a 65 billion business had less than 500 customers when Drupal launched Chrome Firefox and Safari didn t exist yet most people used Netscape Opera or Internet Explorer New ideas for sharing and exchanging content such as public diaries and RSS had yet to gain widespread acceptance and Drupal was among the first to support those Wikipedia was launched on the same day as Drupal and sparked the rise of user generated content Facebook and Twitter didn t exist until 4 5 years later Proprietary software vendors started to feel threathened by open source most didn t understand how a world class operating system could coalesce out of part time hacking by several thousand developers around the world Looking back Drupal has not only survived massive changes in our industry it has also helped drive them Over the past decade and a half I ve seen many content management systems emerge and become obsolete Vignette Interwoven PHP Nuke and Scoop were all popular at some point in the past but Drupal has outlived them all A big reason is from the very beginning we have been about constant evolution and reinvention painful as it is Keeping up with the pace of the web is a funny thing Sometimes you ll look back on choices made years ago and think Well I m glad that was the right decision For example Drupal introduced hooks and modules early on concepts that are commonplace in today s platforms At some point you could even find some of my code in WordPress which Matt Mullenweg started in 2003 with some inspiration from Drupal Another fortuitous early decision was to focus Drupal on the concept of nodes rather than pages It wasn t until 10 years later with the rise of mobile that we started to see the web revolve less and less around pages A node based approach makes it possible to reuse content in different ways for different devices In a way much of the industry is still catching up to that vision Even though the web is a living breathing thing there is a lot of things that we got right Other times we got it wrong For example we added support for OpenID which never took off In the early days I focused completely and utterly on the aesthetics of Drupal s code I spent days trying to do something better with fewer lines of code and more elegant than elsewhere But in the process I didn t focus enough on end user usability shunned JavaScript for too long and later tried to improve usability by adding a dashboard and overlay In the end I feel fortunate that our community is willing to experiment and break things to stay relevant Most recently with the release of Drupal 8 we ve made many big changes that will fuel Drupal s continued adoption I believe we got a lot of things right in Drupal 8 and that we are on the brink of another new and bright era for Drupal I ve undergone a lot of personal reinvention over the past 15 years too In the early days I spent all my time writing code and building Drupal org I quickly learned that a successful open source project requires much more than writing code As Drupal started to grow I found myself an accidental leader and worried about our culture scaling the project attracting a strong team of contributors focusing more and more on Drupal s end users growing the commercial ecosystem around Drupal starting the Drupal Association and providing vision Today I wear a lot of different hats manager of people and projects evangelist fundraiser sponsor public speaker and BDFL At times it is difficult and overwhelming but I would not want it any other way I want to continue to push Drupal to reach new heights and new goals Today we risk losing much of the privacy serendipity and freedom of the web we know As the web evolves from a luxury to a basic human right it s important that we treat it that way To increase our impact we have to continue to make Drupal easier to use I d love to help build a world where people s privacy is safe and Drupal is more approachable And as the pace of innovation continues to accelerate we have to think even more about how to scale the project remain agile and encourage experimentation I think about these issues a lot and am fortunate enough to work with some of the smartest people I know to build the best possible version of the web So here is to another 15 years of evolution reinvention and continued growth No one knows what the web will look like 15 years in the future but we ll keep doing our best to guide Drupal responsibly Continue the conversation on buytaert net Front page news Drupal News Категории Drupal News A guide to issue credits and the Drupal org marketplace 13 Януари 2016 00 34 There s been a lot of positive feedback and a few questions about the recent changes to the marketplace I want to take a minute and talk about how the marketplace made it to where it is now and mention some plans for the future of the marketplace on Drupal org TL DR This is a long post You may not want to read the whole thing so here is a condensed version We want to highlight individuals and organizations that are actively contributing to Drupal You can now attribute your work in the Drupal org issue queues to your employer or a customer Maintainers can award issues credits to people who help resolve issues with code comments design and more These credits can roll up to service providers listed in the Drupal Marketplace And eventually we want to show customers with credits as well Want to know all the details Read on A little history Back at DrupalCon Austin 2014 Dries presented a sketch of an idea for highlighting organizational contributions to Drupal to myself and several business owners in the Drupal community Later that week those initial ideas turned into A method for giving credit to organizations that contribute code to Open Source The idea was to use commit messages to highlight organizational contribution The first draft looked something like this git commit am Issue n by INDIVIDUAL AGENCY CUSTOMER message It was simple and intended to be parsable from our Git logs However contribution is about more than just code and while code contributions are a good place to start we also needed to ensure that tools for providing attribution and credit would be extensible to non code contributions as well That initial conversation turned into an issue that spawned lots of child issues and ideas for how best to collect data that allowed a user on Drupal org to attribute their work to an organization The resulting conversations didn t have a simple solution but the participation in these issues was lively and full of great ideas Determining the format for commit credit is still an active issue A commit credit format alone was not going to get the information onto Drupal org Eventually we settled on a couple of different solutions for tracking organization involvement and pulled all of this together into the current state of the Drupal org Marketplace Organizations that support modules themes and distributions First we added a feature to projects on Drupal org modules themes distributions that allowed maintainers to reference organizations that were supporting a module either by providing time to their developers to give back or by directly funding development Commit credit user interface The next part of the work was giving maintainers a better way to create their commit message related to a particular issue A lot of the complexity of deciding who should get credit for work on Drupal org was simplified into a UI that showed how many people had participated in an issue how much each person had participated and whether that person had uploaded files related to the issue The UI also generated the Git command that would properly tie the resulting code changes to the issue and people involved The result for a relatively large issue thread looks like the image below Attribution While that effort made it a lot easier to create commit credits it didn t solve the problem of attributing issues that didn t result in code change nor did it allow people to give credit to the organizations that made it possible for them to work on that issue by giving them time or by paying for the work directly as a customer To do that we had to figure out a way to add organization attribution to the work being done on an issue Issues and comments are the primary tools for tracking what needs to be built out in Drupal code This is where we determine the features report the bugs plan out the work and more Tracking intent at the point of this interaction was the best way for us to cover the widest range of contribution to Drupal core modules themes and distributions The resulting UI for attributing a comment to an organization is simple and straightforward While the instructions for attributing a contribution are documented there s still some confusion about when to attribute a comment to an organization versus a customer Attributions for organizations These attributions are to allow a person to attribute their participation in a specific issue to a company that allotted time for them to work on the issue This is typically an employer that pays that person s salary or wage This organization must be directly tied to the contributor s user profile on Drupal org as a current or past employer and the organization must have an organization profile on Drupal org Create an organization profile When you use this feature you are highlighting an organization that is contributing code or other improvements through the issue queues to the community Attributions for customers When you attribute a customer you are essentially saying that the work was requested by that customer but you are not employed by them Typically this means one of three possibilities The customer organization paid the contributor s employer The customer organization paid the contributor directly The contributor was volunteering for the customer organization You can select any organization as a customer that has an organization profile on Drupal org When you use the customer attribution you re highlighting a different way of contributing to the Drupal ecosystem and often showing relationships between organizations to solve a problem Marking a comment with I m a volunteer Making it possible to attribute organizations who have supported contribution also helps us to gather data on purely altruistic contributions We went round and round on this attribution feature but in the end we decided to add I m a volunteer as an explicit attribution option in the attribution UI It s deliberately not the default This is because we want to collect the explicit intent of the users making attributions While we are now collecting this data we haven t yet figured out a great way to show this intent on a contributor s profile Possible intent on a comment could include I contributed on my own time as a volunteer and community member On this issue some of my time was paid for by an employer but some of my time was my own I contributed this work as a volunteer for one or more customer organizations The intent of volunteerism is complex which is why it is hard to add up into neat little data to show on a profile Regardless whether they mark I m a volunteer or not contributors can still be awarded issue credit by a maintainer for their work on an issue Attribution versus issue credit versus commit credit what s the difference Attribution is the first step of the process to award an issue credit The contributor attributes their work to one or more organizations and or as a volunteer The next step doesn t come until the maintainer of the project Drupal core module theme distribution gets involved in the process Issue credits Project maintainers may grant issue credits for issues opened against their projects At any time during the life of the issue a maintainer can update the credit UI to credit any of the users who have participated in the issue Any organizations or customers attributed by those users will be credited as well When the issue is closed fixed those assigned credits will appear on the appropriate user and organization profiles Issue credits are more comprehensive than just code They can include reviews designs prototypes or just really helpful comments The maintainer choses what they want to credit even if the issue does not have code associated with it in the form of a patch This is a great way to help highlight contributions to policy and work to keep Drupal org running well Commit credits Maintainers can grant commit credits A commit credit gets added to the Git commit message that accompanies a commit by a maintainer of a project on Drupal org Drupal Core modules themes distributions etc Sites like drupalcores com track this information in the public changelog and use it to highlight contribution numbers based on the number of times a user is mentioned in a commit message Commit credits currently can t be easily tied to organizations the parsing would be cumbersome and require a lot of precision when maintainers entered the information into Git which is a big reason why we needed a UI on Drupal org to help make all the connections and store that information into a database for easy retrieval Showing contributions on Drupal org Right now there are three ways that contributions show up on Drupal org the user profile the organization profile and the marketplace We have some ideas to expand this that I will detail below User profiles Do you log in to Drupal org Great You have a profile On every user profile we show the total number of issues that a contributor has helped fix in the past 90 days You can drill into this information and see the specifics This is a good way to see a facet of how a person is contributing to Drupal There are other examples on a user s profile that show other ways they are involved Organization profiles Any confirmed user can create an organization page on Drupal org Organization profiles are currently related to a single user but we have plans to roll out additional permissions to relate multiple users to an organization On the organization profile we show the number of issues that an organization has contributed to fixing in the last 90 days Organization profiles also show a list of modules that have been supported by that organization whether that organization is a Drupal Association member or Supporting Partner and additional self reported information about their involvement in the Drupal community We are currently working to automate more methods for collecting data about how organizations are contributing to the community through DrupalCon and Drupal Camp sponsorships as well as hosting user groups to help support meetups and giving to Global Training Day events The number of case studies associated with an organization is another indicator of how much they use Drupal and how they are helping get others to use Drupal by sharing their success stories Marketplace We recently rolled out some changes to how the Drupal org Marketplace is ordered in order to better highlight contributing organizations Currently the marketplace is sorted by number of issue credits awarded to an organization in the last 90 days then whether the organization is a supporter then by alphabetical order Every organization on the marketplace shows counts of its users on Drupal org projects modules themes distributions etc supported issue credits in the last 90 days and case studies We also highlight organizations that are funding the ongoing support and development of Drupal org by being in our supporting partner programs Questions we have heard While most people have been excited about the changes to the Marketplace there have been several questions Why is it only Drupal Service providers The marketplace was originally created to highlight Drupal service providers that are active in the Drupal community A Contributing Organizations list is the next step to expand the types of organizations we highlight There are community members that are already working to highlight customers using Drupal that contribute back community volunteers and volunteers that are working for organizations that rely on volunteerism many camps fall into this category These are great ideas Contributing to those issues is a great way to help us figure out the best way forward What about x contribution type Yes there are many ways that organizations contribute We are definitely hoping to add in contributions that we can objectively verify There are so many great things that organizations can do to support Drupal both the local and worldwide community and Drupal org including Sponsor a DrupalCon Help plan a DrupalCon Sponsor organize or host a Drupal Camp Host a Global Training Days event Host a local user group meetup Post a case study of a successful Drupal project Contribute helpful content to Drupal Planet There are many other phenomenal ways organizations give back If you know of one that has objective data that can be added to the algorithm we use to highlight organizations let us know by creating an issue in theDrupal org Customizations queue Why is it so hard to create an organization profile We definitely want to improve this process There are over 650 organization profiles on Drupal org so we know that people have figured it out but it could be much more intuitive We have also had a several requests to add permissions to organization profiles so that multiple people can be editors of those profiles and help administer who is allowed to be associated with the organization Our current method of tying users to organization by using an exact text match is a bit clunky If you want your organization to list you as an employee you must exactly enter the title of the organization as it appears on the organization profile and list that organization as current What about more tools for individual contributions We have so many thoughts on how to improve the way we highlight individuals on their profile We already show issue credits documentation edits commits and lots of self reported information There is a lot of objective data to pull from including DrupalCon attendance whether they have been a speaker at a DrupalCon translation strings submitted to localize drupal org Drupal Association membership modules maintained and many more Engagement with the community involves a lot of factors and we want to highlight as many as possible while still making the user profile useful and relatively succinct Help us make Drupal org better In addition to the questions that have come up above we want your feedback to keep improving the user experience on Drupal org and make it easier to hightlight the companies that are doing so much to make Drupal the leading platform for the web and the individuals that provide their expertise and commitment to the community Drop your ideas into the Drupal org Customizations queue Категории Drupal News Drupal 8 0 2 released 7 Януари 2016 01 32 Update Drupal 8 0 3 is now available Drupal 8 0 2 a maintenance release with numerous bug fixes no security fixes is now available for download See the Drupal 8 0 2 release notes for a full list of included fixes Download Drupal 8 0 2 Upgrading your existing Drupal 8 sites is recommended There are no major nor non backwards compatible features in this release For more information about the Drupal 8 x release series consult the Drupal 8 overview Security information We have a security announcement mailing list and a history of all security advisories as well as an RSS feed with the most recent security advisories We strongly advise Drupal administrators to sign up for the list Drupal 8 includes the built in Update Manager module which informs you about important updates to your modules and themes There are no security fixes in this release of Drupal core Bug reports Drupal 8 0 x is actively maintained so more maintenance releases will be made available according to our monthly release cycle Change Log Drupal 8 0 2 contains bug fixes and documentation and testing improvements only The full list of changes between the 8 0 1 and 8 0 2 releases can be found by reading the 8 0 2 release notes A complete list of all changes in the stable 8 0 x branch can be found in the git commit log Update notes See the 8 0 2 release notes for details on important changes in this release Known issues See the 8 0 2 release notes for known issues Front page news Planet Drupal Drupal version Drupal 8 x Категории Drupal News Selecting a client side framework for Drupal 6 Януари 2016 11 00 Republished from buytaert net Last month my blog post about whether a client side framework is right for Drupal stimulated some excellent insights into how the future of the Drupal front end might look There was broad agreement that incorporating more JavaScript into Drupal s administrative interface is important for a future ready user experience I am confident that adopting a client side framework through progressive decoupling will give us the best of both worlds Of course this does not mean I oppose fully decoupling through any other framework in fact I believe we should redouble our efforts toward a first class API first Drupal But progressive decoupling means that we will be able to work toward a next generation user experience without abandoning much of the work we ve done so far With that in mind I tasked a small team made up of various experts from the Drupal and various JavaScript communities with putting together a list of criteria and a comparison matrix to help us decide on the most appropriate client side framework for progressive decoupling in Drupal JavaScript framework comparison matrix After a hundred hours of work we came up with a criteria document and comparison matrix PDF version Special thanks to all of the following experts who provided review and input Miško Hevery creator of Angular Google and Igor Minar technical lead for Angular Google Ed Faulkner core maintainer for Ember Amitai Burstein Drupal and Elm contributor Gizra Sebastian Siemssen Drupal contributor Elm and React developer Zensations and John Albin Wilkins Drupal 8 mobile initiative lead Alex Bronstein Drupal core maintainer Acquia Wim Leers Drupal core contributor Acquia and Preston So Drupal contributor Acquia Though this is a good starting point that lays the groundwork for a formal adoption process in Drupal core it is time to open our comparison for review by members of both the Drupal and JavaScript communities We should also more rigorously evaluate these frameworks appropriateness through actual development First have we decided on the right criteria regardless of the frameworks themselves This is probably the most important at this stage While many organizations choose to adopt client side frameworks for fully decoupled implementations Drupal is the first to consider layering a framework on top to allow both richly dynamic and more traditional modules to coexist gracefully through progressive decoupling What issues around templates rendering and client side caching should we incorporate into these criteria Is there anything missing or overemphasized Second have we selected the right frameworks to focus on Are there other frameworks libraries or even compile to JavaScript projects such as Elm that should be included in the matrix In my view it is best for Drupal to adopt a framework with an already large community and ecosystem that would allow us to more quickly bridge the gap and resolve any friction during adoption To provide a good frame of reference we ve also included Backbone Angular and Knockout all three slightly older among client side frameworks Others on our shortlist that we didn t consider due to low levels of adoption and small communities are Mithril Riot and Vue Still other ambitious projects such as the Elm and ClojureScript languages are also candidates but their adoption will mean more up front work to support typical features of client side frameworks as well as buy in into an approach where JavaScript is compiled from a different language Finally have we drawn the right conclusions against these criteria In other words did we fill out the cells correctly While they have been reviewed by some of the frameworks experts there might be unexpected gotchas or caveats I m sharing the initial comparison matrix on my blog for maximum reach I want both the Drupal community and the JavaScript framework communities as well as the broader front end community to take note After

    Original URL path: http://www.drupalbg.org/aggregator/sources/3 (2016-02-15)
    Open archived version from archive

  • Drupal News | Drupal BG
    clean up spam to u dddave and others in the webmasters queue or u mshmsh5000 who helped with Drupal Jobs feature development If you have expertise and not just in code and are ready for guidance from the Drupal Association engineering team as to how you can help you can offer your assistance as a volunteer Learn about Volunteering I should also note we strongly encourage most volunteers to first consider giving back to the Drupal project itself but we are certainly happy for help with Drupal org The second way to influence the Drupal org roadmap is to develop a community initiative If you and perhaps a small team of others in the community have some expertise in a particular area and have a particular initiative in mind that you would like to work on you can propose a community initiative View Community Initiatives Community initiatives come in all shapes in sizes from documentation audits with the help of u dead arm to adding two factor authentication to Drupal org with u coltrane to a much larger task like building and deploying DrupalCI with the help of u jthorson u nickscuch u ricardoamaro u bastianwidmer and several others Some initiatives affect a subset of the community project maintainers for example whereas others may affect almost every user Why this new process The hard lesson we ve learned over the course of the past year is that we need to be involved early Even in cases where the community volunteers driving an initiative forward are experts in their area if Association staff are not involved early in the architectural and planning decisions then what should be a positive collaborative effort is often slowed down by architectural refactoring and design decision backtracks That is not fun for anybody and our immense respect for our community collaborators requires that we set them up for success by getting involved early As such our new community initiatives process has several steps Community members plan their contribution in an issue and identify who if anyone is able to volunteer some time to make the contribution The community members propose their initiative to the Association so that we can evaluate it for inclusion on our roadmap This may include a call with the community members proposing the initiative to talk it through in greater detail Association staff evaluate the initiative prioritize it into the roadmap postpone it or if necessary reject initiatives that are not a good fit Prioritized community initiatives are rolled into the larger Drupal org roadmap and monthly or bi monthly community initiative meetings are scheduled to ensure the work moves forward A liaison from the Association engineering team is assigned to help coordinate architectural decisions to provide support and access as needed and to coordinate with the larger team when it is time for the work to be reviewed This process is time intensive and so in general we expect to be able to run only one or maybe two community initiatives at a time in parallel with our other work We realize this may be frustrating but the last year has shown that our most successful initiatives required this close coordination This process is new and will evolve Finding a good process for working closely with such a diverse and passionate community is not easy and we aren t assuming that this new process will be perfect We re going to trial this new community initiative process in 2016 with the goal of increasing the transparency of how we prioritize our work and how the community can help us build a better Drupal org We are committed to making this process better Категории Drupal News 2016 Nominations Open for Drupal Association At Large Director Drupal News 1 Февруари 2016 18 56 Overview It s a great time to be part of the Drupal Association We ve done some amazing work in the last few years and we re in a great position to work with the community to continue to improve and grow fully into our mission As a Drupal Association At Large Director you d be in the center of the action The At large Director position is specifically designed to ensure community representation on the Drupal Association board and we strongly encourage anyone with an interest to nominate themselves today Nominate Yourself Today The Board of Directors of the Drupal Association are responsible for financial oversight and setting the strategic direction of the Drupal Association New board members will contribute to the strategic direction of the Drupal Association Board members are advised of but not responsible for matters related to the day to day operations of the Drupal Association including program execution staffing etc You can learn more about what s expected of a board member in this post and presentation Directors are expected to contribute around five hours per month and attend two in person meetings per year financial assistance is available if required All board members agree to meet the minimum requirements documented in the board member agreement Today we are opening the self nomination form that allows you to throw your hat in the ring We re looking to elect one candidate this year to serve a two year term How to Nominate Yourself To nominate yourself you should be prepared to answer a few questions About Me Tell us about yourself Your background how you got into Drupal etc Motivation Why are you applying for a board position What initiatives do you hope to help drive or what perspectives are you going to try and represent Experience What Drupal community contributions have you taken part in code camps etc Do you have experience in financial oversight developing business strategies or organization governance Availability I am able to travel to three in person board meetings per year either self funded or with financial sponsorship IRC Handle Twitter Handle We ve also made a few changes to the process based on community feedback from the 2015 election We now display your username not your given name on your candidate profile to address privacy concerns that had been raised Nominees should note that given names are required on legal documentation such as our 990 IRS filings but we will do our best to preserve your privacy where we can Updated sidebar block has more information about the elections making it easier to the information you need When you nominate yourself we will ask if you would like to opt in to share your election results data Last year was the first time we published full results from the vote data Candidates that opt in will have their name displayed next to their vote counts as in this example from 2015 We will also need to know that you are available for the next step in the process meet the candidate sessions We are hosting 3 sessions Meet the Candidate Web Conferences Session One Tue 23 Feb 2016 at 16 00 UTC 7 AM PST Tue 23 Feb US and Canada 10 AM EST Tue 23 Feb US and Canada 1 PM Tue 23 Feb Sao Paulo Brasil 3 PM Tue 23 Feb London 11 PM Tue 23 Feb Beijing Session Two Wed 24 Feb 2016 at 21 00 UTC 12 PM PST Wed 24 Feb US and Canada 3 PM EST Wed 24 Feb US and Canada 5 PM Wed 24 Feb Sao Paulo Brasil 8 PM Wed 24 Feb London 4 AM Thu 26 Feb Beijing 7 AM Thu 26 Feb Sydney Australia Session Three Thu 25 Feb 2016 at 01 00 UTC 4 00 PM PST Thu 25 Feb US and Canada 7 00 PM EST Thu 25 Feb US and Canada 9 00 PM Thu 25 Feb Sau Paulo Brasil 12 00 AM Fri 26 Feb London 8 00 AM Fri 26 Feb Beijing 11 00 AM Fri 26 Feb Sydney Australia The nomination form will be open February 1 2016 through February 20 2016 at midnight UTC For a thorough review of the process please see the elections home page If you have any questions please contact Holly Ross Drupal Association Executive Director For the sake of keeping conversational threads in one place the comments on this news item have been closed Please comment on the original post on the Drupal Association website Front page news Drupal News Категории Drupal News Predictions for 2016 Drupal News 19 Януари 2016 00 02 Without a doubt 2015 was one of the Drupal community s best years We continued to grow and change from being on an island to more of a peninsula We also released the best Drupal version ever If you look back at our predictions for 2015 the Drupal 8 release was one of the most predicted events for the year Now the question is what we will be doing in 2016 Will we have a decoupled Drupal Will Drupal 9 be released Will we see a Drupal 6 Legacy Support program It is that time of year when you yes you can predict the future of Drupal take a look at your crystal ball and describe what you see Share your deepest thoughts on what will happen for us as a community what will happen to our code and the difference our work might make Категории Drupal News Drupal 15 years old and still gaining momentum Drupal News 15 Януари 2016 19 57 Republished from buytaert net On December 29 2000 I made a code commit that would change my life it is in this commit that I called my project Drupal and added the GPL license to it The commit where I dubbed my website project Drupal and added the GPL license A couple weeks later on January 15 2001 exactly 15 years ago from today I released Drupal 1 0 0 into the world The early decisions to open source Drupal and use the GPL license set the cornerstone principles for how our community shares with one another and builds upon each other s achievements to this day Drupal is now 15 years old In internet terms that is an eternity In 2001 only 7 percent of the world s population had internet access The mobile internet had not entered the picture less than 50 of the people in the United States had a mobile phone and AT T had just introduced text messaging People searched the web with Lycos Infoseek AltaVista and Hot Bot Google launched in 1998 as a Stanford University research project was still a small private company just beginning its rise to prominence Google AdWords now a 65 billion business had less than 500 customers when Drupal launched Chrome Firefox and Safari didn t exist yet most people used Netscape Opera or Internet Explorer New ideas for sharing and exchanging content such as public diaries and RSS had yet to gain widespread acceptance and Drupal was among the first to support those Wikipedia was launched on the same day as Drupal and sparked the rise of user generated content Facebook and Twitter didn t exist until 4 5 years later Proprietary software vendors started to feel threathened by open source most didn t understand how a world class operating system could coalesce out of part time hacking by several thousand developers around the world Looking back Drupal has not only survived massive changes in our industry it has also helped drive them Over the past decade and a half I ve seen many content management systems emerge and become obsolete Vignette Interwoven PHP Nuke and Scoop were all popular at some point in the past but Drupal has outlived them all A big reason is from the very beginning we have been about constant evolution and reinvention painful as it is Keeping up with the pace of the web is a funny thing Sometimes you ll look back on choices made years ago and think Well I m glad that was the right decision For example Drupal introduced hooks and modules early on concepts that are commonplace in today s platforms At some point you could even find some of my code in WordPress which Matt Mullenweg started in 2003 with some inspiration from Drupal Another fortuitous early decision was to focus Drupal on the concept of nodes rather than pages It wasn t until 10 years later with the rise of mobile that we started to see the web revolve less and less around pages A node based approach makes it possible to reuse content in different ways for different devices In a way much of the industry is still catching up to that vision Even though the web is a living breathing thing there is a lot of things that we got right Other times we got it wrong For example we added support for OpenID which never took off In the early days I focused completely and utterly on the aesthetics of Drupal s code I spent days trying to do something better with fewer lines of code and more elegant than elsewhere But in the process I didn t focus enough on end user usability shunned JavaScript for too long and later tried to improve usability by adding a dashboard and overlay In the end I feel fortunate that our community is willing to experiment and break things to stay relevant Most recently with the release of Drupal 8 we ve made many big changes that will fuel Drupal s continued adoption I believe we got a lot of things right in Drupal 8 and that we are on the brink of another new and bright era for Drupal I ve undergone a lot of personal reinvention over the past 15 years too In the early days I spent all my time writing code and building Drupal org I quickly learned that a successful open source project requires much more than writing code As Drupal started to grow I found myself an accidental leader and worried about our culture scaling the project attracting a strong team of contributors focusing more and more on Drupal s end users growing the commercial ecosystem around Drupal starting the Drupal Association and providing vision Today I wear a lot of different hats manager of people and projects evangelist fundraiser sponsor public speaker and BDFL At times it is difficult and overwhelming but I would not want it any other way I want to continue to push Drupal to reach new heights and new goals Today we risk losing much of the privacy serendipity and freedom of the web we know As the web evolves from a luxury to a basic human right it s important that we treat it that way To increase our impact we have to continue to make Drupal easier to use I d love to help build a world where people s privacy is safe and Drupal is more approachable And as the pace of innovation continues to accelerate we have to think even more about how to scale the project remain agile and encourage experimentation I think about these issues a lot and am fortunate enough to work with some of the smartest people I know to build the best possible version of the web So here is to another 15 years of evolution reinvention and continued growth No one knows what the web will look like 15 years in the future but we ll keep doing our best to guide Drupal responsibly Continue the conversation on buytaert net Front page news Drupal News Категории Drupal News A guide to issue credits and the Drupal org marketplace Drupal News 13 Януари 2016 00 34 There s been a lot of positive feedback and a few questions about the recent changes to the marketplace I want to take a minute and talk about how the marketplace made it to where it is now and mention some plans for the future of the marketplace on Drupal org TL DR This is a long post You may not want to read the whole thing so here is a condensed version We want to highlight individuals and organizations that are actively contributing to Drupal You can now attribute your work in the Drupal org issue queues to your employer or a customer Maintainers can award issues credits to people who help resolve issues with code comments design and more These credits can roll up to service providers listed in the Drupal Marketplace And eventually we want to show customers with credits as well Want to know all the details Read on A little history Back at DrupalCon Austin 2014 Dries presented a sketch of an idea for highlighting organizational contributions to Drupal to myself and several business owners in the Drupal community Later that week those initial ideas turned into A method for giving credit to organizations that contribute code to Open Source The idea was to use commit messages to highlight organizational contribution The first draft looked something like this git commit am Issue n by INDIVIDUAL AGENCY CUSTOMER message It was simple and intended to be parsable from our Git logs However contribution is about more than just code and while code contributions are a good place to start we also needed to ensure that tools for providing attribution and credit would be extensible to non code contributions as well That initial conversation turned into an issue that spawned lots of child issues and ideas for how best to collect data that allowed a user on Drupal org to attribute their work to an organization The resulting conversations didn t have a simple solution but the participation in these issues was lively and full of great ideas Determining the format for commit credit is still an active issue A commit credit format alone was not going to get the information onto Drupal org Eventually we settled on a couple of different solutions for tracking organization involvement and pulled all of this together into the current state of the Drupal org Marketplace Organizations that support modules themes and distributions First we added a feature to projects on Drupal org modules themes distributions that allowed maintainers to reference organizations that were supporting a module either by providing time to their developers to give back or by directly funding development Commit credit user interface The next part of the work was giving maintainers a better way to create their commit message related to a particular issue A lot of the complexity of deciding who should get credit for work on Drupal org was simplified into a UI that showed how many people had participated in an issue how much each person had participated and whether that person had uploaded files related to the issue The UI also generated the Git command that would properly tie the resulting code changes to the issue and people involved The result for a relatively large issue thread looks like the image below Attribution While that effort made it a lot easier to create commit credits it didn t solve the problem of attributing issues that didn t result in code change nor did it allow people to give credit to the organizations that made it possible for them to work on that issue by giving them time or by paying for the work directly as a customer To do that we had to figure out a way to add organization attribution to the work being done on an issue Issues and comments are the primary tools for tracking what needs to be built out in Drupal code This is where we determine the features report the bugs plan out the work and more Tracking intent at the point of this interaction was the best way for us to cover the widest range of contribution to Drupal core modules themes and distributions The resulting UI for attributing a comment to an organization is simple and straightforward While the instructions for attributing a contribution are documented there s still some confusion about when to attribute a comment to an organization versus a customer Attributions for organizations These attributions are to allow a person to attribute their participation in a specific issue to a company that allotted time for them to work on the issue This is typically an employer that pays that person s salary or wage This organization must be directly tied to the contributor s user profile on Drupal org as a current or past employer and the organization must have an organization profile on Drupal org Create an organization profile When you use this feature you are highlighting an organization that is contributing code or other improvements through the issue queues to the community Attributions for customers When you attribute a customer you are essentially saying that the work was requested by that customer but you are not employed by them Typically this means one of three possibilities The customer organization paid the contributor s employer The customer organization paid the contributor directly The contributor was volunteering for the customer organization You can select any organization as a customer that has an organization profile on Drupal org When you use the customer attribution you re highlighting a different way of contributing to the Drupal ecosystem and often showing relationships between organizations to solve a problem Marking a comment with I m a volunteer Making it possible to attribute organizations who have supported contribution also helps us to gather data on purely altruistic contributions We went round and round on this attribution feature but in the end we decided to add I m a volunteer as an explicit attribution option in the attribution UI It s deliberately not the default This is because we want to collect the explicit intent of the users making attributions While we are now collecting this data we haven t yet figured out a great way to show this intent on a contributor s profile Possible intent on a comment could include I contributed on my own time as a volunteer and community member On this issue some of my time was paid for by an employer but some of my time was my own I contributed this work as a volunteer for one or more customer organizations The intent of volunteerism is complex which is why it is hard to add up into neat little data to show on a profile Regardless whether they mark I m a volunteer or not contributors can still be awarded issue credit by a maintainer for their work on an issue Attribution versus issue credit versus commit credit what s the difference Attribution is the first step of the process to award an issue credit The contributor attributes their work to one or more organizations and or as a volunteer The next step doesn t come until the maintainer of the project Drupal core module theme distribution gets involved in the process Issue credits Project maintainers may grant issue credits for issues opened against their projects At any time during the life of the issue a maintainer can update the credit UI to credit any of the users who have participated in the issue Any organizations or customers attributed by those users will be credited as well When the issue is closed fixed those assigned credits will appear on the appropriate user and organization profiles Issue credits are more comprehensive than just code They can include reviews designs prototypes or just really helpful comments The maintainer choses what they want to credit even if the issue does not have code associated with it in the form of a patch This is a great way to help highlight contributions to policy and work to keep Drupal org running well Commit credits Maintainers can grant commit credits A commit credit gets added to the Git commit message that accompanies a commit by a maintainer of a project on Drupal org Drupal Core modules themes distributions etc Sites like drupalcores com track this information in the public changelog and use it to highlight contribution numbers based on the number of times a user is mentioned in a commit message Commit credits currently can t be easily tied to organizations the parsing would be cumbersome and require a lot of precision when maintainers entered the information into Git which is a big reason why we needed a UI on Drupal org to help make all the connections and store that information into a database for easy retrieval Showing contributions on Drupal org Right now there are three ways that contributions show up on Drupal org the user profile the organization profile and the marketplace We have some ideas to expand this that I will detail below User profiles Do you log in to Drupal org Great You have a profile On every user profile we show the total number of issues that a contributor has helped fix in the past 90 days You can drill into this information and see the specifics This is a good way to see a facet of how a person is contributing to Drupal There are other examples on a user s profile that show other ways they are involved Organization profiles Any confirmed user can create an organization page on Drupal org Organization profiles are currently related to a single user but we have plans to roll out additional permissions to relate multiple users to an organization On the organization profile we show the number of issues that an organization has contributed to fixing in the last 90 days Organization profiles also show a list of modules that have been supported by that organization whether that organization is a Drupal Association member or Supporting Partner and additional self reported information about their involvement in the Drupal community We are currently working to automate more methods for collecting data about how organizations are contributing to the community through DrupalCon and Drupal Camp sponsorships as well as hosting user groups to help support meetups and giving to Global Training Day events The number of case studies associated with an organization is another indicator of how much they use Drupal and how they are helping get others to use Drupal by sharing their success stories Marketplace We recently rolled out some changes to how the Drupal org Marketplace is ordered in order to better highlight contributing organizations Currently the marketplace is sorted by number of issue credits awarded to an organization in the last 90 days then whether the organization is a supporter then by alphabetical order Every organization on the marketplace shows counts of its users on Drupal org projects modules themes distributions etc supported issue credits in the last 90 days and case studies We also highlight organizations that are funding the ongoing support and development of Drupal org by being in our supporting partner programs Questions we have heard While most people have been excited about the changes to the Marketplace there have been several questions Why is it only Drupal Service providers The marketplace was originally created to highlight Drupal service providers that are active in the Drupal community A Contributing Organizations list is the next step to expand the types of organizations we highlight There are community members that are already working to highlight customers using Drupal that contribute back community volunteers and volunteers that are working for organizations that rely on volunteerism many camps fall into this category These are great ideas Contributing to those issues is a great way to help us figure out the best way forward What about x contribution type Yes there are many ways that organizations contribute We are definitely hoping to add in contributions that we can objectively verify There are so many great things that organizations can do to support Drupal both the local and worldwide community and Drupal org including Sponsor a DrupalCon Help plan a DrupalCon Sponsor organize or host a Drupal Camp Host a Global Training Days event Host a local user group meetup Post a case study of a successful Drupal project Contribute helpful content to Drupal Planet There are many other phenomenal ways organizations give back If you know of one that has objective data that can be added to the algorithm we use to highlight organizations let us know by creating an issue in theDrupal org Customizations queue Why is it so hard to create an organization profile We definitely want to improve this process There are over 650 organization profiles on Drupal org so we know that people have figured it out but it could be much more intuitive We have also had a several requests to add permissions to organization profiles so that multiple people can be editors of those profiles and help administer who is allowed to be associated with the organization Our current method of tying users to organization by using an exact text match is a bit clunky If you want your organization to list you as an employee you must exactly enter the title of the organization as it appears on the organization profile and list that organization as current What about more tools for individual contributions We have so many thoughts on how to improve the way we highlight individuals on their profile We already show issue credits documentation edits commits and lots of self reported information There is a lot of objective data to pull from including DrupalCon attendance whether they have been a speaker at a DrupalCon translation strings submitted to localize drupal org Drupal Association membership modules maintained and many more Engagement with the community involves a lot of factors and we want to highlight as many as possible while still making the user profile useful and relatively succinct Help us make Drupal org better In addition to the questions that have come up above we want your feedback to keep improving the user experience on Drupal org and make it easier to hightlight the companies that are doing so much to make Drupal the leading platform for the web and the individuals that provide their expertise and commitment to the community Drop your ideas into the Drupal org Customizations queue Категории Drupal News Drupal 8 0 2 released Drupal News 7 Януари 2016 01 32 Update Drupal 8 0 3 is now available Drupal 8 0 2 a maintenance release with numerous bug fixes no security fixes is now available for download See the Drupal 8 0 2 release notes for a full list of included fixes Download Drupal 8 0 2 Upgrading your existing Drupal 8 sites is recommended There are no major nor non backwards compatible features in this release For more information about the Drupal 8 x release series consult the Drupal 8 overview Security information We have a security announcement mailing list and a history of all security advisories as well as an RSS feed with the most recent security advisories We strongly advise Drupal administrators to sign up for the list Drupal 8 includes the built in Update Manager module which informs you about important updates to your modules and themes There are no security fixes in this release of Drupal core Bug reports Drupal 8 0 x is actively maintained so more maintenance releases will be made available according to our monthly release cycle Change Log Drupal 8 0 2 contains bug fixes and documentation and testing improvements only The full list of changes between the 8 0 1 and 8 0 2 releases can be found by reading the 8 0 2 release notes A complete list of all changes in the stable 8 0 x branch can be found in the git commit log Update notes See the 8 0 2 release notes for details on important changes in this release Known issues See the 8 0 2 release notes for known issues Front page news Planet Drupal Drupal version Drupal 8 x Категории Drupal News Selecting a client side framework for Drupal Drupal News 6 Януари 2016 11 00 Republished from buytaert net Last month my blog post about whether a client side framework is right for Drupal stimulated some excellent insights into how the future of the Drupal front end might look There was broad agreement that incorporating more JavaScript into Drupal s administrative interface is important for a future ready user experience I am confident that adopting a client side framework through progressive decoupling will give us the best of both worlds Of course this does not mean I oppose fully decoupling through any other framework in fact I believe we should redouble our efforts toward a first class API first Drupal But progressive decoupling means that we will be able to work toward a next generation user experience without abandoning much of the work we ve done so far With that in mind I tasked a small team made up of various experts from the Drupal and various JavaScript communities with putting together a list of criteria and a comparison matrix to help us decide on the most appropriate client side framework for progressive decoupling in Drupal JavaScript framework comparison matrix After a hundred hours of work we came up with a criteria document and comparison matrix PDF version Special thanks to all of the following experts who provided review and input Miško Hevery creator of Angular Google and Igor Minar technical lead for Angular Google Ed Faulkner core maintainer for Ember Amitai Burstein Drupal and Elm contributor Gizra Sebastian Siemssen Drupal contributor Elm and React developer Zensations and John Albin Wilkins Drupal 8 mobile initiative lead Alex Bronstein Drupal core maintainer Acquia Wim Leers Drupal core contributor Acquia and Preston So Drupal contributor Acquia Though this is a good starting point that lays the groundwork for a formal adoption process in Drupal core it is time to open our comparison for review by members of both the Drupal and JavaScript communities We should also more rigorously evaluate these frameworks appropriateness through actual development First have we decided on the right criteria regardless of the frameworks themselves This is probably the most important at this stage While many organizations choose to adopt client side frameworks for fully decoupled implementations Drupal is the first to consider layering a framework on top to allow both richly dynamic and more traditional modules to coexist gracefully through progressive decoupling What issues around templates rendering and client side caching should we incorporate into these criteria Is there anything missing or overemphasized Second have we selected the right frameworks to focus on Are there other frameworks libraries or even compile to JavaScript projects such as Elm that should be included in the matrix In my view it is best for Drupal to adopt a framework with an already large community and ecosystem that would allow us to more quickly bridge the gap and resolve any friction during adoption To provide a good frame of reference we ve also included Backbone Angular and Knockout all three slightly older among client side frameworks Others on our shortlist that we didn t consider due to low levels of adoption and small communities are Mithril Riot and Vue Still other ambitious projects such as the Elm and ClojureScript languages are also candidates but their adoption will mean more up front work to support typical features of client side frameworks as well as buy in into an approach where JavaScript is compiled from a different language Finally have we drawn the right conclusions against these criteria In other words did we fill out the cells correctly While they have been reviewed by some of the frameworks experts there might be unexpected gotchas or caveats I m sharing the initial comparison matrix on my blog for maximum reach I want both the Drupal community and the JavaScript framework communities as well as the broader front end community to take note After three installments on my blog The future of decoupled Drupal Should we decouple Drupal with a client side framework

    Original URL path: http://www.drupalbg.org/aggregator/categories/3 (2016-02-15)
    Open archived version from archive

  • Информация и помощ | Drupal BG
    гост online Гласуване Колко тестови Друпал сайта имате 1 5 бр 56 5 10 бр 16 10 15 бр 9 15 20 бр 3 20 30 бр 3 30 40 бр 3 40 50 бр 3 над 50 бр 6 Общо гласове 32 2 коментара По стари анкети Разпространи Loading Начало Drupal 6 и 5 Информация и помощ Тук споделяйте всички проблеми свързани с Drupal Правила на Форума Прочети преди да пишеш 16 Януари 2012 10 55 vodoleq Преди да питате и пишете тема потърсете чрез търсачката в сайта ТОЧНО НАД ФОРУМА Е Прочетете ДОКУМЕНТАЦИЯТА Read documentation на всеки модул там създателите му са обяснили всичко подробно Пишете новите теми в правилните Подфоруми Заглавията на темите ТРЯБВА да съдържат описание на проблема теми от рода на Имам проблем Помогнете са излишни Опишете максимално подробно проблема или въпроса си колкото повече данни изложите толкова ПО БЪРЗО ще Ви се помогне Идентифицирайте се или се регистрирайте за да изпращате коментари Tags Информация и помощ Видео записи от Drupal Cemp Bulgaria 2011 16 Февруари 2011 19 36 vodoleq Това е линка към заснетото видео от Друпал Кемп 2011 http live kabinata com video arhives drupal2011 забелязах проблеми с някои от клиповете но повечето работят Ако искате да коментирате дадено видео направете отделна Тема очаквам и по добри предложения целта е по добро систематизиране на информацията за нас и бъдещите ползватели на форума ако някой друг има видео записи нека се свърже с мен 3 коментара Tags Информация и помощ Инсталиране на Друпал 6 на Localhots видео урок 2 6 Ноември 2010 20 15 vodoleq След инсталирането на Xammp е ред и на Друпал В клепчето умишлено съм написал да се спира скайпа защото много хора забравят тази малка подробност Причината е че Скайп и Арачето ползват един и същи порт Варианта за да ползвате двете приложения е от настройките на скайпа да промените да използва алтернативен порт ако 80 ти е вече зает Прочетете повече 1 коментар Tags Информация и помощ Инталиране на XAMMP на Windows 7 Видео урок 1 6 Ноември 2010 20 10 vodoleq За да може да разработвате сайтове на вашия компютър ви е необходимо преди това да инсталирате XAMMP Той е един от най масово използваните и лесни за конфигурация Прочетете повече Идентифицирайте се или се регистрирайте за да изпращате коментари Tags Информация и помощ Питане относно ъпдейт на ядрото на сайт създаден с друпал 6 34 който да стане 6 35 9 Май 2015 17 39 JoaoNY Здравейте аз съм съвсем нов в системата Друпал и да съм честен още доста неща са ми малко чужди Имам нужда отследния съвет Как да вдигна версията на ядротона друпал 6 34 която да стане 6 35 но така че да не прецакам фиксовете които вече са зададени на въпросния сайт А фиксовете са най вече в модула views Понеже се притеснявам че ако ъпдейтна ядрото ще бъгна зааддените фиксове на някои от модулите Благодаря предварително на отзовалите се Поздрави 5 коментара Tags Информация и помощ Тема с блок форум и

    Original URL path: http://www.drupalbg.org/taxonomy/term/1 (2016-02-15)
    Open archived version from archive

  • Association News | Drupal BG
    s in dire need of an overhaul Spending some time on our BDD testing infrastructure will let us have more confidence that our new feature development won t cause unexpected regressions elsewhere on the site Overhauling this infrastructure will take a bit of time now but it s an investment that will pay dividends over time Infrastructure tuning Finally we also spent some time in December tuning our infrastructure We had just switched the last of our content delivery over to Fastly as our CDN for Drupal org and there was some tuning to do in our configuration Our infrastructure team also spent some time rebuilding some of the virtual machines that are part of our back end and cleaning up how we generate the docker images for our new faster development environments As always we d like to say thanks to all the volunteers who work with us and to the Drupal Association Supporters who made it possible for us to work on these projects Follow us on Twitter for regular updates drupal org drupal infra Personal blog tags whats new on Drupal org Категории Association News Drupal Association Board Meeting December 2015 5 Януари 2016 11 00 Last month we held our last board meeting of 2015 where we shared our recap of the Drupal 8 launch and then adjourned to the executive session As always you can review the materials minutes and recording of the meeting but I would like to dive more deeply into some of the board business than was discussed Board meetings in 2016 For the last several years we have held monthly public board meetings and taken great pains to ensure that anyone can attend or at least review materials and recordings The purpose of these meetings has been two fold to conduct board business and to inform the community because we value transparency For a time these two needs aligned very closely As the Association was building its internal capacity and increasing our operational effectiveness it made sense for us to report a lot of detail to the board as much of their focus was operational Now that our staff has grown and our operations have solidified there is less need for the board to step into operations The board is naturally shifting to more strategic topics For example rather than discussing in which city a DrupalCon should be held the board is discussing which kinds of audiences we need at future DrupalCons to better grow the project Strategic discussions have a longer time frame and they just don t need to happen as frequently as operational conversations So we are going to scale back the board meetings to five times per year remote in March at DrupalCon North America remote in July at DrupalCon Europe and remote in November Though we are reducing the number of board meetings that are held each year we remain committed to the community value of transparency Our teams here inside the Association will continue to produce monthly updates on their progress Previously these were documented in the monthly board packet In the future these updates will be shared via the Association blog which is then also republished on Drupal Planet We will also continue the practice of making all board meeting materials available to everyone whether or not they can attend the board meeting in person As always we welcome your questions and your concerns whether you want to share them with our staff directly via twitter or even by snail mail if you re into that sort of thing Board term renewals In between meetings we also used email to confirm the re election of several board seats Congratulations and thank you to Dries Buytaert dries Donna Benjamin kattekrab Sameer Verma sameer verma If you d like you can read about all the board members and their terms Flickr photo Chris Messina Категории Association News 12 Days of Drupal Community Nick Vidal 23 Декември 2015 19 33 The Drupal community is full of people who make the world a brighter place This month we are sharing more about the community members participating in our membership drive in this blog series We work together we motivate each other and we learn together Thank you to our community for inspiring us every day Nick Vidal nickvidal About Nick Nick has been an open source advocate for 15 years a Drupal community and camp organizer since 2007 and he has helped organize some of the Drupal camps in Latin America Nick brings passion to everything he does and he embodies what people think when they stay for the community What Nick says about membership The grant received from the Drupal Association has helped us print a total of 8 000 magazines about Drupal to be freely distributed at events all over Latin America The magazine contained an interview with Dries translated into 3 different languages English Spanish and Portuguese This magazine has been fundamental to spreading Drupal in Latin America It was launched when Dries came for the first time to Latin America back in 2011 Dries came back to Latin America for DrupalCon in 2015 and the scenario has changed dramatically The community has matured If you are not yet a member join the Drupal Association and be part of our success together Personal blog tags Membership community membership 2015 series Категории Association News 12 Days of Drupal Community Claudiu Cristea 21 Декември 2015 23 42 The Drupal community is full of people who make the world a brighter place This month we are sharing more about the community members participating in our membership drive in this blog series We work together we motivate each other and we learn together Thank you to our community for inspiring us every day Claudiu Cristea claudiu cristea About Claudiu Claudiu was awarded a Community Cultivation Grant He is President of Drupal Association Romania and a web developer Claudiu is a Core committer and part of the community for nearly 10 years What Claudiu says about membership Drupal Association helped us run one of our yearly conferences in 2012 when our community was unable to secure all the funds Through the Community Cultivation Grant program we were able to run DrupalCamp Arad 2012 an event organized by Drupal Romania Association The event is important for us because it s the only moment in the year when we can meet together as most of the Drupalers from across Romania If you are not yet a member join the Drupal Association and be part of our success together Personal blog tags Membership community membership 2015 series Категории Association News 12 Days of Drupal Community Donna Benjamin 18 Декември 2015 19 10 The Drupal community is full of people who make the world a brighter place This month we are sharing more about the community members participating in our membership drive in this blog series We work together we motivate each other and we learn together Thank you to our community for inspiring us every day Donna Benjamin kattekrab About Donna Donna is passionate about community and fulfills this by serving on the board of the Drupal Association and by chairing the Community Working Group She has a love of Inkscape Little Ms Drupal and has been a mentor advocate and all around genuine do er of amazing when it comes to our community Donna is known for her advice opinions and empathetic listening skills in making great things in our community happen What Donna says about membership The Drupal Association s work is fundamental to supporting the project at the heart of our community But I suspect there are thousands of people using Drupal every day who have absolutely no idea we exist or what work we do But many of them notice instantly the moment that Drupal org falters Supporting the team that supports our community is what matters most to me Drupal has made a big difference in my life Drupal has helped me keep my own lights on by providing an amazing platform to serve the needs of our clients Years ago we had our own homemade content management system It grew out of components we built for one client or another solving the same problems time and time again But it became unmanageable We couldn t keep up with the maintenance requirements of the system and also continue to serve our clients So we started evaluating the open source PHP content management systems available at the time Drupal answered that call We also discovered the community and the rest as they say is history If you are not yet a member join the Drupal Association and be part of our success together Personal blog tags Membership community membership 2015 series Категории Association News 12 Days of Drupal Community Dhruv Baldawa 17 Декември 2015 19 27 The Drupal community is full of people who make the world a brighter place This month we are sharing more about the community members participating in our membership drive in this blog series We work together we motivate each other and we learn together Thank you to our community for inspiring us every day Dhruv Baldawa dhruvbaldawa About Dhruv Dhruv is a developer who began his journey into Drupal as a Google Summer of Code student He lives in India and received a DrupalCon scholarship in 2012 to travel to Denver which suited him well as he is an avid traveler What Dhruv says about membership When I first posted a draft proposal I had no idea how Drupal worked I was truly amazed at how welcoming open and helping the community is It helped me learn about the various parts of Drupal s codebase the modules and other subsystems It was due to Drupal that I landed my first job Much of what I have achieved so far I owe to Drupal and its amazing community and it is real pleasure to be a part of it If you are not yet a member join the Drupal Association and be part of our success together Personal blog tags Membership community membership 2015 series Категории Association News 12 Days of Drupal Community Solomon Kitumba 16 Декември 2015 21 25 The Drupal community is full of people who make the world a brighter place This month we are sharing more about the community members participating in our membership drive in this blog series We work together we motivate each other and we learn together Thank you to our community for inspiring us every day Solomon Kitumba solomonkitumba About Solomon Solomon is a Community Cultivation Grant recipient and frontend developer He organizes the local community in Kampala Uganda and he spreads the word about Drupal as a Global Training Days trainer and through outreach tours at local universities Solomon loves good UX and calls himself passionately curious What Solomon says about membership The Community Cultivation Grant helped develop our local community We used it to fund our outreach to different groups of people who embraced Drupal as a software and as a community It helped raise the number of community members who both develop for and use Drupal New community members learned that Drupal is not difficult it is a money making tool you can embrace to build sites from simple blogs to very powerful web apps People in the community were shown the power of the community and how we can always help each other and also be part of the global community If you are not yet a member join the Drupal Association and be part of our success together Personal blog tags Membership community membership 2015 series Категории Association News Drupal at European Co Marketing Events in 2015 16 Декември 2015 21 11 As part of our mission to grow Drupal s adoption in global markets the Drupal Association launched a co marketing campaign this year that included exhibiting at major industry events in Europe With help from our sponsors Wunderkraut WunderUK undpaul and Deeson we were able to take Drupal to two marketing industry events dmexco and the Festival of Marketing Why showcase Drupal at marketing events Marketers are constantly seeking out new tools to manage their content and track and improve their customers digital experiences That s why we set out to convince them that Drupal could be the best way to turn their websites the strongest tools in their arsenals into even better platforms for great content and customer experiences Drupal at dmexco Drupal swag is a hit at dmexco Swing by say hello to the Drupal crew from DrupalAssoc Wunderkraut undpaul pic twitter com kVHOWT4lBU Drupal Association DrupalAssoc September 17 2015 Our first co marketing event was dmexco 2015 in Cologne Germany dmexco is a leading international exposition and conference for digital marketing media advertising and technology With the media and publishing sector being a target market for Drupal adoption this two day event was the perfect opportunity to introduce brand marketers and media professionals to the world of Drupal To show attendees why marketers love Drupal we got expert assistance from two strong industry leaders Wunderkraut and undpaul As sponsors of our co marketing campaign they not only helped offset the costs of exhibiting but were also instrumental in conveying our message to the attendees Anja and Luca from undpaul in Hannover and Lea and Daniel from Wunderkraut s Munich office joined our staff on site at the booth They did an outstanding job preparing case studies and answering even the trickiest attendee questions Thanks to all of you for your support The attendees we met at our booth had diverse professional backgrounds Many had not heard of Drupal and were curious to find out who we are and what we do Others were evaluating Drupal as their future CMS or were looking for a specific solution for their company s needs Others simply stopped by to snag some swag Drupal branded sunglasses and stickers were a hit and so were our staff s I love Drupal t shirts Mit Luca auf der dmexco Halle 9 D15 kommt vorbei drupal pic twitter com UbEsGYOOpw Anja Schirwinski aschiwi September 16 2015 Our presence at dmexco allowed us not only to connect with a somewhat untapped audience but also provided great networking with fellow exhibitors It was especially interesting to talk with software developers interested in integrating their products with Drupal And of course it was great running into some familiar Drupal faces in the exhibit halls Overall dmexco was a good experience for us raising awareness and highlighting our community s work in the European market As our first co marketing event it also allowed us to experiment and learn how to best promote Drupal in the marketplace Some of our biggest lessons learned revolved around what questions marketers were asking about Drupal So we updated our collateral to better reflect the answers to those questions and headed out to the Festival of Marketing Drupal at the Festival of Marketing With support from Deeson and Wunder UK we created a Building Block at the Festival of Marketing The Drupal experience included LEGOs how to s demos and case studies and a raffle Had a great time at FOM15 Congratulations to our winner and may the force be with you pic twitter com t2XDIudqn2 Drupal Association DrupalAssoc November 13 2015 Our goal for the event was to promote Drupal as a complete digital marketing solution Going into the event we expected there to be very little knowledge of what Drupal was and we were right But we had a lot of really great conversations at the Festival Visitors to our booth became very receptive and curious when they realized we weren t trying to sell them anything Lots of people got excited and began asking more about how Drupal works In a venue full of marketers and salespeople for proprietary companies many people seemed curious and excited about the concept of open source software It was also wonderful that when people asked what our community was all about answering it was easy after all they were witnessing it first hand Seeing Deeson and Wunder UK working in unison was a great illustration of the Drupal community at work and we couldn t be more thankful that they came together to help us out Категории Association News 12 Days of Drupal Community John P Weiksnar 16 Декември 2015 00 18 The Drupal community is full of people who make the world a brighter place This month we are sharing more about the community members participating in our membership drive in this blog series We work together we motivate each other and we learn together Thank you to our community for inspiring us every day John P Weiksnar jpw1116 About John John is a longtime organizer of the Western New York Drupal User Group WNYDUG and a Drupal evangelist John recently wrote a Drupal related blog series from interviews he conducted at DrupalCon Los Angeles What John says about membership The Community Cultivation Grant lived up to its name by helping us fund and launch our local user group s inaugural Drupal Camp This urban camp was the big bang that spawned our more focused mini camp format With less overhead and only a mountainside resort s boardroom participants got to experience Drupal presentations in a memorable way The best part of all some first time attendees at these events remain part of the local user group and to this day pop in to our monthly in person or online meet ups If you are not yet a member join the Drupal Association and be part of our success together Personal blog tags Membership community membership 2015 series Категории Association News 12 Days of Drupal Community Jeff Geerling 15 Декември 2015 23 29 The Drupal community is full of people who make the world a brighter place This month we are sharing more about the community members participating in our membership

    Original URL path: http://www.drupalbg.org/aggregator/sources/5 (2016-02-15)
    Open archived version from archive



  •