Open vitcpp opened 1 year ago
Dear Sirs,
There is the pgsphere logo at http://pgsphere.github.io/img/pg_sphere.png. I may ask designers to improve it but I have no idea how to mitigate the risks of possible copyright conflicts. If you have some idea who is the owner of the logo or how to avoid possible copyright conflicts, please, share. I would appreciate it . Thank you.
I am not the creator of that logo, and I have no idea who created it, but I would say it was clearly created for "the" pgsphere project, independent from where that project happens to be hosted.
To me it seems ok to use the logo on pgsphere.org and whatever github repo/organization that hosts the code.
@msdemlei ?
The logo could use some improvement, but I very much like the premise of an elephant sitting on a sphere.
Copyright only applies to a specific image. Trademark applies to all images that depict an elephant on a sphere, for example. I rather doubt anything has been trademarked. (I am not a lawyer, but that's my understanding.)
The image probably goes back to the original repository owned by akorotkov ?
Oh right, I had assumed the logo would be new in pgsphere.github.io, but it's already present as a .png in https://github.com/postgrespro/pgsphere/tree/master/doc/img . (Haven't checked the .xcf file there, but I'd assume it matches.)
So the logo is properly part of pgsphere, and if it doesn't carry any extra (C) notices, it's ok to assume the terms from COPYRIGHT.pg_sphere.
Thank you very much for your comments! Once, it is a part of the project, we can change it under the same terms. It is a reasonable argument.
On Tue, Oct 24, 2023 at 08:58:18AM -0700, Ed Sabol wrote:
The image probably goes back to the original repository owned by akorotkov ?
I'm pretty sure it's much older. I've hence just asked Igor Chilingarian about it, and he doesn't remember either. I'd hence say it's fine if we just claim it for the project; whoever the original author is pretty certainly has lost interest in it.
I'd just redo it anyway. It's low-res and pixel-y. One of the LLM AI tools to generate art could whip up an elephant sitting on a sphere easily, I bet.
On Wed, Oct 25, 2023 at 6:44 PM msdemlei @.***> wrote:
On Tue, Oct 24, 2023 at 08:58:18AM -0700, Ed Sabol wrote:
The image probably goes back to the original repository owned by akorotkov ?
I'm pretty sure it's much older. I've hence just asked Igor Chilingarian about it, and he doesn't remember either. I'd hence say it's fine if we just claim it for the project; whoever the original author is pretty certainly has lost interest in it.
It's made by Yanko. I suggest to create a new logo keeping compatibility with old one.
— Reply to this email directly, view it on GitHub https://github.com/postgrespro/pgsphere/issues/88#issuecomment-1779567441, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQURYS674CWEPBZKPAFAEDYBEXXNAVCNFSM6AAAAAA6NEATKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZZGU3DONBUGE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
I'd just redo it anyway. It's low-res and pixel-y. One of the LLM AI tools to generate art could whip up an elephant sitting on a sphere easily, I bet.
I'm not sure, who owns the copyright when using such AI tools :)
Dear All,
I would like to propose to use the abandoned pgsphere repository for pgsphere.org site hosting. It seems we can not use postgrespro/pgsphere because we can not use custom domains for subdirectories in github. It seems, github doesn't support subdomains like pgsphere.postgrespro.github.io. So, the use of the community domain with custom domain configuration helps us.
Another thing I'm concerned, how to publish the docs for new releases automatically from postgrespro devci into the community site. I believe, it is possible, but I have no full confidence about it.
Please, let me know if you have some objections against using the community repo for pgsphere.org site hosting.
Any comments are welcome!
Just to clarify the current situation, this project already has a CI workflow which automatically publishes the documentation to https://postgrespro.github.io/pgsphere/ and going to https://pgsphere.org/ automatically redirects to https://postgrespro.github.io/pgsphere/. This seems to work well in my opinion.
https://github.com/pgsphere/pgsphere.github.io publishes to https://pgsphere.github.io/. @df7cb committed a change there last year to point the documentation section of that website to https://postgrespro.github.io/pgsphere/.
@vitcpp : I think what you are suggesting is getting committer access to https://github.com/pgsphere/pgsphere.github.io in order to publish to https://pgsphere.github.io/ which can be https://pgsphere.org/ (if you remove the current redirect).
The simple fix would be to move everything over to the other organization. Or to push doc changes to repos in both orgs.
The simple fix would be to move everything over to the other organization.
I'd rather not lose the issues and PR history we have in this project, personally.
Hi @esabol, @df7cb, I would not propose to change the existing dev site on github. All the existing dev stuff will be unchanged. My proposal is related to pgsphere.org site only, which purpose to provide some introduction and docs. Now it redirects to postgrespro.github.io/pgsphere. I propose to create a complete web site with some introduction and docs for each version using pgsphere.org domain but with github hosting. Github has the Custom Domain feature. But it can be applied to subdomains only, not to directories. Github doesn't allow to create a subdomain like pgsphere.postgrespro.github.com for which a DNS CNAME record can be created. As the initial version, we can take the existing pgsphere.github.io site with some links to postgrespro repo.
Sorry I didn't actually mean to suggest moving, just that it's one of the options. (Properly moving the repo keeps the issues etc.)
There is probably a way to automatically push doc changes from the main repo to the pgsphere org using GitHub actions. Or just have two git remotes and push to both. Or simply have a front-end web page there like now.
@vitcpp wrote:
My proposal is related to pgsphere.org site only, which purpose to provide some introduction and docs. Now it redirects to postgrespro.github.io/pgsphere. I propose to create a complete web site with some introduction and docs for each version using pgsphere.org domain but with github hosting. Github has the Custom Domain feature.
I understood that. AFAIK, the only thing preventing you from doing what you suggest is that you need committer access to https://github.com/pgsphere/pgsphere.github.io/.
@esabol I think, I have. If you and @df7cb don't mind, I will play a little with the web site. If everything will be ok, we create a CNAME alias for pgsphere.org domain name.
Sure, go ahead. TBH I'm not entirely sure how I ended up "owning" the pgsphere github org. Do whatever you seem sensible.
I concur! :smile:
The domain pgsphere.org is proposed to be the primary project place. A simple site with some description and documentation should be implemented.
Any comments, proposals, requirements are welcome!