[mattermost] <zygmunt.krynicki> good morning :)

[mattermost] <gitlab> Zygmunt Krynicki pushed to branch [master](git.ostc-eu.org/OSTC/containers/commits/master) of [OSTC / containers](git.ostc-eu.org/OSTC/containers) ([Compare changes](git.ostc-eu.org/OSTC/containers/com…2a4becb7bd25866f88ca96f8c37a3c1350f))

[mattermost] <stefan-schmidt> morning folks

[mattermost] <amitk> morning

[mattermost] <pianon> morning

[mattermost] <pianon> @andrei.gherzan @zygmunt.krynicki I had a look and I've got something to share about meta-spdxscanner, may I just create a new gitlab repo and we discuss it there?

[mattermost] <zygmunt.krynicki> yeah,

[mattermost] <zygmunt.krynicki> we have top-level playground group for random things

[mattermost] <zygmunt.krynicki> if you have no better place, perhaps there?

[mattermost] <pianon> @andrei.gherzan yesterday I tried this git.ostc-eu.org/OSTC/OHOS/meta-ohos; the linux build generates the manifest as you showed us yesterday but the zephir and freertos builds don't... or am I missing something?

[mattermost] <gitlab> <git.ostc-eu.org/OSTC/containers|containers>: Pipeline <git.ostc-eu.org/OSTC/containers/-/pipelines/599/failures|#599> of branch <git.ostc-eu.org/OSTC/containers/-/commits/master|master> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 01:00:07

[mattermost] <zygmunt.krynicki> oh fun

[mattermost] <zygmunt.krynicki> the kaniko container thing is crap, it's so incredibly slow

[mattermost] <zygmunt.krynicki> feels like unaccelerated VM

[mattermost] <zygmunt.krynicki> (maybe that's what it is)

[mattermost] <gitlab> Gururaj Shetty pushed to branch [master](git.ostc-eu.org/OSTC/OHOS/docs/developer-guide/commits/master) of [OSTC / OHOS / docs / developer-guide](git.ostc-eu.org/OSTC/OHOS/docs/developer-guide) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/docs/deve…7a2192b6ecc3e5d57cc7d752ca498f07d51))

[mattermost] <zygmunt.krynicki> @robert.drab I like the sources/ structure - nice!

[mattermost] <robert.drab> yeah, well I'll have to pass credits for that one to @andrei.gherzan

[mattermost] <zygmunt.krynicki> as soon as our container images are built, I'll get the reference builds done

[mattermost] <zygmunt.krynicki> and if I can avoid some meetings today, I'll prototype some boot tests on top

[mattermost] <robert.drab> @zygmunt.krynicki would like to help with those tests

[mattermost] <zygmunt.krynicki> I should be building this on my desktop

[mattermost] <zygmunt.krynicki> @robert.drab sure, what do you have on your mind

[mattermost] <robert.drab> as a part of the add boards guide we want to have some structure in place for vendors

[mattermost] <robert.drab> I'd like to prepare a doc template to be filled by the vendors

[mattermost] <zygmunt.krynicki> how is that related to testing?

[mattermost] <zygmunt.krynicki> is the structure you are talking about for conveying vendor-specific tests?

[mattermost] <robert.drab> I'd like to have automatic tests

[mattermost] <zygmunt.krynicki> sure

[mattermost] <robert.drab> e.g. based on the documentation

[mattermost] <zygmunt.krynicki> ah, I understand now

[mattermost] <zygmunt.krynicki> well... we'll see, I understand the goal (make sure docs work) but I think we need something more fundamental before that

[mattermost] <zygmunt.krynicki> and you can always structure it by saying: to see how to build look at build-foo.sh

[mattermost] <zygmunt.krynicki> and then that's that, we just use that in CI and that's working

[mattermost] <zygmunt.krynicki> it's easier than having to process documentation as code

[mattermost] <zygmunt.krynicki> I want to provide a framework where vendors can drop extra tests

[mattermost] <zygmunt.krynicki> both automated and interactive

[mattermost] <zygmunt.krynicki> today I'd like to start on the first part of that - just the automatic testing that can be done in VMs

[mattermost] <robert.drab> ok, do your things, I'll get back at it later

[mattermost] <zygmunt.krynicki> it's just a first approximation of what we'll get as we approach to march, I'm sure there will be course corrections along the way

[mattermost] <robert.drab> sure, I'd like to see some kind of pipeline for the docs though

[mattermost] <robert.drab> that's why I'm bringing it up

[mattermost] <robert.drab> wouldn't want anyone to go through our readme discovering it doesn't work the way it's described

