Create List of Baseimage Inspired Projects

[naftulikay]

I've been a user of baseimage for quite some time, but I'd really like to see a CentOS fork. For a number of reasons, I've stopped using Ubuntu based images.

[FooBarWidget]

Anyone is free to fork this repository and create a CentOS variant, but we won't be doing this because we don't use CentOS containers.

[jwilson8767]

I'm working on a Centos port over here

[Theaxiom]

@jwilson8767 If you don't mind, it would be great to bring your work over to a branch in this repo when the work is completed. I have re-opened this issue to track. Please reference this issue when ready for us to pull over, thanks!

[jwilson8767]

@Theaxiom Right now all the docs are Ubuntu focused, do you have any plans to generalize them for other ports?

[hyperknot]

I'd personally vote for a separate repo like baseimage-centos or similar. Maintaining one OS's particularities etc. is already quite difficult, and definitely needs full attention and "full-time" contributors. Now mixing two OS-es in one repo is just asking for trouble.

[Theaxiom]

You have a point, thanks. I suppose you are correct. Maybe we should add the other repo links to the readme instead.

…

On Aug 16, 2017, at 1:18 PM, Zsolt Ero ***@***.***> wrote: I'd personally vote for a separate repo like baseimage-centos or similar. Mixing issues, maintaining one OS's particularities etc. definitely needs full attention and "full-time" contributors maintaining those very specific issues. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#308 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADetWUz0XsB_iz46_gNkAxBNMpQ4m-Fks5sY06cgaJpZM4If4se>.

[hyperknot]

Yes, links to related projects is a good idea in the README.

[jwilson8767]

Links to forks/ports sound like a start. The next big thing as far as I'm concerned would be to have one the maintainers of phusion/baseimage-docker join me on this Centos fork. Mostly to reduce divergence, but also to ensure that my efforts here don't go to waste as I shift focus to other projects.

[hyperknot]

@jwilson8767 if you start a fork, it's only up to you how much maintenance it receives and how long do you keep it updated. As you can see even with a handful of maintainers on a very stable code base sometimes it takes some time/effort to keep this repo maintained.

[jwilson8767]

I agree completely. My plan is to get this Centos fork stable/production ready, and then to keep it in sync with upstream changes. I just know the amount of time I can put into OSS waxes and wanes as I have paying projects.