profile
viewpoint

bambinos/bambi 495

BAyesian Model-Building Interface (BAMBI) in Python.

aloctavodia/BAP 313

Bayesian Analysis with Python (Second Edition)

canyon289/bayesian-model-evaluation 107

Presented at Scipy Conference 2019

bambinos/Bambi_resources 32

Educational resources

arviz-devs/Exploratory-Analysis-of-Bayesian-Models 11

Educational resources related to ArviZ

53seven/inked 0

A collection of D3 chart implemented in ES6 classes

canyon289/AIND-Isolation 0

Isolation AI Game

push eventpymc-devs/pymcon

Oriol (ZBook)

commit sha 6d387f42c5360fcc91fc778f11f6cfa5febc3d3d

configure internet goodness html metadata, seo tags, nice "card" view for twitter, whats, slack...

view details

Ravin Kumar

commit sha a5f2f997264e4a9b78fb3a9623dc6c5860cf2edd

Merge pull request #38 from pymc-devs/internet_goodness configure internet goodness

view details

push time in 4 hours

PR merged pymc-devs/pymcon

configure internet goodness

html metadata, seo tags, nice "card" view for twitter, whats, slack...

I have pushed to both this branch and my fork so a preview is available. Click here for the preview and most importantly, go to slack and send two messages to yourself:

  1. https://pymc-devs.github.io/pymcon or https://pymc-devs.github.io/pymcon//cfp

image

  1. https://oriolabril.github.io/pymcon/ or https://oriolabril.github.io/pymcon/

image

I have also added a github icon and a heart icon to the footer, github goes to pymc-devs org and heart goes to numfocus page to donate to pymc

+15 -17

1 comment

5 changed files

OriolAbril

pr closed time in 4 hours

pull request commentpymc-devs/pymcon

configure internet goodness

LGTM, merging so we can get this SEO goodness out there asap so the search engines can crawl it

OriolAbril

comment created time in 4 hours

startedmjskay/uncertainty-examples

started time in 5 hours

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 498cbb4626c315d224164317200f45712a2fe023

Change cfp wording

view details

Ravin Kumar

commit sha 626f4ca0a603e762529f1556f436b046d04a5878

Remove extra words

view details

Ravin Kumar

commit sha 9640d0135ddf9ea519830b7ab0e6d181d28a1de1

Consolidate sections

view details

Ravin Kumar

commit sha 4171fbb1d38458611680c2d20662c4b5773a80d8

Update wording slightly

view details

Ravin Kumar

commit sha 581e90510f7bbd3e284808114ceb8331a5c01d00

Update what we look for

view details

Oriol (ZBook)

commit sha c4066c574eafa914497945d626066da7f01289a5

extend details in cfp

view details

Oriol (ZBook)

commit sha b496ea4b09d317e72902ed5a6f3359e179892a57

add faq advise

view details

Ravin Kumar

commit sha 3be072db1de11bff875fd733adacc2d6d3b99545

Fix typo, expand time limit of LBAM and change material to exercises

view details

Ravin Kumar

commit sha 7006feeed698673296f2b803908037bbbb736c06

Modify tutorial section a little

view details

Ravin Kumar

commit sha acd3079dca59decd5372e2aab1e83b447bd8e2d7

Merge pull request #37 from pymc-devs/cfp_wording Change cfp wording slightly

view details

push time in 19 hours

PR merged pymc-devs/pymcon

Change cfp wording slightly

Feel free to edit directly, push, merge whatever

+230 -60

2 comments

1 changed file

canyon289

pr closed time in 19 hours

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 7006feeed698673296f2b803908037bbbb736c06

Modify tutorial section a little

view details

push time in 19 hours

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 3be072db1de11bff875fd733adacc2d6d3b99545

Fix typo, expand time limit of LBAM and change material to exercises

view details

push time in 19 hours

Pull request review commentpymc-devs/pymcon

Change cfp wording slightly

 <h2 class="first">Key Dates</h2>       <p>Deadline for CFP: September 4th, 2020. Anywhere on Earth.</p>       <p>Date of speaker content submission: TBD. Likely first week of October 2020.</p> -      <h2 class="first">Format</h2>+      <h2 class="first">Conference Summary</h2>       <p>       PyMCon 2020 is an asynchronous-first conference.-      All accepted speakers will submit a video or code ahead of time,-      which will be posted in a TBD place (probably YouTube).+      All accepted speakers will submit a video with their presentation ahead of time.       </p> -      <h2 class="first">What we are looking for</h2>       <p>-        We are looking for folks like you to share your cool tricks, best practices,-        and general knowledge with the Bayesian community.-        This conference will have two tracks,-        a "Conjugate Model" track for folks just getting started out,-        and a "No U turn Sampler" track for folks that are already tuned and well warmed up with Bayesian Methods.-        (Track names  and puns subject to change).+      We are looking for folks like you to share your cool tricks, best practices,+      general knowledge, or model build methods with the Bayesian community.+      Presentations should have some relevance to the PyMC community, more details on+      what we look for in a presentation and how to propose one can be found below.       </p>        <p>-          There are three formats we're looking for specifically:+      All presentations will be pre-recorded and will be shared on the PyMC discourse in+      late October for the async component. We are also planning a synchronous component+      for early November. Further details are below as well.       </p> -      <h3 class="first">Talks</h3>-      <p class=normal-text>-        Traditional talks are 30 to 40 minutes in length and should be pre-recorded.-        If accepted, speakers are asked to submit a video file that contains the recording of their talk,-        which will be uploaded and viewed prior to the conference.-        As pre-recorded videos, talks are expected to be polished and crisp.-        Slide contents and language should be professional and comprehendible.-        A successful talk does not have to be about a novel, cutting-edge technology topic but should be distinctive and have the ability to keep the attention of the audience.-        We will provide a platform for audience discussions and Q&A.-        Accepted speakers are asked to be online the day of for at least one session of Q&A to answer questions live, which is 20 minutes long;-        of course, they are free to participate in the discussions with the audience outside of this Q&A session as well.+      <p>+      This conference will have two tracks:+      <ul>+        <li>a "Conjugate Model" track for folks just getting started out,</li>+        <li>and a "No U Turn Sampler" track for folks that are already  warmed up with+          Bayesian Methods.</li>+      </ul> -      </p>+      First time speakers are welcomed and encouraged. Please feel free to reach+      out with questions about submitting a proposal, you can find us at the <a href="https://discourse.pymc.io/t/pymcon-2020-call-for-proposals-is-open/5567">PyMC discourse</a>.  </p> -      <h3 class="first">Tutorials</h3>-      <p class=normal-text>-        Tutorials are dedicated to introducing, promoting, and advancing specific techniques/practices in computational Bayesian statistics with PyMC.-        Each tutorial, also to be recorded, is one hour long and should cover a topic more in depth than a traditional talk.-        Tutorial facilitators are responsible for preparing interactive and carefully designed materials,-        including hands-on exercises that help reinforce the concepts discussed in their topics.-        We will provide the platform (most likely Slack) in which tutorial facilitators can communicate and share materials with their audience prior to the conference.-      </p>--      <h3 class="first">Let's Build a Model</h3>-      <p class=normal-text>-        We are excited to introduce a new conference talk format called Let’s Build a Model (LBAM).-        While sharing many common characteristics with tutorials,-        LBAM talks aim to showcase the exciting (and sometimes messy!) nature of Bayesian modeling.-        In a LBAM talk, the presenter should first establish a specific modeling goal and then proceed to build that Bayesian model from scratch using PyMC (e.g., in a Jupyter notebook).-        A LBAM talk is also a pre-recorded video and should be one hour long.-        We know Bayesian modeling is a considerably involved process and can therefore be daunting to new users.-        With LBAM talks, we aim to address this problem by encouraging presenters to be as thorough as possible,-        while making sure to include relevant “tricks of the trade” that they find useful in their own experience.-      </p>--      <h2 class="first">What we look for in a submission</h2>-      <p class = "normal-text">-        More to come+      <p>+      There are three presentation formats:+      <dl>+        <dt><a class="reference internal" href="#talks">Talks</a></dt>+        <dd>30-40 min video about PyMC tricks, best practices, related library, etc.</dd>+        <dt><a class="reference internal" href="#tutorials">Tutorials</a></dt>+        <dd>60 min video + engaging material diving into a spedific PyMC related topic.</dd>+        <dt><a class="reference internal" href="#lbam">Let's build a model</a></dt>+        <dd>60 min video documenting how to build an example model using PyMC.</dd>+      </dl>       </p> -      <h2 class="first">Format of conference</h2>+      <h2 class="first">Conference Specifics</h2>       <p class=normal-text>         PyMCon 2020 is an asynchronous-first conference,         that will include a both an async discussion and synchronous discussions.-        There are three primary components:+        All presentations have three primary components:            <ul>-            <li>A prerecorded talk, tutorial, or "Let's build a model"</li>+            <li>A prerecorded video</li>             <li>A 1-week forum discussion</li>             <li>A synchronous time for folks to meet!</li>           </ul>       </p>       <h3 class="first">Self-recording (T-3 Weeks prior to conference)</h3>       <p class=normal-text><b>Put on a shirt. Pants optional. Hit record </b> </br>-        You as a speaker will be giving a talk or tutorial as you would at any other conference,+        You as a speaker will be giving a presentation as you would at any other conference,         except that you will be recording it ahead of time.-        PyMCon will collect the recording and post them on online about a week prior to the conference day.+        PyMCon will collect the videos and post them on online about a week prior to the conference day.         </p>       <h3 class="first">Async Discussion (T-1 Week prior to conference)</h3>       <p class=normal-text><b>Put on a shirt. Pants optional. Answer questions on discourse </b> </br>-        All submissions will be posted onto the PyMC discourse so the community as a whole-        can engage, read, and talk, all at their own pace.-        As a speaker, this allows your submission to be seen by a much wider audience+        All presentations will be posted onto the PyMC discourse so the community as a whole+        can engage, read, and comment, all at their own pace.+        As a speaker, this allows your presentation to be seen by a much wider audience         than if just presented once and have a richer conversation with your viewers.       </p>        <h3 class="first">Synchronous Conference Day (T-0 Liftoff!)</h3>        <p class=normal-text><b>Dress your best and meet all the folks </b> </br>         This day will look more like the open source conferences you've loved in the past.-        As an attendee this day will consist of Lightning Talks, Birds of a Feather discussion-        sessions, and discussion sessions from speakers.-        As a speaker we'll ask that you be able to answer questions live for folks that are on the call.+        As an attendee this day will likely consist of Lightning Talks, Birds of a Feather discussion+        sessions, and discussion sessions from speakers. We'd like to have speaker available answer+        questions live for folks in sessions as well.         The exact timing is TBD, but we plan to find time zones that are convenient for everyone-        and may end up doing two synchronous sessions in the same calendar day-        to meet our global community's localities.+        and may end up doing two synchronous sessions in the same calendar day to meet our+        global community's localities.+      </p>+      <h2 class="first">Presentation formats</h2>+      <div id="talks" class="section">+      <h3 class="first">Talks</h3>+      <p class=normal-text>+        Talks will consist of a 30 to 40 minutes video. As pre-recorded videos, talks are+        expected to be polished and crisp.+      </p>+      <p>+        All the content shown in the video (slides, code, plots...) and language should+        be professional, comprehensible and follow PyMCon code of conduct.+        A successful talk does not have to be about a novel, cutting-edge technology+        topic but should be distinctive and have the ability to keep the attention of+        the audience. We will provide a platform for audience discussions and Q&A.+        Accepted speakers are asked to be online the day of for at least one session of+        Q&A to answer questions live, which is 20 minutes long;+        of course, they are free to participate in the discussions with the audience+        outside of this Q&A session as well.+      </p>+      </div>++      <div id="tutorials" class="section">+      <h3 class="first">Tutorials</h3>+      <p class=normal-text>+        Tutorials are dedicated to introducing, promoting, and advancing specific+        techniques/practices in computational Bayesian statistics with PyMC. They should+        cover a topic more in depth than a traditional talk.+        Tutorials will consist of a 60 minutes video and extra material for attendees to+        engage and experiment with the contents of the tutorial.+      </p>+      <p>+        Tutorial facilitators are responsible for preparing interactive and carefully+        designed materials, including hands-on exercises that help reinforce the concepts+        discussed in their topics. We will provide the platform (most likely Slack) in+        which tutorial facilitators can communicate and share materials with their+        audience prior to the conference.+      </p>+      </div>++      <div id="lbam" class="section">+      <h3 class="first">Let's Build a Model</h3>+      <p class=normal-text>+        We are excited to introduce a new conference presentation format called "Let’s+        Build a Model" (LBAM). While sharing some characteristics with tutorials,+        LBAM talks aim to showcase the exciting (and sometimes messy!) nature of+        Bayesian modeling.+      </p>+      <p>+        In a LBAM talk, the presenter should first establish a specific modeling goal+        and then proceed to build that Bayesian model from scratch using PyMC (e.g.,+        in a Jupyter notebook). Like tutorial, LBAM videos should be 60 minutes long.       </p>+      <p>+        We know Bayesian modeling is a considerably involved process and can therefore be daunting to new users.+        With LBAM talks, we aim to address this problem by encouraging speakers to be as thorough as possible,+        while making sure to include relevant “tricks of the trade” that they find useful in their own experience.+      </p>+      </div>++      <h2 class="first">What we are looking for in a proposal</h2>+      <p>+        So many are people are doing so many cools things we don't want to restrict ideas+        with a "strong prior". However we will consider proposals based on the following+        principles+      </p>++      <p class=normal-text><b>Originality</b> </br>+        Proposals should that originality in some dimension whether that be in+        presentation approach, visuals, math, whatever! Be creative and show it off!+        Proposals that are already publicly available or similar to published videos have+        a low probability of being accepted.+      </p>++      <p class=normal-text><b>Relevance to PyMC community</b> </br>+        This doesn't mean you do need to give a talk on PyMC3/4. But it does+        mean think about the diverse and expansive PyMC community and how your presentation+        would elevate them.+      </p>++      <p class=normal-text><b>We're not looking for typos!</b> </br>+        We recognize that folks come from a variety of backgrounds and English isn't+        always the first language. We will not be judging the proposals for typos+        and for accepted speakers who would like language assistance we'll have folks+        who can help.+      </p>++      <h3 class="first">What to include in a proposal</h3>+      <p>+        Submitting a proposal to PyMCon will require the follwing information about the+        speaker:+        <ul>+          <li><b>Contact email.</b> It will be confidential and only accessible to PyMCon+            organizers</li>+          <li><b>Name and short bio.</b> They will be included with the presentation when+            advertizing it and in the PyMC discourse async discussion. The bio should+          not be longer than 100 words.</li>+          <li><b>Prior speaking experience.</b> No prior speaking experience is required+          and it won't be considered when reviewing submissions. It will help us allocate+          resources during the content recording phase.</li>+          <li><b>GMT offset</b> It will not be taken into account when reviewing the+            proposal. It will be used to decide the final time and timetable of PyMCon</li>+          <li><b>Any extra comments.</b> PyMCon aims to be an inclusive conference and we+          are ready to cover any specific need we may have missed.</li>+        </ul>++        Moreover, all accepted speakers will be required to sign up at+        <a href="https://discourse.pymc.io/">PyMC discourse</a>.+      </p>+      <p>+      The proposal itself should include the following information:+        <ul>+          <li><b>Presentation format.</b> As explained above, one of Talk, Tutorial or+          Let's build a model</li>+          <li><b>Intended track.</b> One of "Conjugate Model" or "No U Turn Sampler"</li>+          <li><b>Short description</b> It will be used to advertize the talk in the website+            and let people know about the video and discourse async discussion. It does+            not need to describe the whole presentation and be oriented more as a teaser+            or an elevator pitch to get people interested in your presentation.+            To get the attention of potential viewers you can try to answer some of these+            questions "What common problems are+            mentioned in the talk? Will they learn any lifechanging trick? Why should+            someone whatch this presentation instead of reading PyMC docs or a Bayesian+            stats blog?"+          </li>+          <li><b>Abstract</b> The abstract should be a detailed description of what will+            be covered in the presentation. It should provide information about the+            audience: "What specific concepts will be needed to follow the presentation?+            Will libraries other than PyMC3 and its dependencies be used?" and a detailed+            outline of the presentation: its objective and key takeaways, and the general+            structure of the presentation. Include links to relevant source code, articles,+            videos or other information that add context to your proposal.+          </li>+        </ul>+      </p>++      <style>.centered {text-align: center;}</style>+      <div class="centered">+         <a href ="https://forms.gle/uHcTE53bpUYPHHJ79" class="btn btn-sm normal-text">Click here to submit</a>+      </div>+++      <div id="faq" class="section">+      <h2 class="first">How to submit FAQ</h2>+      <p>+      Here are some tips and tricks to maximize your chances of your proposal being+      accepted.+      </p>+      <h3 class="first">Increase your acceptance probability</h3>+      <p>+      Here are some tricks and best practices to get your proposal accepted.+      <ul>+        <li><b>Submit early.</b> Submissions can be modified up until the submission+          deadline.</li>+        <li><b>Identify your target audience.</b> Clearly identify who your target+          audience is, what background is required for attendees to benefit from your+          presentation, and what the key takeaways are.</li>+        <li><b>Get feedback</b>, especially from those in your target audience.</li>+      </ul>+      </p>+      <h3 class="first">What to avoid</h3>+      <ul>+        <li><b>Overly long proposals</b> Keep it simple, clear and focused. Good+          proposals provide the most important information within the brief summary.+          Abstracts of more than 400 words should be a warning.</li>+        <li><b>Disconnected from the PyMC community</b> While talking about other+          libraries, especially if similar to PyMC, is definitely interesting and they+          can be mentioned in the presentation, the talk should be interesting to the+          PyMC community.</li>+        <li><b>Sales pitch</b> We are a community of open source developers and users+          of open source scientific computing tools. You can reference your closed-source+          product or platform, but the audience will find the talk more interesting if+          they can try your techniques within the PyData ecosystem. Your problem+          definition, proposed techniques, broad issues you solved, and business domain+          might be interesting, but sales pitches and "how to use our product" talks+          are typically rejected.</li>+        <li><b>Repeated presentation</b> We have a strong preference for new material+          and fresh faces, and as such, if your talk is already available online it is+          unlikely to be accepted for the conference. If your PyMC related talk is already+          online, it is probably better to <a href="https://forms.gle/8P1pNdHPyTQqevWa9">contact us</a>+          and get it added to the+          <a href="https://docs.pymc.io/learn.html">PyMC3 docs</a></li>+      </ul>+      <p>+      The tips above were adapted from the PyData and JupyterCon resources. We also

Great resources

canyon289

comment created time in 19 hours

Pull request review commentpymc-devs/pymcon

Change cfp wording slightly

 <h2 class="first">Key Dates</h2>       <p>Deadline for CFP: September 4th, 2020. Anywhere on Earth.</p>       <p>Date of speaker content submission: TBD. Likely first week of October 2020.</p> -      <h2 class="first">Format</h2>+      <h2 class="first">Conference Summary</h2>       <p>       PyMCon 2020 is an asynchronous-first conference.-      All accepted speakers will submit a video or code ahead of time,-      which will be posted in a TBD place (probably YouTube).+      All accepted speakers will submit a video with their presentation ahead of time.       </p> -      <h2 class="first">What we are looking for</h2>       <p>-        We are looking for folks like you to share your cool tricks, best practices,-        and general knowledge with the Bayesian community.-        This conference will have two tracks,-        a "Conjugate Model" track for folks just getting started out,-        and a "No U turn Sampler" track for folks that are already tuned and well warmed up with Bayesian Methods.-        (Track names  and puns subject to change).+      We are looking for folks like you to share your cool tricks, best practices,+      general knowledge, or model build methods with the Bayesian community.+      Presentations should have some relevance to the PyMC community, more details on+      what we look for in a presentation and how to propose one can be found below.       </p>        <p>-          There are three formats we're looking for specifically:+      All presentations will be pre-recorded and will be shared on the PyMC discourse in+      late October for the async component. We are also planning a synchronous component+      for early November. Further details are below as well.       </p> -      <h3 class="first">Talks</h3>-      <p class=normal-text>-        Traditional talks are 30 to 40 minutes in length and should be pre-recorded.-        If accepted, speakers are asked to submit a video file that contains the recording of their talk,-        which will be uploaded and viewed prior to the conference.-        As pre-recorded videos, talks are expected to be polished and crisp.-        Slide contents and language should be professional and comprehendible.-        A successful talk does not have to be about a novel, cutting-edge technology topic but should be distinctive and have the ability to keep the attention of the audience.-        We will provide a platform for audience discussions and Q&A.-        Accepted speakers are asked to be online the day of for at least one session of Q&A to answer questions live, which is 20 minutes long;-        of course, they are free to participate in the discussions with the audience outside of this Q&A session as well.+      <p>+      This conference will have two tracks:+      <ul>+        <li>a "Conjugate Model" track for folks just getting started out,</li>+        <li>and a "No U Turn Sampler" track for folks that are already  warmed up with+          Bayesian Methods.</li>+      </ul> -      </p>+      First time speakers are welcomed and encouraged. Please feel free to reach+      out with questions about submitting a proposal, you can find us at the <a href="https://discourse.pymc.io/t/pymcon-2020-call-for-proposals-is-open/5567">PyMC discourse</a>.  </p> -      <h3 class="first">Tutorials</h3>-      <p class=normal-text>-        Tutorials are dedicated to introducing, promoting, and advancing specific techniques/practices in computational Bayesian statistics with PyMC.-        Each tutorial, also to be recorded, is one hour long and should cover a topic more in depth than a traditional talk.-        Tutorial facilitators are responsible for preparing interactive and carefully designed materials,-        including hands-on exercises that help reinforce the concepts discussed in their topics.-        We will provide the platform (most likely Slack) in which tutorial facilitators can communicate and share materials with their audience prior to the conference.-      </p>--      <h3 class="first">Let's Build a Model</h3>-      <p class=normal-text>-        We are excited to introduce a new conference talk format called Let’s Build a Model (LBAM).-        While sharing many common characteristics with tutorials,-        LBAM talks aim to showcase the exciting (and sometimes messy!) nature of Bayesian modeling.-        In a LBAM talk, the presenter should first establish a specific modeling goal and then proceed to build that Bayesian model from scratch using PyMC (e.g., in a Jupyter notebook).-        A LBAM talk is also a pre-recorded video and should be one hour long.-        We know Bayesian modeling is a considerably involved process and can therefore be daunting to new users.-        With LBAM talks, we aim to address this problem by encouraging presenters to be as thorough as possible,-        while making sure to include relevant “tricks of the trade” that they find useful in their own experience.-      </p>--      <h2 class="first">What we look for in a submission</h2>-      <p class = "normal-text">-        More to come+      <p>+      There are three presentation formats:+      <dl>+        <dt><a class="reference internal" href="#talks">Talks</a></dt>+        <dd>30-40 min video about PyMC tricks, best practices, related library, etc.</dd>+        <dt><a class="reference internal" href="#tutorials">Tutorials</a></dt>+        <dd>60 min video + engaging material diving into a spedific PyMC related topic.</dd>+        <dt><a class="reference internal" href="#lbam">Let's build a model</a></dt>+        <dd>60 min video documenting how to build an example model using PyMC.</dd>+      </dl>       </p> -      <h2 class="first">Format of conference</h2>+      <h2 class="first">Conference Specifics</h2>       <p class=normal-text>         PyMCon 2020 is an asynchronous-first conference,         that will include a both an async discussion and synchronous discussions.-        There are three primary components:+        All presentations have three primary components:            <ul>-            <li>A prerecorded talk, tutorial, or "Let's build a model"</li>+            <li>A prerecorded video</li>             <li>A 1-week forum discussion</li>             <li>A synchronous time for folks to meet!</li>           </ul>       </p>       <h3 class="first">Self-recording (T-3 Weeks prior to conference)</h3>       <p class=normal-text><b>Put on a shirt. Pants optional. Hit record </b> </br>-        You as a speaker will be giving a talk or tutorial as you would at any other conference,+        You as a speaker will be giving a presentation as you would at any other conference,         except that you will be recording it ahead of time.-        PyMCon will collect the recording and post them on online about a week prior to the conference day.+        PyMCon will collect the videos and post them on online about a week prior to the conference day.         </p>       <h3 class="first">Async Discussion (T-1 Week prior to conference)</h3>       <p class=normal-text><b>Put on a shirt. Pants optional. Answer questions on discourse </b> </br>-        All submissions will be posted onto the PyMC discourse so the community as a whole-        can engage, read, and talk, all at their own pace.-        As a speaker, this allows your submission to be seen by a much wider audience+        All presentations will be posted onto the PyMC discourse so the community as a whole+        can engage, read, and comment, all at their own pace.+        As a speaker, this allows your presentation to be seen by a much wider audience         than if just presented once and have a richer conversation with your viewers.       </p>        <h3 class="first">Synchronous Conference Day (T-0 Liftoff!)</h3>        <p class=normal-text><b>Dress your best and meet all the folks </b> </br>         This day will look more like the open source conferences you've loved in the past.-        As an attendee this day will consist of Lightning Talks, Birds of a Feather discussion-        sessions, and discussion sessions from speakers.-        As a speaker we'll ask that you be able to answer questions live for folks that are on the call.+        As an attendee this day will likely consist of Lightning Talks, Birds of a Feather discussion+        sessions, and discussion sessions from speakers. We'd like to have speaker available answer+        questions live for folks in sessions as well.         The exact timing is TBD, but we plan to find time zones that are convenient for everyone-        and may end up doing two synchronous sessions in the same calendar day-        to meet our global community's localities.+        and may end up doing two synchronous sessions in the same calendar day to meet our+        global community's localities.+      </p>+      <h2 class="first">Presentation formats</h2>+      <div id="talks" class="section">+      <h3 class="first">Talks</h3>+      <p class=normal-text>+        Talks will consist of a 30 to 40 minutes video. As pre-recorded videos, talks are+        expected to be polished and crisp.+      </p>+      <p>+        All the content shown in the video (slides, code, plots...) and language should+        be professional, comprehensible and follow PyMCon code of conduct.+        A successful talk does not have to be about a novel, cutting-edge technology+        topic but should be distinctive and have the ability to keep the attention of+        the audience. We will provide a platform for audience discussions and Q&A.+        Accepted speakers are asked to be online the day of for at least one session of+        Q&A to answer questions live, which is 20 minutes long;+        of course, they are free to participate in the discussions with the audience+        outside of this Q&A session as well.+      </p>+      </div>++      <div id="tutorials" class="section">+      <h3 class="first">Tutorials</h3>+      <p class=normal-text>+        Tutorials are dedicated to introducing, promoting, and advancing specific+        techniques/practices in computational Bayesian statistics with PyMC. They should+        cover a topic more in depth than a traditional talk.+        Tutorials will consist of a 60 minutes video and extra material for attendees to+        engage and experiment with the contents of the tutorial.+      </p>+      <p>+        Tutorial facilitators are responsible for preparing interactive and carefully+        designed materials, including hands-on exercises that help reinforce the concepts+        discussed in their topics. We will provide the platform (most likely Slack) in+        which tutorial facilitators can communicate and share materials with their+        audience prior to the conference.+      </p>+      </div>++      <div id="lbam" class="section">+      <h3 class="first">Let's Build a Model</h3>+      <p class=normal-text>+        We are excited to introduce a new conference presentation format called "Let’s+        Build a Model" (LBAM). While sharing some characteristics with tutorials,+        LBAM talks aim to showcase the exciting (and sometimes messy!) nature of+        Bayesian modeling.+      </p>+      <p>+        In a LBAM talk, the presenter should first establish a specific modeling goal+        and then proceed to build that Bayesian model from scratch using PyMC (e.g.,+        in a Jupyter notebook). Like tutorial, LBAM videos should be 60 minutes long.       </p>+      <p>+        We know Bayesian modeling is a considerably involved process and can therefore be daunting to new users.+        With LBAM talks, we aim to address this problem by encouraging speakers to be as thorough as possible,+        while making sure to include relevant “tricks of the trade” that they find useful in their own experience.+      </p>+      </div>++      <h2 class="first">What we are looking for in a proposal</h2>+      <p>+        So many are people are doing so many cools things we don't want to restrict ideas+        with a "strong prior". However we will consider proposals based on the following+        principles+      </p>++      <p class=normal-text><b>Originality</b> </br>+        Proposals should that originality in some dimension whether that be in+        presentation approach, visuals, math, whatever! Be creative and show it off!+        Proposals that are already publicly available or similar to published videos have+        a low probability of being accepted.+      </p>++      <p class=normal-text><b>Relevance to PyMC community</b> </br>+        This doesn't mean you do need to give a talk on PyMC3/4. But it does+        mean think about the diverse and expansive PyMC community and how your presentation+        would elevate them.+      </p>++      <p class=normal-text><b>We're not looking for typos!</b> </br>+        We recognize that folks come from a variety of backgrounds and English isn't+        always the first language. We will not be judging the proposals for typos+        and for accepted speakers who would like language assistance we'll have folks+        who can help.+      </p>++      <h3 class="first">What to include in a proposal</h3>+      <p>+        Submitting a proposal to PyMCon will require the follwing information about the+        speaker:+        <ul>+          <li><b>Contact email.</b> It will be confidential and only accessible to PyMCon+            organizers</li>+          <li><b>Name and short bio.</b> They will be included with the presentation when+            advertizing it and in the PyMC discourse async discussion. The bio should+          not be longer than 100 words.</li>+          <li><b>Prior speaking experience.</b> No prior speaking experience is required+          and it won't be considered when reviewing submissions. It will help us allocate+          resources during the content recording phase.</li>+          <li><b>GMT offset</b> It will not be taken into account when reviewing the+            proposal. It will be used to decide the final time and timetable of PyMCon</li>+          <li><b>Any extra comments.</b> PyMCon aims to be an inclusive conference and we+          are ready to cover any specific need we may have missed.</li>+        </ul>++        Moreover, all accepted speakers will be required to sign up at+        <a href="https://discourse.pymc.io/">PyMC discourse</a>.+      </p>+      <p>+      The proposal itself should include the following information:+        <ul>+          <li><b>Presentation format.</b> As explained above, one of Talk, Tutorial or+          Let's build a model</li>+          <li><b>Intended track.</b> One of "Conjugate Model" or "No U Turn Sampler"</li>+          <li><b>Short description</b> It will be used to advertize the talk in the website