[mattermost] <zygmunt.krynicki> @robert.drab there are ways to handle that, just not sure how to do that efficiently (normally doctests are for `>>> 2 + 2` `4` kind of output

[mattermost] <robert.drab> I was thinking rigid section structure in a doc + regex

[mattermost] <zygmunt.krynicki> can I switch tracks a little and ask you about the set of tests you think we should run against our linux images - tests that are compatible with virtualization, for now.

[mattermost] <zygmunt.krynicki> I was thinking about LTP as the starting point but I wanted to extend the question to everyone here

[mattermost] <zygmunt.krynicki> @iwx1009099 o/

[mattermost] <zygmunt.krynicki> let's chat here after the call

[mattermost] <zygmunt.krynicki> can you start by telling me if you are setting up your workstation/laptop for building the code from gitee or the code from ostc?

[mattermost] <zygmunt.krynicki> In both cases, you should be able to install everything required entirely automatically if you are using Ubuntu 20.04 that we internally support - other Debian derivatives are also easy to support but it's a bit more work.

[mattermost] <zygmunt.krynicki> I'm also wondering which documentation page you were following

[mattermost] <zygmunt.krynicki> @iwx1009099 ^ have a look

[mattermost] <ile> I'm trying to get code from ostc. My laptop has Ubuntu... but 18.04. I was following this: git.ostc-eu.org/OSTC/OHOS/docs/deve…/quick-start/build-open-harmony.rst

[mattermost] <zygmunt.krynicki> right, 18.04 is not supported, do you think you could upgrade to 20.04?

[mattermost] <zygmunt.krynicki> it's a supported upgrade so everything should be fine

[mattermost] <zygmunt.krynicki> once you are on 20.04 all the tools in the PPA will be available

[mattermost] <robert.drab> I was thinking two things, one is testing build process

[mattermost] <ile> Yes, I can upgrade it. (btw, that should be mentioned in prereqs)

[mattermost] <zygmunt.krynicki> yes, I totally agree - thanks for catching this

[mattermost] <robert.drab> i.e. does your additional layer break any of already supported build types

[mattermost] <ile> I aim to please ;)

[mattermost] <robert.drab> and second is tests for and on the hardware itself

[mattermost] <robert.drab> if we could agree on the way that those tests are described, we could use it later on for automatic testing

[mattermost] <andrei.gherzan> @piana that is sadly expected. On those sides the image generation routines was overridden

[mattermost] <zygmunt.krynicki> my current plan is to use spread for most tasks

[mattermost] <zygmunt.krynicki> and checkbox for any interactive testing once we reach that moment

[mattermost] <andrei.gherzan> That's something we will need to look into.

[mattermost] <andrei.gherzan> Can you create an issue in meta-ohos for it?

[mattermost] <zygmunt.krynicki> I can share the fosdem talk about spread to help you understand why I want this solution

[mattermost] <zygmunt.krynicki> (though in private until it is public)

[mattermost] <zygmunt.krynicki> can you send a quick PR to say that those instructions are for Ubuntu 20.04? You can even do that without opening a terminal, straight from the gitlab web IDE

[mattermost] <gitlab> Adam Szpilko pushed to branch [master](git.ostc-eu.org/OSTC/planning/scrum/commits/master) of [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum) ([Compare changes](git.ostc-eu.org/OSTC/planning/scrum…8a95f904560497fdef95357cd413e9b2b65))

[mattermost] <robert.drab> guys, I can take a look at that one if you want, just describe which manifest is missing

[mattermost] <gitlab> Adam Szpilko pushed to branch [master](git.ostc-eu.org/OSTC/planning/scrum/commits/master) of [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum) ([Compare changes](git.ostc-eu.org/OSTC/planning/scrum…0cf2a7944f6f512ae4f41306118883e3752))

[mattermost] <andrei.gherzan> The image manifest.

[mattermost] <andrei.gherzan> git.yoctoproject.org/cgit/cgit.cgi/…ree/meta/classes/image.bbclass#n239

[mattermost] <andrei.gherzan> git.yoctoproject.org/cgit/cgit.cgi/…y/tree/meta/lib/oe/manifest.py#n192

[mattermost] <andrei.gherzan> Wrong ping @piana. This should have been @pianon

[mattermost] <piana> @pianon read followup to thread

[mattermost] <andrei.gherzan> @adam.szpilko ^

[mattermost] <andrei.gherzan> Did we fix the status options for requirements?

[mattermost] <andrei.gherzan> Also, can we add the version field for the "Assigned to me" filter?

[mattermost] <adam.szpilko> Hi @andrei.gherzan , let me leave the answer for @sebastian.serewa , he has a product backlog owner and he already set/setting options there, @sebastian.serewa , could you update Andrei?

[mattermost] <andrei.gherzan> Let's clarify this before the meeting so I can update my requirements.

[mattermost] <adam.szpilko> Do you mean the today meeting about requirements?

[mattermost] <andrei.gherzan> yes @adam.szpilko

[mattermost] <gitlab> <git.ostc-eu.org/OSTC/containers|containers>: Pipeline <git.ostc-eu.org/OSTC/containers/-/pipelines/599/failures|#599> of branch <git.ostc-eu.org/OSTC/containers/-/commits/master|master> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 02:26:02

[mattermost] <sebs> @andrei.gherzan what states are you missing at the moment? You should be able to put into "in progress" state. Can't you?

