Sure, we can have module name like bigtop-distro-select.
Do you mean that you're going to name the module (same as "component"
in the Bigtop terminology, I think) bigtop-distro-select,
and still the script in question bdp-select? If so, is there any
reason that the script must be that name?
(No offence, I just want to understand your thoughts and its
background, and avoid the conflict or user's confusion with existing
trademarks or products)
On Jul 7, 2022, at 08:37, Kengo Seki <[email protected]> wrote:
The following concern Masatake mentioned before is an important point,
so I talked to Brahma for clarifying his intention on the ASF Slack
yesterday.
Multiple versions of the same package (deb/rpm) can not be installed at the
same time.
IIRC, HDP uses convention in which the product version is part of package name
for addressing this.
I don't like to bring the awkward package name convention to Bigtop
at least by default.
He's planning to adopt the same mitigation as HDP for now, but he
doesn't intend to change the default package naming convention of
Bigtop,
but just add a new functionality to include an extra part into the
package name for avoiding conflict, which is disabled by default.
And Brahma, let me confirm about the following reply:
Sure, we can have module name like bigtop-distro-select.
Do you mean that you're going to name the module (same as "component"
in the Bigtop terminology, I think) bigtop-distro-select,
and still the script in question bdp-select? If so, is there any
reason that the script must be that name?
(No offence, I just want to understand your thoughts and its
background, and avoid the conflict or user's confusion with existing
trademarks or products)
Kengo Seki <[email protected]>
On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
<[email protected]> wrote:
The name of stack based no Bigtop should be Bigtop.
If you can not accept the name like bigtop-*, the work should done outside of
Bigtop.
I will cast -1 if someone submit a patch to add a module with the name spoiling
branding.
Sure, we can have module name like bigtop-distro-select.
Initially we'll do this separate branch.
On 06/07/22, 8:55 AM, "Masatake Iwasaki" <[email protected]> wrote:
I believe it's for project name. isn't it.?
projects and products.
IMO, We need to create folders and refer stacknames so
ambari-select,bigtop-select wn't looks good.
The name of stack based no Bigtop should be Bigtop.
If you can not accept the name like bigtop-*, the work should done outside
of Bigtop.
I will cast -1 if someone submit a patch to add a module with the name
spoiling branding.
On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
I believe it's for project name. isn't it.?
On 06/07/22, 7:27 AM, "Masatake Iwasaki" <[email protected]> wrote:
But As we are not releasing as enterprise should be fine I think. IMO, We need
to create folders and refer stacknames so ambari-select,bigtop-select wn't
looks good.
Not fine.
We have a trademark policy.
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gDhqEuyGhsdvPKcxrA65I4G9BRD86Ai%2BoasW0ycTfng%3D&reserved=0
On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
Should we avoid unrecognized brand which may be trademark of someone?
ambari-select or bigtop-select should be enough.
Not sure, where to confirm whether there is already trademark. When I googled
found so many.
But As we are not releasing as enterprise should be fine I think. IMO, We need
to create folders and refer stacknames so ambari-select,bigtop-select wn't
looks good.
May be you can refer the initial proposal [2] where I mentioned some more
names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
Finally thanks a bunch for long healthy discussions on this. Mostly we all same
page now.
1.
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFYaWY1a45yniMuLQaZjKVQGt9kE5elMrLNh8Cm9HL4%3D&reserved=0
2.
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3awZ5TFt9AyItE5CkLBLSANkjX4KIr%2FqCrdDirKEBew%3D&reserved=0
On 06/07/22, 4:01 AM, "Masatake Iwasaki" <[email protected]> wrote:
We have still not officially finalized the new replacement name for
hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
the purpose of bdp-select and conf-select remains the same.
Should we avoid unrecognized brand which may be trademark of someone?
ambari-select or bigtop-select should be enough.
On 2022/06/29 13:52, Viraj Jasani wrote:
Hi Ambari/Bigtop dev,
As per the new roadmap of Apache Ambari, we would like to propose moving
certain scripts (previously known as hdp-select and conf-select) to Bigtop
so that their rpm installation could be managed independently.
These scripts are a basic necessity in the Ambari framework for the
installation of various Bigdata packages. The only major changes they would
receive is when we onboard new services and components to Ambari, else they
usually do not receive updates. In the past, we used to get hdp-select rpm
downloaded and installed from HDP repositories.
We have still not officially finalized the new replacement name for
hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
the purpose of bdp-select and conf-select remains the same.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