This also is really good

canyon289

comment created time in 19 hours

Pull request review commentpymc-devs/pymcon

Change cfp wording slightly

 <h2 class="first">Key Dates</h2>       <p>Deadline for CFP: September 4th, 2020. Anywhere on Earth.</p>       <p>Date of speaker content submission: TBD. Likely first week of October 2020.</p> -      <h2 class="first">Format</h2>+      <h2 class="first">Conference Summary</h2>       <p>       PyMCon 2020 is an asynchronous-first conference.-      All accepted speakers will submit a video or code ahead of time,-      which will be posted in a TBD place (probably YouTube).+      All accepted speakers will submit a video with their presentation ahead of time.       </p> -      <h2 class="first">What we are looking for</h2>       <p>-        We are looking for folks like you to share your cool tricks, best practices,-        and general knowledge with the Bayesian community.-        This conference will have two tracks,-        a "Conjugate Model" track for folks just getting started out,-        and a "No U turn Sampler" track for folks that are already tuned and well warmed up with Bayesian Methods.-        (Track names  and puns subject to change).+      We are looking for folks like you to share your cool tricks, best practices,+      general knowledge, or model build methods with the Bayesian community.+      Presentations should have some relevance to the PyMC community, more details on+      what we look for in a presentation and how to propose one can be found below.       </p>        <p>-          There are three formats we're looking for specifically:+      All presentations will be pre-recorded and will be shared on the PyMC discourse in+      late October for the async component. We are also planning a synchronous component+      for early November. Further details are below as well.       </p> -      <h3 class="first">Talks</h3>-      <p class=normal-text>-        Traditional talks are 30 to 40 minutes in length and should be pre-recorded.-        If accepted, speakers are asked to submit a video file that contains the recording of their talk,-        which will be uploaded and viewed prior to the conference.-        As pre-recorded videos, talks are expected to be polished and crisp.-        Slide contents and language should be professional and comprehendible.-        A successful talk does not have to be about a novel, cutting-edge technology topic but should be distinctive and have the ability to keep the attention of the audience.-        We will provide a platform for audience discussions and Q&A.-        Accepted speakers are asked to be online the day of for at least one session of Q&A to answer questions live, which is 20 minutes long;-        of course, they are free to participate in the discussions with the audience outside of this Q&A session as well.+      <p>+      This conference will have two tracks:+      <ul>+        <li>a "Conjugate Model" track for folks just getting started out,</li>+        <li>and a "No U Turn Sampler" track for folks that are already  warmed up with+          Bayesian Methods.</li>+      </ul> -      </p>+      First time speakers are welcomed and encouraged. Please feel free to reach+      out with questions about submitting a proposal, you can find us at the <a href="https://discourse.pymc.io/t/pymcon-2020-call-for-proposals-is-open/5567">PyMC discourse</a>.  </p> -      <h3 class="first">Tutorials</h3>-      <p class=normal-text>-        Tutorials are dedicated to introducing, promoting, and advancing specific techniques/practices in computational Bayesian statistics with PyMC.-        Each tutorial, also to be recorded, is one hour long and should cover a topic more in depth than a traditional talk.-        Tutorial facilitators are responsible for preparing interactive and carefully designed materials,-        including hands-on exercises that help reinforce the concepts discussed in their topics.-        We will provide the platform (most likely Slack) in which tutorial facilitators can communicate and share materials with their audience prior to the conference.-      </p>--      <h3 class="first">Let's Build a Model</h3>-      <p class=normal-text>-        We are excited to introduce a new conference talk format called Let’s Build a Model (LBAM).-        While sharing many common characteristics with tutorials,-        LBAM talks aim to showcase the exciting (and sometimes messy!) nature of Bayesian modeling.-        In a LBAM talk, the presenter should first establish a specific modeling goal and then proceed to build that Bayesian model from scratch using PyMC (e.g., in a Jupyter notebook).-        A LBAM talk is also a pre-recorded video and should be one hour long.-        We know Bayesian modeling is a considerably involved process and can therefore be daunting to new users.-        With LBAM talks, we aim to address this problem by encouraging presenters to be as thorough as possible,-        while making sure to include relevant “tricks of the trade” that they find useful in their own experience.-      </p>--      <h2 class="first">What we look for in a submission</h2>-      <p class = "normal-text">-        More to come+      <p>+      There are three presentation formats:+      <dl>+        <dt><a class="reference internal" href="#talks">Talks</a></dt>+        <dd>30-40 min video about PyMC tricks, best practices, related library, etc.</dd>+        <dt><a class="reference internal" href="#tutorials">Tutorials</a></dt>+        <dd>60 min video + engaging material diving into a spedific PyMC related topic.</dd>+        <dt><a class="reference internal" href="#lbam">Let's build a model</a></dt>+        <dd>60 min video documenting how to build an example model using PyMC.</dd>+      </dl>       </p> -      <h2 class="first">Format of conference</h2>+      <h2 class="first">Conference Specifics</h2>       <p class=normal-text>         PyMCon 2020 is an asynchronous-first conference,         that will include a both an async discussion and synchronous discussions.-        There are three primary components:+        All presentations have three primary components:            <ul>-            <li>A prerecorded talk, tutorial, or "Let's build a model"</li>+            <li>A prerecorded video</li>             <li>A 1-week forum discussion</li>             <li>A synchronous time for folks to meet!</li>           </ul>       </p>       <h3 class="first">Self-recording (T-3 Weeks prior to conference)</h3>       <p class=normal-text><b>Put on a shirt. Pants optional. Hit record </b> </br>-        You as a speaker will be giving a talk or tutorial as you would at any other conference,+        You as a speaker will be giving a presentation as you would at any other conference,         except that you will be recording it ahead of time.-        PyMCon will collect the recording and post them on online about a week prior to the conference day.+        PyMCon will collect the videos and post them on online about a week prior to the conference day.         </p>       <h3 class="first">Async Discussion (T-1 Week prior to conference)</h3>       <p class=normal-text><b>Put on a shirt. Pants optional. Answer questions on discourse </b> </br>-        All submissions will be posted onto the PyMC discourse so the community as a whole-        can engage, read, and talk, all at their own pace.-        As a speaker, this allows your submission to be seen by a much wider audience+        All presentations will be posted onto the PyMC discourse so the community as a whole+        can engage, read, and comment, all at their own pace.+        As a speaker, this allows your presentation to be seen by a much wider audience         than if just presented once and have a richer conversation with your viewers.       </p>        <h3 class="first">Synchronous Conference Day (T-0 Liftoff!)</h3>        <p class=normal-text><b>Dress your best and meet all the folks </b> </br>         This day will look more like the open source conferences you've loved in the past.-        As an attendee this day will consist of Lightning Talks, Birds of a Feather discussion-        sessions, and discussion sessions from speakers.-        As a speaker we'll ask that you be able to answer questions live for folks that are on the call.+        As an attendee this day will likely consist of Lightning Talks, Birds of a Feather discussion+        sessions, and discussion sessions from speakers. We'd like to have speaker available answer+        questions live for folks in sessions as well.         The exact timing is TBD, but we plan to find time zones that are convenient for everyone-        and may end up doing two synchronous sessions in the same calendar day-        to meet our global community's localities.+        and may end up doing two synchronous sessions in the same calendar day to meet our+        global community's localities.+      </p>+      <h2 class="first">Presentation formats</h2>+      <div id="talks" class="section">+      <h3 class="first">Talks</h3>+      <p class=normal-text>+        Talks will consist of a 30 to 40 minutes video. As pre-recorded videos, talks are+        expected to be polished and crisp.+      </p>+      <p>+        All the content shown in the video (slides, code, plots...) and language should+        be professional, comprehensible and follow PyMCon code of conduct.+        A successful talk does not have to be about a novel, cutting-edge technology+        topic but should be distinctive and have the ability to keep the attention of+        the audience. We will provide a platform for audience discussions and Q&A.+        Accepted speakers are asked to be online the day of for at least one session of+        Q&A to answer questions live, which is 20 minutes long;+        of course, they are free to participate in the discussions with the audience+        outside of this Q&A session as well.+      </p>+      </div>++      <div id="tutorials" class="section">+      <h3 class="first">Tutorials</h3>+      <p class=normal-text>+        Tutorials are dedicated to introducing, promoting, and advancing specific+        techniques/practices in computational Bayesian statistics with PyMC. They should+        cover a topic more in depth than a traditional talk.+        Tutorials will consist of a 60 minutes video and extra material for attendees to+        engage and experiment with the contents of the tutorial.+      </p>+      <p>+        Tutorial facilitators are responsible for preparing interactive and carefully+        designed materials, including hands-on exercises that help reinforce the concepts+        discussed in their topics. We will provide the platform (most likely Slack) in+        which tutorial facilitators can communicate and share materials with their+        audience prior to the conference.+      </p>+      </div>++      <div id="lbam" class="section">+      <h3 class="first">Let's Build a Model</h3>+      <p class=normal-text>+        We are excited to introduce a new conference presentation format called "Let’s+        Build a Model" (LBAM). While sharing some characteristics with tutorials,+        LBAM talks aim to showcase the exciting (and sometimes messy!) nature of+        Bayesian modeling.+      </p>+      <p>+        In a LBAM talk, the presenter should first establish a specific modeling goal

