Topics

Request Creation Review for honeycomb-vpp


Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES@Cisco) <mmarsale@...>
 

Hello TSC members,

 

Please accept this project proposal for honeycomb-vpp for consideration.

https://wiki.fd.io/view/Project_Proposals/honeycomb-vpp

 

Regards,

Maros


Edward Warnicke
 

Maros,
Typically, the recommendation for repo names is that they be lowercase, short, and suitable for use as a C identifier.
In particular, for honeycomb-vpp as it will be publishing to nexus user a groupId io.fd.${reponame} and would typically use
packages io.fd.{$reponame} its probably a good idea *not* to have a  ‘-‘ in the repo name.

Ed

On Oct 27, 2016, at 4:21 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hello TSC members,
 
Please accept this project proposal for honeycomb-vpp for consideration.
 
Regards,
Maros


Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES@Cisco) <mmarsale@...>
 

Hey,

 

You are right, it’s not very short. But we wanted expressiveness over compactness here… to make it clear what the repo contains.

Regarding the group ID, we would like to use: “io.fd.honeycomb.vpp. And I’m not sure we can derive an exact repository name from it.

 

But if there are any suggestions for what would be better than a dash or perhaps a different name, we will be pleased to discuss them.

 

Thanks,

Maros

 

From: Ed Warnicke (eaw)
Sent: Friday, October 28, 2016 6:52 PM
To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...>
Cc: tsc@...; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>; Ni, Hongjun <hongjun.ni@...>; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Stefan Kobza -X (skobza - PANTHEON TECHNOLOGIES at Cisco) <skobza@...>
Subject: Re: Request Creation Review for honeycomb-vpp

 

Maros,

            Typically, the recommendation for repo names is that they be lowercase, short, and suitable for use as a C identifier.

In particular, for honeycomb-vpp as it will be publishing to nexus user a groupId io.fd.${reponame} and would typically use

packages io.fd.{$reponame} its probably a good idea *not* to have a  ‘-‘ in the repo name.

 

Ed

 

On Oct 27, 2016, at 4:21 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

 

Hello TSC members,

 

Please accept this project proposal for honeycomb-vpp for consideration.

 

Regards,

Maros

 


Wiles, Keith
 

On Oct 31, 2016, at 2:09 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hey,

You are right, it’s not very short. But we wanted expressiveness over compactness here… to make it clear what the repo contains.
Regarding the group ID, we would like to use: “io.fd.honeycomb.vpp. And I’m not sure we can derive an exact repository name from it.

But if there are any suggestions for what would be better than a dash or perhaps a different name, we will be pleased to discuss them.
Poking my nose in here just to give my opinion :-) Personally I would remove the VPP from the name as it seem redundant as the project is on the FD.io site and related to VPP already. The word honeycomb is already being using by the honeycomb folk, so just honeycomb is not useful. I would think using some phrase then use the abbreviation instead would be reasonable e.g. TLDK or VPP. Another option would be to use some name related to honeycomb like honeyjar or honeypot or honeybee or something.


Thanks,
Maros

From: Ed Warnicke (eaw)
Sent: Friday, October 28, 2016 6:52 PM
To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...>
Cc: tsc@...; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>; Ni, Hongjun <hongjun.ni@...>; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Stefan Kobza -X (skobza - PANTHEON TECHNOLOGIES at Cisco) <skobza@...>
Subject: Re: Request Creation Review for honeycomb-vpp

Maros,
Typically, the recommendation for repo names is that they be lowercase, short, and suitable for use as a C identifier.
In particular, for honeycomb-vpp as it will be publishing to nexus user a groupId io.fd.${reponame} and would typically use
packages io.fd.{$reponame} its probably a good idea *not* to have a ‘-‘ in the repo name.

Ed

On Oct 27, 2016, at 4:21 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hello TSC members,

Please accept this project proposal for honeycomb-vpp for consideration.
https://wiki.fd.io/view/Project_Proposals/honeycomb-vpp

Regards,
Maros

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc
Regards,
Keith


Keith Burns <alagalah@...>
 

Can someone remind me of the correct process please?

IIRC a project sits out on the wiki as RFC for two weeks until it gets a TSC hearing.

I assume that one can ask questions about the proposal during that time. What is the correct forum?

There's nothing on https://wiki.fd.io/view/Project_Proposals to indicate the right process for actually soliciting feedback. 


On Thu, Oct 27, 2016, 3:21 AM Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hello TSC members,

 

Please accept this project proposal for honeycomb-vpp for consideration.

https://wiki.fd.io/view/Project_Proposals/honeycomb-vpp

 

Regards,

Maros

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc


Edward Warnicke
 

You can just reply in thread to the announcement on the mailing list.

Upon looking at the https://wiki.fd.io/view/Project_Proposals I could see how that would be less than clear, and so updated it to (hopefully) make it clearer :)

Ed



On Thu, Nov 3, 2016 at 6:34 AM, Keith Burns <alagalah@...> wrote:
Can someone remind me of the correct process please?

IIRC a project sits out on the wiki as RFC for two weeks until it gets a TSC hearing.

I assume that one can ask questions about the proposal during that time. What is the correct forum?

There's nothing on https://wiki.fd.io/view/Project_Proposals to indicate the right process for actually soliciting feedback. 

On Thu, Oct 27, 2016, 3:21 AM Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hello TSC members,

 

Please accept this project proposal for honeycomb-vpp for consideration.

https://wiki.fd.io/view/Project_Proposals/honeycomb-vpp

 

Regards,

Maros

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc


Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES@Cisco) <mmarsale@...>
 

Hey Keith,

Thanks for the suggestions.

The reasons we chose honeycomb-vpp instead of some bee themed name are:
- Couldn't find a bee themed name that would express clearly what the project will hold
- If in the future some VPP plugins decide that they want dedicated projects for their honeycomb bindings, we would like to encourage using a common prefix to clearly identify the contents of such project. The prefix would currently be: "honeycomb-" and "dash" was chosen as the separator.

So we would like to keep such naming, but "honeycomb-" as a prefix seems long and "dash" as separator seems to be not ideal...

We could shorten the "honeycomb" part of the prefix to "hc" or "HC" to solve the length.
Regarding the separator. Multi-word named projects in fd.io currently use underscore or dash as a separator (https://gerrit.fd.io/r/#/admin/projects/) so we wanted to go with the convention there and chose a dash. However we can still change the separator, what do you and rest of TSC members think ?

Regards,
Maros

-----Original Message-----
From: Wiles, Keith [mailto:keith.wiles@...]
Sent: Monday, October 31, 2016 12:48 PM
To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...>
Cc: Ed Warnicke (eaw) <eaw@...>; tsc@...; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>
Subject: Re: [tsc] Request Creation Review for honeycomb-vpp


On Oct 31, 2016, at 2:09 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hey,

You are right, it’s not very short. But we wanted expressiveness over compactness here… to make it clear what the repo contains.
Regarding the group ID, we would like to use: “io.fd.honeycomb.vpp. And I’m not sure we can derive an exact repository name from it.

But if there are any suggestions for what would be better than a dash or perhaps a different name, we will be pleased to discuss them.
Poking my nose in here just to give my opinion :-) Personally I would remove the VPP from the name as it seem redundant as the project is on the FD.io site and related to VPP already. The word honeycomb is already being using by the honeycomb folk, so just honeycomb is not useful. I would think using some phrase then use the abbreviation instead would be reasonable e.g. TLDK or VPP. Another option would be to use some name related to honeycomb like honeyjar or honeypot or honeybee or something.


Thanks,
Maros

From: Ed Warnicke (eaw)
Sent: Friday, October 28, 2016 6:52 PM
To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco)
<mmarsale@...>
Cc: tsc@...; Marek Gradzki -X (mgradzki - PANTHEON
TECHNOLOGIES at Cisco) <mgradzki@...>; Ni, Hongjun
<hongjun.ni@...>; Jan Srnicek -X (jsrnicek - PANTHEON
TECHNOLOGIES at Cisco) <jsrnicek@...>; Stefan Kobza -X (skobza -
PANTHEON TECHNOLOGIES at Cisco) <skobza@...>
Subject: Re: Request Creation Review for honeycomb-vpp

Maros,
Typically, the recommendation for repo names is that they be lowercase, short, and suitable for use as a C identifier.
In particular, for honeycomb-vpp as it will be publishing to nexus
user a groupId io.fd.${reponame} and would typically use packages io.fd.{$reponame} its probably a good idea *not* to have a ‘-‘ in the repo name.

Ed

On Oct 27, 2016, at 4:21 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hello TSC members,

