Your VTN Proposal has been accepted intoBootstrap State


Andrew Grimberg
 

Kudo-san,

I have provisioned the vtn repository (please note the repo name is
lowercase). It is at present only visible to the initial committers
listed on the project proposal page
( https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):Proposal#Initial_Committers ) of note I could not find accounts in the system for the following listed initial committers:

Takayuki Kawagishi (kawagishi-takayuki@...)
Taiki Kondo (kondo-taiki@...)
Kasumi Takeshige (takeshige-kasumi@...)
Shigeru Yasuda (s-yasuda@...)

If initial committers are not able to see the repository in the web
interface while logged into Gerrit they will need to log out and log
back in for Gerrit to pick up the changes to their access.

I can add them to the list ACL once they have created accounts and I'm
notified (I search on the email address when looking them up to add, if
they registered with different addresses I need either their username or
the email address they registered with).

You will want to identify a project committer to do the originating code
submission to Gerrit. I'm available to help walk someone through doing
that. The repository does exist and the first commit is an empty one
attached to my account (this is produced by Gerrit when I initialize the
repository).

Once the code has been loaded into the repository let me know and I will
make it publicly accessible.

On the topic of not getting the source to compile. I finally worked
through the build dependency issues I was having on my test system. I
need to re-run on a clean VM to make sure I've captured them all before
I can get the Jenkins instance setup for automated patch verification.

Please note, that until I have Jenkins configured java assets produced
from merges of patches into master will not be able to show up in the
Nexus repository as we limit pushing to the repository to Jenkins only.
Admittedly, from what I see of the final build, there aren't any that
are eligible for push any way as we only allow pushes of the
org.opendaylight.<project> namespace from a given project. The two jar
objects I see are not of that namespace, they're in objs.jobjs
namespace.

-Andy-

On Fri, 2013-06-14 at 14:24 +0900, m-kudo@... wrote:
Phil san,

We are so delighted to hear that our proposal was approved.
As Yamabe san is out of town through this weekend, please let me express
our thankfulness to the TSC for this approval on behalf of him.

Regarding the repository name, we want to use VTN. So, please create
the repository with this name.

Regarding a contact of troubleshooting for full build, please contact
Yamabe san.

Again, thank you very much for the approval, and we are really excited
to work on the OpenDaylight project.

Best regards,
--
M. Kudo


Yamabe-san:

I am pleased to inform you that the OpenDaylight project proposal titled
"OpenDaylight Virtual Tenant Network" has been approved by the TSC for
entering the BootStrap state.

The next step will be uploading the source code into the OpenDaylight
repository. To do this, you will need to choose a suitable repository name
for the project. You are not required to choose the name "VTN" for your
repository, but if you do choose "VTN" it has already been pre-approved by
the TSC. If you wish to use another name, please send email to the TSC
requesting approval for the name of your choice. Please understand that
the TSC is not recommending the name "VTN", but rather has pre-approved it
on the assumption that "VTN" is the name you will want to use.

From working with the VTN code during the Inbound Code Review process, the
admin team has had some difficulty in getting the project to fully build in
the Jenkins CI environment. Can you please indicate a contact for Andrew
Grimberg (cc-ed) to work with in troubleshooting and fixing these build
issues?

Thanks Yamabe-san, and congratulations on your contribution to the
OpenDaylight Project.

Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
--
Andrew J Grimberg
Systems Administrator
The Linux Foundation


Ed Warnicke (eaw) <eaw@...>
 

Kudo san,

Might I respectfully suggest that we use a lower case convention for repo names? In this case that would be 'vtn' rather than 'VTN'. Would that be acceptable to you?

On Jun 14, 2013, at 11:58 AM, "m-kudo@..." <m-kudo@...> wrote:

Phil san,

We are so delighted to hear that our proposal was approved.
As Yamabe san is out of town through this weekend, please let me express
our thankfulness to the TSC for this approval on behalf of him.

Regarding the repository name, we want to use VTN. So, please create
the repository with this name.

Regarding a contact of troubleshooting for full build, please contact
Yamabe san.

Again, thank you very much for the approval, and we are really excited
to work on the OpenDaylight project.

Best regards,
--
M. Kudo


Yamabe-san:

I am pleased to inform you that the OpenDaylight project proposal titled
"OpenDaylight Virtual Tenant Network" has been approved by the TSC for
entering the BootStrap state.

The next step will be uploading the source code into the OpenDaylight
repository. To do this, you will need to choose a suitable repository name
for the project. You are not required to choose the name "VTN" for your
repository, but if you do choose "VTN" it has already been pre-approved by
the TSC. If you wish to use another name, please send email to the TSC
requesting approval for the name of your choice. Please understand that
the TSC is not recommending the name "VTN", but rather has pre-approved it
on the assumption that "VTN" is the name you will want to use.

From working with the VTN code during the Inbound Code Review process, the
admin team has had some difficulty in getting the project to fully build in
the Jenkins CI environment. Can you please indicate a contact for Andrew
Grimberg (cc-ed) to work with in troubleshooting and fixing these build
issues?

Thanks Yamabe-san, and congratulations on your contribution to the
OpenDaylight Project.

Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc


m-kudo@...
 

Phil san,

We are so delighted to hear that our proposal was approved.
As Yamabe san is out of town through this weekend, please let me express
our thankfulness to the TSC for this approval on behalf of him.

Regarding the repository name, we want to use VTN. So, please create
the repository with this name.

Regarding a contact of troubleshooting for full build, please contact
Yamabe san.

Again, thank you very much for the approval, and we are really excited
to work on the OpenDaylight project.

Best regards,
--
M. Kudo

Yamabe-san:

I am pleased to inform you that the OpenDaylight project proposal titled
"OpenDaylight Virtual Tenant Network" has been approved by the TSC for
entering the BootStrap state.

The next step will be uploading the source code into the OpenDaylight
repository. To do this, you will need to choose a suitable repository name
for the project. You are not required to choose the name "VTN" for your
repository, but if you do choose "VTN" it has already been pre-approved by
the TSC. If you wish to use another name, please send email to the TSC
requesting approval for the name of your choice. Please understand that
the TSC is not recommending the name "VTN", but rather has pre-approved it
on the assumption that "VTN" is the name you will want to use.

From working with the VTN code during the Inbound Code Review process, the
admin team has had some difficulty in getting the project to fully build in
the Jenkins CI environment. Can you please indicate a contact for Andrew
Grimberg (cc-ed) to work with in troubleshooting and fixing these build
issues?

Thanks Yamabe-san, and congratulations on your contribution to the
OpenDaylight Project.

Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb