MoM 19.05.2017

[ewelinawilkosz]

Participants: @Andrey9kin @buep @ewelinawilkosz2

Goal: Decide about the JenkinsAsCode's WoW and responsibilities

CloudBees may work on a similar solution but it doesn't seem like we can expect anything in the nearest future. We've decided to continue with JAC development/improvement

@ewelinawilkosz2 will be a Benevolent Dictator of JAC
@Andrey9kin will be a technical advisor

We agreed that the main focus should be now on defining efficient workflow for JAC implementation - many of us, who uses JAC for customers, already have made a lot of updates in general configuration scripts/properties files. There is a risk that we may end up with reinventing the same things couple of time because we don't know it was already made by someone in customer's repository (it has probably already happened). To avoid that we need an easy way to share our changes with others.
Separating "what" & "how" would help to achieve this goal.

One idea was to keep scripts in one common repository, instead of having copies in customer's repos. It would also make it much easier to upgrade customer's jenkins to version used in this repository.

It was also mentioned that documentation should be improved.

In upcoming weeks I will work on proposals:

1. how to split repository - common part (scripts), and configuration (properties)
2. workflow
3. how to introduce solutions already present in customers' repos
   As a result we will have some new issues here.

Another topic was building a community around JAC, so far we decided that as a BD I am also responsible for that

[Andrey9kin]

@ewelinawilkosz2 great notes! Thanks

[buep]

Contributed with #195, #196, #197 from my own personal notes so we don't forget. They are from this meeting here.