Core Team: Sprint 1

Development
1

All,

A group of developers from each major area of concern has formed to
prioritize and tackle what we are calling "core" issues on a sprint by
sprint basis. The first such sprint started today (4/20) and is intended to
last for 3 weeks at a time. At the end of each Sprint there will be a demos
as before that will showcase work done by the Core team and work being done
in other areas of the project (e.g. feature teams related to atomic
support, remote management, etc).

This first Sprint was seeded with ideas from the team members as well as
some currently ongoing work throughout the project. For future sprints, my
intent will be to send out an email and present the community with an
opportunity to comment and seed ideas prior to planning. Below you will
find two lists. The first set of items below is what the team has discussed
and committed to for the first sprint. The second list is what you might
call the 'backlog' of items and concerns pulled currently from the group.
That is the list we will build on based on input from the community and
team. You will also notice that these stories are broken down by major
areas of concern, and that we are attempting to pull stories from each area
per sprint.

For now, I am planning to gather the existing stories and create new ones
where appropriate and mark them against a Redmine tracker for tracking.
While this isn't ideal to me, the tracker will at least allow us to gather
together multiple issues from projects and subprojects.

As always, your input and thoughts are appreciated so that we can iterate
on this over time.

Eric

Sprint 1 Stories

··· ============

Backlog
======

  • Infrastructure

  • test parallelization across Foreman, plugins and Katello

  • running Foreman test suite per plugin

  • Create a downstream only CI for the purpose of cve / downstream
    patches (Eyal Edri’s team can assist but we need to know what we ask first).

  • Move CI jobs to JJB

  • Packaging

  • Ubunu/Debian packaging

  • Community

  • identification and prioritization of PRs – strategies and
    implementation to achieve this

  • identification of supported plugins and official support policy

  • focusing on community PRs and concerns

  • publicizing meeting notes and gathering feedback

  • Processes

  • Both upstream/downstream release process should be own by the core
    team & any external contributors who want to help

  • Patch review process

  • Security process

  • Processes that we should automate

  • Technologies

  • API

  • Hammer

  • identification of and prioritization of Hammer core bugs

  • Feature #8979: Package hammer with ruby193 scl - Packaging - Foreman Package hammer with ruby193
    scl

  • Smart Proxy

  • Modularization of smart-proxy plugin providers:

  • Add support for dhcp

  • UI

  • Installer

  • web UI for installer

  • Compute Resources / Fog

  • SELinux

  • Internationalization

  • Taxonomies

  • Authorization and Authentication

  • supporting SAML authentication backend –
    https://bugzilla.redhat.com/show_bug.cgi?id=1199091

  • Plugins

  • Move foreman_tasks into core

  • Other plugins worthy of moving into core?

2

> All,
>
> A group of developers from each major area of concern has formed to
> prioritize and tackle what we are calling "core" issues on a sprint by
> sprint basis. The first such sprint started today (4/20) and is intended to
> last for 3 weeks at a time. At the end of each Sprint there will be a demos
> as before that will showcase work done by the Core team and work being done
> in other areas of the project (e.g. feature teams related to atomic
> support, remote management, etc).
>
> This first Sprint was seeded with ideas from the team members as well as
> some currently ongoing work throughout the project. For future sprints, my
> intent will be to send out an email and present the community with an
> opportunity to comment and seed ideas prior to planning. Below you will
> find two lists. The first set of items below is what the team has discussed
> and committed to for the first sprint. The second list is what you might
> call the 'backlog' of items and concerns pulled currently from the group.
> That is the list we will build on based on input from the community and
> team. You will also notice that these stories are broken down by major
> areas of concern, and that we are attempting to pull stories from each area
> per sprint.
>
> For now, I am planning to gather the existing stories and create new ones
> where appropriate and mark them against a Redmine tracker for tracking.
> While this isn't ideal to me, the tracker will at least allow us to gather
> together multiple issues from projects and subprojects.
>
> As always, your input and thoughts are appreciated so that we can iterate
> on this over time.
>
>
> Eric
>
>
> Sprint 1 Stories
> ============
>
> - Installer
>
>
> - scenario based installer
>
>
> - break out specific stories in collaboration with KoF team (martin/eric)
>
>
> - Infrastructure
>
>
> - test parallelization across Foreman and Katello for development
> environments (dlobatogl)

