[trip] 1st Foreman Construction Day report

Support
1

Hi all,

(This is part 3 of my conference coverage, with FOSDEM and CfgMgmt at [1,2])

So on Feb 3rd we had our first ever Foreman Construction Day[4] - a day for
user and developer communities to get together and hack on stuff in person.
I have to say, from where I was sat, it seemed a big success.

We had around 20 people present, and using an unconference-style process,
we quickly decided on some things to hack on. There was:

  • A foreman_ansible hacking group
  • A networking improvements group
  • A translations group looking at integrating the work done by downstream
    translators
  • A foreman_deployments usecase/hacking group
  • Some devs helping new plugin authors to modify Foreman for their usecases

I also ran a "beginners" group looking at provisioning, hostgroups, and
node classification, which helped a number of our newer users get a good
start in Foreman.

In the afternoon, we also got a group together to meet with the Puppet
community about fixing puppet 4 support in Foreman - you can read a
seperate report on that here[4]

I spent a good deal of time moving between the groups and checking they
were finding the time useful, and that there were no blockers for people -
happily, everything seemed to run smoothly. At the end of the day, we
recombined to check on how people had found the day - it seems everyone
enjoyed themselves, found the day useful, and would participate in another
one in the future. Result! :slight_smile:

I'd really like to encourage the people who participated in these groups
to reply to this thread and say what outcomes they had from the day, and
how it was useful for them - I couldn't be present in every group for very
long, after all :wink:

As the community guy, it made me very happy to see this work well, and I
really hope we can plan more soon.

Greg

[1] https://groups.google.com/d/topic/foreman-users/AbbzdHBixzk/discussion
[2] https://groups.google.com/d/topic/foreman-users/P4pTrrpO7CI/discussion
[3]
https://www.eventbrite.com/e/foreman-construction-day-registration-19911909056#
[4] https://groups.google.com/d/topic/foreman-dev/Ijvodu1hJkE/discussion

2

I will look to Benjamin to chime in here. But this is what we did
around translations:

  1. We pushed new PRs to get localization into remote execution,
    openscap, and a few of the hammer plugins. At this point, the following
    plugins are localized and setup for translation

Foreman Core + hammer
Bootdisk + hammer
Foreman setup
Discover + hammer
Docker + hammer
Remote Execution + hammer
Tasks + hammer
Katello + hammer
OpenScap

It is pretty trivial to add, so other plugin authors should do the same.

  1. We evaluated moving to Zanata from Transifex. It did not seem like a
    good time to do this because of a few factors:

a) There is no auto-approval of translators
b) There is no notion of an "org" in zanata which allows for a custom
user experience.
c) There is no ability to suggest partial phrases while translating.

We can re-evaluate this after a and b are closed, since there are some
features we would like in zanata (e.g. versioning)

  1. We discussed how to get string usptream, since today we have failed
    to do this. Benjamin suggested putting new strings in via the transifex
    API, insetad of using the a po based merge process. This would limit the
    impact on translators, and if there is any language actually doing
    reviews it would allow them to do that. We will work on this during the
    year.

– bk

··· On 02/18/2016 05:46 AM, Greg Sutcliffe wrote: > Hi all, > > (This is part 3 of my conference coverage, with FOSDEM and CfgMgmt at [1,2]) > > So on Feb 3rd we had our first ever Foreman Construction Day[4] - a day > for user and developer communities to get together and hack on stuff in > person. I have to say, from where I was sat, it seemed a big success. > > We had around 20 people present, and using an unconference-style > process, we quickly decided on some things to hack on. There was: > > * A foreman_ansible hacking group > * A networking improvements group > * A translations group looking at integrating the work done by > downstream translators