User:Denisarnaud

Denis Arnaud

I first installed RedHat (version 5, in 1998) with Oracle 8, when that latter was delivered on Linux for the first time... on a small Pentium-based computer with 600MB of disk and 64MB of RAM, hence proving to my hierarchy that Linux was ready for professional use. I started to be involved in the Fedora building process by translating documents and package descriptions, and have become a packager in 2009.

Contact

• Location: Grasse, France (Paris Time, CET UTC+1 / CEST UTC+2)
• Email: mailto:denis.arnaud_fedora@m4x.org
• GPG key: Denis Arnaud (Fedora Packager)
• Fedora Account / FAS: denisarnaud
• Fedora VOIP: Extension #5105604 / SIP Address: sip:denisarnaud@fedoraproject.org
• Fedora People Page: http://denisarnaud.fedorapeople.org
• GitHub: denisarnaud
• SourceForge: denis_arnaud
• Ohloh: denis_arnaud
• Launchpad (e.g., for OpenStack): denis-arnaud-lp
• StackOverflow: denis-arnaud
• Geonames: denis.arnaud
• Twitter: denis_arnaud
• Skype: denis.arnaud100
• Google Talk: denis.arnaud
• Yahoo! Messaging: denis_arnaud
• AIM: darnaud100
• Blog: http://fossdev.blogspot.com

Activities within Fedora

Boost

• Boost-1.48 for EPEL 5 and 6:
  • Boost-1.48 Review request in Bugzilla
  • Boost-1.48 Copr's project
  • Boost-1.48 SCL (Software Collection)
• Boost 1.55 Feature for Fedora 21 (completed in June 2014)(Boost 1.56 was not ready in time)
• Boost 1.54 Feature for Fedora 20 (completed in October 2013)
• Boost 1.53 Feature for Fedora 19 (completed in March 2013)
• Boost 1.50 Feature for Fedora 18 (completed in October 2012)
• Boost 1.48 Feature for Fedora 17 (completed in February 2012)
• Boost 1.47 Feature for Fedora 16 (completed in September 2011)
• Boost 1.46 Feature for Fedora 15 (completed in early 2011)
• Boost 1.44 Feature for Fedora 14 (completed mid 2010)
• Boost 1.41 Feature for Fedora 13 (completed in early 2010)
• Boost-1.41 for EPEL 4/5 Review Request (completed mid 2011)
• Modularized Boost:
  • Boost super-project GitHub repository
  • Getting Started with Modular Boost (Trac Web site for Modularized Boost)
  • Contribution Tutorial for Boost.Geometry (as an example of Boost module)

Bringing and maintaining a few packages to Fedora

• My own open source software:
  • Hypertable: RE2, the fast C++ alternative to backtracking RE engines (PkgApp / PkgDB / Google code)
  • OpenTREP, OpenTravelData and OpenGeo++
  • Airline Travel Market simulation components: RMOL (PkgApp / PkgDB / SF), Standard Airline IT C++ Library (PkgApp / PkgDB / SF).
  • Extra CPPUnit and CruiseControl Tools
• Some others which have made their way into Fedora (e.g., WSDLPull, SOCI, R-msm, R-RM2)
• Some others not yet in Fedora (e.g., BLCR, Eucalyptus, Slurm)

A few quick links on Fedora packages (to ease my maintenance tasks)

• First of all:
  • A link to the wonderful Fedora Community platform (not enough advertised!)
  • A link to another wonderfull Fedora application for search and information about packages (same comment as above)

• Notification system (FMN)

• Full list of packages waiting for a reviewer here.

• List of my packages available in Fedora.

• List of my packages that have passed review, are under review or await review.

• List of (open or closed) reviews for my packages.

• Reviews I have done: see full list or just packages under review or packages that have passed review.

• List of reviews where I have left some comments.

• The ticket for my application to the proven-packager group.

• Bugzilla Review Request template for simulator-related projects

• Bugzilla template for creating a typical review request

Material for Reviews

Tracking of Package Requests

• New Review Requests, waiting for review (Cached for faster access)
• Review requests needing a sponsor
• Packages Currently Under Review (Cached for faster access)
• Packages Reviewed but not Closed
• General Cache for the Package Review Status

Documentation

Packaging

General

• Welcome page for the package maintainers
• Packaging Guidelines
• Packaging tricks

Specific guidelines

• RPM macros
• CMake
• Python
• R
• MPI
• MinGW / MinGW future
• Scriplets/Snippets
• Naming
• Patch upstream status
• Licensing Guidelines and Fedora Licensing
• Software Collection (SCL) guidelines - Draft

Package testing

• Proven tester procedure
• Critical path packages
• Jenkins@infra

