<?xml version='1.0' encoding='UTF-8'?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://sunpy.org/</id>
  <title>Blog - Posted in 2016</title>
  <updated>2026-04-16T16:25:23.305918+00:00</updated>
  <link href="https://sunpy.org/"/>
  <link href="https://sunpy.org/blog/2016/atom.xml" rel="self"/>
  <generator uri="https://ablog.readthedocs.io/" version="0.11.13">ABlog</generator>
  <entry>
    <id>https://sunpy.org/posts/2016/2016-05-31-SPD2016/</id>
    <title>SPD 2016</title>
    <updated>2016-05-31T00:00:00+00:00</updated>
    <author>
      <name>Steven Christe</name>
    </author>
    <content type="html">&lt;section id="spd-2016"&gt;

&lt;p&gt;You can find all of the material for the introductory sessions of scientific python and sunpy can be found &lt;a class="reference external" href="https://github.com/ehsteve/2016SPD-Python-SunPy"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;/section&gt;
</content>
    <link href="https://sunpy.org/posts/2016/2016-05-31-SPD2016/"/>
    <summary>You can find all of the material for the introductory sessions of scientific python and sunpy can be found here.</summary>
    <category term="conference" label="conference"/>
    <category term="outreach" label="outreach"/>
    <category term="talks" label="talks"/>
    <published>2016-05-31T00:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://sunpy.org/posts/2016/2016-05-26-SunPy-07/</id>
    <title>SunPy 0.7</title>
    <updated>2016-05-26T00:00:00+00:00</updated>
    <author>
      <name>Stuart Mumford</name>
    </author>
    <content type="html">&lt;section id="sunpy-0-7"&gt;