This item appears both in the sprint and in the backlog?

··· On 04/20, Eric D Helms wrote: > > > - https://github.com/theforeman/foreman/pull/2299 > > > - Packaging > > > - unify the way we build our packages upstream (katello / foreman) > > > - follow up on the mailing list with discussion (ehelms) > - reuse upstream packing (e.g. pinning gem versions, spec files etc) > downstream > - document differences between upstream and downstream packaging > maintenance (ehelms) > > > - Technologies > > > - plugins > > > - Migration of katello entites to scoped search > > > - Tracker: http://projects.theforeman.org/issues/4638 > > > - pick a set of stories/models to tackle (jsherrill) > > > - Content View http://projects.theforeman.org/issues/8692 > > > - ContentViewPuppetModule http://projects.theforeman.org/issues/8693 > > > - Hammer > > > - identification of and prioritization of Hammer core bugs > > > - http://projects.theforeman.org/issues/10105 host create fails with > "Missing arguments for 'interfaces_attributes'" > > > - being actively worked on for 1.8 release (tomas) > > > - http://projects.theforeman.org/issues/7534 --debug output prints > password > > > - look at the hammer side of the issue (martin/eric) > > > - http://projects.theforeman.org/issues/7453 Add hammer man page > > > - pr submitted (shlomi) > - review (tomas/martin) > > > - http://projects.theforeman.org/issues/9971 hammer erratum list: Search > with repository name fails > > > - pr submitted (mbacovsky) > > > - review (inecas) > > > - test if this fixes: http://projects.theforeman.org/issues/8640 hammer > could not update host and report: host not found (martin) > > > - Smart Proxy > > > - Modularization of smart-proxy plugin providers. > > > - Complete dns > > > - Needs review: https://github.com/theforeman/smart-proxy/pull/256 > (dlobatog/ehelms) > > > - Config file migrations > > > - Needs review: https://github.com/theforeman/smart-proxy/pull/272 > (lzap/dcleal) > > > - UI > > > - centralizing on Patternfly across Foreman and supported plugins > (dlobatog) > > > - https://github.com/theforeman/foreman/pull/2137 - needs reviewers, > testing with plugins, & adhering to some patternfly conventions > > > - needs reviewers (ehelms/ ) > > > - testing with plugins (dlobatog/ehelms) > > > - patternfly conventions (dlobatog/ehelms) > > > > *Backlog* > *======* > > - Infrastructure > > > - test parallelization across Foreman, plugins and Katello > > > - running Foreman test suite per plugin > > > - Create a downstream only CI for the purpose of cve / downstream > patches (Eyal Edri's team can assist but we need to know what we ask first). > > > - Move CI jobs to JJB > > > - Packaging > > > - Ubunu/Debian packaging > > > - Community > > > - identification and prioritization of PRs -- strategies and > implementation to achieve this > > > - identification of supported plugins and official support policy > > > - focusing on community PRs and concerns > > > - publicizing meeting notes and gathering feedback > > > - Processes > > > - Both upstream/downstream release process should be own by the core > team & any external contributors who want to help > > > - Patch review process > > > - Security process > > > - Processes that we should automate > > > - Technologies > > > - API > > > - Hammer > > > - identification of and prioritization of Hammer core bugs > > > - http://projects.theforeman.org/issues/8979 Package hammer with ruby193 > scl > > > - Smart Proxy > > > - Modularization of smart-proxy plugin providers: > > > - Add support for dhcp > > > - UI > > > - Installer > > > - web UI for installer > > > - Compute Resources / Fog > > > - SELinux > > > - Internationalization > > > - Taxonomies > > > - Authorization and Authentication > > > - supporting SAML authentication backend -- > https://bugzilla.redhat.com/show_bug.cgi?id=1199091 > > > - Plugins > > > - Move foreman_tasks into core > > > - Other plugins worthy of moving into core? > > -- > You received this message because you are subscribed to the Google Groups "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.

–
Daniel Lobato Garcia

@eLobatoss
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato