Move this repository into a new github org

[qu1queee]

Idea:

Moving to a new repository positions the build as a more generic solution in the k8s landscape. This will end-up with the same repo under this new umbrella org, but with a different name.

@sbose78 to provide all of the details.

[sbose78]

I'll wait for consensus on this! :)

[gorkem]

+1 Also a web site for it too.

What are the options for the name?

[qu1queee]

+1, in case it was not clear I also want this :)

[zhangtbj]

The org name could be broader.

I think we will have more functions or repos inside of the new org.

Like addions, additional support or.... other builds like local or Functions build :)

[sbose78]

Likely options:

• github.com/image-build
• github.com/kube-build

Any other ideas?

[sbose78]

cc @otaviof @siamaksade

[sbose78]

Checklist for moving to a new Github org

• [ ] Decide on a name!
• [ ] Refactor source code to change package names.
• [ ] Transfer repo.
• [ ] Ensure travis CI works.
• [ ] Ensure Openshift CI works.

[zhangtbj]

I think kube scope is broder than image :)

But it is a pity github already has:

• https://github.com/kubebuild
• https://github.com/SataQiu/kube-build
• https://github.com/buildservice
• https://github.com/kbuild
• https://github.com/buildengine
• http://github.com/imagebuild

Just FYI.

[qu1queee]

I like github.com/kube-build

[DhritiShikhar]

+1 for github.com/kube-build

FYI, https://github.com/kubebuilder is available.

[DhritiShikhar]

In addition to the new github org, may be we should also have a dedicated mailing list for build?

[siamaksade]

Not sure kube-build is desirable while there is an existing org called kubebuild.

We could also use abbreviations like k8s-build as the org name and call it Kubernetes Build.

[sbose78]

Yeah, kube-build is a bad idea.

[otaviof]

I also think the k8s-build is good idea 👍

[qu1queee]

any updates on this?

[sbose78]

Blocked https://github.com/k8s-build this.

[zhangtbj]

Hi Shoubhik,

Do we decide to use k8s-build as the new org name?

If yes, can you also help add us into that org?

Thanks!

[adambkaplan]

@sbose78 @qu1queee bad news, folks. The acronym K8S is trademarked by the Linux Foundation [1], so if we name the project k8s-build we would likely get in legal hot water.

In light of this information I oppose k8s-build.

[1] https://www.linuxfoundation.org/trademark-list/

[adambkaplan]

Alternatives from a discussion I had with @sbose78 and @siamaksade:

1. kiba or kiba-build, acronym for Kubernetes Image Build API. There is an existing "kiba" project officially known as "Kiba ETL" [1][2]. Kiba is also a reference to a character in Naruto [3].
2. kbf - "a container image build framework for Kubernetes". Taking a page from OKD's naming [4].

[1] https://www.kiba-etl.org/ [2] https://github.com/thbar/kiba [3] https://naruto.fandom.com/wiki/Kiba_Inuzuka [4] https://github.com/openshift/okd

[zhangtbj]

bad news... :(

But I think less people know what is kiba, because less people use it as k8s.

How about kube-build (https://github.com/kube-build) or something?

[siamaksade]

@zhangtbj kubebuild already exists without the hyphen and it's also too closer to kubebuilder.

I'd vote for @adambkaplan suggestions with a small modification:

1. kib
2. kbf

[SaschaSchwarze0]

KiBa: https://de.wikipedia.org/wiki/KiBa_(Getr%C3%A4nk) :-)

[qu1queee]

kiba reminds me of https://en.wikipedia.org/wiki/Kibana. I think kib sounds better.

Some some proposals:

1. o-cicd, stands for OCI Container Image Continuous Delivery
2. kib-o, stands for Kubernetes Image Builder OCI based

[adambkaplan]

1. o-cicd, stands for OCI Container Image Continuous Delivery

IMO calling this project "CI/CD" is misleading. Full CI/CD pipelines are way beyond our scope and competes with Tekton.

2. `kib-o`, stands for `Kubernetes Image Builder OCI based`

I'm inclined to drop the -o because OCI is an image format. Build strategies do not have to push images in OCI format.

[adambkaplan]

It sounds like kib and kbf are our top names - if there are no objections I can take this to Red Hat's open source program office so we can run due diligence and agree on a name.

cc @sbose78 @siamaksade @SaschaSchwarze0 @qu1queee @zhangtbj

[qu1queee]

Based on the current ideas, +1 on kib @adambkaplan , and thanks for your help!

[sbose78]

We've gone for https://github.com/shipwright-io :)

[sbose78]

And moved!