[mattermost] <GitLab> Andrei Gherzan (andrei.gherzan) [commented on merge request !7](git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/7#note_2043) in [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos): *Draft: Add Avenger96 Linux support*

[mattermost] <stefan-schmidt> I for one can only #77 in being specified and not in progress

[mattermost] <GitLab> Andrei Gherzan (andrei.gherzan) [commented on merge request !7](git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/7#note_2044) in [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos): *Draft: Add Avenger96 Linux support*

[mattermost] <andrei.gherzan> ^ exactly

[mattermost] <andrei.gherzan> Sounds like the OP default

[mattermost] <sebs> ok, let's talk during the review

[mattermost] <GitLab> Robert Drab (robert.drab) [commented on merge request !7](git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/7#note_2045) in [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos): *Draft: Add Avenger96 Linux support*

[mattermost] <ektor5> @zbigniew.bodek I booted core-image-sato on B68, everything looks fine to video

[mattermost] <zbigniew.bodek> 👌

[mattermost] <GitLab> Robert Drab (robert.drab) approved merge request [!8 *Updated README, added SECO intel bblayers*](git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/8) in [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos)

[mattermost] <zbigniew.bodek> I guess sato will be using x11, but we intend to use wayland/drm+ weston. I wonder if core-image-weston works as well

[mattermost] <zbigniew.bodek> just thinking out loud. I don't know what will be the final decision what to use in the end

[mattermost] <GitLab> Robert Drab (robert.drab) [commented on merge request !20](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/20#note_2047) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Feature/SECO B68 support*

[mattermost] <ektor5> Shall we amend it?

[mattermost] <GitLab> Robert Drab (robert.drab) [commented on merge request !8](git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/8#note_2048) in [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos): *Updated README, added SECO intel bblayers*

[mattermost] <robert.drab> yes, and push it with -f to your branch

[mattermost] <robert.drab> ah, and please change the commit message to imperative mood

[mattermost] <robert.drab> ah, and please change the commit title to imperative mood

[mattermost] <GitLab> Ettore Chimenti pushed to branch [feature/seco_b68_support](git.ostc-eu.org/OSTC/OHOS/meta-ohos/commits/feature/seco_b68_support) of [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/meta-ohos…53c750b26bf87666ea3eb76443f31308c5d))

[mattermost] <GitLab> Ettore Chimenti pushed to branch [feature/seco_b68_support](git.ostc-eu.org/OSTC/OHOS/meta-ohos/commits/feature/seco_b68_support) of [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/meta-ohos…063d8017ff541b29bd777d3830af76e87fc))

[mattermost] <GitLab> Ettore Chimenti pushed to branch [feature/seco_b68_support](git.ostc-eu.org/OSTC/OHOS/manifest/commits/feature/seco_b68_support) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…e5a2bc40679729027a36c05bb2c1008661e))

[mattermost] <ektor5> should be done :)

[mattermost] <robert.drab> cool, thanks!

[mattermost] <GitLab> Robert Drab pushed to branch [develop](git.ostc-eu.org/OSTC/OHOS/manifest/commits/develop) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…fc965d43d0127f8e618f1e87eefa5066d62))

[mattermost] <andrei.gherzan> So @seb

[mattermost] <andrei.gherzan> So @sebastian.serewa @jaroslaw.marek I have 4 comments:

[mattermost] <andrei.gherzan> 1. wishlist name is currently "-"? Can we make this clearer?

[mattermost] <andrei.gherzan> 2. can we have a filter for accountable (not assigned). The PR will need that to track the progress of things they are not assigned to too.

[mattermost] <andrei.gherzan> 3. As we discussed above, status needs fixing?

[mattermost] <andrei.gherzan> 4. Can we add version and progress fields to the assigned and accountable filters (see 2)?

[mattermost] <andrei.gherzan> 5. have "risk" in the "Estimates and time" section

[mattermost] <andrei.gherzan> 6. Clarify the "Estimated time" field to be similar to "Remaining hours " in terms of specifying the unit.

[mattermost] <zygmunt.krynicki> @jaroslaw.marek I'm looking at git.ostc-eu.org/groups/OSTC/-/boards and there are 20 issues in the TODO column; when I look at git.ostc-eu.org/groups/OSTC/-/milestones/1 I see only 4 issues with in the unstarted column (todo) and some issues that have a mixture of labels.

[mattermost] <zygmunt.krynicki> @jaroslaw.marek we should spend a moment to clean this up so that the upcoming Tuesday sprint end can be reviewed

[mattermost] <sebs> @andrei.gherzan 1. done, 2. see [here](project.ostc-eu.org/projects/open-s…center-eu/work_packages?query_id=29) 3. after the lunch, 4. reqs are grouped by version, see [here](project.ostc-eu.org/projects/open-s…center-eu/work_packages?query_id=34). 5. it's already there. 6. remainging hours will be removed

[mattermost] <Jarek> right, @adam.szpilko can you please do it just this time as we are at the end of the sprint it will be the fastest way to do it, but next time it should be done during sprint planning, as discussed earlier

[mattermost] <sebs> if there are still any doubts in this context, please let me know.

[mattermost] <andrei.gherzan> 2. What I mean is to have a default view, similar to the "Assigned to me" one for the accountable too.

[mattermost] <andrei.gherzan> 4. Sure, But can the default views include those two columns too by default (progress and version)?

[mattermost] <andrei.gherzan> 5. It is not for me.

[mattermost] <andrei.gherzan> 6. Sure, remaining hours can be removed but I was suggesting to have the "Estimated time" also include the time until in its name.

[mattermost] <andrei.gherzan> @sebastian.serewa does this make sense?

