DOCSLIB.ORG

Drupal 8 Development Retrospective

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Drupal 8 Development Retrospective Drupal 8 Development Retrospective A timeline and retrospective from a core contributor 2011 2016 Drupal 7, Gates & Initiatives • DrupalCon Chicago 2011, Drupal 8 development starts immediately. • Dries discusses “gates” and initiatives to lead Drupal 8 development to improve quality and release management. • Initiatives include: Web Services, HTML5, UUID, and CMI • Followed by Multilingual, Scotch and Spark. 2011 2016 • PostgreSQL had critical bugs in 2010 during Drupal 7 RC1. Promised myself to be involved earlier in Drupal 8 development. • Woo! Drupal 7 is released, let’s go build some sites! • Entity API • Organic Groups • Views 2011 2012 2016 Symfony2 Adopted and Code Freeze Announced • DrupalCon Denver 2012: • Symfony2 adopted. • DrupalCon Munich 2012: • Code Slush and Code Freeze announced. • Moshe presents Migrate as an alternative to Upgrade Path at core conversation. 2011 2012 2016 • Began learning about Drupal 8. • Worked with Web Services initiative to bring Serializer and serialization module into Drupal 8. • Skeptical of Moshe’s Migrate proposal. • Took code freeze seriously: • Began porting contributed modules. • Began PostgreSQL bug fixes. 2011 2013 2016 Migrate adopted, Backdrop announced • Migrate is adopted as a new initiative. • Plugin API is rewritten again. • Some grow frustrated at the new OOP architecture. • Backdrop announced as alternative to compete in the smaller markets. Start dropping features from Drupal 8. 2011 2013 2016 • Became a mentor at DrupalCon Portland 2013. • PostgreSQL driver development • Blocked on a single issue for 9 months. 2011 2014 2016 Plugin, Performance, and Testing • Plugin API refactored again. • Configuration returns to database, but CMI still utilizes YAML for import/export. • DrupalCI initiative kicks into gear to improve drupal.org testing infrastructure. • Backdrop 1.0 release. 2011 2014 2016 • Made my pitch for PostgreSQL at DrupalCon Amsterdam 2014. • Joined up with DrupalCI Initiative as a way to be able to test patches in PostgreSQL instead of upload & pray. 2011 2015 2016 Drupal 8 Final Development Push • PHP version requirement increment • Update to newer Symfony 2 and other dependencies. • Good Code initiative started to utilize PHP features such as assert • Release Candidate 1 • Backdrop 1.1 released. 2011 2015 2016 • Fixed PostgreSQL driver with bzrudi71, stefan_r, and daffie using an external drupalci test bot. • DrupalCI initiative goes live on drupal.org. • My contributed modules lag behind for Drupal 7 maintenance because I’m too focused on Drupal 8 development. Retrospective • Initiatives: Were they successful? • Discussion as to whether leads felt empowered or not. • WSCII went well, but Crell felt like he could not make decisions. • Multilingual went well and Gabor felt like he could and did make decisions. • Clearer guidelines established and make it easier for feature development to be worked on in parallel to bug fixes. Retrospective • Symfony 2 Adoption: Was it worth it? • There was too much in Drupal to change. • And work is not complete. We need to focus on continuing to improve code quality as we shift to a more modern architecture. Retrospective • Symfony 2 Adoption: Was it worth it? • There was too much in Drupal to change. • And work is not complete. We need to focus on continuing to improve code quality as we shift to a more modern architecture. Retrospective • Code freeze announcement was meaningless in 2012. • Could we have done a better job at sticking to dates? • Or was Drupal 8 ready when it was ready? • Scale back the feature creep with minor version updates in development of Drupal 8.x.0 and Drupal 9.y.0. Retrospective • Anyone remember “small core”? • Providing a great CMS out-of-the-box for people to create and build web sites is the goal. • Josh Koenig: But is the “iron price” of Drupal too high for simple web sites? • Me: We must focus on reducing the burden of site maintenance and improve education for making Drupal more accessible for people who want to build a site, not a blog. Retrospective • PostgreSQL • SQL Server driver still exists in contrib and is able to influence core, but not enough to block release candidate. • JSON Field module exists to leverage PostgreSQL 9.2-9.4 native JSON. • We now have testing infrastructure and system that can test any database driver with docker containers. • Still things to improve about the driver, sacrifices made. Retrospective • Composer • Will be a nightmare for site builders or those who are not familiar with development practices. • Moving Drupal (and eventually contrib) to use semantic versioning. Retrospective • Migrate • I was correct. We face the same problems in Upgrade Path as we do Migrate out in the wild. • But Migrate does a better job and is flexible to handle many different “upgrade” situations. • It works fairly well. Retrospective • I am excited to build Drupal 8 web sites leveraging modern PHP and JavaScript dependencies. • PostgreSQL 9.4 is amazing and I want to leverage it to store entities objects in JSON with Serializer. • Configuration Management is going to rock. • WOOOOOO LET’S BUILD SOME DRUPAL 8 SITES! • Wait, this seems like deja vu….
Load more