This is great instruction

canyon289

comment created time in 19 hours

Pull request review commentpymc-devs/pymcon

Change cfp wording slightly

 <h2 class="first">Key Dates</h2>       <p>Deadline for CFP: September 4th, 2020. Anywhere on Earth.</p>       <p>Date of speaker content submission: TBD. Likely first week of October 2020.</p> -      <h2 class="first">Format</h2>+      <h2 class="first">Conference Summary</h2>       <p>       PyMCon 2020 is an asynchronous-first conference.-      All accepted speakers will submit a video or code ahead of time,-      which will be posted in a TBD place (probably YouTube).+      All accepted speakers will submit a video with their presentation ahead of time.       </p> -      <h2 class="first">What we are looking for</h2>       <p>-        We are looking for folks like you to share your cool tricks, best practices,-        and general knowledge with the Bayesian community.-        This conference will have two tracks,-        a "Conjugate Model" track for folks just getting started out,-        and a "No U turn Sampler" track for folks that are already tuned and well warmed up with Bayesian Methods.-        (Track names  and puns subject to change).+      We are looking for folks like you to share your cool tricks, best practices,+      general knowledge, or model build methods with the Bayesian community.+      Presentations should have some relevance to the PyMC community, more details on+      what we look for in a presentation and how to propose one can be found below.       </p>        <p>-          There are three formats we're looking for specifically:+      All presentations will be pre-recorded and will be shared on the PyMC discourse in+      late October for the async component. We are also planning a synchronous component+      for early November. Further details are below as well.       </p> -      <h3 class="first">Talks</h3>-      <p class=normal-text>-        Traditional talks are 30 to 40 minutes in length and should be pre-recorded.-        If accepted, speakers are asked to submit a video file that contains the recording of their talk,-        which will be uploaded and viewed prior to the conference.-        As pre-recorded videos, talks are expected to be polished and crisp.-        Slide contents and language should be professional and comprehendible.-        A successful talk does not have to be about a novel, cutting-edge technology topic but should be distinctive and have the ability to keep the attention of the audience.-        We will provide a platform for audience discussions and Q&A.-        Accepted speakers are asked to be online the day of for at least one session of Q&A to answer questions live, which is 20 minutes long;-        of course, they are free to participate in the discussions with the audience outside of this Q&A session as well.+      <p>+      This conference will have two tracks:+      <ul>+        <li>a "Conjugate Model" track for folks just getting started out,</li>+        <li>and a "No U Turn Sampler" track for folks that are already  warmed up with+          Bayesian Methods.</li>+      </ul> -      </p>+      First time speakers are welcomed and encouraged. Please feel free to reach+      out with questions about submitting a proposal, you can find us at the <a href="https://discourse.pymc.io/t/pymcon-2020-call-for-proposals-is-open/5567">PyMC discourse</a>.  </p> -      <h3 class="first">Tutorials</h3>-      <p class=normal-text>-        Tutorials are dedicated to introducing, promoting, and advancing specific techniques/practices in computational Bayesian statistics with PyMC.-        Each tutorial, also to be recorded, is one hour long and should cover a topic more in depth than a traditional talk.-        Tutorial facilitators are responsible for preparing interactive and carefully designed materials,-        including hands-on exercises that help reinforce the concepts discussed in their topics.-        We will provide the platform (most likely Slack) in which tutorial facilitators can communicate and share materials with their audience prior to the conference.-      </p>--      <h3 class="first">Let's Build a Model</h3>-      <p class=normal-text>-        We are excited to introduce a new conference talk format called Let’s Build a Model (LBAM).-        While sharing many common characteristics with tutorials,-        LBAM talks aim to showcase the exciting (and sometimes messy!) nature of Bayesian modeling.-        In a LBAM talk, the presenter should first establish a specific modeling goal and then proceed to build that Bayesian model from scratch using PyMC (e.g., in a Jupyter notebook).-        A LBAM talk is also a pre-recorded video and should be one hour long.-        We know Bayesian modeling is a considerably involved process and can therefore be daunting to new users.-        With LBAM talks, we aim to address this problem by encouraging presenters to be as thorough as possible,-        while making sure to include relevant “tricks of the trade” that they find useful in their own experience.-      </p>--      <h2 class="first">What we look for in a submission</h2>-      <p class = "normal-text">-        More to come+      <p>+      There are three presentation formats:+      <dl>+        <dt><a class="reference internal" href="#talks">Talks</a></dt>+        <dd>30-40 min video about PyMC tricks, best practices, related library, etc.</dd>+        <dt><a class="reference internal" href="#tutorials">Tutorials</a></dt>+        <dd>60 min video + engaging material diving into a spedific PyMC related topic.</dd>+        <dt><a class="reference internal" href="#lbam">Let's build a model</a></dt>+        <dd>60 min video documenting how to build an example model using PyMC.</dd>+      </dl>       </p> -      <h2 class="first">Format of conference</h2>+      <h2 class="first">Conference Specifics</h2>       <p class=normal-text>         PyMCon 2020 is an asynchronous-first conference,         that will include a both an async discussion and synchronous discussions.-        There are three primary components:+        All presentations have three primary components:            <ul>-            <li>A prerecorded talk, tutorial, or "Let's build a model"</li>+            <li>A prerecorded video</li>             <li>A 1-week forum discussion</li>             <li>A synchronous time for folks to meet!</li>           </ul>       </p>       <h3 class="first">Self-recording (T-3 Weeks prior to conference)</h3>       <p class=normal-text><b>Put on a shirt. Pants optional. Hit record </b> </br>-        You as a speaker will be giving a talk or tutorial as you would at any other conference,+        You as a speaker will be giving a presentation as you would at any other conference,         except that you will be recording it ahead of time.-        PyMCon will collect the recording and post them on online about a week prior to the conference day.+        PyMCon will collect the videos and post them on online about a week prior to the conference day.         </p>       <h3 class="first">Async Discussion (T-1 Week prior to conference)</h3>       <p class=normal-text><b>Put on a shirt. Pants optional. Answer questions on discourse </b> </br>-        All submissions will be posted onto the PyMC discourse so the community as a whole-        can engage, read, and talk, all at their own pace.-        As a speaker, this allows your submission to be seen by a much wider audience+        All presentations will be posted onto the PyMC discourse so the community as a whole+        can engage, read, and comment, all at their own pace.+        As a speaker, this allows your presentation to be seen by a much wider audience         than if just presented once and have a richer conversation with your viewers.       </p>        <h3 class="first">Synchronous Conference Day (T-0 Liftoff!)</h3>        <p class=normal-text><b>Dress your best and meet all the folks </b> </br>         This day will look more like the open source conferences you've loved in the past.-        As an attendee this day will consist of Lightning Talks, Birds of a Feather discussion-        sessions, and discussion sessions from speakers.-        As a speaker we'll ask that you be able to answer questions live for folks that are on the call.+        As an attendee this day will likely consist of Lightning Talks, Birds of a Feather discussion+        sessions, and discussion sessions from speakers. We'd like to have speaker available answer+        questions live for folks in sessions as well.         The exact timing is TBD, but we plan to find time zones that are convenient for everyone-        and may end up doing two synchronous sessions in the same calendar day-        to meet our global community's localities.+        and may end up doing two synchronous sessions in the same calendar day to meet our+        global community's localities.+      </p>+      <h2 class="first">Presentation formats</h2>+      <div id="talks" class="section">+      <h3 class="first">Talks</h3>+      <p class=normal-text>+        Talks will consist of a 30 to 40 minutes video. As pre-recorded videos, talks are+        expected to be polished and crisp.+      </p>+      <p>+        All the content shown in the video (slides, code, plots...) and language should+        be professional, comprehensible and follow PyMCon code of conduct.+        A successful talk does not have to be about a novel, cutting-edge technology+        topic but should be distinctive and have the ability to keep the attention of+        the audience. We will provide a platform for audience discussions and Q&A.+        Accepted speakers are asked to be online the day of for at least one session of+        Q&A to answer questions live, which is 20 minutes long;+        of course, they are free to participate in the discussions with the audience+        outside of this Q&A session as well.+      </p>+      </div>++      <div id="tutorials" class="section">+      <h3 class="first">Tutorials</h3>+      <p class=normal-text>+        Tutorials are dedicated to introducing, promoting, and advancing specific+        techniques/practices in computational Bayesian statistics with PyMC. They should+        cover a topic more in depth than a traditional talk.+        Tutorials will consist of a 60 minutes video and extra material for attendees to+        engage and experiment with the contents of the tutorial.+      </p>+      <p>+        Tutorial facilitators are responsible for preparing interactive and carefully+        designed materials, including hands-on exercises that help reinforce the concepts+        discussed in their topics. We will provide the platform (most likely Slack) in+        which tutorial facilitators can communicate and share materials with their+        audience prior to the conference.+      </p>+      </div>++      <div id="lbam" class="section">+      <h3 class="first">Let's Build a Model</h3>+      <p class=normal-text>+        We are excited to introduce a new conference presentation format called "Let’s+        Build a Model" (LBAM). While sharing some characteristics with tutorials,+        LBAM talks aim to showcase the exciting (and sometimes messy!) nature of

Love the messy part

canyon289

comment created time in 19 hours

Pull request review commentpymc-devs/pymcon