Please accept this project proposal for honeycomb-vpp for consideration.
https://wiki.fd.io/view/Project_Proposals/honeycomb-vpp

Regards,
Maros

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc
Regards,
Keith


Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES@Cisco) <mmarsale@...>
 

Hey,

We are still trying to find a better alternative for the name of the new "honeycomb-vpp" project. Problems with "honeycomb-vpp" are:
- length
- separator (dash or underscore as a separator could be avoided to e.g. make group ID more readable)

Just a reminder: The scope of the project will be: honeycomb translation code for VPP and its plugins. It's currently part of the honeycomb project, but deserves a dedicated one.

And the 2 finalists for the name are:
- ambrosia (sticking with the honey theme)
- hc2vpp (making it explicit that it will be ... honeycomb to vpp ... translation)

So (anyone) feel free to provide your feedback or vote for the final name.

Thanks,
Maros

-----Original Message-----
From: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco)
Sent: Monday, November 07, 2016 9:50 AM
To: 'Wiles, Keith' <keith.wiles@...>
Cc: Ed Warnicke (eaw) <eaw@...>; tsc@...; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>
Subject: RE: [tsc] Request Creation Review for honeycomb-vpp

Hey Keith,

Thanks for the suggestions.

The reasons we chose honeycomb-vpp instead of some bee themed name are:
- Couldn't find a bee themed name that would express clearly what the project will hold
- If in the future some VPP plugins decide that they want dedicated projects for their honeycomb bindings, we would like to encourage using a common prefix to clearly identify the contents of such project. The prefix would currently be: "honeycomb-" and "dash" was chosen as the separator.

So we would like to keep such naming, but "honeycomb-" as a prefix seems long and "dash" as separator seems to be not ideal...

We could shorten the "honeycomb" part of the prefix to "hc" or "HC" to solve the length.
Regarding the separator. Multi-word named projects in fd.io currently use underscore or dash as a separator (https://gerrit.fd.io/r/#/admin/projects/) so we wanted to go with the convention there and chose a dash. However we can still change the separator, what do you and rest of TSC members think ?

Regards,
Maros

-----Original Message-----
From: Wiles, Keith [mailto:keith.wiles@...]
Sent: Monday, October 31, 2016 12:48 PM
To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...>
Cc: Ed Warnicke (eaw) <eaw@...>; tsc@...; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>
Subject: Re: [tsc] Request Creation Review for honeycomb-vpp


On Oct 31, 2016, at 2:09 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hey,

You are right, it’s not very short. But we wanted expressiveness over compactness here… to make it clear what the repo contains.
Regarding the group ID, we would like to use: “io.fd.honeycomb.vpp. And I’m not sure we can derive an exact repository name from it.

But if there are any suggestions for what would be better than a dash or perhaps a different name, we will be pleased to discuss them.
Poking my nose in here just to give my opinion :-) Personally I would remove the VPP from the name as it seem redundant as the project is on the FD.io site and related to VPP already. The word honeycomb is already being using by the honeycomb folk, so just honeycomb is not useful. I would think using some phrase then use the abbreviation instead would be reasonable e.g. TLDK or VPP. Another option would be to use some name related to honeycomb like honeyjar or honeypot or honeybee or something.


Thanks,
Maros

From: Ed Warnicke (eaw)
Sent: Friday, October 28, 2016 6:52 PM
To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco)
<mmarsale@...>
Cc: tsc@...; Marek Gradzki -X (mgradzki - PANTHEON
TECHNOLOGIES at Cisco) <mgradzki@...>; Ni, Hongjun
<hongjun.ni@...>; Jan Srnicek -X (jsrnicek - PANTHEON
TECHNOLOGIES at Cisco) <jsrnicek@...>; Stefan Kobza -X (skobza -
PANTHEON TECHNOLOGIES at Cisco) <skobza@...>
Subject: Re: Request Creation Review for honeycomb-vpp

Maros,
Typically, the recommendation for repo names is that they be lowercase, short, and suitable for use as a C identifier.
In particular, for honeycomb-vpp as it will be publishing to nexus
user a groupId io.fd.${reponame} and would typically use packages io.fd.{$reponame} its probably a good idea *not* to have a ‘-‘ in the repo name.

Ed

On Oct 27, 2016, at 4:21 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hello TSC members,

Please accept this project proposal for honeycomb-vpp for consideration.
https://wiki.fd.io/view/Project_Proposals/honeycomb-vpp

