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> 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> wrote: > >> What about Markdown? >> >> >> --Randy >> >> VP, Technology and Strategy, Cloud Software >> Juniper Networks >> +1 (415) 787-2253 [SMS or voice] >> ASSISTANT: Stephanie Concepcion, sconcepc...@juniper.net >> TWITTER: twitter.com/randybias >> LINKEDIN: linkedin.com/in/randybias >> >> >> >> *** Sent from mobile, pls forgive tpyoes *** >> >> On May 15, 2017, at 20:21, Edgar Magana <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> 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 >>>> TWITTER: @randybias >>>> LINKEDIN: linkedin.com/in/randybias >>>> >>>> >>>> From: Edgar Magana <edgar.mag...@workday.com> >>>> Date: Monday, May 15, 2017 at 1:50 PM >>>> To: "CARVER, PAUL" <pc2...@att.com>, Randy Bias <rb...@juniper.net>, >>>> "dev@lists.opencontrail.org" <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> on behalf of "CARVER, PAUL" >>>> <pc2...@att.com> >>>> Date: Monday, May 15, 2017 at 5:06 AM >>>> To: "ran...@juniper.net" <ran...@juniper.net>, >>>> "dev@lists.opencontrail.org" <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 >>>> >>>> > _______________________________________________ > Dev mailing list > Dev@lists.opencontrail.org > http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
_______________________________________________ Dev mailing list Dev@lists.opencontrail.org http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