Package updating

• Updates Policy
• Update how-to
• Upstream release monitoring

Package retiring

• How to remove a package at end of life

Reviews

• Package Review Guidelines
• Package Review Process
• Package SCM/Git Request
• Package Review SIG
• Tom "Spot" Callaway's Review Cheat Sheet

Compositions / Collections

• How to use and edit comps.xml for package groups

Tools

• Koji how-to
• Bodhi-client how-to
• Fedora Easy Karma (f-e-k)
• Fedora-Review tool
• Create a new rel-eng ticket
• mockchain use cases and examples (April 2012)

Package information pages (and database)

• Fedora package database (DB) portal
• Package List
• My packages

Hacking on Fedora/RedHat/CentOS

• Out 0f office notification
• All the SIGs (Special Interest Groups)
  • Geographic Information System (GIS) SIG
  • Cloud SIG
  • Package Review SIG
  • Science and Technology SIG
  • Server SIG

NoSQL

• NoSQL SIG
• Hadoop on Fedora (from F20)
• Hypertable

Virtualisation / Cloud Computing

General

• Virtualisation
• Getting started with virtualization

Cloud SIG

• Meeting logs
• Cloud guide / Fedora in the cloud

Cloud solutions submitted to Fedora

• Marketing material
  • Cloud SIG
  • OpenStack in Fedora
• Fedora 17 feature: XAPI / Xen tool stack
• Fedora 16 feature: Aeolus
• Eucalyptus (AWS-compatible IaaS)
• Docker Cloud Image
• Cloud image creation with Koji's Image Factory
  • Fedora 17 feature: Eucalyptus
• Fedora 17 feature: Open vSwitch
• GSOC 2012 - Bringing the Cloud to the Fedora Desktop
• OpenStack
  • OpenStack in Fedora
  • OpenStack status reports
  • Getting started with OpenStack
    • Getting started with OpenStack (Grizzly) on Fedora 19 (Test Day:2013-04-02 OpenStack)
    • Getting started with OpenStack (Folsom) on Fedora 18 (Test Day:2012-09-18 OpenStack)
    • Getting started with OpenStack (Essex) on Fedora 17 / My own hands on guide for OpenStack on Fedora 17
    • Getting started with OpenStack Nova
    • Getting started with OpenStack on EPEL (CentOS/RedHat)
    • Set up and (QA) test of Quantum v2
  • devstack
  • Installing and running OpenStack Horizon Dashboard
  • Fedora 19 feature: OpenStack Grizzly (next stable release)
  • Fedora 18 feature: OpenStack Folsom (current stable release)
  • OpenShift Origin
    • Fedora 18 feature: OpenShift Origin (OpenShift on top of OpenStack)
  • [2012-03-08] OpenStack Test Day
  • Fedora 18 feature: OpenStack using Oz for image building
• oVirt packaging
• Fedora 17 feature: OpenNebula
• CloudStack
• Fedora 15 feature: BoxGrinder
• CloudFS / Fedora 16 feature: HekaFS
• Fedora 16 feature: Sheepdog
• Cloud images (mainly for Amazon EC2)
  • VM Image Creation

Amazon (EC2)

• EC2 Primer

Tools

• (third party) Review helper tool
• Fedora active user Python script (see also the corresponding Git repository)
• Get the tree of dependencies of any given package:

repoquery --requires --recursive --output=ascii-tree pkgname

Brainstorming Section about Packaging

Using Git Work-flow for Packaging

• Building Debian packages with a Git workflow using "git-buildpackage":
  • http://wiki.debian.org/PackagingWithGit
  • http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html
  • http://www.eyrie.org/~eagle/notes/debian/git.html
• Keeping patches as commits on a "patch-queue" branch:
  • https://honk.sigxcpu.org/piki/development/debian_packages_in_git/
• Another tool for managing Debian packages with Git, "git-dpm":
  • http://git-dpm.alioth.debian.org/
  • http://git-dpm.alioth.debian.org/examples.html
• Recent discussions on Git packaging workflows in Debian:
  • http://wiki.debian.org/GitPackagingWorkflow
  • http://wiki.debian.org/GitPackagingWorkflow/DebConf11BOF
  • http://lists.debian.org/debian-devel/2011/07/msg00771.html
• TopGit, a patch-queue manager:
  • http://repo.or.cz/w/topgit.git?a=blob;f=README
• Recent discussions in Fedora about that subject:
  • http://lists.fedoraproject.org/pipermail/devel/2011-September/156403.html
  • https://rwmj.wordpress.com/2011/08/09/nice-rpm-git-patch-management-trick
• Proposal to add version control key within the specification file