&lt;p&gt;SunPy 0.7 has arrived!
This release is a culmination of about 10 months of work from 27 different people.
This release brings many changes, the highlights are:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;p&gt;Python 3.4 and 3.5 support. This is the first version of SunPy to support
Python 3, we recommend that users start to consider moving to Python 3, please
report any issues you may have.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;New coordinate framework. The new &lt;code class="docutils literal notranslate"&gt;&lt;span class="pre"&gt;sunpy.coordinates&lt;/span&gt;&lt;/code&gt; module provides a
high-level interface to converting between different physical coordinate
systems such as Helioprojective and Heliographic.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;New &lt;code class="docutils literal notranslate"&gt;&lt;span class="pre"&gt;draw_rectangle&lt;/span&gt;&lt;/code&gt; and &lt;code class="docutils literal notranslate"&gt;&lt;span class="pre"&gt;draw_contours&lt;/span&gt;&lt;/code&gt; helpers for &lt;code class="docutils literal notranslate"&gt;&lt;span class="pre"&gt;Map&lt;/span&gt;&lt;/code&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Support for masks in SunPy &lt;code class="docutils literal notranslate"&gt;&lt;span class="pre"&gt;Map&lt;/span&gt;&lt;/code&gt; and &lt;code class="docutils literal notranslate"&gt;&lt;span class="pre"&gt;MapCube&lt;/span&gt;&lt;/code&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For this version of SunPy we have started building our &lt;a class="reference external" href="https://docs.conda.io/en/latest/"&gt;conda&lt;/a&gt; packages on the excellent &lt;a class="reference external" href="https://conda-forge.org/"&gt;conda forge&lt;/a&gt; service.
This means you need to add the conda-forge channel to your conda installation.
If you have never installed SunPy before we recommend you follow our &lt;a class="reference external" href="https://docs.sunpy.org/en/stable/tutorial/installation.html"&gt;installation instruction&lt;/a&gt;.
If you are upgrading from a previous release run the following two commands if you installed via &lt;code class="docutils literal notranslate"&gt;&lt;span class="pre"&gt;conda&lt;/span&gt;&lt;/code&gt;:&lt;/p&gt;
&lt;div class="highlight-default notranslate"&gt;&lt;div class="highlight"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="n"&gt;conda&lt;/span&gt; &lt;span class="n"&gt;config&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;add&lt;/span&gt; &lt;span class="n"&gt;channels&lt;/span&gt; &lt;span class="n"&gt;conda&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;forge&lt;/span&gt;
&lt;span class="n"&gt;conda&lt;/span&gt; &lt;span class="n"&gt;upgrade&lt;/span&gt; &lt;span class="n"&gt;sunpy&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;If you installed via &lt;code class="docutils literal notranslate"&gt;&lt;span class="pre"&gt;pip&lt;/span&gt;&lt;/code&gt; then you can upgrade with:&lt;/p&gt;
&lt;div class="highlight-default notranslate"&gt;&lt;div class="highlight"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="n"&gt;pip&lt;/span&gt; &lt;span class="n"&gt;install&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;U&lt;/span&gt; &lt;span class="n"&gt;sunpy&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;The following excellent people contributed to SunPy 0.7 (a * indicates their first contribution):&lt;/p&gt;
&lt;div class="highlight-default notranslate"&gt;&lt;div class="highlight"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="n"&gt;Stuart&lt;/span&gt; &lt;span class="n"&gt;Mumford&lt;/span&gt;
&lt;span class="n"&gt;Pritish&lt;/span&gt; &lt;span class="n"&gt;Chakraborty&lt;/span&gt;
&lt;span class="n"&gt;Steven&lt;/span&gt; &lt;span class="n"&gt;Christe&lt;/span&gt;
&lt;span class="n"&gt;Jack&lt;/span&gt; &lt;span class="n"&gt;Ireland&lt;/span&gt;
&lt;span class="n"&gt;Brigitta&lt;/span&gt; &lt;span class="n"&gt;Sipocz&lt;/span&gt;
&lt;span class="n"&gt;David&lt;/span&gt; &lt;span class="n"&gt;Perez&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;Suarez&lt;/span&gt;
&lt;span class="n"&gt;Punyaslok&lt;/span&gt; &lt;span class="n"&gt;Pattnaik&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="n"&gt;Michael&lt;/span&gt; &lt;span class="n"&gt;S&lt;/span&gt; &lt;span class="n"&gt;Kirk&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="n"&gt;Andrew&lt;/span&gt; &lt;span class="n"&gt;Leonard&lt;/span&gt;
&lt;span class="n"&gt;Alex&lt;/span&gt; &lt;span class="n"&gt;Hamilton&lt;/span&gt;
&lt;span class="n"&gt;Andrew&lt;/span&gt; &lt;span class="n"&gt;Inglis&lt;/span&gt;
&lt;span class="n"&gt;Daniel&lt;/span&gt; &lt;span class="n"&gt;Ryan&lt;/span&gt;
&lt;span class="n"&gt;Sally&lt;/span&gt; &lt;span class="n"&gt;Dacie&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="n"&gt;Sanskar&lt;/span&gt; &lt;span class="n"&gt;Modi&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="n"&gt;Albert&lt;/span&gt; &lt;span class="n"&gt;Y&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt; &lt;span class="n"&gt;Shih&lt;/span&gt;
&lt;span class="n"&gt;Erik&lt;/span&gt; &lt;span class="n"&gt;M&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt; &lt;span class="n"&gt;Bray&lt;/span&gt;
&lt;span class="n"&gt;Larry&lt;/span&gt; &lt;span class="n"&gt;Manley&lt;/span&gt;
&lt;span class="n"&gt;Priyank&lt;/span&gt; &lt;span class="n"&gt;Lodha&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="n"&gt;Nabil&lt;/span&gt; &lt;span class="n"&gt;Freij&lt;/span&gt;
&lt;span class="n"&gt;Ankit&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="n"&gt;Igor&lt;/span&gt; &lt;span class="n"&gt;Babuschkin&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="n"&gt;Ole&lt;/span&gt; &lt;span class="n"&gt;Streicher&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="n"&gt;Simon&lt;/span&gt; &lt;span class="n"&gt;Liedtke&lt;/span&gt;
&lt;span class="n"&gt;Sudarshan&lt;/span&gt; &lt;span class="n"&gt;Konge&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="n"&gt;Tessa&lt;/span&gt; &lt;span class="n"&gt;D&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt; &lt;span class="n"&gt;Wilkinson&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;span class="n"&gt;Thomas&lt;/span&gt; &lt;span class="n"&gt;Robitaille&lt;/span&gt;
&lt;span class="n"&gt;yasintoda&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;Happy Pythoning!&lt;/p&gt;
&lt;/section&gt;
</content>
    <link href="https://sunpy.org/posts/2016/2016-05-26-SunPy-07/"/>
    <summary>SunPy 0.7 has arrived!