Regards,
Maros

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc
Regards,
Keith


Jerome Tollet
 

I would vote for hc2cpp. Less poetic but easier to understand.
Jerome

Le 09/11/2016 18:11, « tsc-bounces@... au nom de Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) » <tsc-bounces@... au nom de mmarsale@...> a écrit :

Hey,

We are still trying to find a better alternative for the name of the new "honeycomb-vpp" project. Problems with "honeycomb-vpp" are:
- length
- separator (dash or underscore as a separator could be avoided to e.g. make group ID more readable)

Just a reminder: The scope of the project will be: honeycomb translation code for VPP and its plugins. It's currently part of the honeycomb project, but deserves a dedicated one.

And the 2 finalists for the name are:
- ambrosia (sticking with the honey theme)
- hc2vpp (making it explicit that it will be ... honeycomb to vpp ... translation)

So (anyone) feel free to provide your feedback or vote for the final name.

Thanks,
Maros

-----Original Message-----
From: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco)
Sent: Monday, November 07, 2016 9:50 AM
To: 'Wiles, Keith' <keith.wiles@...>
Cc: Ed Warnicke (eaw) <eaw@...>; tsc@...; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>
Subject: RE: [tsc] Request Creation Review for honeycomb-vpp

Hey Keith,

Thanks for the suggestions.

The reasons we chose honeycomb-vpp instead of some bee themed name are:
- Couldn't find a bee themed name that would express clearly what the project will hold
- If in the future some VPP plugins decide that they want dedicated projects for their honeycomb bindings, we would like to encourage using a common prefix to clearly identify the contents of such project. The prefix would currently be: "honeycomb-" and "dash" was chosen as the separator.

So we would like to keep such naming, but "honeycomb-" as a prefix seems long and "dash" as separator seems to be not ideal...

We could shorten the "honeycomb" part of the prefix to "hc" or "HC" to solve the length.
Regarding the separator. Multi-word named projects in fd.io currently use underscore or dash as a separator (https://gerrit.fd.io/r/#/admin/projects/) so we wanted to go with the convention there and chose a dash. However we can still change the separator, what do you and rest of TSC members think ?

Regards,
Maros

-----Original Message-----
From: Wiles, Keith [mailto:keith.wiles@...]
Sent: Monday, October 31, 2016 12:48 PM
To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...>
Cc: Ed Warnicke (eaw) <eaw@...>; tsc@...; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>
Subject: Re: [tsc] Request Creation Review for honeycomb-vpp


> On Oct 31, 2016, at 2:09 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:
>
> Hey,
>
> You are right, it’s not very short. But we wanted expressiveness over compactness here… to make it clear what the repo contains.
> Regarding the group ID, we would like to use: “io.fd.honeycomb.vpp. And I’m not sure we can derive an exact repository name from it.
>
> But if there are any suggestions for what would be better than a dash or perhaps a different name, we will be pleased to discuss them.

Poking my nose in here just to give my opinion :-) Personally I would remove the VPP from the name as it seem redundant as the project is on the FD.io site and related to VPP already. The word honeycomb is already being using by the honeycomb folk, so just honeycomb is not useful. I would think using some phrase then use the abbreviation instead would be reasonable e.g. TLDK or VPP. Another option would be to use some name related to honeycomb like honeyjar or honeypot or honeybee or something.

>
> Thanks,
> Maros
>
> From: Ed Warnicke (eaw)
> Sent: Friday, October 28, 2016 6:52 PM
> To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco)
> <mmarsale@...>
> Cc: tsc@...; Marek Gradzki -X (mgradzki - PANTHEON
> TECHNOLOGIES at Cisco) <mgradzki@...>; Ni, Hongjun
> <hongjun.ni@...>; Jan Srnicek -X (jsrnicek - PANTHEON
> TECHNOLOGIES at Cisco) <jsrnicek@...>; Stefan Kobza -X (skobza -
> PANTHEON TECHNOLOGIES at Cisco) <skobza@...>
> Subject: Re: Request Creation Review for honeycomb-vpp
>
> Maros,
> Typically, the recommendation for repo names is that they be lowercase, short, and suitable for use as a C identifier.
> In particular, for honeycomb-vpp as it will be publishing to nexus
> user a groupId io.fd.${reponame} and would typically use packages io.fd.{$reponame} its probably a good idea *not* to have a ‘-‘ in the repo name.
>
> Ed
>
> On Oct 27, 2016, at 4:21 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:
>
> Hello TSC members,
>
> Please accept this project proposal for honeycomb-vpp for consideration.
> https://wiki.fd.io/view/Project_Proposals/honeycomb-vpp
>
> Regards,
> Maros
>
> _______________________________________________
> tsc mailing list
> tsc@...
> https://lists.fd.io/mailman/listinfo/tsc

