It appears that maybe the mailing list bounced it. I did receive a response from Randy which was addressed to both me personally and to dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org> but I don’t see the message in the mailing list archive. The following is copied from Randy’s email.
You can find the deck at: https://www.slideshare.net/randybias/rebooting-the-opencontrail-community<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.slideshare.net_randybias_rebooting-2Dthe-2Dopencontrail-2Dcommunity&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=xtmPik_TP2fjPVGWP4yBRQ&m=qBJyN21tFUOQnhwSbT_-DNeThodF6UM5T02kTVn5uvc&s=lfZg1Oe-5RFdrXESq16Kkoe4oddxD7yt-9rbJBlla78&e=> The Google group can be found at: https://groups.google.com/forum/#!forum/opencontrail-founding<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_forum_-23-21forum_opencontrail-2Dfounding&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=xtmPik_TP2fjPVGWP4yBRQ&m=qBJyN21tFUOQnhwSbT_-DNeThodF6UM5T02kTVn5uvc&s=EPSfK2ER9MzTWj6yWXP6H-qk2CsLqTqgd23L8_Nl26s&e=> From: Edgar Magana [mailto:edgar.mag...@workday.com] Sent: Wednesday, May 24, 2017 13:44 To: Harshad Nakil <hna...@gmail.com>; CARVER, PAUL <pc2...@att.com> Cc: dev@lists.opencontrail.org Subject: Re: [opencontrail-dev] Slide deck from the OCUG meeting Folks, Just reviewing my notes and it seems that the slide deck has not been shared yet. I know that Randy is in PTO for a couple of weeks, does anyone else has access to those slides? Thanks, Edgar From: Harshad Nakil <hna...@gmail.com<mailto:hna...@gmail.com>> Date: Tuesday, May 16, 2017 at 7:08 AM To: "CARVER, PAUL" <pc2...@att.com<mailto:pc2...@att.com>> Cc: Edgar Magana <edgar.mag...@workday.com<mailto:edgar.mag...@workday.com>>, "dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>" <dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>> Subject: Re: [opencontrail-dev] Slide deck from the OCUG meeting Usually in community people take responsibility and initiative to do what they want. Whoever is first to take initiative wins :) Currently developers have put the documents where code is. One can show the way by taking initiative. Regards -Harshad On May 16, 2017, at 3:38 AM, CARVER, PAUL <pc2...@att.com<mailto:pc2...@att.com>> wrote: If I remember correctly, rst has a bit of a Python linkage while markdown is more widely used, but the most important question is tooling. Github will render both automatically but should Github be the primary place for Contrail publication? OpenStack publishes to https://docs.openstack.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.openstack.org&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ZWVtTGwUHCdPj1Vh-UXDmvp6UaWOsOGFj3V-tf7XnF4&s=kPELO5QDZh_t_Em3sLdqnt_qqlanvszkCIYmFj6hSok&e=> by rendering source files in Git to HTML with Github serving only as a secondary mirror of the Git repos. The older documentation has been in Docbook XML but a lot of programmers dislike dealing with that at all (and I strongly agreed, I'd much rather deal with either markdown or rst than Docbook) so much of OpenStack documentation has moved to rst. If we're going to have a https://docs.opencontrail.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.opencontrail.org&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=ZWVtTGwUHCdPj1Vh-UXDmvp6UaWOsOGFj3V-tf7XnF4&s=HTeY3vpCmOroNHfQF1PhqQazyPnwFPvSHXsLCqn34IQ&e=> generated by Jenkins/Zuul from source files in Git repos then someone will need to setup the CI pipeline so it would be worth getting input from whoever has the most experience with the existing Contrail CI pipelines. The important thing is to be clear about it because you can't mix and match. I recently cleaned up networking-vpp documentation because someone had written markdown in an rst file and that doesn't render properly at all, even with Github's automatic rendering. -- Paul Carver V: 732.545.7377 C: 908.803.1656 -------- Original message -------- From: Harshad Nakil <hna...@gmail.com<mailto:hna...@gmail.com>> Date: 5/16/17 00:38 (GMT-05:00) To: Edgar Magana <edgar.mag...@workday.com<mailto:edgar.mag...@workday.com>> Cc: dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org> Subject: Re: [opencontrail-dev] Slide deck from the OCUG meeting We have been using markdown for all documentation. But of course "community" thinks that developers don't understand anything. Regards -Harshad On May 15, 2017, at 9:32 PM, Edgar Magana <edgar.mag...@workday.com<mailto:edgar.mag...@workday.com>> wrote: Hi, Those will work as well. Maybe, this is a good opportunity to get feedback from the community. What do you OpenContrail member wanted to use? Cheers, Edgar On May 15, 2017, at 8:22 PM, Randy Bias <rb...@juniper.net<mailto:rb...@juniper.net>> wrote: What about Markdown? --Randy VP, Technology and Strategy, Cloud Software Juniper Networks +1 (415) 787-2253<tel:+1%20(415)%20787-2253> [SMS or voice] ASSISTANT: Stephanie Concepcion, sconcepc...@juniper.net<mailto:sconcepc...@juniper.net> TWITTER: twitter.com/randybias<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_randybias&d=DwMGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=pbb5xL1uJX8mJDD60Lrf3dMcwxguG5fbrjXvOJuBvD4&s=40mhqwVgH0lX9HLy33rxwU9rZ0UFDc_kZCeOuk8uqoA&e=> LINKEDIN: linkedin.com/in/randybias<https://urldefense.proofpoint.com/v2/url?u=http-3A__linkedin.com_in_randybias&d=DwMGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=pbb5xL1uJX8mJDD60Lrf3dMcwxguG5fbrjXvOJuBvD4&s=Cufvq1eE1ythvp3h5fzO7KUD3YAW_L8nfRJ8IPnjPeE&e=> *** Sent from mobile, pls forgive tpyoes *** On May 15, 2017, at 20:21, Edgar Magana <edgar.mag...@workday.com<mailto:edgar.mag...@workday.com>> wrote: Randy, In my experience .rst files are very easy to manage for documentation and processes. Edgar On May 15, 2017, at 8:05 PM, Randy Bias <rb...@juniper.net<mailto:rb...@juniper.net>> wrote: What format in Github? --Randy Vice President, Technology & Strategy, Cloud Software Juniper Networks +1 (415) 787-2253 [Google Voice] ASSISTANT: Stephanie Concepcion, sconcepc...@juniper.net<mailto:sconcepc...@juniper.net> TWITTER: @randybias LINKEDIN: linkedin.com/in/randybias<https://urldefense.proofpoint.com/v2/url?u=http-3A__linkedin.com_in_randybias&d=DwMGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=pbb5xL1uJX8mJDD60Lrf3dMcwxguG5fbrjXvOJuBvD4&s=Cufvq1eE1ythvp3h5fzO7KUD3YAW_L8nfRJ8IPnjPeE&e=> From: Edgar Magana <edgar.mag...@workday.com<mailto:edgar.mag...@workday.com>> Date: Monday, May 15, 2017 at 1:50 PM To: "CARVER, PAUL" <pc2...@att.com<mailto:pc2...@att.com>>, Randy Bias <rb...@juniper.net<mailto:rb...@juniper.net>>, "dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>" <dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>> Subject: Re: [opencontrail-dev] Slide deck from the OCUG meeting Folks, These are all excellent points. Would it be possible to have all these details in github repos? That will be easy to follow up the conversations instead of using email. Well, just my proposal. It is working well for other open source communities such as OpenStack. Thanks, Edgar From: Dev <dev-boun...@lists.opencontrail.org<mailto:dev-boun...@lists.opencontrail.org>> on behalf of "CARVER, PAUL" <pc2...@att.com<mailto:pc2...@att.com>> Date: Monday, May 15, 2017 at 5:06 AM To: "ran...@juniper.net<mailto:ran...@juniper.net>" <ran...@juniper.net<mailto:ran...@juniper.net>>, "dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>" <dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>> Subject: [opencontrail-dev] Slide deck from the OCUG meeting Randy, Thanks for your presentation at the Open Contrail Users Group last week. Can you please post a public link to your slide deck for people who were unable to attend or who didn’t take phone photos of every slide. Especially, the link to the Google Group needs to go out so that everyone on the Dev mailing list can sign up. I have a list of potential topics for the first meeting of whatever forum you end up organizing. * Compiling Contrail from source – There has been a fair amount of discussion of this on the mailing list recently * Discussion of issues people are encountering * Build scripts * Prerequisites * Documentation of the build process * Due dates * An overview of current key dates in the process (blueprint, code complete, testing, documentation, beta, GA) * Discussion of any changes that might help contributors plan better * Dates for dates – set expectations on how and when the key dates for future releases will be set * Missed date management – discussion of how slipped dates for Juniper’s GA release impact community development * Testing procedures * Discussion of how third party developers should expect to interact with Juniper during the time period between code freeze and beta and GA * Discussion of beta vs release candidate and whether there are process improvements needed in order to ensure that third party developers are able to catch and fix bugs in the features they are developing * Overview of test framework, not just unit tests but functional and full stack automated tests * Documentation * How are non-Juniper developers expected to deliver documentation for features that they develop? * When is documentation due? * Core reviewer / TSC / meetings * What are the expectations for a non-Juniper developer to become a core reviewer? * Does Contrail have anything equivalent to a Technical Steering Committee? * Are there any regularly scheduled meetings (e.g. on Slack/IRC or teleconference) for developers to sync up on progress of their changes, discuss code reviews, discuss bugs, etc * Build system problems – How can non-Juniper contributors effectively troubleshoot issues like this: https://jenkins.opencontrail.org/job/ci-contrail-vrouter-systest-ubuntu14-mitaka/480/console<https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.opencontrail.org_job_ci-2Dcontrail-2Dvrouter-2Dsystest-2Dubuntu14-2Dmitaka_480_console&d=DwMFAg&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=672AiZ61UGMFTc1WfPGBmgJYUEzVnbC9i9hqKSlloZo&s=j-50PyEc_ppikIVehQAGlLvpHxEL8q7515cEI087XEo&e=> _______________________________________________ Dev mailing list Dev@lists.opencontrail.org<mailto:Dev@lists.opencontrail.org> http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opencontrail.org_mailman_listinfo_dev-5Flists.opencontrail.org&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=xtmPik_TP2fjPVGWP4yBRQ&m=-82g0JOxB4MmO2WE5pdM4Ax_lUx7cCMCvqDI0E0Kxpw&s=_4v1bQKzoqVSdZzyDH5Tdf5DhvRs--Zrjln19VV9Ywo&e=>
_______________________________________________ Dev mailing list Dev@lists.opencontrail.org http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
