Env and Stacks/Nominations

We're OPEN!
The nomination period is in progress! Please add your nomination before 23:59:59 UTC on January 19, 2015!

The following elections will take place in January 2015:

• Environment and Stacks Working Group (four seats)
• FESCo (Engineering) (five seats)

All dates and times noted are UTC time.

Env and Stacks Elections January 2015

As per the responses to the mailing list request, the following finish their terms, and the seats are up for re-election:

• Bohuslav Kabrda (bkabrda)
• Tadej Janež (tjanez)
• Sam Kottler (samkottler)
• Petr Kovář (pkovar)

More information at the Env and Stacks Env and Stacks wiki page and Governance Charter.

Eligible Voters
Voting eligibility is determined by a community member's Fedora Account System (FAS) memberships.

To vote for Environment and Stacks Working Group you must have cla_done + one other "non-cla" group in FAS.

Candidates

Slavek Kabrda (bkabrda)

Introduction

• Mission Statement:
  • Ensure that Fedora is a developer friendly distribution well integrated with upstream tooling.

• Past work summary:
  • I've been member of Env & Stacks WG since its inception.
  • I was Ruby and JRuby maintainer for more than a year.
  • I've been primary maintainer of Python 2 and 3 interpreter packages for more than year and a half. I also maintain a decent number of Python extension packages in Fedora.
  • I'm author of DevAssistant, a tool which is supposed to help developers with their everyday tasks. DevAssistant has been part of Fedora Workstation since Fedora 21.

• Future plans:
  • Ensure that Fedora's developer tooling integrates well with upstream tools, instead of fighting them.
    • Continue driving the DevPI pilot, which is supposed to create a downstream Fedora mirror of Python Package Index. Try to apply the experience from this pilot to other languages.
    • Review the "rings" proposal for Fedora.next with other members of Env & Stacks WG and put it to work. Most importantly, we should promote Copr/Playground and define how non-RPM content of the outer rings (as mentioned in the DevPI plans) fits into Fedora future.
  • Make sure that DevAssistant continuously improves, making it an ultimate developer tool - and Fedora along with it.
  • Continue driving the migration of Fedora to Python 3 as a default - for benefit of Fedora and wider Python community.
  • Evolve Python packaging in Fedora to be more automated and thus simpler. The concepts and thoughts from the improvements should be appliable to packaging of other (dynamic) languages as well.

ColinWalters (walters)

Introduction

• Mission Statement:
  • Drive continuous delivery, containerization, atomic upgrades, and high quality FOSS in Fedora

• Past work summary:
  • Long ago, maintainer of Debian build-essential
  • Extensive experience not just with the RPM world, but with other build systems and packaging tools, such as Debian, OpenEmbedded, Docker, and others
  • Current maintainer of https://github.com/projectatomic/rpm-ostree/ and OSTree
  • Author of https://wiki.gnome.org/Projects/GnomeContinuous - one of the fastest public OS continuous delivery systems

• Future plans:
  • Improve Docker and other container systems in Fedora - e.g. better tools to generate and maintain images
  • Improve rpm-ostree with package layering and other features
  • Try to migrate some of the GnomeContinuous technologies into Fedora, such as:
    • Teaching fedpkg/koji about upstream git repositories instead of lookaside cache of tarballs
    • Building completely as non-root (even buildroot construction) via https://git.gnome.org/browse/linux-user-chroot

Tomas Tomecek (ttomecek)

Introduction

• Mission Statement:
  • Make Fedora user friendly GNU/Linux distribution

• Past work summary:
  • python, django, web developer
  • Fedora packager
  • currently working on tooling around docker
  • was working on tooling around static analysis

• Future plans:
  • Make Fedora #1 GNU/Linux distro for developers
    • provide Fedora with docker ecosystem (build system, docs, image store, workflows) and integrate it with existing Fedora infrastructure
    • development stacks should be easily available to developers
    • it should be easy to set up a development environment and start coding right away