This release is a culmination of about 10 months of work from 27 different people.
This release brings many changes, the highlights are:</summary>
    <category term="0.7" label="0.7"/>
    <category term="sunpy" label="sunpy"/>
    <published>2016-05-26T00:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://sunpy.org/posts/2016/2016-03-21-python-in-astronomy/</id>
    <title>First impressions from SunPy at Python in Astronomy 2016</title>
    <updated>2016-03-31T00:00:00+00:00</updated>
    <author>
      <name>Steven Christe</name>
    </author>
    <content type="html">&lt;section id="first-impressions-from-sunpy-at-python-in-astronomy-2016"&gt;

&lt;p&gt;Steven Christe &lt;a class="reference external" href="https://github.com/ehsteve"&gt;(&amp;#64;ehsteve)&lt;/a&gt; and Stuart Mumford &lt;a class="reference external" href="https://github.com/Cadair"&gt;(&amp;#64;Cadair)&lt;/a&gt; got to attend the (great) &lt;a class="reference external" href="https://python-in-astronomy.github.io/2016/"&gt;Python in Astronomy&lt;/a&gt; conference which took place in Seattle Washington from 21-25th of March 2016.&lt;/p&gt;
&lt;p&gt;An introduction to SunPy was presented by Steven and you can find the presentation (and citation) at &lt;a class="reference external" href="https://zenodo.org/record/48637"&gt;Zenodo&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Great discussions took place on future plans for &lt;a class="reference external" href="https://docs.astropy.org/en/stable/nddata/index.html"&gt;NDData&lt;/a&gt;,a new &lt;a class="reference external" href="https://github.com/astropy/astropy-APEs/pull/12"&gt;Time Series object&lt;/a&gt;,in Astropy, among many others.&lt;/p&gt;
&lt;/section&gt;
</content>
    <link href="https://sunpy.org/posts/2016/2016-03-21-python-in-astronomy/"/>
    <summary>Steven Christe (@ehsteve) and Stuart Mumford (@Cadair) got to attend the (great) Python in Astronomy conference which took place in Seattle Washington from 21-25th of March 2016.</summary>
    <category term="conference" label="conference"/>
    <category term="outreach" label="outreach"/>
    <category term="tutorials" label="tutorials"/>
    <category term="workshop" label="workshop"/>
    <published>2016-03-31T00:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://sunpy.org/posts/2016/2016-03-07-march-update/</id>
    <title>SunPy Update - March 2016</title>
    <updated>2016-03-07T00:00:00+00:00</updated>
    <author>
      <name>Stuart Mumford</name>
    </author>
    <content type="html">&lt;section id="sunpy-update-march-2016"&gt;

&lt;p&gt;Hello all,&lt;/p&gt;
&lt;p&gt;Once again I am a week late, but here is a quick recap.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="february-news"&gt;
&lt;h1&gt;February News&lt;/h1&gt;
&lt;section id="unified-downloader-aka-fido"&gt;
&lt;h2&gt;Unified Downloader aka Fido&lt;/h2&gt;
&lt;p&gt;We had a very successful sprint on the Unified downloader a couple of weeks ago, and progress is being made towards having it ready to be merged.
The two main things that need to be completed now are adding extra tests of the clients through the Fido interface and improving the documentation.&lt;/p&gt;
&lt;p&gt;We are maintaining a list of issues outstanding on the unidown branch &lt;a class="reference external" href="https://github.com/sunpy/sunpy/issues?q=is%3Aissue+is%3Aopen+label%3Aunidown"&gt;here&lt;/a&gt; as always feel free to ask for advice if you would like to tackle any of them.
Fido is a key feature of SunPy 0.7 and will permit the development of the LightCurve object.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="google-summer-of-code"&gt;
&lt;h2&gt;Google Summer of Code&lt;/h2&gt;
&lt;aside class="system-message"&gt;
&lt;p class="system-message-title"&gt;System Message: INFO/1 (&lt;span class="docutils literal"&gt;/home/docs/checkouts/readthedocs.org/user_builds/sunpyorg/checkouts/489/posts/2016/2016-03-07-march-update.rst&lt;/span&gt;, line 14); &lt;em&gt;&lt;a href="#id1"&gt;backlink&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Duplicate explicit target name: “openastronomy”.&lt;/p&gt;
&lt;/aside&gt;
&lt;p&gt;&lt;a class="reference external" href="https://openastronomy.org/"&gt;OpenAstronomy&lt;/a&gt; got accepted as a GSOC 2016 mentoring Organisation.
This is a significant new development as it indidcates outside recognition of the maturity and quality of the efforts comprising Open Astronomy (SunPy’s previous GSOC students came via the Python Foundation as the mentoring Organisation).
This is the first time in 4 years thathe GSOC Org application SunPy has put in (individually or as a team) has been accepted!
What this means for SunPy is that we will get some money per student from Google.
For more information on GSOC see the &lt;a class="reference external" href="https://openastronomy.org/"&gt;OpenAstronomy&lt;/a&gt; website, and it’s not too late to submit project ideas.&lt;/p&gt;
&lt;/section&gt;
&lt;/section&gt;
&lt;section id="coming-up-in-march"&gt;
&lt;h1&gt;Coming up in March&lt;/h1&gt;
&lt;section id="python-in-astronomy-2016"&gt;
&lt;h2&gt;Python in Astronomy 2016&lt;/h2&gt;
&lt;p&gt;The Python in Astronomy conference is running between the 21st and the 25th of March at the e-Science Institute at the University of Washington in Seattle.
There will a strong SunPy contingent attending, keep your eyes open on social media and on the internet for talks and materials from the conference.
There will be no meeting on the 21st March due to this conference.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="weekly-developer-discussions"&gt;
&lt;h2&gt;Weekly Developer Discussions&lt;/h2&gt;
&lt;p&gt;The weekly meetings will be continuing this month, they are at 1700UTC each week.
We are using Google Hangouts and you can be notified of them by following our Google+ page (normally the join link is posted in IRC once the meeting has started).
These meetings are also recorded and uploaded to YouTube, so you can catch up even if you can not attend in person.&lt;/p&gt;
&lt;p&gt;Links to coming meetings are below:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;p&gt;Meeting on &lt;a class="reference external" href="https://plus.google.com/events/cjoctfv55r7220lj0ffdv636tng"&gt;7/3&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Meeting on &lt;a class="reference external" href="https://plus.google.com/events/ccinoddrb5mhi8l58vu1ah2ti5s"&gt;14/3&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;21/3 There will be no meeting this week due to Python in Astronomy 2016.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Meeting on &lt;a class="reference external" href="https://plus.google.com/events/cjiuftsuopsdc7v374qpe1khvl0"&gt;28/3&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/section&gt;
&lt;section id="reviewing-pull-requests"&gt;
&lt;h2&gt;Reviewing Pull Requests&lt;/h2&gt;
&lt;p&gt;As always, reviews on pull requests are always welcome, you don’t have to have merge permissions or anything other than a GitHub account to review PRs.
You can find a list of all the PRs that need reviewing &lt;a class="reference external" href="https://github.com/sunpy/sunpy/labels/%5BReview%5D"&gt;here.&lt;/a&gt;&lt;/p&gt;
&lt;/section&gt;
&lt;section id="getting-in-touch"&gt;
&lt;h2&gt;Getting in touch&lt;/h2&gt;
&lt;p&gt;Finally, I wanted to remind everyone about our public communication methods.
We have two mailing lists, SunPy and sunpy-dev, the main SunPy list is used for general questions and announcements, and the sunpy-dev list is used for developer discussion and organisational emails.
We also have the IRC channel (#SunPy on Freenode), which normally has someone hanging out in it, and is an excellent place to get some real-time help,or to just come for a chat.
We also have our Google+ page and a Twitter account.&lt;/p&gt;
&lt;p&gt;Happy Pythoning,
Stuart&lt;/p&gt;
&lt;/section&gt;
&lt;/section&gt;
</content>
    <link href="https://sunpy.org/posts/2016/2016-03-07-march-update/"/>
    <summary>Hello all,</summary>
    <category term="monthly" label="monthly"/>
    <category term="status" label="status"/>
    <category term="sunpy" label="sunpy"/>
    <published>2016-03-07T00:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://sunpy.org/posts/2016/2016-02-15-Monthly-Update/</id>
    <title>SunPy Update - February 2016</title>
    <updated>2016-02-15T00:00:00+00:00</updated>
    <author>
      <name>Stuart Mumford</name>
    </author>
    <content type="html">&lt;section id="sunpy-update-february-2016"&gt;

&lt;p&gt;Hello all,&lt;/p&gt;
&lt;p&gt;Sorry for the delay to the January update, but it is here at last.&lt;/p&gt;
&lt;p&gt;There has been quite a lot going on in the six weeks since the last update, thanks to David for collating most of this news.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="january-and-february-news"&gt;
&lt;h1&gt;January and February News&lt;/h1&gt;
&lt;section id="sunpy"&gt;
&lt;h2&gt;SunPy&lt;/h2&gt;
&lt;p&gt;SunPy is using now the latest version of &lt;a class="reference external" href="https://github.com/astropy/astropy-helpers"&gt;astropy-helpers&lt;/a&gt; (v1.1.1) and astropy’s &lt;a class="reference external" href="https://github.com/astropy/ci-helpers"&gt;ci-helpers&lt;/a&gt; which eases the maintenance of the package and the tests running.&lt;/p&gt;
&lt;p&gt;Few new “badges” has been added now to the readme file in the repository, these badges show the status of the repository, like number of downloads, whether the development version is passing all its tests or not (via &lt;a class="reference external" href="https://travis-ci.org/sunpy/sunpy"&gt;Travis&lt;/a&gt; and &lt;a class="reference external" href="https://ci.appveyor.com/project/sunpy/sunpy"&gt;appveyor&lt;/a&gt; ), the amount of code tested, two quality measurements and one that shows the impact in academia.
All these are little helpers to keep an eye on the quality and usage of our beloved project.&lt;/p&gt;
&lt;p&gt;One of the important tests problem solved in this last month has been the figures tests.
Some visualisation is being tested for every new contribution people submit - as with any other tests - and if they differ the test suite tells us
something has changed (or is broken). The figures tested are in the new &lt;a class="reference external" href="https://github.com/sunpy/sunpy-figure-tests"&gt;sunpy-figure-test&lt;/a&gt; repository.
There you can see the figures and compare them with the previous versions - including the environment used to create them.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="openastronomy-workshop"&gt;
&lt;h2&gt;OpenAstronomy workshop&lt;/h2&gt;
&lt;p&gt;January started with a 5-day workshop which extended a 2-day &lt;a class="reference external" href="https://software-carpentry.org/"&gt;software-carpentry&lt;/a&gt; bootcamp with an
introduction to Astropy and SunPy.
Read more about the success of the workshop in the &lt;a class="reference external" href="https://openastronomy.org//2016/01/15/Workshop.html"&gt;openastronomy blog&lt;/a&gt;.
This workshop will be repeated in the future, but if you want to organise one don’t hesitate to contact us about it.&lt;/p&gt;
&lt;/section&gt;
&lt;/section&gt;
&lt;section id="coming-up"&gt;
&lt;h1&gt;Coming up&lt;/h1&gt;
&lt;section id="google-summer-of-code"&gt;
&lt;h2&gt;Google Summer of Code&lt;/h2&gt;
&lt;p&gt;SunPy is joining many other teams to apply together under the OpenAstronomy umbrella to Google Summer of code.
If you want to mentor or help mentoring one of the &lt;a class="reference external" href="https://github.com/sunpy/sunpy/wiki/GSoC-2016-Ideas-Page"&gt;summer projects already proposed&lt;/a&gt; contact us.
If you have some ideas or see that there’s something missing in SunPy… tell us and we can create a project plan for that.&lt;/p&gt;
&lt;p&gt;If you are a candidate student, please, don’t wait till the last week to get in touch.
Get yourself known in the IRC and mailing list… we don’t have all the projects ready yet but they will be soon.
Don’t forget that a contribution before applying is compulsory to being accepted.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="weekly-developer-discussions"&gt;
&lt;h2&gt;Weekly Developer Discussions&lt;/h2&gt;
&lt;p&gt;The weekly meetings will be continuing this month, they are at 1700UTC each week.
We are using Google Hangouts and you can be notified of them by following our Google+ page (normally the join link is posted in IRC once the meeting has started).
These meetings are also recorded and uploaded to YouTube, so you can catch up even if you can not attend in person.&lt;/p&gt;
&lt;p&gt;Links to coming meetings can are below:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;p&gt;Meeting on &lt;a class="reference external" href="https://plus.google.com/events/cqj6t37am6vdn73hvb0njc3fv8"&gt;15/2&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Meeting on &lt;a class="reference external" href="https://plus.google.com/events/gi6kd6e97s8mjh9skif8qj0tn8"&gt;22/2&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Meeting on &lt;a class="reference external" href="https://plus.google.com/events/jt7tb05t7k6ct9cqk4i3lnbjj0"&gt;29/2&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/section&gt;
&lt;section id="reviewing-pull-requests"&gt;
&lt;h2&gt;Reviewing Pull Requests&lt;/h2&gt;
&lt;p&gt;As always, reviews on pull requests are always welcome, you don’t have to have merge permissions or anything other than a GitHub account to review PRs.
You can find a list of all the PRs that need reviewing &lt;a class="reference external" href="https://plus.google.com/events/jt7tb05t7k6ct9cqk4i3lnbjj0"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="getting-in-touch"&gt;
&lt;h2&gt;Getting in touch&lt;/h2&gt;
&lt;p&gt;Finally, I wanted to remind everyone about our public communication methods.
We have two mailing lists, SunPy and sunpy-dev, the main SunPy list is used for general questions and announcements, and the sunpy-dev list is used for developer discussion and organisational emails.
We also have the IRC channel (#SunPy on Freenode), which normally has someone hanging out in it, and is an excellent place to get some real-time help or to just come for a chat.
We also have our Google+ page and a Twitter account.&lt;/p&gt;
&lt;p&gt;Happy Pythoning,
David and Stuart&lt;/p&gt;
&lt;/section&gt;
&lt;/section&gt;
</content>
    <link href="https://sunpy.org/posts/2016/2016-02-15-Monthly-Update/"/>
    <summary>Hello all,</summary>
    <category term="monthly" label="monthly"/>
    <category term="status" label="status"/>
    <category term="sunpy" label="sunpy"/>
    <published>2016-02-15T00:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://sunpy.org/posts/2016/2016-01-01-Monthly-Update/</id>
    <title>SunPy Update - January 2016</title>
    <updated>2016-01-01T00:00:00+00:00</updated>
    <author>
      <name>Stuart Mumford</name>
    </author>
    <content type="html">&lt;section id="sunpy-update-january-2016"&gt;

&lt;p&gt;Hello all,&lt;/p&gt;
&lt;p&gt;Sorry for the lack of a December update, the news for December can be summed up as: “Stuart passed his Viva with minor corrections.”&lt;/p&gt;
&lt;p&gt;Seeing how we are now in 2016 and the original milestone for 0.7 is the end of January, I hope that many people have made “contribute to SunPy” a new years resolution!!
Before we can release 0.7 we need a working Python 3 port, and the unidown branch merged, and the Lightcurve factory implemented.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="december-news"&gt;
&lt;h1&gt;December News&lt;/h1&gt;
&lt;section id="astropy-1-1"&gt;
&lt;h2&gt;Astropy 1.1&lt;/h2&gt;
&lt;p&gt;Astropy 1.1 has been released, so you should upgrade your Astropy!
Also astropy_helpers 1.1 has been released and David has opened &lt;a class="reference external" href="https://github.com/sunpy/sunpy/pull/1627"&gt;PR #1627&lt;/a&gt; to update the version in SunPy with the new release, which should hopefully fix issues we were having with sphinx and doctests on Travis.&lt;/p&gt;
&lt;/section&gt;
&lt;/section&gt;
&lt;section id="coming-up-in-january"&gt;
&lt;h1&gt;Coming up in January&lt;/h1&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference internal" href="../../posts/2016/2016-01-01-Monthly-Update/"&gt;&lt;span class="doc"&gt;SunPy and Astropy Workshop&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference internal" href="../../posts/2016/2016-01-01-Monthly-Update/"&gt;&lt;span class="doc"&gt;Weekly Developer Meetings&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference internal" href="../../posts/2016/2016-01-01-Monthly-Update/"&gt;&lt;span class="doc"&gt;Reviewing Pull Requests&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference internal" href="../../posts/2016/2016-01-01-Monthly-Update/"&gt;&lt;span class="doc"&gt;Summer of Code Project Ideas&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;section id="openastronomy-sunpy-and-astropy-workshop"&gt;
&lt;h2&gt;OpenAstronomy SunPy and Astropy Workshop&lt;/h2&gt;
&lt;p&gt;On 11th to 15th of January at the University of Sheffield there will be a 5 day workshop, with the first two days being a two day Software Carpentry workshop, teaching bash, git and Python.
While the rest of the week covers more SunPy and Astropy specific topics. More information can be found on the &lt;a class="reference external" href="https://openastronomy.org//2016-01-11-Sheffield/"&gt;website&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;There are still places available, you can register &lt;a class="reference external" href="https://docs.google.com/forms/d/e/1FAIpQLSdOD4fDCk7mShxu25cxp-aRetjYuF9cc0P7XjbWbtRHtskQBQ/viewform?c=0&amp;amp;w=1&amp;amp;usp=send_form"&gt;here.&lt;/a&gt;&lt;/p&gt;
&lt;/section&gt;
&lt;section id="weekly-developer-discussions"&gt;
&lt;h2&gt;Weekly Developer Discussions&lt;/h2&gt;
&lt;p&gt;The weekly meetings will be continuing this month, they are at 1600UTC each week.
We are using Google Hangouts and you can be notified of them by following our &lt;a class="reference external" href="https://plus.google.com/+SunpyOrg/posts"&gt;Google+ page&lt;/a&gt; (normally the join link is posted in IRC once the meeting has started).
These meetings are also recorded and uploaded to YouTube, so you can catch up even if you can not attend in person.&lt;/p&gt;
&lt;p&gt;Links to November’s meetings are below:&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;p&gt;Meeting on &lt;a class="reference external" href="https://plus.google.com/events/cr3kkqcvei6nigk65fkl59eh30s"&gt;4/1&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Meeting on &lt;a class="reference external" href="https://plus.google.com/events/c7nf7hqubums62940jnrailrmh0"&gt;11/1&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Meeting on &lt;a class="reference external" href="https://plus.google.com/events/c78i30ns96p6uvs04mn13fdeap0"&gt;18/1&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Meeting on &lt;a class="reference external" href="https://plus.google.com/events/cfgp94dc6eerig5q3g4fcqmaepk"&gt;25/1&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/section&gt;
&lt;section id="id5"&gt;
&lt;h2&gt;Reviewing Pull Requests&lt;/h2&gt;
&lt;aside class="system-message"&gt;
&lt;p class="system-message-title"&gt;System Message: INFO/1 (&lt;span class="docutils literal"&gt;/home/docs/checkouts/readthedocs.org/user_builds/sunpyorg/checkouts/489/posts/2016/2016-01-01-Monthly-Update.rst&lt;/span&gt;, line 56); &lt;em&gt;&lt;a href="#id5"&gt;backlink&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Duplicate implicit target name: “reviewing pull requests”.&lt;/p&gt;
&lt;/aside&gt;
&lt;p&gt;As always, reviews on pull requests are always welcome, you don’t have to have merge permissions or anything other than a GitHub account to review PRs.
You can find a list of all the PRs that need reviewing &lt;a class="reference external" href="https://github.com/sunpy/sunpy/labels/%5BReview%5D"&gt;here :&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Another easy way to get involved is with labelling issues, if you are interested in doing this but don’t have permissions to label issues on GitHub, swing by the IRC channel and talk to me (Cadair).
Issues that are not labelled can be found &lt;a class="reference external" href="https://github.com/sunpy/sunpy/issues?utf8=%E2%9C%93&amp;amp;q=is%3Aopen+no%3Alabel"&gt;here&lt;/a&gt;&lt;/p&gt;
&lt;/section&gt;
&lt;section id="id8"&gt;
&lt;h2&gt;Summer of Code Project Ideas&lt;/h2&gt;
&lt;aside class="system-message"&gt;
&lt;p class="system-message-title"&gt;System Message: INFO/1 (&lt;span class="docutils literal"&gt;/home/docs/checkouts/readthedocs.org/user_builds/sunpyorg/checkouts/489/posts/2016/2016-01-01-Monthly-Update.rst&lt;/span&gt;, line 65); &lt;em&gt;&lt;a href="#id8"&gt;backlink&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Duplicate implicit target name: “summer of code project ideas”.&lt;/p&gt;
&lt;/aside&gt;
&lt;p&gt;As usual this year SunPy will be applying for the GSOC and SOCIS summer of code programs.
As always, the most important part of these applications is having an interesting project ideas list and people willing to mentor students.
If you have any interesting project ideas related to SunPy (they do not have to be on the SunPy code base), then please drop us a line on the mailing list, or edit this &lt;a class="reference external" href="https://github.com/sunpy/sunpy/wiki/GSoC-2016-Ideas-Page"&gt;wiki page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;As we did last year we will be initially applying for GSOC under the &lt;a class="reference external" href="https://openastronomy.org/"&gt;OpenAstronomy banner&lt;/a&gt;, so suggestions of ways to improve that site, or general involvement with OpenAstronomy would be welcome.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="getting-in-touch"&gt;
&lt;h2&gt;Getting in touch&lt;/h2&gt;
&lt;aside class="system-message"&gt;
&lt;p class="system-message-title"&gt;System Message: INFO/1 (&lt;span class="docutils literal"&gt;/home/docs/checkouts/readthedocs.org/user_builds/sunpyorg/checkouts/489/posts/2016/2016-01-01-Monthly-Update.rst&lt;/span&gt;, line 26); &lt;em&gt;&lt;a href="#id9"&gt;backlink&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Duplicate explicit target name: “google+ page”.&lt;/p&gt;
&lt;/aside&gt;
&lt;p&gt;Finally, I wanted to remind everyone about our public communication methods.
We have two mailing lists, &lt;a class="reference external" href="https://groups.google.com/forum/#!forum/sunpy"&gt;SunPy&lt;/a&gt; and sunpy, the main SunPy list is used for general questions and announcements, and the sunpy-dev list is used for developer discussion and organisational emails.
We also have the IRC channel, which normally has someone hanging out in it, and is an excellent place to get some real-time help, or to just come for a chat.
We also have our &lt;a class="reference external" href="https://plus.google.com/+SunpyOrg/posts"&gt;Google+ page&lt;/a&gt; and a &lt;a class="reference external" href="https://twitter.com/sunpyproject"&gt;Twitter&lt;/a&gt; account.&lt;/p&gt;
&lt;p&gt;Happy Pythoning,
Stuart&lt;/p&gt;
&lt;/section&gt;
&lt;/section&gt;
</content>
    <link href="https://sunpy.org/posts/2016/2016-01-01-Monthly-Update/"/>
    <summary>Hello all,</summary>
    <category term="monthly" label="monthly"/>
    <category term="status" label="status"/>
    <category term="sunpy" label="sunpy"/>
    <published>2016-01-01T00:00:00+00:00</published>
  </entry>
</feed>