Change cfp wording slightly

 <h2 class="first">Key Dates</h2>       <p>Deadline for CFP: September 4th, 2020. Anywhere on Earth.</p>       <p>Date of speaker content submission: TBD. Likely first week of October 2020.</p> -      <h2 class="first">Format</h2>+      <h2 class="first">Conference Summary</h2>       <p>       PyMCon 2020 is an asynchronous-first conference.-      All accepted speakers will submit a video or code ahead of time,-      which will be posted in a TBD place (probably YouTube).+      All accepted speakers will submit a video with their presentation ahead of time.       </p> -      <h2 class="first">What we are looking for</h2>       <p>-        We are looking for folks like you to share your cool tricks, best practices,-        and general knowledge with the Bayesian community.-        This conference will have two tracks,-        a "Conjugate Model" track for folks just getting started out,-        and a "No U turn Sampler" track for folks that are already tuned and well warmed up with Bayesian Methods.-        (Track names  and puns subject to change).+      We are looking for folks like you to share your cool tricks, best practices,+      general knowledge, or model build methods with the Bayesian community.+      Presentations should have some relevance to the PyMC community, more details on+      what we look for in a presentation and how to propose one can be found below.       </p>        <p>-          There are three formats we're looking for specifically:+      All presentations will be pre-recorded and will be shared on the PyMC discourse in+      late October for the async component. We are also planning a synchronous component+      for early November. Further details are below as well.       </p> -      <h3 class="first">Talks</h3>-      <p class=normal-text>-        Traditional talks are 30 to 40 minutes in length and should be pre-recorded.-        If accepted, speakers are asked to submit a video file that contains the recording of their talk,-        which will be uploaded and viewed prior to the conference.-        As pre-recorded videos, talks are expected to be polished and crisp.-        Slide contents and language should be professional and comprehendible.-        A successful talk does not have to be about a novel, cutting-edge technology topic but should be distinctive and have the ability to keep the attention of the audience.-        We will provide a platform for audience discussions and Q&A.-        Accepted speakers are asked to be online the day of for at least one session of Q&A to answer questions live, which is 20 minutes long;-        of course, they are free to participate in the discussions with the audience outside of this Q&A session as well.+      <p>+      This conference will have two tracks:+      <ul>+        <li>a "Conjugate Model" track for folks just getting started out,</li>+        <li>and a "No U Turn Sampler" track for folks that are already  warmed up with+          Bayesian Methods.</li>+      </ul> -      </p>+      First time speakers are welcomed and encouraged. Please feel free to reach+      out with questions about submitting a proposal, you can find us at the <a href="https://discourse.pymc.io/t/pymcon-2020-call-for-proposals-is-open/5567">PyMC discourse</a>.  </p> -      <h3 class="first">Tutorials</h3>-      <p class=normal-text>-        Tutorials are dedicated to introducing, promoting, and advancing specific techniques/practices in computational Bayesian statistics with PyMC.-        Each tutorial, also to be recorded, is one hour long and should cover a topic more in depth than a traditional talk.-        Tutorial facilitators are responsible for preparing interactive and carefully designed materials,-        including hands-on exercises that help reinforce the concepts discussed in their topics.-        We will provide the platform (most likely Slack) in which tutorial facilitators can communicate and share materials with their audience prior to the conference.-      </p>--      <h3 class="first">Let's Build a Model</h3>-      <p class=normal-text>-        We are excited to introduce a new conference talk format called Let’s Build a Model (LBAM).-        While sharing many common characteristics with tutorials,-        LBAM talks aim to showcase the exciting (and sometimes messy!) nature of Bayesian modeling.-        In a LBAM talk, the presenter should first establish a specific modeling goal and then proceed to build that Bayesian model from scratch using PyMC (e.g., in a Jupyter notebook).-        A LBAM talk is also a pre-recorded video and should be one hour long.-        We know Bayesian modeling is a considerably involved process and can therefore be daunting to new users.-        With LBAM talks, we aim to address this problem by encouraging presenters to be as thorough as possible,-        while making sure to include relevant “tricks of the trade” that they find useful in their own experience.-      </p>--      <h2 class="first">What we look for in a submission</h2>-      <p class = "normal-text">-        More to come+      <p>+      There are three presentation formats:+      <dl>+        <dt><a class="reference internal" href="#talks">Talks</a></dt>+        <dd>30-40 min video about PyMC tricks, best practices, related library, etc.</dd>+        <dt><a class="reference internal" href="#tutorials">Tutorials</a></dt>+        <dd>60 min video + engaging material diving into a spedific PyMC related topic.</dd>+        <dt><a class="reference internal" href="#lbam">Let's build a model</a></dt>+        <dd>60 min video documenting how to build an example model using PyMC.</dd>+      </dl>       </p> -      <h2 class="first">Format of conference</h2>+      <h2 class="first">Conference Specifics</h2>       <p class=normal-text>         PyMCon 2020 is an asynchronous-first conference,         that will include a both an async discussion and synchronous discussions.-        There are three primary components:+        All presentations have three primary components:            <ul>-            <li>A prerecorded talk, tutorial, or "Let's build a model"</li>+            <li>A prerecorded video</li>             <li>A 1-week forum discussion</li>             <li>A synchronous time for folks to meet!</li>           </ul>       </p>       <h3 class="first">Self-recording (T-3 Weeks prior to conference)</h3>       <p class=normal-text><b>Put on a shirt. Pants optional. Hit record </b> </br>-        You as a speaker will be giving a talk or tutorial as you would at any other conference,+        You as a speaker will be giving a presentation as you would at any other conference,         except that you will be recording it ahead of time.-        PyMCon will collect the recording and post them on online about a week prior to the conference day.+        PyMCon will collect the videos and post them on online about a week prior to the conference day.         </p>       <h3 class="first">Async Discussion (T-1 Week prior to conference)</h3>       <p class=normal-text><b>Put on a shirt. Pants optional. Answer questions on discourse </b> </br>-        All submissions will be posted onto the PyMC discourse so the community as a whole-        can engage, read, and talk, all at their own pace.-        As a speaker, this allows your submission to be seen by a much wider audience+        All presentations will be posted onto the PyMC discourse so the community as a whole+        can engage, read, and comment, all at their own pace.+        As a speaker, this allows your presentation to be seen by a much wider audience         than if just presented once and have a richer conversation with your viewers.       </p>        <h3 class="first">Synchronous Conference Day (T-0 Liftoff!)</h3>        <p class=normal-text><b>Dress your best and meet all the folks </b> </br>         This day will look more like the open source conferences you've loved in the past.-        As an attendee this day will consist of Lightning Talks, Birds of a Feather discussion-        sessions, and discussion sessions from speakers.-        As a speaker we'll ask that you be able to answer questions live for folks that are on the call.+        As an attendee this day will likely consist of Lightning Talks, Birds of a Feather discussion+        sessions, and discussion sessions from speakers. We'd like to have speaker available answer+        questions live for folks in sessions as well.         The exact timing is TBD, but we plan to find time zones that are convenient for everyone-        and may end up doing two synchronous sessions in the same calendar day-        to meet our global community's localities.+        and may end up doing two synchronous sessions in the same calendar day to meet our+        global community's localities.+      </p>+      <h2 class="first">Presentation formats</h2>+      <div id="talks" class="section">+      <h3 class="first">Talks</h3>+      <p class=normal-text>+        Talks will consist of a 30 to 40 minutes video. As pre-recorded videos, talks are+        expected to be polished and crisp.+      </p>+      <p>+        All the content shown in the video (slides, code, plots...) and language should+        be professional, comprehensible and follow PyMCon code of conduct.+        A successful talk does not have to be about a novel, cutting-edge technology+        topic but should be distinctive and have the ability to keep the attention of+        the audience. We will provide a platform for audience discussions and Q&A.+        Accepted speakers are asked to be online the day of for at least one session of+        Q&A to answer questions live, which is 20 minutes long;+        of course, they are free to participate in the discussions with the audience+        outside of this Q&A session as well.+      </p>+      </div>++      <div id="tutorials" class="section">+      <h3 class="first">Tutorials</h3>+      <p class=normal-text>+        Tutorials are dedicated to introducing, promoting, and advancing specific+        techniques/practices in computational Bayesian statistics with PyMC. They should+        cover a topic more in depth than a traditional talk.+        Tutorials will consist of a 60 minutes video and extra material for attendees to+        engage and experiment with the contents of the tutorial.+      </p>+      <p>+        Tutorial facilitators are responsible for preparing interactive and carefully+        designed materials, including hands-on exercises that help reinforce the concepts+        discussed in their topics. We will provide the platform (most likely Slack) in

Im going to change this to discourse since we for sure are going to have that one where tutorial folks can interact with their attendees

canyon289

comment created time in 19 hours

Pull request review commentpymc-devs/pymcon

Change cfp wording slightly

 <h2 class="first">Key Dates</h2>       <p>Deadline for CFP: September 4th, 2020. Anywhere on Earth.</p>       <p>Date of speaker content submission: TBD. Likely first week of October 2020.</p> -      <h2 class="first">Format</h2>+      <h2 class="first">Conference Summary</h2>       <p>       PyMCon 2020 is an asynchronous-first conference.-      All accepted speakers will submit a video or code ahead of time,-      which will be posted in a TBD place (probably YouTube).+      All accepted speakers will submit a video with their presentation ahead of time.       </p> -      <h2 class="first">What we are looking for</h2>       <p>-        We are looking for folks like you to share your cool tricks, best practices,-        and general knowledge with the Bayesian community.-        This conference will have two tracks,-        a "Conjugate Model" track for folks just getting started out,-        and a "No U turn Sampler" track for folks that are already tuned and well warmed up with Bayesian Methods.-        (Track names  and puns subject to change).+      We are looking for folks like you to share your cool tricks, best practices,+      general knowledge, or model build methods with the Bayesian community.+      Presentations should have some relevance to the PyMC community, more details on+      what we look for in a presentation and how to propose one can be found below.       </p>        <p>-          There are three formats we're looking for specifically:+      All presentations will be pre-recorded and will be shared on the PyMC discourse in+      late October for the async component. We are also planning a synchronous component+      for early November. Further details are below as well.       </p> -      <h3 class="first">Talks</h3>-      <p class=normal-text>-        Traditional talks are 30 to 40 minutes in length and should be pre-recorded.-        If accepted, speakers are asked to submit a video file that contains the recording of their talk,-        which will be uploaded and viewed prior to the conference.-        As pre-recorded videos, talks are expected to be polished and crisp.-        Slide contents and language should be professional and comprehendible.-        A successful talk does not have to be about a novel, cutting-edge technology topic but should be distinctive and have the ability to keep the attention of the audience.-        We will provide a platform for audience discussions and Q&A.-        Accepted speakers are asked to be online the day of for at least one session of Q&A to answer questions live, which is 20 minutes long;-        of course, they are free to participate in the discussions with the audience outside of this Q&A session as well.+      <p>+      This conference will have two tracks:+      <ul>+        <li>a "Conjugate Model" track for folks just getting started out,</li>+        <li>and a "No U Turn Sampler" track for folks that are already  warmed up with

We probably shouldnt because you have to be really bayesian to get what it means and beginner and advanced are more straightforward haha

canyon289

comment created time in 19 hours

Pull request review commentpymc-devs/pymcon

Change cfp wording slightly

 <h2 class="first">Key Dates</h2>       <p>Deadline for CFP: September 4th, 2020. Anywhere on Earth.</p>       <p>Date of speaker content submission: TBD. Likely first week of October 2020.</p> -      <h2 class="first">Format</h2>+      <h2 class="first">Conference Summary</h2>       <p>       PyMCon 2020 is an asynchronous-first conference.-      All accepted speakers will submit a video or code ahead of time,-      which will be posted in a TBD place (probably YouTube).+      All accepted speakers will submit a video with their presentation ahead of time.       </p> -      <h2 class="first">What we are looking for</h2>       <p>-        We are looking for folks like you to share your cool tricks, best practices,-        and general knowledge with the Bayesian community.-        This conference will have two tracks,-        a "Conjugate Model" track for folks just getting started out,-        and a "No U turn Sampler" track for folks that are already tuned and well warmed up with Bayesian Methods.-        (Track names  and puns subject to change).+      We are looking for folks like you to share your cool tricks, best practices,+      general knowledge, or model build methods with the Bayesian community.+      Presentations should have some relevance to the PyMC community, more details on+      what we look for in a presentation and how to propose one can be found below.       </p>        <p>-          There are three formats we're looking for specifically:+      All presentations will be pre-recorded and will be shared on the PyMC discourse in+      late October for the async component. We are also planning a synchronous component+      for early November. Further details are below as well.       </p> -      <h3 class="first">Talks</h3>-      <p class=normal-text>-        Traditional talks are 30 to 40 minutes in length and should be pre-recorded.-        If accepted, speakers are asked to submit a video file that contains the recording of their talk,-        which will be uploaded and viewed prior to the conference.-        As pre-recorded videos, talks are expected to be polished and crisp.-        Slide contents and language should be professional and comprehendible.-        A successful talk does not have to be about a novel, cutting-edge technology topic but should be distinctive and have the ability to keep the attention of the audience.-        We will provide a platform for audience discussions and Q&A.-        Accepted speakers are asked to be online the day of for at least one session of Q&A to answer questions live, which is 20 minutes long;-        of course, they are free to participate in the discussions with the audience outside of this Q&A session as well.+      <p>+      This conference will have two tracks:+      <ul>+        <li>a "Conjugate Model" track for folks just getting started out,</li>+        <li>and a "No U Turn Sampler" track for folks that are already  warmed up with

