On Thu, May 23, 2019 at 11:23 AM Pablo Estrada wrote:
> My main point is that there should be a limited number of top level
>> guessable prefixes. Looks like main prefixes today are runners-*, sdk-*,
>> and io-*. As long as this list small it should be fine (which is the case
>> today). Also, pro
>
> My main point is that there should be a limited number of top level
> guessable prefixes. Looks like main prefixes today are runners-*, sdk-*,
> and io-*. As long as this list small it should be fine (which is the case
> today). Also, probably we document this structure somewhere. JIRA componen
On Thu, May 23, 2019 at 10:28 AM Pablo Estrada wrote:
> I've added the io-python-hadoop component [1]. We can continue to discuss
> naming conventions for components[2].
>
> The way Java is set up, we have:
> sdk-java-*
> io-java-*
>
> For Python, we have:
> sdk-py-*
> io-python-*
>
> We could be
I've added the io-python-hadoop component [1]. We can continue to discuss
naming conventions for components[2].
The way Java is set up, we have:
sdk-java-*
io-java-*
For Python, we have:
sdk-py-*
io-python-*
We could be consistent with the old Java IO components by doing `io-py-*`.
I think doin
On Thu, May 23, 2019 at 9:20 AM Valentyn Tymofieiev
wrote:
> Hi,
>
> Could someone please help with addition io-python-hadoop or similar
> component to Jira?
>
> Also, there is a small discrepancy in naming py vs python between:
>
> io-python-gcp and sdk-py-core - consider unifying them.
>
+1 on
Hi,
Could someone please help with addition io-python-hadoop or similar
component to Jira?
Also, there is a small discrepancy in naming py vs python between:
io-python-gcp and sdk-py-core - consider unifying them.
Thank you!