[mattermost] <GitLab> Andrei Gherzan (andrei.gherzan) [commented on merge request !7](git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/7#note_2052) in [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos): *Draft: Add Avenger96 Linux support*

[mattermost] <robert.drab> @zygmunt.krynicki @andrei.gherzan I'm thinking of MRs and pipelines for multiple repositories, i.e. manifest and meta-ohos

[mattermost] <robert.drab> so it seems first changes should land in the meta-ohos and then in the manifest

[mattermost] <andrei.gherzan> Yes.

[mattermost] <robert.drab> but in manifest we have only tag revision of the meta-ohos

[mattermost] <zygmunt.krynicki> what's the context, sorry?

[mattermost] <andrei.gherzan> We can just bump hashes.

[mattermost] <robert.drab> well, we could

[mattermost] <robert.drab> but also we can stick to the git -flow for manifest as well

[mattermost] <robert.drab> as currently for initial ease of use all changes went directly to the master

[mattermost] <andrei.gherzan> That works too.

[mattermost] <andrei.gherzan> Or even multiple manifests

[mattermost] <robert.drab> yes, like develop or bleeding

[mattermost] <robert.drab> or whatever

[mattermost] <andrei.gherzan> I've usually done it with multiple manifests in the pasts

[mattermost] <andrei.gherzan> I've usually done it with multiple manifests in the past

[mattermost] <andrei.gherzan> But really both should work just as good.

[mattermost] <robert.drab> I'm leaning towards git-flow like master, targeted for the first time users

[mattermost] <robert.drab> where all is stable

[mattermost] <robert.drab> and develop for, well, developers

[mattermost] <robert.drab> we can have multiple manifests as well, just keep the default.xml and master for release-quality user entry point

[mattermost] <andrei.gherzan> Detail it a bit so I understand exactly what you aim at

[mattermost] <robert.drab> I'm aiming at testing meta-ohos changes without bumping master/default.xml manifest

[mattermost] <robert.drab> that's one thing

[mattermost] <andrei.gherzan> So you want to have a matching branch in the manifest which points to the dev branch in meta-ohos?

[mattermost] <sebs> 2. yes, it possible. You can create your own set of views (on top of the shared public views). Just create a new view and mark it as your favourite, and not public. Let me know if u needed more support on this.

[mattermost] <robert.drab> the other is the git-flow

[mattermost] <andrei.gherzan> Yes - the latter i'm interested to see exactly how you see it.

[mattermost] <robert.drab> ok, so with the git-flow, currently we didn't use that branching workflow for manifest

[mattermost] <robert.drab> as repo takes master by default

[mattermost] <andrei.gherzan> yes ( can be set with flag)

[mattermost] <robert.drab> yes, exactly

[mattermost] <robert.drab> so I'd like us to state it clearly in the docs that we work that way everywhere throughout our repositories

[mattermost] <andrei.gherzan> Sure. But how do you see git-flow working on the manifest repo?

[mattermost] <robert.drab> same as everywhere else, MRs to develop branch

[mattermost] <andrei.gherzan> Uh I see! For sure.

[mattermost] <andrei.gherzan> I thought you went a bit deeper into branching and stuff.

[mattermost] <robert.drab> and merge to master for revision tagging only

[mattermost] <andrei.gherzan> So teh dev will ontain hashes

[mattermost] <andrei.gherzan> So the dev will ontain hashes

[mattermost] <andrei.gherzan> So the dev will contain hashes

[mattermost] <andrei.gherzan> And master merges with tags

[mattermost] <robert.drab> I would think so

[mattermost] <sebs> 3. It's feasible, but not sure it will be usefull to all. Progress+version can be tracked in [this](project.ostc-eu.org/projects/open-s…center-eu/work_packages?query_id=34) view. If there are still doubts, let's discuss during next review.

[mattermost] <robert.drab> and therefore developers have a way of checking changes in other repositories

[mattermost] <robert.drab> like meta-ohos

[mattermost] <robert.drab> does this make sense?

[mattermost] <andrei.gherzan> Yup

[mattermost] <andrei.gherzan> Clear now - agreed.

[mattermost] <robert.drab> I don't know why is it so hard lately for me to express clearly 🤷‍♂️

[mattermost] <robert.drab> so in case of Seco MRs

[mattermost] <robert.drab> after we merge meta-ohos

[mattermost] <andrei.gherzan> Maybe it's about the my "ears" too :)

[mattermost] <robert.drab> in manifest MR: meta-ohos should point to that newly merged commit

[mattermost] <robert.drab> and MR should be to develop branch

[mattermost] <robert.drab> I wanted to describe the procedure in the add board guide

[mattermost] <andrei.gherzan> It's more of a contribution documentation. I think is should reside in every repository really. But it would help to be mentioned there too.

[mattermost] <robert.drab> agreed, that's why I started with unviersall git-flow approach in all the repos

[mattermost] <robert.drab> as for the place for the "Guide" I'd put it probably in the meta-ohos/docs/

[mattermost] <andrei.gherzan> 👍

[mattermost] <robert.drab> and reference it in the meta

[mattermost] <robert.drab> and reference it in the meta-ohos README

[mattermost] <andrei.gherzan> Nice - to avoid duplication

[mattermost] <gitlab> <git.ostc-eu.org/OSTC/containers|containers>: Pipeline <git.ostc-eu.org/OSTC/containers/-/pipelines/599/failures|#599> of branch <git.ostc-eu.org/OSTC/containers/-/commits/master|master> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 02:26:02

[mattermost] <robert.drab> right, also contributing.md probably should land in top level OHOS/docs

[mattermost] <robert.drab> so it can be referenced where needed

[mattermost] <andrei.gherzan> Good point

[mattermost] <robert.drab> I'll tak with Guru about that and git-flow

[mattermost] <robert.drab> I'll talk with Guru about that and git-flow

[mattermost] <andrei.gherzan> Thanks, @robert.drab

[mattermost] <robert.drab> no problem

[mattermost] <robert.drab> so one thing left is the location for the board documentation

[mattermost] <robert.drab> and for that I don't have a good place yet, seems it could go along with the flavours

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/600/failures|#600> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/…68_support|feature/seco_b68_support> by Ettore Chimenti (ektor5) has failed in 00:16

[mattermost] <andrei.gherzan> It very much sounds to me as part of the project documentation

[mattermost] <andrei.gherzan> so OHOS/docs

[mattermost] <andrei.gherzan> For the spec/guide

[mattermost] <andrei.gherzan> For the actual boards it's something we need to figure out

[mattermost] <robert.drab> yeah, supported H/W seems like the top most level

[mattermost] <andrei.gherzan> I was thinking about meta-ohos/docs but that;s not really the case

[mattermost] <andrei.gherzan> What brings support is the manifest really

[mattermost] <andrei.gherzan> I'd say keep it in the same top level for now

[mattermost] <andrei.gherzan> Just not overcomplicate

[mattermost] <sebs> 5. corrected it already a bit. Time units are not changeable in OpenProject (easily), so I'm afraid we'll have to get used to this. Have a look and let me know if there are still any doubts in this.

[mattermost] <robert.drab> yeah, so it seems OHOS/docs

[mattermost] <andrei.gherzan> Yeah - under a nice structure

[mattermost] <andrei.gherzan> Maybe file per board, directory per board under boards or something

[mattermost] <robert.drab> sure, will do something simple

[mattermost] <gitlab> Zygmunt Krynicki pushed to branch [master](git.ostc-eu.org/OSTC/containers/commits/master) of [OSTC / containers](git.ostc-eu.org/OSTC/containers) ([Compare changes](git.ostc-eu.org/OSTC/containers/com…a5082d9ddf839f4aab3b95037fd4a880808))

[mattermost] <andrei.gherzan> Thanks again!

[mattermost] <sawicki> this may speedup builds a little bit ;)

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/601/failures|#601> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/-/commits/develop|develop> by Robert Drab (robert.drab) has failed in 00:16