I mostly made these as jokes and was assuming someone was going to delete them cause theyre not very good jokes. But if we want to double down we can haha

canyon289

comment created time in 19 hours

pull request commentpymc-devs/pymcon

Change cfp wording slightly

Will continue reviewing in next ~4 hours. So far looking good. Will keep reading and adding comments

canyon289

comment created time in a day

Pull request review commentpymc-devs/pymcon

Change cfp wording slightly

 <h2 class="first">Key Dates</h2>       <p>Deadline for CFP: September 4th, 2020. Anywhere on Earth.</p>       <p>Date of speaker content submission: TBD. Likely first week of October 2020.</p> -      <h2 class="first">Format</h2>+      <h2 class="first">Conference Summary</h2>       <p>       PyMCon 2020 is an asynchronous-first conference.-      All accepted speakers will submit a video or code ahead of time,-      which will be posted in a TBD place (probably YouTube).+      All accepted speakers will submit a video with their presentation ahead of time.       </p> -      <h2 class="first">What we are looking for</h2>       <p>-        We are looking for folks like you to share your cool tricks, best practices,-        and general knowledge with the Bayesian community.-        This conference will have two tracks,-        a "Conjugate Model" track for folks just getting started out,-        and a "No U turn Sampler" track for folks that are already tuned and well warmed up with Bayesian Methods.-        (Track names  and puns subject to change).+      We are looking for folks like you to share your cool tricks, best practices,+      general knowledge, or model build methods with the Bayesian community.+      Presentations should have some relevance to the PyMC community, more details on+      what we look for in a presentation and how to propose one can be found below.       </p>        <p>-          There are three formats we're looking for specifically:+      All presentations will be pre-recorded and will be shared on the PyMC discourse in+      late October for the async component. We are also planning a synchronous component+      for early November. Further details are below as well.       </p> -      <h3 class="first">Talks</h3>-      <p class=normal-text>-        Traditional talks are 30 to 40 minutes in length and should be pre-recorded.-        If accepted, speakers are asked to submit a video file that contains the recording of their talk,-        which will be uploaded and viewed prior to the conference.-        As pre-recorded videos, talks are expected to be polished and crisp.-        Slide contents and language should be professional and comprehendible.-        A successful talk does not have to be about a novel, cutting-edge technology topic but should be distinctive and have the ability to keep the attention of the audience.-        We will provide a platform for audience discussions and Q&A.-        Accepted speakers are asked to be online the day of for at least one session of Q&A to answer questions live, which is 20 minutes long;-        of course, they are free to participate in the discussions with the audience outside of this Q&A session as well.+      <p>+      This conference will have two tracks:+      <ul>+        <li>a "Conjugate Model" track for folks just getting started out,</li>+        <li>and a "No U Turn Sampler" track for folks that are already  warmed up with+          Bayesian Methods.</li>+      </ul> -      </p>+      First time speakers are welcomed and encouraged. Please feel free to reach+      out with questions about submitting a proposal, you can find us at the <a href="https://discourse.pymc.io/t/pymcon-2020-call-for-proposals-is-open/5567">PyMC discourse</a>.  </p> -      <h3 class="first">Tutorials</h3>-      <p class=normal-text>-        Tutorials are dedicated to introducing, promoting, and advancing specific techniques/practices in computational Bayesian statistics with PyMC.-        Each tutorial, also to be recorded, is one hour long and should cover a topic more in depth than a traditional talk.-        Tutorial facilitators are responsible for preparing interactive and carefully designed materials,-        including hands-on exercises that help reinforce the concepts discussed in their topics.-        We will provide the platform (most likely Slack) in which tutorial facilitators can communicate and share materials with their audience prior to the conference.-      </p>--      <h3 class="first">Let's Build a Model</h3>-      <p class=normal-text>-        We are excited to introduce a new conference talk format called Let’s Build a Model (LBAM).-        While sharing many common characteristics with tutorials,-        LBAM talks aim to showcase the exciting (and sometimes messy!) nature of Bayesian modeling.-        In a LBAM talk, the presenter should first establish a specific modeling goal and then proceed to build that Bayesian model from scratch using PyMC (e.g., in a Jupyter notebook).-        A LBAM talk is also a pre-recorded video and should be one hour long.-        We know Bayesian modeling is a considerably involved process and can therefore be daunting to new users.-        With LBAM talks, we aim to address this problem by encouraging presenters to be as thorough as possible,-        while making sure to include relevant “tricks of the trade” that they find useful in their own experience.-      </p>--      <h2 class="first">What we look for in a submission</h2>-      <p class = "normal-text">-        More to come+      <p>+      There are three presentation formats:+      <dl>+        <dt><a class="reference internal" href="#talks">Talks</a></dt>+        <dd>30-40 min video about PyMC tricks, best practices, related library, etc.</dd>+        <dt><a class="reference internal" href="#tutorials">Tutorials</a></dt>+        <dd>60 min video + engaging material diving into a spedific PyMC related topic.</dd>

Small typo, I can fix.

What do you think about adding ranges for the building example model as well. 30 mins to as long as you want?

canyon289

comment created time in a day

MemberEvent

pull request commentpymc-devs/pymcon

Change cfp wording slightly

Per slack conversation don't use the word submission but proposal to be consistent

canyon289

comment created time in a day

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 581e90510f7bbd3e284808114ceb8331a5c01d00

Update what we look for

view details

push time in a day

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 4171fbb1d38458611680c2d20662c4b5773a80d8

Update wording slightly

view details

push time in a day

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 9640d0135ddf9ea519830b7ab0e6d181d28a1de1

Consolidate sections

view details

push time in a day

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 626f4ca0a603e762529f1556f436b046d04a5878

Remove extra words

view details

push time in a day

PR opened pymc-devs/pymcon

Change cfp wording
+12 -8

0 comment

1 changed file

pr created time in a day

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 498cbb4626c315d224164317200f45712a2fe023

Change cfp wording

view details

push time in a day

create barnchpymc-devs/pymcon

branch : cfp_wording

created branch time in a day

Pull request review commentarviz-devs/arviz

