Hello everyone, I wanted to share the latest updates regarding the accounts renaming: * X (Twitter): https://x.com/ASFCloudberry (Done. X URL allows a maximum of 15 characters. ApacheCloudberry exceeds this limit, so rename X to ASFCloudberry.) * Youtube: https://www.youtube.com/@ApacheCloudberry (Done) * Slack: https://apache-cloudberry.slack.com (Done. The new `communityinviter` tool has errors, waiting for the developer to help fix) * LinkedIn: https://linkedin.com/company/apache-cloudberry (Done) * WeChat Account: ApacheCloudberry (Done)
The deactivated accounts: - Dockhub: https://hub.docker.com/u/cloudberrydb (Done) - https://portal.cloud.hashicorp.com/vagrant/discover/cloudberrydb/ (already submitted one ticket to ask for help) - Email address: i...@cloudberrydb.com, secur...@cloudberrydb.com (Done) Hi @Tushar, had added you as admin to LinkedIn and Slack workspace. If you want to help manage X and YouTube too, please let me know your account ID. I also added one notification to the original cloudberrydb GitHub homepage: https://github.com/cloudberrydb. Best, Dianjin Wang On Thu, Nov 7, 2024 at 1:47 PM Ed Espino <esp...@apache.org> wrote: > Dianjin, > > Thank you for the suggestion. While I understand the intent to create a > space for community extensions and tools, we need to exercise significant > caution when creating repositories that could be associated with Apache > Cloudberry (incubating). Any code repositories outside the Apache project's > governance pose potential risks, particularly around licensing compliance. > There's a specific concern that third-party contributions with incompatible > licenses (such as GPL) could inadvertently affect the project's Apache > licensing status. > > Perhaps we could explore alternative approaches that maintain a clear > separation between official Apache Cloudberry components and > community-contributed tools while ensuring proper license management and > compliance. > > -=e > > On Wed, Nov 6, 2024 at 7:40 PM Tushar Pednekar <tushar.pedne...@gmail.com> > wrote: > > > I like the approach for contrib . > > Happy to take on the social media work. > > ________________________________ > > From: Dianjin Wang <wangdian...@gmail.com> > > Sent: Wednesday, November 6, 2024 7:36:34 PM > > To: dev@cloudberry.apache.org <dev@cloudberry.apache.org> > > Subject: Re: Cloudberry Social Media Accounts Renaming > > > > I forgot to mention an important change regarding the original > CloudberryDB > > GitHub organization. > > > > The org `github.com/cloudberrydb` <http://github.com/cloudberrydb> < > http://github.com/cloudberrydb> should > > be renamed to ` > > github.com/cloudberry-contrib` <http://github.com/cloudberry-contrib> < > http://github.com/cloudberry-contrib> or > > a similar name. We can use this org to > > host some non-Apache License extensions or tools, and other customized > > tools for Cloudberry, but declare that they are not officially maintained > > by the PPMC. > > > > Let me know what you think. > > > > Best, > > Dianjin Wang > > > > > > On Thu, Nov 7, 2024 at 10:45 AM Dianjin Wang <wangdian...@gmail.com> > > wrote: > > > > > Hi all, > > > > > > I would like to start one discussion thread on the social media > accounts > > > renaming for Cloudberry. Refer to the ASF policy[1] and other ASF > project > > > name formats, the new URLs will be like: > > > > > > * X (Twitter): https://x.com/cloudberrydb ~> > > > https://x.com/ApacheCloudberry > > > * Youtube: https://www.youtube.com/@cloudberrydb ~> * > > > https://www.youtube.com/@ApacheCloudberry > > > * WeChat Account: CloudberryDB ~> ApacheCloudberry > > > * Slack: https://cloudberrydb.slack.com/ ~> > > > https://apache-cloudberry.slack.com/ (Slack workspace URL can only > > > contain lowercase letters, numbers and dashes and must start with a > > letter > > > or number.) > > > * LinkedIn: https://www.linkedin.com/company/cloudberrydb/ ~> > > > https://www.linkedin.com/company/apache-cloudberry (LinkedIn URL can > > > contain only lowercase alphabetic letters, numbers, Chinese, Japanese, > or > > > Korean characters and hyphens.) > > > > > > Some accounts will be deactivated: > > > - Dockhub: https://hub.docker.com/u/cloudberrydb > > > - https://portal.cloud.hashicorp.com/vagrant/discover/cloudberrydb/ > > > - Email address: i...@cloudberrydb.com, secur...@cloudberrydb.com > > > > > > The project name search is still waiting for approval from the ASF > brand > > > team, once gets approved, then we can rename them officially. > > > > > > We use the Gmail account `cloudberr...@gmail.com` to log in for X and > > > Youtube accounts. I already shared the credentials with Ed. Also added > Ed > > > as an admin or owner to the Slack workspace and LinkedIn accounts. > > > > > > Managing these social accounts will not be easy work. If you're > > interested > > > in maintaining (Only open to PPMC members), welcome to let me know. As > > per > > > Apache brand social media best practices suggestion[2], it would be > > better > > > to use some tools like Hootsuite, not sure if we can use it for free or > > > have a discount, will ask the infra or brand team. > > > > > > BTW, I'm working on the Apache Cloudberry new website. Once it goes > live, > > > the old domain name cloudberrydb.org will redirect to > > > cloudberry.apache.org. > > > > > > If any questions or feedback, feel free to let me know. Thanks! > > > > > > [1] https://incubator.apache.org/guides/publicity.html > > > [2] https://apache.org/foundation/marks/socialmedia > > > > > > Best, > > > Dianjin Wang > > > > > > > > -- > Ed Espino > Apache Cloudberry (incubating) & MADlib >