[mattermost] <GitLab> Robert Drab pushed to branch [develop](git.ostc-eu.org/OSTC/OHOS/meta-ohos/commits/develop) of [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/meta-ohos…063d8017ff541b29bd777d3830af76e87fc))

[mattermost] <GitLab> Robert Drab (robert.drab) merged merge request [!8 *Updated README, added SECO intel bblayers*](git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/8) in [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos)

[mattermost] <GitLab> Alberto Merciai removed branch feature/seco_b68_support from [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos)

[mattermost] <GitLab> Robert Drab (robert.drab) [commented on merge request !20](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/20#note_2054) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Feature/SECO B68 support*

[mattermost] <pianon> @andrei.gherzan @zygmunt.krynicki check git.ostc-eu.org/playground/meta-spdx/-/issues/1

[mattermost] <andrei.gherzan> I'll check it out later today

[mattermost] <GitLab> Alberto Merciai (alb3rt0) [commented on merge request !20](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/20#note_2057) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Feature/SECO B68 support*

[mattermost] <GitLab> Alberto Merciai (alb3rt0) [commented on merge request !20](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/20#note_2058) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Feature/SECO B68 support*

[mattermost] <gitlab> [[OSTC / infrastructure / tools and spells](git.ostc-eu.org/OSTC/infrastructure/tools)] Issue [#3 Code Mirroring](git.ostc-eu.org/OSTC/infrastructure/tools/-/issues/3) opened by Sridhar B.D. (sridharbd)

[mattermost] <GitLab> Alberto Merciai pushed to branch [feature/seco_b68_support](git.ostc-eu.org/OSTC/OHOS/manifest/commits/feature/seco_b68_support) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…8282a0dc34e5a3657f3911853f187456889))

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/603/failures|#603> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/…68_support|feature/seco_b68_support> by Alberto Merciai (alb3rt0) has failed in 00:05

[mattermost] <gitlab> [[OSTC / infrastructure / tools and spells](git.ostc-eu.org/OSTC/infrastructure/tools)] Issue [#4 code mirroring](git.ostc-eu.org/OSTC/infrastructure/tools/-/issues/4) opened by Sridhar B.D. (sridharbd)

[mattermost] <gitlab> Sridhar B.D. (sridharbd) opened merge request [!6 *Draft: Resolve "code mirroring"*](git.ostc-eu.org/OSTC/infrastructure/tools/-/merge_requests/6) in [OSTC / infrastructure / tools and spells](git.ostc-eu.org/OSTC/infrastructure/tools)

[mattermost] <GitLab> Zygmunt Krynicki pushed new branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) to [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <GitLab> Robert Drab (robert.drab) merged merge request [!20 *Feature/SECO B68 support*](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/20) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <GitLab> Robert Drab pushed to branch [develop](git.ostc-eu.org/OSTC/OHOS/manifest/commits/develop) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…8282a0dc34e5a3657f3911853f187456889))

[mattermost] <GitLab> Ettore Chimenti removed branch feature/seco_b68_support from [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <gitlab> Zygmunt Krynicki (Zygmunt.Krynicki) [commented on merge request !6](git.ostc-eu.org/OSTC/infrastructure…/tools/-/merge_requests/6#note_2064) in [OSTC / infrastructure / tools and spells](git.ostc-eu.org/OSTC/infrastructure/tools): *Draft: Resolve "code mirroring"*

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/607/failures|#607> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/-/commits/develop|develop> by Robert Drab (robert.drab) has failed in 00:04

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/606/failures|#606> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/…x/pipeline-linux|fix/pipeline-linux> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 01:58

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…08b0a96c2d1b885dc34e8eef20a3e4f78eb))

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/610/failures|#610> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/…x/pipeline-linux|fix/pipeline-linux> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 01:20

[mattermost] <gitlab> Sridhar B.D. (sridharbd) opened merge request [!7 *this scripts will helps you mirror the code from gitee to gitlab*](git.ostc-eu.org/OSTC/infrastructure/tools/-/merge_requests/7) in [OSTC / infrastructure / tools and spells](git.ostc-eu.org/OSTC/infrastructure/tools)

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…13bd4ab5f2ef0d9334ada591e9f04c5c499))

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/613/failures|#613> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/…x/pipeline-linux|fix/pipeline-linux> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 01:21

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…79c5c833cf93ca7e8c116a6e46268bf8027))

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/614/failures|#614> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/…x/pipeline-linux|fix/pipeline-linux> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 00:07

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…14d326f21e7f622aafee4fd261eab075eb2))

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/615/failures|#615> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/…x/pipeline-linux|fix/pipeline-linux> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 00:29