[WIP] More docker fixes

 RUN find /opt/arviz/ -type f -print0 | xargs -0 dos2unix RUN rm -f arviz/tests/saved_models/*.pkl RUN find -type d -name __pycache__ -exec rm -rf {} + -#  Install editable using the setup.py+# Install editable using the setup.py RUN /bin/bash -c "source /root/.bashrc" && pip install -e .

Why do we need to install editable here each time the containe runs? We could do this earlier in the installation and it would still work?

canyon289

comment created time in 2 days

push eventarviz-devs/arviz

Brandon T. Willard

commit sha ccd8eb7e25b7a52dd3baecb4cca13456bed53d10

Fix bug in warning that raises TypeError (#1346) Co-authored-by: Brandon T. Willard <brandonwillard@users.noreply.github.com>

view details

push time in 2 days

PR merged arviz-devs/arviz

Fix bug in warning that raises TypeError

Description

This PR fixes a bug in a warning message that causes ArviZ to instead throw a TypeError.

Checklist

  • [x] Follows official PR format
  • [x] Code style correct (follows pylint and black guidelines)
+1 -1

1 comment

1 changed file

brandonwillard

pr closed time in 2 days

push eventcanyon289/arviz

Ravin Kumar

commit sha 9759f25d18494ed44a31808c38649a5f693a027d

Make change so i can comment

view details

push time in 2 days

pull request commentarviz-devs/arviz

[WIP] More docker fixes

This is the problem.

Last line should install arviz into the env, but apparently it installs it inside base. How do we activate env --> install to env with pip

Ok I try and fix this too before I sleep

canyon289

comment created time in 2 days

Pull request review commentarviz-devs/arviz

[WIP] More docker fixes

 RUN apt-get update && apt-get install -y git build-essential pandoc vim ffmpeg \  # Copy needed scripts COPY $SRC_DIR /opt/arviz/requirements*.txt-COPY $SRC_DIR /opt/arviz/scripts+COPY $SRC_DIR /opt/arviz

Fixed

canyon289

comment created time in 2 days

push eventcanyon289/arviz

Ravin Kumar

commit sha e0df4421be78cf3f811eead8db73cfeada1e8973

Fix scripts again

view details

push time in 2 days

Pull request review commentarviz-devs/arviz

[WIP] More docker fixes

 RUN apt-get update && apt-get install -y git build-essential pandoc vim ffmpeg \  # Copy needed scripts COPY $SRC_DIR /opt/arviz/requirements*.txt-COPY $SRC_DIR /opt/arviz/scripts+COPY $SRC_DIR /opt/arviz

ah i see. Ok let me try and figure this out

canyon289

comment created time in 2 days

push eventcanyon289/arviz

Ravin Kumar

commit sha 572c4c67abc8c5cbbf574b38bcf2874c316dc792

Fix setuptools problem

view details

push time in 2 days

pull request commentarviz-devs/arviz

[WIP] More docker fixes

Alright well docker seems fixed. Now just our doc builds are broken because were missing a plot image

canyon289

comment created time in 2 days

PR opened arviz-devs/arviz

[WIP] More docker fixes
+1 -1

0 comment

1 changed file

pr created time in 2 days

create barnchcanyon289/arviz

branch : more_docker_fixes

created branch time in 2 days

push eventarviz-devs/arviz

Ari Hartikainen

commit sha 4f9736bfed105cd36d014e2169291ff74d04fc85

Update Docker (#1344) * improve docker interface * source bashrc Co-authored-by: ahartikainen <ahartikainen@github.com>

view details

push time in 2 days

PR merged arviz-devs/arviz

Update Docker

Add .dockerignore Install local ArviZ Update default python

+30 -16

1 comment

4 changed files

ahartikainen

pr closed time in 2 days

push eventpymc-devs/pymcon

Fernando Irarrazaval

commit sha d0e3c0acc4c23ae298e7290b70a66258caada985

Changed 'Give a talk' to 'Talk at PyMCon'; Updated homepage button margins

view details

Fernando Irarrazaval

commit sha 9953bb3a13a0d8e6e747f59e8f0bd23daea8e8c8

Added favicon using PyMC logo

view details

Fernando Irarrazaval

commit sha 46fbd716389eed880200bcff157c57efc02d6b27

Updated button text

view details

Ravin Kumar

commit sha 15e2f58af1c3d74e86db93b466ade4e9b960714c

Merge pull request #36 from cuchoi/homepage-buttons-2 Changed 'Give a talk' to 'Submit a proposal'; Added favicon

view details

push time in 2 days

PR merged pymc-devs/pymcon

Changed 'Give a talk' to 'Submit a proposal'; Added favicon

Favicon:

image

Updated "Give a talk" to "Submit a proposal" as discussed in this PR

image

+6 -6

0 comment

3 changed files

cuchoi

pr closed time in 2 days

issue commentbambinos/bambi

Revisit Automatic Priors in Bambi and possibly improve automatic priors

Likewise. It helps tremendously to have this historical context.

canyon289

comment created time in 2 days

Pull request review commentpymc-devs/pymcon

Changed 'Give a talk' to 'Talk at PyMCon'; Added favicon

                 <div class="intro-lead-in">An asynchronous-first virtual conference for the Bayesian community</div>                 <div class="intro-lead-in-sub">First Week of November (Tentative)</div>                 <div class="intro-lead-in-sub">Location: Global</div>-                <a href="./cfp" class="btn btn-info btn-lg btn-mr-10">Give a talk</a>+                <a href="./cfp" class="btn btn-info btn-lg btn-margins">Talk at PyMCon</a>

Can this line be changed to something like "Submit a proposal"? Talks are just one of the formats, we have tutorials and "Build a Model" as well!

cuchoi

comment created time in 2 days

PR closed arviz-devs/arviz

distplot will convert list into numpy array automatically...

Description

fixes #1277

Checklist

<!-- Feel free to remove check-list items aren't relevant to your change -->

  • [x] Follows official PR format
  • [ ] Includes a sample plot to visually illustrate the changes (only for plot-related functions)
  • [ ] New features are properly documented (with an example if appropriate)?
  • [ ] Includes new or updated tests to cover the new feature
  • [ ] Code style correct (follows pylint and black guidelines)
  • [x] Changes are listed in changelog

<!-- Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at

  • https://github.com/arviz-devs/arviz/blob/master/CONTRIBUTING.md
  • https://github.com/arviz-devs/arviz/blob/master/CODE_OF_CONDUCT.md

We understand that PRs can sometimes be overwhelming, especially as the reviews start coming in. Please let us know if the reviews are unclear or the recommended next step seems overly demanding, if you would like help in addressing a reviewer's comments, or if you have been waiting too long to hear back on your PR. -->

+3 -0

5 comments

1 changed file

Shreyaansh-darkside

pr closed time in 2 days

pull request commentarviz-devs/arviz

distplot will convert list into numpy array automatically...

@Shreyaansh-darkside This PR now has a merge conflict and is stale. I'm going to close

Shreyaansh-darkside

comment created time in 2 days

pull request commentarviz-devs/arviz

General fixes (isort, plotting)

I skimmed this, its hard to review it all but everything i saw made logical sense. Very inclined to just merge

ahartikainen

comment created time in 2 days

push eventpymc-devs/pymcon

Fernando Irarrazaval

commit sha 8a569791c7f1562286b65ad995126c225f26630f

Updated instructions for running Docker

view details

Fernando Irarrazaval

commit sha 3b353902562ed8e7321fc25be2a3d00312fd1037

Addde above the fold buttons; updated contact us section

view details

Ravin Kumar

commit sha 6890f0717f55acae10fde7cb6b0d8eab75275f5f

Merge pull request #34 from cuchoi/homepage-buttons Added tagline and buttons to the above the fold content; Modified the Contact Us section

view details

push time in 3 days

PR merged pymc-devs/pymcon

Added tagline and buttons to the above the fold content; Modified the Contact Us section
  1. Added tagline and buttons to the above the fold content : image

  2. Added a link to a Google Form in the Contact Us section: image

  3. Also updated the instruction for running Docker and added a make command.

+40 -13

2 comments

5 changed files

cuchoi

pr closed time in 3 days

pull request commentpymc-devs/pymcon

Added tagline and buttons to the above the fold content; Modified the Contact Us section

Thanks! I think this will make the website easier to navigate

Given that we have 3 different types of content and one of them is called talk, I would use a different text for the "give a talk" button, for example "submit a proposal" or "speak at pymcon". Otherwise I would expect to go to a page specific for talks a la jupytercon

@cuchoi going to merge so we get this out there, but would you mind making this change in another PR? And if you can't drop a message in the marketing channel so someone else can pick up on it? Thanks a bunch for this contribution

cuchoi

comment created time in 3 days

issue openedarviz-devs/arviz

Doc builds are failing on master

Seems like something in khat bokeh is causing issues. Will look into it if no one beats me to it

image

https://dev.azure.com/ArviZ/ArviZ/_build/results?buildId=3176&view=logs&j=5e60a62b-366f-55f7-ec2d-5209191ccb17&t=d329c065-fdc0-50e4-eb39-ac3f74121b84&l=1099

created time in 3 days

Pull request review commentpymc-devs/pymcon

Added tagline and buttons to the above the fold content; Modified the Contact Us section

 serve: 	docker run -it -p 4000:4000 --rm --mount type=bind,source="$(PWD)",target=/srv/jekyll jekyll/jekyll:latest /bin/bash 	# docker run --mount type=bind,source="$(pwd)",target=/srv/jekyll/ --rm -it -p 4000:4000 -env JEKYLL_ENV=production jekyll/jekyll:latest /bin/bash +serve-locally:

Thanks, I got real lazy with this one so i appreciate you making this much nicer

cuchoi

comment created time in 5 days

pull request commentpymc-devs/pymc3

Fix ArviZ version on test environment

Reached out for help upgrading the default in default anaconda channel https://github.com/ContinuumIO/anaconda-issues/issues/11973

AlexAndorra

comment created time in 5 days

issue openedContinuumIO/anaconda-issues

Could use help updating PyMC and ArviZ in default channel

<!-- Thanks for opening an issue! Please fill out the following template in full.

A few things to keep in mind:

  • This issue tracker is for issues with installing Anaconda or Miniconda or with packages built by Anaconda, Inc. like Anaconda Navigator. It is also a place to request packages or other enhancements of the Anaconda Distribution.

  • For conda issues, you should open an issue at https://github.com/conda/conda/issues

  • For conda-build issues, you should open an issue at https://github.com/conda/conda-build

  • For an issue with a particular conda-forge package, you should open an issue on the corresponding feedstock: https://github.com/conda-forge -->

Actual Behavior

I'm a maintainer for PyMC and ArviZ and was wondering how to get help updating the packages in the default channel. We do know about conda-forge but being upfront we're debugging a really weird issue with conda installations, and subsequently realized we have no idea how to packages get updated in the default channel, and that updating them might fix the problem.

To be specific I could use help in two ways

  1. Understanding the correct way to get packages updated in the default channel (and how we can best help)
  2. Actually get the packages updated in the default channel

https://github.com/conda-forge/arviz-feedstock https://github.com/conda-forge/pymc3-feedstock

And up front thanks, Anaconda has been a great tool as an individual user but also as a maintainer so appreciate the effort ya'll put into this.

<!-- What actually happens? --> ArviZ v0.6.1 and PyMC 3.8 get installed

Expected Behavior

PyMC v3.9.2 and ArviZ v0.9.0 are installed

Steps to Reproduce

conda install -y arviz pymc3

Anaconda or Miniconda version:

conda 4.8.3

Operating System:

Ubuntu 20.04

conda list --show-channel-urls
# packages in environment at /home/canyon/miniconda3/envs/conda_test:
#
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                        main    defaults
arviz                     0.6.1                      py_0    defaults
binutils_impl_linux-64    2.31.1               h6176602_1    defaults
binutils_linux-64         2.31.1               h6176602_9    defaults
blas                      1.0                         mkl    defaults
bzip2                     1.0.8                h7b6447c_0    defaults
ca-certificates           2020.6.24                     0    defaults
certifi                   2020.6.20                py38_0    defaults
cftime                    1.2.1            py38heb32a55_0    defaults
curl                      7.71.1               hbc83047_1    defaults
cycler                    0.10.0                   py38_0    defaults
freetype                  2.10.2               h5ab3b9f_0    defaults
gcc_impl_linux-64         7.3.0                habb00fd_1    defaults
gcc_linux-64              7.3.0                h553295d_9    defaults
gxx_impl_linux-64         7.3.0                hdf63c60_1    defaults
gxx_linux-64              7.3.0                h553295d_9    defaults
h5py                      2.10.0           py38h7918eee_0    defaults
hdf4                      4.2.13               h3ca952b_2    defaults
hdf5                      1.10.4               hb1b8bf9_0    defaults
icu                       58.2                 he6710b0_3    defaults
intel-openmp              2020.1                      217    defaults
jpeg                      9b                   h024ee3a_2    defaults
kiwisolver                1.2.0            py38hfd86e86_0    defaults
krb5                      1.18.2               h173b8e3_0    defaults
ld_impl_linux-64          2.33.1               h53a641e_7    defaults
libcurl                   7.71.1               h20c2e04_1    defaults
libedit                   3.1.20191231         h14c3975_1    defaults
libffi                    3.3                  he6710b0_2    defaults
libgcc-ng                 9.1.0                hdf63c60_0    defaults
libgfortran-ng            7.3.0                hdf63c60_0    defaults
libgpuarray               0.7.6                h14c3975_0    defaults
libnetcdf                 4.7.3                hb80b6cc_0    defaults
libpng                    1.6.37               hbc83047_0    defaults
libssh2                   1.9.0                h1ba5d50_1    defaults
libstdcxx-ng              9.1.0                hdf63c60_0    defaults
mako                      1.1.3                      py_0    defaults
markupsafe                1.1.1            py38h7b6447c_0    defaults
matplotlib-base           3.2.2            py38hef1b27d_0    defaults
mkl                       2020.1                      217    defaults
mkl-service               2.3.0            py38he904b0f_0    defaults
mkl_fft                   1.1.0            py38h23d657b_0    defaults
mkl_random                1.1.1            py38h0573a6f_0    defaults
ncurses                   6.2                  he6710b0_1    defaults
netcdf4                   1.5.3            py38hbf33ddf_0    defaults
numpy                     1.19.1           py38hbc911f0_0    defaults
numpy-base                1.19.1           py38hfa32c7d_0    defaults
openssl                   1.1.1g               h7b6447c_0    defaults
packaging                 20.4                       py_0    defaults
pandas                    1.0.5            py38h0573a6f_0    defaults
patsy                     0.5.1                    py38_0    defaults
pip                       20.1.1                   py38_1    defaults
pygpu                     0.7.6            py38heb32a55_0    defaults
pymc3                     3.8                        py_0    defaults
pyparsing                 2.4.7                      py_0    defaults
python                    3.8.5                hcff3b4d_0    defaults
python-dateutil           2.8.1                      py_0    defaults
pytz                      2020.1                     py_0    defaults
readline                  8.0                  h7b6447c_0    defaults
scipy                     1.5.0            py38h0b6359f_0    defaults
setuptools                49.2.0                   py38_0    defaults
six                       1.15.0                     py_0    defaults
sqlite                    3.32.3               h62c20be_0    defaults
theano                    1.0.4            py38hfd86e86_0    defaults
tk                        8.6.10               hbc83047_0    defaults
tornado                   6.0.4            py38h7b6447c_1    defaults
tqdm                      4.47.0                     py_0    defaults
wheel                     0.34.2                   py38_0    defaults
xarray                    0.16.0                     py_0    defaults
xz                        5.2.5                h7b6447c_0    defaults
zlib                      1.2.11               h7b6447c_3    defaults

</details>

channels_logs.txt install_logs.txt

created time in 5 days

push eventpymc-devs/pymcon

Colin

commit sha 76b861f159f56cfcbf70062fe8c18c0da2a438e4

Fix colin Just get rid of colon, keep colin.

view details

Ravin Kumar

commit sha ab650aa9a7067214d9e4ffeb63fd568c7e1be9e4

Merge pull request #33 from pymc-devs/fix-colin Fix colin

view details

push time in 8 days

PR merged pymc-devs/pymcon

Fix colin

Just get rid of colon, keep colin.

+1 -1

0 comment

1 changed file

ColCarroll

pr closed time in 8 days

Pull request review commentpymc-devs/pymcon

Add Colin

 Sid was born in New Delhi and did a large share of his growing up in Melbourne. - title: Colin Carroll   name: Colin_Carroll   subtitle: Marketing Committee-  twitter:-  github:-  web:-  img: Pymc4.png-  thumbnail: Pymc4.png-  alt:-  topic:-  description:+  twitter: colindcarroll+  github: ColCarroll+  web: https://colindcarroll.com/+  img: colin.png+  thumbnail: colin.png+  alt: Picture of Colin+  topic: Colin is a contributor to PyMC3 and ArviZ. He is enthusiastic about open source science, data visualization, and his small dog Pete.+  description: Colin is a software engineer at Google Research Cambridge. He is interested in statistical computing and visualization, particularly as related to Bayesian methods. He is heavily involved in open source: a core contributor to PyMC3, a Python library for Bayesian modelling and inference, as well as ArviZ, a Bayesian visualization and diagnostic library. He received his PhD in mathematics from Rice University, where he researched geometric measure theory.

Yep Ill fix just got busy

ColCarroll

comment created time in 8 days

push eventpymc-devs/pymcon

Colin Carroll

commit sha c331dc543242bec0cc957cb8b4fe70588abf6536

Add colin

view details

Colin Carroll

commit sha abb690b19a48a0d51540a13e626c63a0ab8980a2

Put me where i belong

view details

Ravin Kumar

commit sha 5d051d476779081f4373b50d4ae5b53957f01d8d

Merge pull request #32 from pymc-devs/colin Add Colin

view details

push time in 8 days

PR merged pymc-devs/pymcon

Add Colin

image

+8 -8

0 comment

2 changed files

ColCarroll

pr closed time in 8 days

issue closedarviz-devs/arviz

Broken link in CONTRIBUTION.md

Describe the bug I noticed on step 4 the virtualenvs link is broken here: https://python-guide-pt-br.readthedocs.io/en/latest/dev/virtualenvs/

I believe this is the correct link: https://python-guide-cn.readthedocs.io/en/latest/dev/virtualenvs.html

With the go-ahead, I can put a quick PR in for that 🙂

closed time in 9 days

ari-hacks

issue commentarviz-devs/arviz

Broken link in CONTRIBUTION.md

Fixed. Thanks @ari-hacks!

ari-hacks

comment created time in 9 days

issue closedarviz-devs/arviz

How do you plot just some dimensions of a variable?

Short Description

e.g. az.plot_trace(fit, var_names=["z.2.73", "z.2.84"]) to get traceplots for two particular elements of a z matrix. I tried that and "z[2,73]" and couldn't get anything to work. "like" and "regex" filter_vars options also don't seem to know about the individual elements of z.

closed time in 9 days

seantalts

issue commentarviz-devs/arviz

How do you plot just some dimensions of a variable?

This issue looks resolved. If its not we can reopen

seantalts

comment created time in 9 days

issue closedarviz-devs/arviz

Pytest 6.0 seems to have broken pylint checks

The pytest devs suggested using pytest-pylint as a possible fix. If that doesn't work might just add a bunch of ignores everywhere

image

https://dev.azure.com/ArviZ/ArviZ/_build/results?buildId=3023&view=logs&j=e6a7683b-6131-58a8-ef68-5f3a9120796c&t=b52e026f-cc99-5e74-288f-e4d4024efc71

closed time in 9 days

canyon289

issue commentarviz-devs/arviz

Pytest 6.0 seems to have broken pylint checks

This has been fixed

canyon289

comment created time in 9 days

push eventarviz-devs/arviz

Ari Hartikainen

commit sha 4c9fb4f32af76a792c500fc76f8bfe4cbafcc9ec

Restructure plotting (#1312) * restructure autocorrplot * restructure bpvplot * restructure compareplot * restructure densityplot * restructure distcomparisonplot * restructure distplot * restructure elpdplot * restructure energyplot * restructure essplot * restructure forestplot * restructure hdiplot * restructure jointplot * restructure kdeplot * restructure khatplot * restructure loopitplot * restructure mcseplot * restructure pairplot * pairplot additions * restructure parallelplot * restructure posteriorplot * restructure ppcplot * restructure rankplot * restructure traceplot * restructure violinplot * fix bpvplot * fix distplot * fix elpdplot * fix energyplot * fix essplot * fix khatplot * fix hdiplot * fix loopitplot * fix pairplot * fix posteriorplot * fix traceplot * fix elpd * fix kde * fix khat * fix loopitplot * fix mcse * fix parallel * fix ppc * fix forest * fix trace * fix pair * Fix pairplot * add kw normalizer for mpl code * update changelog * _posterior to posterior * Fix import * updates based on the suggestions * define default colors * fix jointplot * fix jointplot * contourf kwargs * remove kw Co-authored-by: ahartikainen <ahartikainen@github.com>

view details

push time in 9 days

PR merged arviz-devs/arviz

Restructure plotting

Restructure plotting.

backend related defaults to backend code.

+1029 -928

11 comments

71 changed files

ahartikainen

pr closed time in 9 days

pull request commentarviz-devs/arviz

Restructure plotting

I dont want there to be a merge conflict so I'm going to merge this and keep reviewing. If stuff comes up I'll make an issue ticket

ahartikainen

comment created time in 9 days

push eventpymc-devs/pymcon

Quan Nguyen

commit sha f74bfe5fe42c47b95f28f5cc0bd5891b69eb405d

add last name to teams.yml

view details

Ravin Kumar

commit sha beb614873c3221fe5e7a14087dd1410b44a24d8f

Merge pull request #31 from KrisNguyen135/gh-pages add last name to teams.yml

view details

push time in 9 days

PR merged pymc-devs/pymcon

add last name to teams.yml
+2 -2

2 comments

1 changed file

KrisNguyen135

pr closed time in 9 days

pull request commentpymc-devs/pymcon

add quan's info to teams.yml

29 was merged. This is ready for rebase

KrisNguyen135

comment created time in 9 days

push eventpymc-devs/pymcon

Oriol (ZBook)

commit sha a0990e6641699252570ac5634582eee34c8e9711

fix couple issues in code of conduct

view details

Oriol (ZBook)

commit sha bee3e633a0952bc15b33b0496b5c0389cd3e21bd

improve lists

view details

Oriol (ZBook)

commit sha 77889eccfb6a166b9126a3d7552ba4c908ff418a

fix issue with speakers id now we can have a section for speakers and another for organizers

view details

Oriol (ZBook)

commit sha 08fd4df484b263647712629278812ea6c3c3a18c

add social media links to organizer profiles

view details

Ravin Kumar

commit sha 5bcb8e293eed1659b4feb6f63400cd9e00425a2d

Merge pull request #29 from OriolAbril/coc_and_fixes fix couple issues in code of conduct and extend profiles of organizers

view details

push time in 9 days

issue closedpymc-devs/pymcon

Add link to anonymyous form

See oriols comment linked below

Originally posted by @OriolAbril in https://github.com/pymc-devs/pymcon/pull/17/files

closed time in 9 days

canyon289

pull request commentarviz-devs/arviz

Restructure plotting

I'll take a look at this in next ~24 hours but dont let me block a merge either

ahartikainen

comment created time in 9 days

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 00e63188585da2e1e8f9c3ede69f8261970f3dc4

Fix pop up window not working

view details

Ravin Kumar

commit sha 3ec951c18f59e906b27ebd86d56840a9c21dff78

Fix image

view details

Ravin Kumar

commit sha 54b2d877ea2d4e44c3d588a8d86ce170fceae2e8

Make content submission more clear

view details

Ravin Kumar

commit sha 0f20636b694237385ae458eba2473c02c424a356

Add CFP button to homepage

view details

Ravin Kumar

commit sha ce6e2ede9dbdb3a8289dfa3230efa0dc7f5979d8

Merge pull request #28 from pymc-devs/even_more_fixes Even more fixes

view details

push time in 9 days

PR merged pymc-devs/pymcon

Even more fixes
  • Fix pop up
  • Fix PyMC4 image size
  • Add CFP button and change header verbiage a little
+5 -3

1 comment

3 changed files

canyon289

pr closed time in 9 days

pull request commentpymc-devs/pymcon

Even more fixes

Self merging as our CFP is announced just now and we want things to be shiny :)

canyon289

comment created time in 9 days

PR opened pymc-devs/pymcon

Even more fixes
  • Fix pop up
  • Fix PyMC4 image size
  • Add CFP button and change header verbiage a little
+5 -3

0 comment

3 changed files

pr created time in 9 days

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 0f20636b694237385ae458eba2473c02c424a356

Add CFP button to homepage

view details

push time in 9 days

create barnchpymc-devs/pymcon

branch : even_more_fixes

created branch time in 9 days

issue openedpymc-devs/pymcon

The team member pop up window is broken

Right now when you click on it nothing happens. I broke it in the PR below that Oriol noted

The other team members template in include also has to be added to 2017 home layout for the zooming in part to work

Originally posted by @OriolAbril in https://github.com/pymc-devs/pymcon/pull/26#issuecomment-667989888

created time in 9 days

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 88fbe7230d2ce3082914c3356a920267b9c77d0c

Fix chris's image

view details

Ravin Kumar

commit sha 2b8b4cb05ecd61659ea9080ccc8af45ba48c360d

Change pictures to rocket and rearrange

view details

Ravin Kumar

commit sha 18b97f4d3fdb07a62eae01031eb933a235785bdf

Fix volunter layout with rows

view details

Ravin Kumar

commit sha 749480d2e13f384bf25b3dc1e3386756767445fc

Update contact form and mission

view details

Ravin Kumar

commit sha 1d9c03c84c83b55a77567b3819974abb24f629a8

Merge branch 'gh-pages' into fixes

view details

Ravin Kumar

commit sha d8e52e1c722b5a56857ae4ad2a1a1c88b13b4bf1

Move hector back up now that the rows thing is figured out

view details

Ravin Kumar

commit sha 0d76c8e88f86365613e97de5c1cdc482f0d255bd

Merge pull request #26 from pymc-devs/fixes Additional fixes

view details

push time in 9 days

PR merged pymc-devs/pymcon

Additional fixes

Change TBD picture to something nicer Fix layout of team member pictures Remove contact form that doesnt work Add link to volunteer signup

+44 -70

3 comments

5 changed files

canyon289

pr closed time in 9 days

pull request commentpymc-devs/pymcon

Additional fixes

Merging so we can announce CFP. Will fix up Oriols comment later in follow up PR

canyon289

comment created time in 9 days

push eventpymc-devs/pymcon

Ravin Kumar

commit sha d8e52e1c722b5a56857ae4ad2a1a1c88b13b4bf1

Move hector back up now that the rows thing is figured out

view details

push time in 9 days

push eventpymc-devs/pymcon

Hector

commit sha 43e2889376b8e9aef8fc63de3586ce506bfb36ab

cfp proofing

view details

Hector

commit sha bdf31f987e645a4de68f786741daa404e21648fa

coc proofing

view details

Hector

commit sha 44556f7478016b597cd8ec82f87a86fafa55d3b0

mission proofing

view details

Hector

commit sha a3c662bb901519d278ee5f8248c8bfd4adfe5715

Update cfp formatting.

view details

Ravin Kumar

commit sha ac715d6a35a358959d3c18c8401bd424ec849794

Merge pull request #23 from hectormz/proofing Proofing changes

view details

Ravin Kumar

commit sha 1d9c03c84c83b55a77567b3819974abb24f629a8

Merge branch 'gh-pages' into fixes

view details

push time in 9 days

push eventpymc-devs/pymcon

Hector

commit sha 43e2889376b8e9aef8fc63de3586ce506bfb36ab

cfp proofing

view details

Hector

commit sha bdf31f987e645a4de68f786741daa404e21648fa

coc proofing

view details

Hector

commit sha 44556f7478016b597cd8ec82f87a86fafa55d3b0

mission proofing

view details

Hector

commit sha a3c662bb901519d278ee5f8248c8bfd4adfe5715

Update cfp formatting.

view details

Ravin Kumar

commit sha ac715d6a35a358959d3c18c8401bd424ec849794

Merge pull request #23 from hectormz/proofing Proofing changes

view details

push time in 9 days

pull request commentpymc-devs/pymcon

Additional fixes

Isnt the template right here in inclues here?

https://github.com/pymc-devs/pymcon/blob/gh-pages/_includes/2017_data/team_members_info.html

canyon289

comment created time in 9 days

PR opened pymc-devs/pymcon

Additional fixes

Change TBD picture to something nicer Fix layout of team member pictures Remove contact form that doesnt work Add link to volunteer signup

+54 -79

0 comment

5 changed files

pr created time in 10 days

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 749480d2e13f384bf25b3dc1e3386756767445fc

Update contact form and mission

view details

push time in 10 days

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 18b97f4d3fdb07a62eae01031eb933a235785bdf

Fix volunter layout with rows

view details

push time in 10 days

push eventpymc-devs/pymcon

Ravin Kumar

commit sha 2b8b4cb05ecd61659ea9080ccc8af45ba48c360d

Change pictures to rocket and rearrange

view details

push time in 10 days

create barnchpymc-devs/pymcon

branch : fixes

created branch time in 10 days

push eventpymc-devs/pymcon

Christopher Krapu

commit sha bab320c4d6c079681bffc8e5f94f4bbf39e9ee96

Added bio for Chris Krapu

view details

Ravin Kumar

commit sha 88730976a6bccab02501c00b4b54693f7bd043f6

Merge pull request #25 from ckrapu/patch-1 Added bio for Chris Krapu

view details

push time in 10 days

PR merged pymc-devs/pymcon

Added bio for Chris Krapu
+9 -6

0 comment

1 changed file

ckrapu

pr closed time in 10 days

push eventpymc-devs/pymcon

Hector

commit sha 2c00f7d3ce9d79408cf6add4623c074849b3dcc8

Add contact info

view details

Ravin Kumar

commit sha 3682fc32b36de51f0e4d34ee243bb980366ff931

Merge pull request #24 from hectormz/add-contact Add Hector contact info

view details

push time in 10 days

PR merged pymc-devs/pymcon

Add Hector contact info

I followed @OriolAbril 's pattern, let me know if I did something wrong.

+10 -7

0 comment

2 changed files

hectormz

pr closed time in 10 days

issue commentpymc-devs/pymcon

Add link to anonymyous form

We should let NumFOCUS review because they're neutral and not a part of this conference. If it's Thomas or I then the same issue could occur

canyon289

comment created time in 10 days

pull request commentpymc-devs/pymcon

Fixed mission formatting. Sentence structure

Thanks for this one as well

sidravi1

comment created time in 10 days

more