Recommended publications
  • Sql Server to Aurora Postgresql Migration Playbook
    Microsoft SQL Server To Amazon Aurora with Post- greSQL Compatibility Migration Playbook 1.0 Preliminary September 2018 © 2018 Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offer- ings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without war- ranty of any kind, whether express or implied. This document does not create any warranties, rep- resentations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agree- ments, and this document is not part of, nor does it modify, any agreement between AWS and its cus- tomers. - 2 - Table of Contents Introduction 9 Tables of Feature Compatibility 12 AWS Schema and Data Migration Tools 20 AWS Schema Conversion Tool (SCT) 21 Overview 21 Migrating a Database 21 SCT Action Code Index 31 Creating Tables 32 Data Types 32 Collations 33 PIVOT and UNPIVOT 33 TOP and FETCH 34 Cursors 34 Flow Control 35 Transaction Isolation 35 Stored Procedures 36 Triggers 36 MERGE 37 Query hints and plan guides 37 Full Text Search 38 Indexes 38 Partitioning 39 Backup 40 SQL Server Mail 40 SQL Server Agent 41 Service Broker 41 XML 42 Constraints
    [Show full text]
  • On Snakes and Elephants Using Python Inside Postgresql
    On snakes and elephants Using Python inside PostgreSQL Jan Urba´nski [email protected] New Relic PyWaw Summit 2015, Warsaw, May 26 Jan Urba´nski (New Relic) On snakes and elephants PyWaw Summit 1 / 32 For those following at home Getting the slides $ wget http://wulczer.org/pywaw-summit.pdf Jan Urba´nski (New Relic) On snakes and elephants PyWaw Summit 2 / 32 1 Introduction Stored procedures PostgreSQL's specifics 2 The PL/Python language Implementation Examples 3 Using PL/Python Real-life applications Best practices Jan Urba´nski (New Relic) On snakes and elephants PyWaw Summit 3 / 32 Outline 1 Introduction Stored procedures PostgreSQL's specifics 2 The PL/Python language 3 Using PL/Python Jan Urba´nski (New Relic) On snakes and elephants PyWaw Summit 4 / 32 What are stored procedures I procedural code callable from SQL I used to implement operations that are not easily expressed in SQL I encapsulate business logic Jan Urba´nski (New Relic) On snakes and elephants PyWaw Summit 5 / 32 Stored procedure examples Calling stored procedures SELECT purge_user_records(142); SELECT lower(username) FROM users; CREATE TRIGGER notify_user_trig AFTER UPDATEON users EXECUTE PROCEDURE notify_user(); Jan Urba´nski (New Relic) On snakes and elephants PyWaw Summit 6 / 32 Stored procedure languages I most RDBMS have one blessed language in which stored procedures can we written I Oracle has PL/SQL I MS SQL Server has T-SQL I but Postgres is better Jan Urba´nski (New Relic) On snakes and elephants PyWaw Summit 7 / 32 Stored procedures in Postgres I a stored
    [Show full text]
  • Ubuntu Server Guide Basic Installation Preparing to Install
    Ubuntu Server Guide Welcome to the Ubuntu Server Guide! This site includes information on using Ubuntu Server for the latest LTS release, Ubuntu 20.04 LTS (Focal Fossa). For an offline version as well as versions for previous releases see below. Improving the Documentation If you find any errors or have suggestions for improvements to pages, please use the link at thebottomof each topic titled: “Help improve this document in the forum.” This link will take you to the Server Discourse forum for the specific page you are viewing. There you can share your comments or let us know aboutbugs with any page. PDFs and Previous Releases Below are links to the previous Ubuntu Server release server guides as well as an offline copy of the current version of this site: Ubuntu 20.04 LTS (Focal Fossa): PDF Ubuntu 18.04 LTS (Bionic Beaver): Web and PDF Ubuntu 16.04 LTS (Xenial Xerus): Web and PDF Support There are a couple of different ways that the Ubuntu Server edition is supported: commercial support and community support. The main commercial support (and development funding) is available from Canonical, Ltd. They supply reasonably- priced support contracts on a per desktop or per-server basis. For more information see the Ubuntu Advantage page. Community support is also provided by dedicated individuals and companies that wish to make Ubuntu the best distribution possible. Support is provided through multiple mailing lists, IRC channels, forums, blogs, wikis, etc. The large amount of information available can be overwhelming, but a good search engine query can usually provide an answer to your questions.
    [Show full text]
  • Mysql to Postgres Migration
    MySQL to Postgres Migration Deepak Murthy Who am I Database Administrator working at Pictage Inc The company provides online image hosting, printing and sales solutions, and services to professional photographers. The company is a leader in the industry. Pictage services more than 10,000 professional photographers all over the United States. Pictage is the photographer's one-stop and complete partner enabling online viewing, selling, and printing professional images. www.pictage.com www.shootq.com mysql2psql It can create postgresql dump file from mysql database or directly load data from mysql to postgresql (at about 100 000 records per minute). Translates most data types and indexes. Authors Max Lapshin et. al contents Installation requirements Things to take care before migration Migration of only schema Migration of only data Migration of both schema and data Excluding tables during migration Migrating only the selected tables Things to take care after migration Problems during migration Installation requirements Postgres 8.4 and above, Mysql 5.1 and above Ruby 1.9.1 – latest version Ruby gem 1.8.14 - Package manager for Ruby postgresql-server-dev-9.1 - The postgresql-devel package contains the header files and libraries ruby1.9.1-dev: This package contains the header files and library, necessary to make extension library for Ruby 1.9.1 Other libraries required: libmysqlclient-dev, libmysql- ruby1.9 Install Ruby postgresql interface (gem install pg) and Ruby mysql interface (gem install mysql) Things to take care before migration Generate a mysql2pgsql.yml file Create a separate user to access the mysql database or existing user which has capability to dump the database.
    [Show full text]
  • SPI Annual Report 2015
    Software in the Public Interest, Inc. 2015 Annual Report July 12, 2016 To the membership, board and friends of Software in the Public Interest, Inc: As mandated by Article 8 of the SPI Bylaws, I respectfully submit this annual report on the activities of Software in the Public Interest, Inc. and extend my thanks to all of those who contributed to the mission of SPI in the past year. { Martin Michlmayr, SPI Secretary 1 Contents 1 President's Welcome3 2 Committee Reports4 2.1 Membership Committee.......................4 2.1.1 Statistics...........................4 3 Board Report5 3.1 Board Members............................5 3.2 Board Changes............................6 3.3 Elections................................6 4 Treasurer's Report7 4.1 Income Statement..........................7 4.2 Balance Sheet............................. 13 5 Member Project Reports 16 5.1 New Associated Projects....................... 16 5.2 Updates from Associated Projects................. 16 5.2.1 0 A.D.............................. 16 5.2.2 Chakra............................ 16 5.2.3 Debian............................. 17 5.2.4 Drizzle............................. 17 5.2.5 FFmpeg............................ 18 5.2.6 GNU TeXmacs........................ 18 5.2.7 Jenkins............................ 18 5.2.8 LibreOffice.......................... 18 5.2.9 OFTC............................. 19 5.2.10 PostgreSQL.......................... 19 5.2.11 Privoxy............................ 19 5.2.12 The Mana World....................... 19 A About SPI 21 2 Chapter 1 President's Welcome SPI continues to focus on our core services, quietly and competently supporting the activities of our associated projects. A huge thank-you to everyone, particularly our board and other key volun- teers, whose various contributions of time and attention over the last year made continued SPI operations possible! { Bdale Garbee, SPI President 3 Chapter 2 Committee Reports 2.1 Membership Committee 2.1.1 Statistics On January 1, 2015 we had 512 contributing and 501 non-contributing mem- bers.
    [Show full text]
  • Install Perl Modules
    How to install OTRS (Open Source Trouble Ticket System) on Ubuntu 16.04 Prerequisites Ubuntu 16.04. Min 2GB of Memory. Root privileges. Step 1 - Install Apache and PostgreSQL In this first step, we will install the Apache web server and PostgreSQL. We will use the latest versions from the Ubuntu repository. Login to your Ubuntu server with SSH: ssh [email protected] Update Ubuntu repository. sudo apt-get update Install Apache2 and a PostgreSQL with the apt: sudo apt-get install -y apache2 libapache2-mod-perl2 postgresql Then make sure that Apache and PostgreSQL are running by checking the server port. netstat -plntu You will see port 80 is used by apache, and port 5432 used by PostgreSQL database. Step 2 - Install Perl Modules OTRS is based on Perl, so we need to install some Perl modules that are required by OTRS. Install perl modules for OTRS with this apt command: sudo apt-get install -y libapache2-mod-perl2 libdbd-pg-perl libnet-dns-perl libnet-ldap-perl libio-socket-ssl-perl libpdf-api2-perl libsoap-lite-perl libgd-text-perl libgd-graph-perl libapache- dbi-perl libarchive-zip-perl libcrypt-eksblowfish-perl libcrypt-ssleay-perl libencode-hanextra- perl libjson-xs-perl libmail-imapclient-perl libtemplate-perl libtemplate-perl libtext-csv-xs-perl libxml-libxml-perl libxml-libxslt-perl libpdf-api2-simple-perl libyaml-libyaml-perl When the installation is finished, we need to activate the Perl module for apache, then restart the apache service. a2enmod perl systemctl restart apache2 Next, check the apache module is loaded with the command below: apachectl -M | sort And you will see perl_module under 'Loaded Modules' section.
    [Show full text]
  • A Live Linux Based on KNOPPIX/DEBIAN with Special Emphasis on Scientific Packages Including ROOT Motivation (Students)
    ● Debian ROOT packages by ROOT team and Chr. H. Christensen ● Collaboration of Helmut Wolters (german), Vinc. Vangoni (Italian), Pedro Ferreia (French), Oscar Diaz Fouces (Spanish) ... PAIPIX: a live linux based on KNOPPIX/DEBIAN with special emphasis on scientific packages including ROOT Motivation (students) ● A live system requiring no installation ● Including latex to be able to undestand the source arXiv scientific papers. ● Including code development environments ● It should also support portuguese State of the art Several live systems available based either on Debian: KNOPPIX...or Gentoo. The major Linux releases like REDHAT or SUSE include a live DVD. While KNOPPIX was by far the best and most used, it did not met our goals Motivation (Supplement) The informatics people at my University discouraged me to do anything.... Choices ● Compressed file system of KNOPPIX seemed the best ● There was information around on how to extend modify the CD images ● It was based on the powerful and free Debian system ● Including only full Latex implied already to go from CD to DVD ● Once we opted for DVD the road was open to include: ●Scientific applications available in Debian ●New scientific applications by creating Debian packages ●Also the SERVER tools like web, database and Content M. Systems ●Nice things to help interesting the students like ... games ● Once installed on disk it becomes normal DEBIAN Scientific Packages Selected from Debian Development/ Prog. Visual Studio e .net gcc; g++; g77; .. Kdevelop Development Debuger and profiler Visual Studio e .net ddd valgrind Development Development (test) Visual Fortran and .net gcc-4.0; g++-4.0; gfortran-4.0; g95 Development fortran Java JDK Sun ..
    [Show full text]
  • ODBC Driver for Postgresql
    Contents I Table of Contents Part I What's New 1 Part II General Information 4 1 Overvie..w... .............................................................................................................................. 4 2 Feature..s.. ............................................................................................................................... 6 3 Compa.t.i.b..i.l.i.t.y.. ........................................................................................................................ 8 4 Requi.r.e..m...e..n..t.s.. ..................................................................................................................... 11 5 Licen.s.i.n..g.. ............................................................................................................................ 11 6 Gettin.g.. .S...u..p..p..o..r.t. .................................................................................................................. 14 Part III Using ODBC Driver 16 1 Install.a..t.i.o..n.. .......................................................................................................................... 16 Window s .......................................................................................................................................................... 17 Window s Sile.n...t. ..................................................................................................................................................... 20 macOS .........................................................................................................................................................
    [Show full text]
  • Maxim Kisselyov
    Maxim Kisselyov Kazakhstan, Nur-Sultan +77072065149(C), [email protected] Professional Objective IT Professional with 10+ years experience in Network Systems Administration with a primary focus on high loaded servers and on CISCO has to achieve a position in which it will be able to use my skills, education, and experience to your companies benefit. Fluent English. Ready to relocate. Education Bachelors in “Automated Electric Drives and Automation of Technological Processes and Production”, Pavlodar State University, Pavlodar 1997 Certificates and courses ITIL Foundation, 2015 JCCP(Tokyo), Utilization of Information and Control Systems in the Oil Downstream, 2014 Share Point,2013 Microsoft Certified Systems Engineer, 2007 Microsoft Certified Systems Administrator, 2006 Microsoft Certified Professional, 2005 Skills MCSE, ITIL, CISCO/HP ROUTING AND SWITCHING, NETWORK MANAGEMENT , IT SECURITY, DATA CENTER (HP OnboardAdmin), SIP, UNIX, AVAYA, ASTERISK, TMG, SQUID, BIND, DNS, PERL, ACTIVE DIRECTORY, POSTFIX, DOVECOT, DJANGO, DOCKER, LXC, CASSANDRA, ELASTICSEARCH, PUPPET, CHEF, OFFICE365, HP EVA, EXCHANGE 2010, SHAREPOINT 2010, HYPER-V, MS SQL, MySQL, POSTGRESQL, OpenWRT, OwnCloud, CAPTIVE PORTALS Completely responsible for Installation, configuring & troubleshooting of Network & Software & Hardware issues in Data Center. Experience “NAT Kazakhstan” LLP, Kazakhstan, Nur-Sultan www.nat.kz Advisory Engineer 2019-current Advisory in all IT aspects “ARTA Software” LLP, Kazakhstan, Nur-Sultan, www.arta.pro Systems manager 2017-2019 docker,
    [Show full text]
  • Postgresql Programmer's Guide
    PostgreSQL Programmer’s Guide The PostgreSQL Development Team Edited by Thomas Lockhart PostgreSQL Programmer’s Guide by The PostgreSQL Development Team Edited by Thomas Lockhart PostgreSQL is Copyright © 1996-9 by the Postgres Global Development Group. Table of Contents Summary......................................................................................................................................i 1. Introduction ............................................................................................................................1 Resources............................................................................................................................1 Terminology........................................................................................................................2 Notation ..............................................................................................................................3 Y2K Statement....................................................................................................................3 Copyrights and Trademarks................................................................................................4 2. Architecture ............................................................................................................................5 Postgres Architectural Concepts .........................................................................................5 3. Extending SQL: An Overview...............................................................................................7
    [Show full text]
  • Download Python Postgresql Tutorial
    Python PostgreSQL 1 Python PostgreSQL About the Tutorial Python is a general-purpose interpreted, interactive, object-oriented, and high-level programming language. It was created by Guido van Rossum during 1985-1990. Like Perl, Python source code is also available under the GNU General Public License (GPL). This tutorial gives enough understanding on Python programming language. This tutorial explains how to communicate with PostgreSQL database in detail, along with examples. Audience This tutorial is designed for python programmers who would like to understand the psycog2 modules in detail. Prerequisites Before proceeding with this tutorial, you should have a good understanding of python programming language. It is also recommended to have basic understanding of the databases — PostgreSQL. Copyright & Disclaimer Copyright 2020 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website or its contents including this tutorial. If you discover any errors on our website or in this tutorial, please notify
    [Show full text]
  • An Introduction to SQL and Postgresql Computing Laboratory
    An Introduction to SQL and PostgreSQL Computing Laboratory Department of Computing Ian Moor The PostgreSQL System PostgreSQL is a free relational database system supporting the SQL language available on a variety of hardware platforms. SQL SQL (Structured Query Language) is the standard relational query language with statements to create, remove, retrieve and maintain data in a relational database. SQL contains three main types of commands, Data Definition language (DDL), Data Manipulation language (DML), and Data Control language (DCL) statements. The specific version of SQL used by PostgreSQL can be used interactively via the psql front-end, embedded in programming languages like C or called from Java, perl and tcl. PostgreSQL supports a subset of SQL3 with extra types and commands. SQL syntax • SQL keywords and names contain alpha-numeric characters (including ‘_’) and must begin with a letter or ‘_’ and are case insensitive. A name containing other characters or which is an SQL keyword must be written in double quotes ‘"’. Column names, table names and database names are separate, so a column can have the same name as the table it is in. Keywords are usually written in uppercase letters. • The comment syntax is the same as C : /* ...*/, (but // comments are not allowed). Also ‘--’ comments out the rest of the line. • SQL statements end with ‘;’. Simple Data Types Every column in an SQL table must have a type describing the data in it. SQL supports integer data: as INT4 (4 bytes) and INT2 (2 bytes), Floating point data is stored as FLOAT8 (8 bytes) or FLOAT (4 bytes). Character data is held as fixed length strings padded with blanks: CHAR(n) where n is the length.
    [Show full text]