Closed blacklabelops closed 5 years ago
Any chance you'd be willing to transfer the projects over to another group? Likely with new names. I might be willing to take them on.
Yes, I would be willing to transfer the projects.
@Firefishy @blacklabelops https://github.com/cptactionhank/docker-atlassian-confluence seems to be the alternative in this space. Steffen, thank you for doing this in the first place!
Also, if either of you are interested, I just got done revamping this particular image with stuff done in other Confluence & Java images; kept getting performance complaints on my GCE-hosted install. https://gist.github.com/unquietwiki/5e4dc5f86c9e3989fbf1c34c30543037 if you feel like taking a look.
Hello, I would like to be one of you please include me in the group
I'm also willing to participate.
I can create an organization/group and add @blacklabelops. Steffen can then add those people he wants to maintain going forward.
Does this sound good to everyone?
Can we discuss the group name here?
Using "Atlassian" in the name might cause issues surrounding copyright and/or intellectual property. So, then I was thinking to use the stock symbol of "TEAM". However, that could have the same type of issues (see here for some reading).
Some of my suggestions are as follows:
atldocker sounds good: atlops could be confused with the airport.
On Wed, Jan 23, 2019 at 2:26 PM Jonathan Hult notifications@github.com wrote:
Using "Atlassian" in the name might cause issues surrounding copyright and/or intellectual property. So, then I was thinking to use the stock symbol of "TEAM". However, that could have the same type of issues (see here https://www.altacit.com/publication/ticker-symbols-trademarks/ for some reading).
Some of my suggestions are as follows:
- atldocker
- atlops
- atlcontainers
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/blacklabelops/confluence/issues/61#issuecomment-456990984, or mute the thread https://github.com/notifications/unsubscribe-auth/AA9fv6p3qiEDx6CCutCxQNMJoAYESIdkks5vGOGzgaJpZM4YCwhF .
--
Michael Adams https://unquietwiki.com/ http://www.unquietwiki.com/
Looks good, lets wait some days for more suggestions.
I am still indecisive about atlops or atldocker. What do you guys say?
I'm okay with either; maybe a slight preference towards atldocker.
I guess we stick with atldocker, can you create a group?
I have created the organization: https://github.com/atldocker
I have invited @blacklabelops. Once he accepts, I should be able to allow him to invite others.
@blacklabelops, are you okay with transferring some or most of your repos to the new organization? I believe this would be very beneficial since, "When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred." Steps on how to transfer can be found here.
@blacklabelops, thanks for joining and adding @Firefishy.
Any thoughts on transferring the repos?
Comes next.
Is the intent here to make this a ridiculously simple transition so we just change docker-compose lines like this:
jira:
image: blacklabelops/jira:7.12.1
to this:
jira:
image: atldocker/jira:7.12.1
?
Also... @blacklabelops Thanks a tonne for your great work on these images, and good luck with whatever you are working on next. :)
Repository transfer this weekend.
@Firefishy and @jhult please send me your email adresses to my email adress. There is no message system on github.
Emailed my details.
This has been completed.
Same question as before...
Can upgrades be done simply by replacing blacklabelops
with atldocker
in docker-compose files?
Well... there is a problem in that we didn't snag the Docker Hub username atldocker
. So, at the moment, you need to clone the repository and then build yourself.
Timing is impeccable/odd. I just posted about this in #67.
Any tips on build instructions? I need to upgrade out of the WebDAV vulnerability.
The dockerhub/blacklabelops version is really dangerously stuck on 6.12.0!!!
I will stop supporting and implementing Docker images starting in early 2019.
Repositories will be transferred to blacklabelops-legacy and archived for read only purpose.
The following repositories and images are affected:
January 2019
March 2019