[mattermost] <zygmunt.krynicki> sorry for the spam, everyone, we're getting thre

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…162b1f6692340bf5d8bbf748862fe3fdf59))

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/616/failures|#616> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/…x/pipeline-linux|fix/pipeline-linux> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 00:29

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…f19a27125077c250d47887f779d69b5d30b))

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/617|#617> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/…x/pipeline-linux|fix/pipeline-linux> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 00:00

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…1adb50276fc26122c3cc4a91d3fe2013931))

[mattermost] <GitLab> <git.ostc-eu.org/OSTC/OHOS/manifest|manifest>: Pipeline <git.ostc-eu.org/OSTC/OHOS/manifest/-/pipelines/618/failures|#618> of branch <git.ostc-eu.org/OSTC/OHOS/manifest/…x/pipeline-linux|fix/pipeline-linux> by Zygmunt Krynicki (Zygmunt.Krynicki) has failed in 00:30

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…368e4031d297ee70d7a4eb60faa26093631))

[mattermost] <zygmunt.krynicki> @robert.drab I will have a question to you in a moment

[mattermost] <zygmunt.krynicki> @robert.drab when is TEMPLATECONF required? only once or every time I source oe-init-build-env?

[mattermost] <andrei.gherzan> Only the first time you create a built

[mattermost] <andrei.gherzan> It's copied afterwards

[mattermost] <zygmunt.krynicki> ta

[mattermost] <GitLab> [[OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)] Issue [#7 Create git-repo mirror for speedup](git.ostc-eu.org/OSTC/OHOS/manifest/-/issues/7) opened by Zygmunt Krynicki (Zygmunt.Krynicki)

[mattermost] <andrei.gherzan> But thay needs clarified in readme @robert.drab

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…9449aec9136265d11212200feec3ecb22c8))

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…b031956f75ac7669fd27c58ea67024053a8))

[mattermost] <GitLab> Zygmunt Krynicki (Zygmunt.Krynicki) opened merge request [!21 *Switch to a local pipeline, fix linux build*](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/21) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <zygmunt.krynicki> @andrei.gherzan @robert.drab can you look at git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/21

[mattermost] <zygmunt.krynicki> hopefully this will pass

[mattermost] <zygmunt.krynicki> I will follow up with simplifications to commonly repeated strings and builds for the remaining targets

[mattermost] <zygmunt.krynicki> but at least CI won't be red all the time anymore

[mattermost] <robert.drab> yeah, I've lumped those two commands together

[mattermost] <robert.drab> definitely have to explain that one

[mattermost] <robert.drab> @zygmunt.krynicki if you point to the existing build directory while sourcing oe-init-build-env then it will use onfig from the build directory, not from the templateconf

[mattermost] <zygmunt.krynicki> yeah, I've adjusted the pipeline script to reflect that already

[mattermost] <robert.drab> but it's not like a one-off thing, but one-off per build directory

[mattermost] <robert.drab> ok, cool

[mattermost] <zygmunt.krynicki> I'd merge it when green and iterate

[mattermost] <zygmunt.krynicki> I'll happily address all non-critical comments when the tree no longer breaks on any pull request

[mattermost] <gitlab> Zygmunt Krynicki pushed to branch [master](git.ostc-eu.org/OSTC/containers/commits/master) of [OSTC / containers](git.ostc-eu.org/OSTC/containers) ([Compare changes](git.ostc-eu.org/OSTC/containers/com…2adc903dd36c4745bbc0152921b86d95fff))

[mattermost] <GitLab> Andrei Gherzan (andrei.gherzan) [commented on merge request !21](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/21#note_2076) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Switch to a local pipeline, fix linux build*

[mattermost] <GitLab> Zygmunt Krynicki (Zygmunt.Krynicki) [commented on merge request !21](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/21#note_2077) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Switch to a local pipeline, fix linux build*

[mattermost] <GitLab> Zygmunt Krynicki (Zygmunt.Krynicki) [commented on merge request !21](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/21#note_2079) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Switch to a local pipeline, fix linux build*

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/pipeline-linux](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/pipeline-linux) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…5a3e1dc9eae6f591ffd104fc8ebedd6a991))

