In Contributor's Guide

Total Page:16

File Type:pdf, Size:1020Kb

In Contributor's Guide LilyPond The music typesetter Contributor’s Guide The LilyPond development team ☛ ✟ This manual documents contributing to LilyPond version 2.21.82. It discusses technical issues and policies that contributors should follow. This manual is not intended to be read sequentially; new contributors should only read the sections which are relevant to them. For more information about different jobs, see Section “Help us” in Contributor’s Guide. ✡ ✠ ☛ ✟ For more information about how this manual fits with the other documentation, or to read this manual in other formats, see Section “Manuals” in General Information. If you are missing any manuals, the complete documentation can be found at http://lilypond.org/. ✡ ✠ Copyright ⃝c 2007–2020 by the authors. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections. A copy of the license is included in the section entitled “GNU Free Documentation License”. For LilyPond version 2.21.82 i Table of Contents 1 Introduction to contributing .................................. 1 1.1 Help us ................................................... ......................... 1 1.2 Overview of work flow ................................................... .......... 2 1.3 Summary for experienced developers ............................................... 2 1.4 Mentors ................................................... ........................ 3 2 Quick start................................................... ... 5 2.1 LilyDev................................................... ......................... 5 Installing LilyDev in VirtualBox ................................................... .. 5 Configuring LilyDev in VirtualBox ................................................... 7 2.2 Compiling with LilyDev................................................... ......... 8 2.3 Now start work! ................................................... ................ 9 3 Working with source code .................................... 10 3.1 Setting up ................................................... ..................... 10 3.1.1 Installing Git ................................................... ............. 10 3.1.2 Cloning and forking the repository ........................................... 10 3.1.3 Configuring Git ................................................... ........... 10 3.2 Git cheat sheet ................................................... ................ 11 Pulling recent changes ................................................... ........... 11 Viewing the history ................................................... .............. 11 Switching branches ................................................... .............. 11 Listing branches ................................................... ................. 12 Staging and committing files ................................................... ..... 12 Amending and reverting changes ................................................... 12 Uploading your branch for review ................................................... 12 Deleting branches ................................................... ................ 12 3.3 Lifecycle of a merge request ................................................... .... 13 3.3.1 Uploading a patch for review ................................................. 13 3.3.2 Automated and manual testing............................................... 13 3.3.3 Patch countdown ................................................... ......... 13 3.3.4 Merging to master ................................................... ........ 14 3.3.5 Abandoned patches ................................................... ....... 14 3.4 Writing good commit messages................................................... 14 3.5 Commit access................................................... ................. 15 3.6 Further Git documentation resources .............................................. 16 3.7 Repository directory structure ................................................... 16 3.8 Other repositories................................................... .............. 18 4 Compiling ................................................... .. 20 4.1 Overview of compiling ................................................... ......... 20 4.2 Requirements ................................................... .................. 20 4.2.1 Requirements for running LilyPond .......................................... 20 4.2.2 Requirements for compiling LilyPond......................................... 21 Fedora................................................... ........................ 21 Linux Mint ................................................... ................... 22 OpenSUSE ................................................... ................... 22 ii Ubuntu................................................... ....................... 23 Other ................................................... ........................ 23 4.2.3 Requirements for building documentation .................................... 24 4.3 Getting the source code ................................................... ........ 25 4.4 Configuring make ................................................... .............. 26 4.4.1 Running ./autogen.sh ................................................... ... 26 4.4.2 Running ../configure ................................................... ... 26 Configuration options ................................................... ......... 26 Checking build dependencies ................................................... .. 26 Configuring target directories ................................................... 27 4.5 Compiling LilyPond ................................................... ........... 27 4.5.1 Using make ................................................... ............... 27 4.5.2 Saving time with the -j option............................................... 28 4.5.3 Useful make variables ................................................... ..... 28 4.6 Post-compilation options ................................................... ....... 28 4.6.1 Installing LilyPond from a local build ........................................ 28 4.6.2 Generating documentation ................................................... 28 Documentation editor’s edit/compile cycle ....................................... 28 Building documentation ................................................... ...... 29 Building a single document ................................................... ... 29 Saving time with CPU_COUNT ................................................... .. 30 Installing documentation................................................... ...... 30 Building documentation without compiling ....................................... 30 4.6.3 Testing LilyPond binary ................................................... .. 31 4.7 Problems ................................................... ...................... 31 Compiling on MacOS X................................................... .......... 31 FreeBSD................................................... ......................... 32 International fonts ................................................... ............... 32 Using lilypond python libraries................................................... ... 32 4.8 Concurrent stable and development versions....................................... 32 4.9 Build system ................................................... .................. 33 5 Documentation work ......................................... 34 5.1 Introduction to documentation work .............................................. 34 5.2 \version in documentation files .................................................. 34 5.3 Documentation suggestions ................................................... .... 35 5.4 Texinfo introduction and usage policy ............................................. 36 5.4.1 Texinfo introduction ................................................... ...... 36 5.4.2 Documentation files ................................................... ....... 36 5.4.3 Sectioning commands ................................................... ..... 37 5.4.4 LilyPond formatting ................................................... ...... 38 5.4.5 Text formatting ................................................... ........... 40 5.4.6 Syntax survey................................................... ............. 40 Comments ................................................... .................... 40 Cross references ................................................... .............. 41 External links ................................................... ................ 41 Fixed-width font................................................... .............. 41 Indexing................................................... ...................... 42 Lists................................................... .......................... 43 Special characters................................................... ............. 43 Miscellany ................................................... .................... 43 5.4.7 Other text concerns ................................................... ....... 44 5.5 Documentation policy................................................... .......... 44 5.5.1 Books ................................................... .................... 44 iii 5.5.2 Section
Recommended publications
  • Source Code Trees in the VALLEY of THE
    PROGRAMMING GNOME Source code trees IN THE VALLEY OF THE CODETHORSTEN FISCHER So you’ve just like the one in Listing 1. Not too complex, eh? written yet another Unfortunately, creating a Makefile isn’t always the terrific GNOME best solution, as assumptions on programs program. Great! But locations, path names and others things may not be does it, like so many true in all cases, forcing the user to edit the file in other great programs, order to get it to work properly. lack something in terms of ease of installation? Even the Listing 1: A simple Makefile for a GNOME 1: CC=/usr/bin/gcc best and easiest to use programs 2: CFLAGS=`gnome-config —cflags gnome gnomeui` will cause headaches if you have to 3: LDFLAGS=`gnome-config —libs gnome gnomeui` type in lines like this, 4: OBJ=example.o one.o two.o 5: BINARIES=example With the help of gcc -c sourcee.c gnome-config —libs —cflags 6: gnome gnomeui gnomecanvaspixbuf -o sourcee.o 7: all: $(BINARIES) Automake and Autoconf, 8: you can create easily perhaps repeated for each of the files, and maybe 9: example: $(OBJ) with additional compiler flags too, only to then 10: $(CC) $(LDFLAGS) -o $@ $(OBJ) installed source code demand that everything is linked. And at the end, 11: do you then also have to copy the finished binary 12: .c.o: text trees. Read on to 13: $(CC) $(CFLAGS) -c $< manually into the destination directory? Instead, 14: find out how. wouldn’t you rather have an easy, portable and 15: clean: quick installation process? Well, you can – if you 16: rm -rf $(OBJ) $(BINARIES) know how.
    [Show full text]
  • Red Hat Enterprise Linux 6 Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
    [Show full text]
  • The Javascript Revolution
    Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Shockers: Scribble & Fortuna Congrats on sneaky strategizing to get yourself to the top :) The moment of fruit: the class has spoken Shockers: Scribble & Fortuna Congrats on sneaky strategizing to get yourself to the top :) The moment of fruit: the class has spoken Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Congrats on sneaky strategizing to get yourself to the top :) The moment of fruit: the class has spoken Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Shockers: Scribble & Fortuna The moment of fruit: the class has spoken Top teams present at Segfault Tank on 4/21: 1 Duel: 6 (2 extra shifted from self votes) 2 Ambassador: 4 3 QuickSource: 3 4 ChalkBoard: 3 5 Fortuna Beer: 3 Bottom teams present in class this Thursday 4/16: 1 Scribble: 2 2 ClearViz: 2 3 AllInOne: 1 4 TripSplitter: 0 Shockers: Scribble & Fortuna Congrats on sneaky strategizing
    [Show full text]
  • Download Piano Composition App for Windows 10 Musescore 2 Is a Powerful Windows 10 App for Music Composition and Practice
    download piano composition app for windows 10 MuseScore 2 is a powerful Windows 10 app for music composition and practice. MuseScore 2 is an open sourced and highly functional app with a long list of features to help musicians compose or play music. The app is available for free on PCs through the Windows Store but isn't available on Windows 10 Mobile or any other Windows devices. A few highlights of MuseScore 2 include: Composing music with multiple parts. Ability to add lyrics. Option to import music from a vast Musescore library. Ability to export or print music. Playing back sheet music. Plugin support to enhance the app. If you compose music or just want to playback music as part of practicing to hear how it's supposed to sound, MuseScore 2 is a must have app. Composing with MuseScore 2. MuseScore 2 allows you to compose long scores with multiple staves of music. You can add from a wide range of instruments and place them on either the treble or bass clef. Writing music from scratch is pretty straightforward. You click on the staff and can either press the letter keys and enter their respective note or select them using a mouse. You can easily change the length of notes or rests and play around with your music. This is a big advantage over composing with paper and pencil. If you'd like to import a song that someone has already composed and tweak it you can use Musescore's large music library. Musescore users measure over 3 million so there isn't a shortage of music to choose from.
    [Show full text]
  • Entation to Be Used by Developers and Webmasters
    Programming with SPIP DOCUMENTATION TO BE USED BY DEVELOPERS AND WEBMASTERS SPIP’s version 2.1.0+ / August 2010 SPIP’s version 2.1.0+ / August 2010 SPIP is both a publication system and a development platform. After a quick tour of SPIP’s features, we will describe how it works and explain how to develop with it using helpful examples wherever possible. This documentation targets webmasters with knowledge of PHP, SQL, HTML, CSS and JavaScript. Contents Preface..................................................................................... 7 Notes about this documentation............................................... 9 Introduction ............................................................................ 11 The templates ........................................................................ 15 Contents of the directories ..................................................... 87 Extending SPIP .................................................................... 101 Functionalities ...................................................................... 197 Forms ................................................................................... 229 SQL access.......................................................................... 253 Creating your own plugins.................................................... 303 Examples ............................................................................. 315 Glossary ............................................................................... 321 Index ...................................................................................
    [Show full text]
  • Volume 51 April, 2011
    Volume 51 April, 2011 e17: Create Your Own Custom Themes e17: Running Ecomorph, Part 2: Settings e17: Tips & Tricks Video: Part 3 ­ Converting Files With MyMencoder Video: Part 4 ­ MyMencoderDVD Removing A Logo With Avidemux Using Scribus, Part 4: Layers Game Zone: Pipewalker Plus Rudge's Rain: Making Music More With PCLinuxOS Inside! WindowMaker on PCLinuxOS: Working With Icons Burning CDs Over The Internet With Or Without An ISO Alternate OS: Icaros, Part 2 Firefox Add­on: Video DownloadHelper Learning rtmpdump Through Examples TTaabbllee OOff CCoonntteennttss by Paul Arnote (parnote) 3 Welcome From The Chief Editor 4 e17: Running Ecomorph, Part 2 ­ Settings The holidays have finally come and gone, the 6 Using Scribus, Part 4: Layers packages have all been unwrapped, the Christmas tree and other holiday decorations are coming down, 7 Screenshot Showcase and a new year is upon us. Texstar and the The PCLinuxOS name, logo and colors are the trademark of 8 Video: Part 3 ­ Converting Files With MyMencoder PTCexLsitnaru. xOS Packaging Crew are busy putting the 12 ms_meme's Nook: Top Of My Desktop new tool chain to good use, working on getting the PTChLeiNnEuWxOPSCL2in0u1x0OSreMleagaaszeinneeisaaremrotnothclyoomnlpinle tion. The 13 Double Take & Mark's Quick Gimp Tip upudbalicteatsiocnocnontitnaiuneingtoPCroLlilnuoxuOtSa­rtealanteadmmatzeirniagls.pIat icse, with 14 e17: Create Your Own Custom Themes litpeurbalisllhyehdupnrimdraeridlysfoorfmneemwbearsnodf tuhpedPaCtLeindupxOaSckages community. The Magazine staff is comprised of volunteers 20 Screenshot Showcase bferocmomtheinPgCaLvinauixlOabSlecoemvmeurnyityw. eek. 21 Video: Part 4 ­ MyMencoderDVD TVhisisit musoonntlihne'samt hattgp:a//zwiwnwe.pccolovsemrafge.caotmures snow covered 25 Screenshot Showcase photos from ms_meme. On the inside, the contents This release was made possible by the following volunteers: 26 Alternate OS: Icaros, Part 2 are hot enough to melt that snow.
    [Show full text]
  • High Tech on a Low Budget
    HIGH TECH ON A LOW BUDGET Finding Technology That Teaches Without Breaking The Bank Iowa Bandmaster's Association Conference May 11, 2012 2:00pm Chad Criswell- Southeast Polk Community Schools All of the links provided in this document are also available as clickable links at www.MusicEdMagic.com Based on the National Standards and on content guidelines available at: www.menc.org/resources/view/the-school-music-program-a-new-vision 1 & 2 - Singing or Playing alone and with others, a varied repertoire of music. Software and iPad Apps: Special Needs: SmartMusic Kinectar- Free http://www.smartmusic.com http://www.kinectar.org eJamming http://www.ejamming.com iPad Apps: Skype APS Music Master Pro http://www.skype.com ForScore Trombone Pro/Trumpet Pro/French Horn Pro Song Surgeon Flute+ http://www.songsurgeon.com/ Instruments in Reach Clarinet Quiz Aviary Tonara http://www.aviary.com Seline and Seline HD Community Band http://www.community-band.com 3. Improvising melodies, variations, and accompaniments. Software: iShed Jazz Impro-visor- FREE http://www.themusicinteractive.com/TMI/Downloads http://www.cs.hmc.edu/~keller/jazz/improvisor O Generator iPad Apps: http://www.o-music.tv Loopseque Improvox Aviary- FREE http://www.aviary.com Hardware: JamStudio - FREE BOSS BR-80 Digital Audio Recorder http://www.jamstudio.com 4. Composing and arranging music within specified guidelines. Music Notation Software: Finale Notepad 2012- FREE iPad Notation Apps: http://www.finalenotepad.com Notion - $15 Scorio- $4 MuseScore- FREE http://www.musescore.com Composition Tutorials: PyWare MusicWriter Touch Secret Composer http://www.pyware.com/musicwriter/ http://www.secretcomposer.com Hyperscore Digital Audio Workstations: http://www.hyperscore.com Ardour - (Pay what you feel it is worth) - Mac and Linux http://www.ardour.org Noteflight http://www.musicedmagic.com/music-technology/essential-free- LMMS- FREE - Windows and Linux music-education-software.html http://lmms.sourceforge.net 5.
    [Show full text]
  • Leafpad Download
    Leafpad download LINK TO DOWNLOAD Download Leafpad Latest Version for Linux – The last but not least software you can take as an option for a text editor is Leafpad. Have you ever heard about it before? If not, let’s come to define it based on Wikipedia. Well, it is stated that Leafpad is an open source . Download Leafpad for Linux - Leafpad is a GTK based simple text editor. 11/5/ · I n this article, we are going to learn How to install Leafpad Linux text editor in Ubuntu. Leafpad is a nice open-source text editor for Linux. It’s not an advanced text editor like vi but a simple lightweight GTK+ based user-friendly text editor application comes with some basic features mentioned below.. Print documents. Search for any phrase or word & replace it. The Leafpad program tool can be installed in such operational systems, as Linux, FreeBSD and Maemo. Among the disadvantages of the utility is the absence of syntax highlight and the capability of non- printed (system) symbols display. For close acquaintance with the app abilities, just download Leafpad for free from the official web-resource. Leafpad - posted in Linux How-To and Tutorial Section: Leafpad is a basic text renuzap.podarokideal.rues: Display line numbers - Limitless undo/redo Installation instructions are provided below by. Leafpad is not available for Windows but there are plenty of alternatives that runs on Windows with similar functionality. The most popular Windows alternative is Notepad++, which is both free and Open renuzap.podarokideal.ru that doesn't suit you, our users have ranked more than 50 alternatives to Leafpad and loads of them are available for Windows so hopefully you can find a suitable replacement.
    [Show full text]
  • The GNOME Desktop Environment
    The GNOME desktop environment Miguel de Icaza ([email protected]) Instituto de Ciencias Nucleares, UNAM Elliot Lee ([email protected]) Federico Mena ([email protected]) Instituto de Ciencias Nucleares, UNAM Tom Tromey ([email protected]) April 27, 1998 Abstract We present an overview of the free GNU Network Object Model Environment (GNOME). GNOME is a suite of X11 GUI applications that provides joy to users and hackers alike. It has been designed for extensibility and automation by using CORBA and scripting languages throughout the code. GNOME is licensed under the terms of the GNU GPL and the GNU LGPL and has been developed on the Internet by a loosely-coupled team of programmers. 1 Motivation Free operating systems1 are excellent at providing server-class services, and so are often the ideal choice for a server machine. However, the lack of a consistent user interface and of consumer-targeted applications has prevented free operating systems from reaching the vast majority of users — the desktop users. As such, the benefits of free software have only been enjoyed by the technically savvy computer user community. Most users are still locked into proprietary solutions for their desktop environments. By using GNOME, free operating systems will have a complete, user-friendly desktop which will provide users with powerful and easy-to-use graphical applications. Many people have suggested that the cause for the lack of free user-oriented appli- cations is that these do not provide enough excitement to hackers, as opposed to system- level programming. Since most of the GNOME code had to be written by hackers, we kept them happy: the magic recipe here is to design GNOME around an adrenaline response by trying to use exciting models and ideas in the applications.
    [Show full text]
  • Values and Configuration of Users in the Design of Software Source Code
    International Journal of Communication 11(2017), 1112–1132 1932–8036/20170005 Values and Configuration of Users in the Design of Software Source Code STÉPHANE COUTURE1 Glendon College, York University, Canada Based on an empirical study of two free and open source software projects, this article focuses on how choices of design within software source code are articulated with values and may favor certain categories of actors over others. After introducing the aim and approach of the study and presenting the studied projects, the article analyzes two controversies that show the articulation of values, configuration of users, and source code design. In conclusion, I argue for the importance for communication and media studies to study the use of source code and how its design may reflect values or may facilitate or constrain the agencies of certain categories of people. Keywords: software source code, free and open source software, digital technologies, configuration of users, values, science and technology studies When I am a graphic designer, my interface is Photoshop, with its buttons, its windows, etc. When I am developer, my interface is code. It is through code that I interact with what I am building, a program. (Interview sf03, July 2009) This quote from an interview I conducted in the course of this study grasps a fundamental argument I want to bring forward in this article: that software source code should be analyzed as an interface with which actors interact to build or modify software. Although metaphors of code are regularly mobilized in communication studies, few studies seem to have been done to closely and empirically investigate what source code exactly is and how its design may reflect values or may facilitate or restrain the capacity of some people to participate in the making of digital technologies.
    [Show full text]
  • Musical Notation Codes Index
    Music Notation - www.music-notation.info - Copyright 1997-2019, Gerd Castan Musical notation codes Index xml ascii binary 1. MidiXML 1. PDF used as music notation 1. General information format 2. Apple GarageBand Format 2. MIDI (.band) 2. DARMS 3. QuickScore Elite file format 3. SMDL 3. GUIDO Music Notation (.qsd) Language 4. MPEG4-SMR 4. WAV audio file format (.wav) 4. abc 5. MNML - The Musical Notation 5. MP3 audio file format (.mp3) Markup Language 5. MusiXTeX, MusicTeX, MuTeX... 6. WMA audio file format (.wma) 6. MusicML 6. **kern (.krn) 7. MusicWrite file format (.mwk) 7. MHTML 7. **Hildegard 8. Overture file format (.ove) 8. MML: Music Markup Language 8. **koto 9. ScoreWriter file format (.scw) 9. Theta: Tonal Harmony 9. **bol Exploration and Tutorial Assistent 10. Copyist file format (.CP6 and 10. Musedata format (.md) .CP4) 10. ScoreML 11. LilyPond 11. Rich MIDI Tablature format - 11. JScoreML RMTF 12. Philip's Music Writer (PMW) 12. eXtensible Score Language 12. Creative Music File Format (XScore) 13. TexTab 13. Sibelius Plugin Interface 13. MusiXML: My own format 14. Mup music publication program 14. Finale Plugin Interface 14. MusicXML (.mxl, .xml) 15. NoteEdit 15. Internal format of Finale (.mus) 15. MusiqueXML 16. Liszt: The SharpEye OMR 16. XMF - eXtensible Music 16. GUIDO XML engine output file format Format 17. WEDELMUSIC 17. Drum Tab 17. NIFF 18. ChordML 18. Enigma Transportable Format 18. Internal format of Capella (ETF) (.cap) 19. ChordQL 19. CMN: Common Music 19. SASL: Simple Audio Score 20. NeumesXML Notation Language 21. MEI 20. OMNL: Open Music Notation 20.
    [Show full text]
  • Downloads." the Open Information Security Foundation
    Performance Testing Suricata The Effect of Configuration Variables On Offline Suricata Performance A Project Completed for CS 6266 Under Jonathon T. Giffin, Assistant Professor, Georgia Institute of Technology by Winston H Messer Project Advisor: Matt Jonkman, President, Open Information Security Foundation December 2011 Messer ii Abstract The Suricata IDS/IPS engine, a viable alternative to Snort, has a multitude of potential configurations. A simplified automated testing system was devised for the purpose of performance testing Suricata in an offline environment. Of the available configuration variables, seventeen were analyzed independently by testing in fifty-six configurations. Of these, three variables were found to have a statistically significant effect on performance: Detect Engine Profile, Multi Pattern Algorithm, and CPU affinity. Acknowledgements In writing the final report on this endeavor, I would like to start by thanking four people who made this project possible: Matt Jonkman, President, Open Information Security Foundation: For allowing me the opportunity to carry out this project under his supervision. Victor Julien, Lead Programmer, Open Information Security Foundation and Anne-Fleur Koolstra, Documentation Specialist, Open Information Security Foundation: For their willingness to share their wisdom and experience of Suricata via email for the past four months. John M. Weathersby, Jr., Executive Director, Open Source Software Institute: For allowing me the use of Institute equipment for the creation of a suitable testing
    [Show full text]