Regards,
Keith

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc


Ni, Hongjun
 

I vote for hc2vpp.

Thanks,
Hongjun

-----Original Message-----
From: honeycomb-dev-bounces@... [mailto:honeycomb-dev-bounces@...] On Behalf Of Jerome Tollet (jtollet)
Sent: Thursday, November 10, 2016 4:25 AM
To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...>; Wiles, Keith <keith.wiles@...>
Cc: tsc@...; honeycomb-dev@...; Lori Jakab <lorand.jakab@...>; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Ed Warnicke (eaw) <eaw@...>
Subject: Re: [honeycomb-dev] [tsc] Request Creation Review for honeycomb-vpp

I would vote for hc2cpp. Less poetic but easier to understand.
Jerome

Le 09/11/2016 18:11, « tsc-bounces@... au nom de Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) » <tsc-bounces@... au nom de mmarsale@...> a écrit :

Hey,

We are still trying to find a better alternative for the name of the new "honeycomb-vpp" project. Problems with "honeycomb-vpp" are:
- length
- separator (dash or underscore as a separator could be avoided to e.g. make group ID more readable)

Just a reminder: The scope of the project will be: honeycomb translation code for VPP and its plugins. It's currently part of the honeycomb project, but deserves a dedicated one.

And the 2 finalists for the name are:
- ambrosia (sticking with the honey theme)
- hc2vpp (making it explicit that it will be ... honeycomb to vpp ... translation)

So (anyone) feel free to provide your feedback or vote for the final name.

Thanks,
Maros

-----Original Message-----
From: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco)
Sent: Monday, November 07, 2016 9:50 AM
To: 'Wiles, Keith' <keith.wiles@...>
Cc: Ed Warnicke (eaw) <eaw@...>; tsc@...; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>
Subject: RE: [tsc] Request Creation Review for honeycomb-vpp

Hey Keith,

Thanks for the suggestions.

The reasons we chose honeycomb-vpp instead of some bee themed name are:
- Couldn't find a bee themed name that would express clearly what the project will hold
- If in the future some VPP plugins decide that they want dedicated projects for their honeycomb bindings, we would like to encourage using a common prefix to clearly identify the contents of such project. The prefix would currently be: "honeycomb-" and "dash" was chosen as the separator.

So we would like to keep such naming, but "honeycomb-" as a prefix seems long and "dash" as separator seems to be not ideal...

We could shorten the "honeycomb" part of the prefix to "hc" or "HC" to solve the length.
Regarding the separator. Multi-word named projects in fd.io currently use underscore or dash as a separator (https://gerrit.fd.io/r/#/admin/projects/) so we wanted to go with the convention there and chose a dash. However we can still change the separator, what do you and rest of TSC members think ?

Regards,
Maros

-----Original Message-----
From: Wiles, Keith [mailto:keith.wiles@...]
Sent: Monday, October 31, 2016 12:48 PM
To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...>
Cc: Ed Warnicke (eaw) <eaw@...>; tsc@...; Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>
Subject: Re: [tsc] Request Creation Review for honeycomb-vpp


> On Oct 31, 2016, at 2:09 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:
>
> Hey,
>
> You are right, it’s not very short. But we wanted expressiveness over compactness here… to make it clear what the repo contains.
> Regarding the group ID, we would like to use: “io.fd.honeycomb.vpp. And I’m not sure we can derive an exact repository name from it.
>
> But if there are any suggestions for what would be better than a dash or perhaps a different name, we will be pleased to discuss them.

Poking my nose in here just to give my opinion :-) Personally I would remove the VPP from the name as it seem redundant as the project is on the FD.io site and related to VPP already. The word honeycomb is already being using by the honeycomb folk, so just honeycomb is not useful. I would think using some phrase then use the abbreviation instead would be reasonable e.g. TLDK or VPP. Another option would be to use some name related to honeycomb like honeyjar or honeypot or honeybee or something.