[mattermost] <GitLab> Andrei Gherzan (andrei.gherzan) [commented on merge request !21](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/21#note_2083) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Switch to a local pipeline, fix linux build*

[mattermost] <GitLab> Zygmunt Krynicki (Zygmunt.Krynicki) [commented on merge request !21](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/21#note_2085) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Switch to a local pipeline, fix linux build*

[mattermost] <GitLab> Andrei Gherzan (andrei.gherzan) [commented on merge request !21](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/21#note_2086) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Switch to a local pipeline, fix linux build*

[mattermost] <GitLab> Zygmunt Krynicki (Zygmunt.Krynicki) [commented on merge request !21](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/21#note_2087) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest): *Switch to a local pipeline, fix linux build*

[mattermost] <GitLab> Zygmunt Krynicki (Zygmunt.Krynicki) [commented on merge request !7](git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/7#note_2088) in [OSTC / OHOS / meta-ohos](git.ostc-eu.org/OSTC/OHOS/meta-ohos): *Draft: Add Avenger96 Linux support*

[mattermost] <sebs> 4. I hope it's been clarified. I'll share the diagram once it's ready.

[mattermost] <sebs> Any other issues by no?

[mattermost] <sebs> Any other issues by now?

[mattermost] <andrei.gherzan> @sebastian.serewa the numbering failed so I'll drop that.

[mattermost] <andrei.gherzan> I am aware of how to create views for me but I thought this would be a nice thing to have for everyone. I can stick to a local view otherwise. CC @stefan-schmidt @idlethread @bero @zygmunt.krynicki Would you guys find it useful to have a default filter for "accountable" too as we have it for "assigned"? I guess when you do the daily, weekly review you look at the accountable as a superset.

[mattermost] <andrei.gherzan> re filter columns: It would be useful because I could update progress without going in each entry - directly from the listing.

[mattermost] <zygmunt.krynicki> yeah, accountable is practical

[mattermost] <stefan-schmidt> Might be useful but for < 10 req per PT I could deal without them as well

[mattermost] <sebs> [sold!](project.ostc-eu.org/projects/open-s…center-eu/work_packages?query_id=37)

[mattermost] <andrei.gherzan> Great! @stefan-schmidt yup - with scalability in mind. But also optimisation.

[mattermost] <andrei.gherzan> Thanks @sebastian.serewa

[mattermost] <GitLab> [[OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)] Issue [#6 Adapt CI runner to new build structure](git.ostc-eu.org/OSTC/OHOS/manifest/-/issues/6) closed by Zygmunt Krynicki (Zygmunt.Krynicki)

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [master](git.ostc-eu.org/OSTC/OHOS/manifest/commits/master) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…5a3e1dc9eae6f591ffd104fc8ebedd6a991))

[mattermost] <GitLab> Zygmunt Krynicki (Zygmunt.Krynicki) merged merge request [!21 *Switch to a local pipeline, fix linux build*](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/21) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <GitLab> Zygmunt Krynicki removed branch fix/pipeline-linux from [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <zygmunt.krynicki> @robert.drab default branch for the manifest repository is master, do you want that to be develop instead?

[mattermost] <robert.drab> yes, forgot to change that, thx!

[mattermost] <zygmunt.krynicki> done

[mattermost] <zygmunt.krynicki> can you go and change what's in mater vs develop

[mattermost] <zygmunt.krynicki> I think master is the real develop now

[mattermost] <zygmunt.krynicki> and develop doesn't have CI fixes, for example

[mattermost] <zygmunt.krynicki> I have some follow ups I'd like to sned

[mattermost] <zygmunt.krynicki> *send

[mattermost] <robert.drab> it was up until now

[mattermost] <robert.drab> from now on develop is the CI

[mattermost] <robert.drab> so latest changes from Seco are not merged to master

[mattermost] <robert.drab> my idea is that in master we'll keep manifest with tag revisions wherever possible

[mattermost] <zygmunt.krynicki> yeah but can you push stuff from master to develop

[mattermost] <zygmunt.krynicki> master has CI fixes that we just landed

[mattermost] <robert.drab> ah, ok

[mattermost] <robert.drab> I didn't get that

[mattermost] <zygmunt.krynicki> no need for a PR, just push directly

[mattermost] <robert.drab> yeah, did that like two hours ago :)

[mattermost] <zygmunt.krynicki> I'll open a PR with some small changes and then some more targets

[mattermost] <robert.drab> ok

[mattermost] <GitLab> Zygmunt Krynicki pushed new branch [fix/sanity-check](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/sanity-check) to [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <zygmunt.krynicki> cool, just ping me when done

[mattermost] <andrei.gherzan> @robert.drab what touchscreen were you guys playing with on avenger?

[mattermost] <robert.drab> have to redirect that to @zbigniew.bodek

[mattermost] <robert.drab> I just have plain avenger board on hand

[mattermost] <zygmunt.krynicki> can I just push myself

[mattermost] <zygmunt.krynicki> git.ostc-eu.org/OSTC/OHOS/manifest/-/branches I want master == develop as a starting point

[mattermost] <zbigniew.bodek> arrow.com/en/products/96boards-display-7/linksprite-technologies-inc

[mattermost] <GitLab> Robert Drab pushed to branch [develop](git.ostc-eu.org/OSTC/OHOS/manifest/commits/develop) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…a6887296ecf226c6b5066fbcd5ff2ade7f7))

[mattermost] <zygmunt.krynicki> woot! thanks

[mattermost] <zygmunt.krynicki> should we protect master?

[mattermost] <GitLab> Zygmunt Krynicki (Zygmunt.Krynicki) opened merge request [!22 *Selectively disable connectivity checker*](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/22) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <robert.drab> yes, on other repositories I set merge/push to only maintainers

[mattermost] <zygmunt.krynicki> I just looked, it's set up correctly

[mattermost] <zygmunt.krynicki> thanks!

[mattermost] <zygmunt.krynicki> CC @andrei.gherzan

[mattermost] <robert.drab> anytime

[mattermost] <andrei.gherzan> Thanks @zbigniew.bodek

[mattermost] <GitLab> Andrei Gherzan (andrei.gherzan) approved merge request [!22 *Selectively disable connectivity checker*](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/22) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <andrei.gherzan> Approved

[mattermost] <zygmunt.krynicki> ta!

[mattermost] <zygmunt.krynicki> set to merge when CI is green plz

[mattermost] <GitLab> Zygmunt Krynicki pushed to branch [fix/sanity-check](git.ostc-eu.org/OSTC/OHOS/manifest/commits/fix/sanity-check) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…2bfafdf6ea1246d6e6faf2f99a700c9997f))

[mattermost] <zygmunt.krynicki> That's the rebase button

[mattermost] <gitlab> Robert Drab (robert.drab) opened merge request [!1 *Update DoD.md*](git.ostc-eu.org/OSTC/planning/scrum/-/merge_requests/1) in [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum)

[mattermost] <GitLab> Andrei Gherzan (andrei.gherzan) merged merge request [!22 *Selectively disable connectivity checker*](git.ostc-eu.org/OSTC/OHOS/manifest/-/merge_requests/22) in [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <GitLab> Andrei Gherzan pushed to branch [develop](git.ostc-eu.org/OSTC/OHOS/manifest/commits/develop) of [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/manifest/…2bfafdf6ea1246d6e6faf2f99a700c9997f))

[mattermost] <GitLab> Zygmunt Krynicki removed branch fix/sanity-check from [OSTC / OHOS / manifest](git.ostc-eu.org/OSTC/OHOS/manifest)

[mattermost] <gitlab> Robert Drab (robert.drab) [commented on merge request !1](git.ostc-eu.org/OSTC/planning/scrum/-/merge_requests/1#note_2094) in [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum): *Update DoD.md*

[mattermost] <gitlab> Gururaj Shetty pushed to branch [master](git.ostc-eu.org/OSTC/OHOS/docs/developer-guide/commits/master) of [OSTC / OHOS / docs / developer-guide](git.ostc-eu.org/OSTC/OHOS/docs/developer-guide) ([Compare changes](git.ostc-eu.org/OSTC/OHOS/docs/deve…b64367144b3767d392f73806d58070582af))

[mattermost] <gitlab> Zygmunt Krynicki (Zygmunt.Krynicki) [commented on merge request !1](git.ostc-eu.org/OSTC/planning/scrum/-/merge_requests/1#note_2095) in [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum): *Update DoD.md*

[mattermost] <gitlab> Adam Szpilko pushed to branch [master](git.ostc-eu.org/OSTC/planning/scrum/commits/master) of [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum) ([Compare changes](git.ostc-eu.org/OSTC/planning/scrum…baec6978be6a28dc6b4da5642c3ab3a0377))

[mattermost] <gitlab> Adam Szpilko (adam.szpilko) merged merge request [!1 *Update DoD.md*](git.ostc-eu.org/OSTC/planning/scrum/-/merge_requests/1) in [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum)

[mattermost] <zygmunt.krynicki> git.ostc-eu.org/OSTC/planning/scrum…/-/merge_requests/1/diffs#note_2094

[mattermost] <gitlab> Robert Drab (robert.drab) [commented on merge request !1](git.ostc-eu.org/OSTC/planning/scrum/-/merge_requests/1#note_2097) in [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum): *Update DoD.md*

[mattermost] <zygmunt.krynicki> merging something under one minute after opening a PR is probably too fast

[mattermost] <gitlab> Robert Drab (robert.drab) [commented on merge request !1](git.ostc-eu.org/OSTC/planning/scrum/-/merge_requests/1#note_2098) in [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum): *Update DoD.md*

[mattermost] <zygmunt.krynicki> more on Monday

[mattermost] <gitlab> Robert Drab (robert.drab) opened merge request [!2 *Update DoD.md*](git.ostc-eu.org/OSTC/planning/scrum/-/merge_requests/2) in [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum)

[mattermost] <robert.drab> same here

[mattermost] <robert.drab> have a good one guys

[mattermost] <gitlab> Zygmunt Krynicki (Zygmunt.Krynicki) approved merge request [!2 *Update DoD.md*](git.ostc-eu.org/OSTC/planning/scrum/-/merge_requests/2) in [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum)

[mattermost] <gitlab> Adam Szpilko pushed to branch [master](git.ostc-eu.org/OSTC/planning/scrum/commits/master) of [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum) ([Compare changes](git.ostc-eu.org/OSTC/planning/scrum…01e37b555e00532babcf62314c5db47ce0a))

[mattermost] <gitlab> Adam Szpilko (adam.szpilko) merged merge request [!2 *Update DoD.md*](git.ostc-eu.org/OSTC/planning/scrum/-/merge_requests/2) in [OSTC / planning / Scrum](git.ostc-eu.org/OSTC/planning/scrum)