>
> Thanks,
> Maros
>
> From: Ed Warnicke (eaw)
> Sent: Friday, October 28, 2016 6:52 PM
> To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco)
> <mmarsale@...>
> Cc: tsc@...; Marek Gradzki -X (mgradzki - PANTHEON
> TECHNOLOGIES at Cisco) <mgradzki@...>; Ni, Hongjun
> <hongjun.ni@...>; Jan Srnicek -X (jsrnicek - PANTHEON
> TECHNOLOGIES at Cisco) <jsrnicek@...>; Stefan Kobza -X (skobza -
> PANTHEON TECHNOLOGIES at Cisco) <skobza@...>
> Subject: Re: Request Creation Review for honeycomb-vpp
>
> Maros,
> Typically, the recommendation for repo names is that they be lowercase, short, and suitable for use as a C identifier.
> In particular, for honeycomb-vpp as it will be publishing to nexus
> user a groupId io.fd.${reponame} and would typically use packages io.fd.{$reponame} its probably a good idea *not* to have a ‘-‘ in the repo name.
>
> Ed
>
> On Oct 27, 2016, at 4:21 AM, Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:
>
> Hello TSC members,
>
> Please accept this project proposal for honeycomb-vpp for consideration.
> https://wiki.fd.io/view/Project_Proposals/honeycomb-vpp
>
> Regards,
> Maros
>
> _______________________________________________
> tsc mailing list
> tsc@...
> https://lists.fd.io/mailman/listinfo/tsc

Regards,
Keith

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc

_______________________________________________
honeycomb-dev mailing list
honeycomb-dev@...
https://lists.fd.io/mailman/listinfo/honeycomb-dev


Keith Burns <alagalah@...>
 

Ok cool. 

Can someone explain why we are doing this?

What's wrong with the original scope of honeycomb?

Is it that the original scope of honeycomb was too restrictive?

Why couldn't this be a sub project?

Can honeycomb-vpp run standalone or does it need honeycomb?

What is the size impact of honeycomb + honeycomb-vpp if both are required?

How is distribution and packaging going to be done?

We have limited resources, is there a need to siphon off resources to do PM/PTL work for yet another project?

What exactly is honeycomb for if not the vpp control plane agent?




On Thu, Nov 3, 2016, 11:37 AM Edward Warnicke <hagbard@...> wrote:
You can just reply in thread to the announcement on the mailing list.

Upon looking at the https://wiki.fd.io/view/Project_Proposals I could see how that would be less than clear, and so updated it to (hopefully) make it clearer :)

Ed



On Thu, Nov 3, 2016 at 6:34 AM, Keith Burns <alagalah@...> wrote:
Can someone remind me of the correct process please?

IIRC a project sits out on the wiki as RFC for two weeks until it gets a TSC hearing.

I assume that one can ask questions about the proposal during that time. What is the correct forum?

There's nothing on https://wiki.fd.io/view/Project_Proposals to indicate the right process for actually soliciting feedback. 

On Thu, Oct 27, 2016, 3:21 AM Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hello TSC members,

 

Please accept this project proposal for honeycomb-vpp for consideration.

https://wiki.fd.io/view/Project_Proposals/honeycomb-vpp

 

Regards,

Maros

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc


Joel Halpern
 

The original text called for a separate list for such discussions.  Since the TSC needs to see and understand the discussions, in order that approval reflects the actual input, we agree that the TSC list (which is open to all) was the place for such discussion.

 

From: tsc-bounces@... [mailto:tsc-bounces@...] On Behalf Of Keith Burns
Sent: Thursday, November 03, 2016 9:34 AM
To: Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...>; tsc@...
Cc: Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <jsrnicek@...>; Ed Warnicke (eaw) <eaw@...>; Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>
Subject: Re: [tsc] Request Creation Review for honeycomb-vpp

 

Can someone remind me of the correct process please?

 

IIRC a project sits out on the wiki as RFC for two weeks until it gets a TSC hearing.

 

I assume that one can ask questions about the proposal during that time. What is the correct forum?

 

There's nothing on https://wiki.fd.io/view/Project_Proposals to indicate the right process for actually soliciting feedback. 

On Thu, Oct 27, 2016, 3:21 AM Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at Cisco) <mmarsale@...> wrote:

Hello TSC members,

 

Please accept this project proposal for honeycomb-vpp for consideration.

https://wiki.fd.io/view/Project_Proposals/honeycomb-vpp

 

Regards,

Maros

_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc