We should have a page like the members but with info of who has done what (being a GSOC admin, mentor, student, member of the committee, SOC on PiA...) which can be linked with the open badges we started to produce last year.

For Astropy we have used a standard heading format for each project which I think would be good to use for other projects:

*Suggested Mentor(s):* Michael Droettboom

*Difficulty:* Intermediate to Expert

*Astronomy knowledge needed:* none

*Programming skills:* Python, Unix features

This should be put directly under the title

On the PSF there's a template for orgs with certain stuff that should appear on the site

For example,

Tell the students a bit about your organization. Here's some questions you might want to answer:

• What software are you creating?
• Why is it interesting?
• Who uses it?
• What languages is it written in?
• How is it going to change the world?

Students find the ideas and contact the central openastronomy mailing list and then some of us have to redirect them to the messaging tool or mailing list that sub-org uses. We can skip that step if we put the info on the project description.

Can you make it possible to link to specific GSoC projects?
http://openastronomy.github.io/gsoc2015/ideas.html

Different, but related feature request: would adding a table at the top summarising the project ideas be useful to get a quick overview?

I would like to have a link on the Astropy wiki pointing to the OpenAstronomy astropy ideas. I can click on the astropy tag from http://openastronomy.org/gsoc/gsoc2017/, but I can't see a way to get that from a URL.

I use this issue to collect pie in the sky ideas, and we'll see how many of them can become real project ideas. cc @eteq

• get regions and photutils to mesh better together

We should be explicit about the CoC when students apply.

I think I know why #236 didn't see a Giles status. Example log: https://circleci.com/gh/OpenAstronomy/openastronomy.github.io/180

- ./_site/gsoc/background.html
  *  External link https://mirca.github.io/gsoc-application/ failed: 404 No error
- ./_site/gsoc/suborg_guidelines.html
  *  External link https://socis.esa.int failed: response code 0 means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed out.
             Sometimes, making too many requests at once also breaks things.
             Either way, the return message (if any) from the server is: SSL peer certificate or SSH remote key was not OK
- ./_site/members/index.html
  *  External link https://asaip.psu.edu/organizations/iaa/iaa-working-group-of-cosmostatistics/ failed: 404 No error
- ./_site/projects/2018/poliastro/reference-frames.html
  *  External link http://aa.usno.navy.mil/publications/docs/Circular_179.pdf failed: response code 0 means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed out.
             Sometimes, making too many requests at once also breaks things.
             Either way, the return message (if any) from the server is: Couldn't resolve host name
- ./_site/projects/2019/astropy/stcs_regions.html
  *  External link https://github.com/at88mph/opencadc_stc/tree/master/opencadc_stc failed: 404 No error
- ./_site/projects/2019/poliastro/validation-framework.html
  *  External link https://blog.poliastro.space/poliastro-benchmarks/ failed: 404 No error
htmlproofer 3.15.1 | Error:  HTML-Proofer found 6 failures!

The application asks for a webpage where to explain how to join to an IRC or mailing list.

Post your 2020 GSOC project ideas here.

How to get in touch with organisation may have changed. Also now we have matrix connected with all.

It needs to be added to the list in the config yaml file.

1. Critical dependencies (SPOF) - may block the entire display of the page in case of failure:

- https://ajax.googleapis.com/ajax/libs/jquery/3.1.1/jquery.min.js
- fonts.googleapis.com/css?family=Fira+Sans:400,40[...]italic,500,500italic,700

2. We could reduce 19% (29.5 KiB) by minifying the assets:

- /css/bootstrap/bootstrap.css
- /css/bootstrap/bootstrap-responsive.css
- /css/swc.css

3. 78.7KiB of JavaScript is parsed during initial page load. We could defer parsing JavaScript to reduce blocking of page rendering:

- ajax.googleapis.co[...]n.js (78.5KiB)
- https://openastronomy.org/ (180B of inline JavaScript)

4. These png-s are resized on browser side:

openastronomy.org/img/icons[...]s_icon.png (displayed size: 16x16)
openastronomy.org/img/icons[...]l_icon.png (displayed size: 16x16)
openastronomy.org/img/logo/[...]te_svg.png (displayed size: 125x60)
openastronomy.org/img/icons[...]c_icon.png (displayed size: 16x16)

5. Jekyll - Content Security Policy could be set - e.g:
   We can partially implement it with meta http-equiv or by adding custom headers to _config.yml
   https://jekyllrb.com/docs/configuration/webrick/

# Custom headers
webrick:
  headers:
    Content-Security-Policy: default-src 'none'; script-src 'self'; connect-src 'self'; img-src 'self'; style-src 'self'; 
    My-Other-Header: My-Other-Value

7. We could use this for caching:
   https://github.com/benbalter/jekyll-include-cache

8. We should define a lang attribute on the html root

There is no favicon which should be there in the title bar. I will like to work to include a favicon in the site.

assigned to: @RafaelSdeSouza @emilleishida @migueldvb

In some cases, the visitor needs to zoom out so to see the content at the bottom.

The most recent version of ChiantiPy is on GitHub. It would be nice to have a link to that page in addition to/instead of the Source Forge page.

While previous mentors are kept listed, previous admins got overwritten with the current ones. Would be nice to keep track who were admin in previous years along with the mentor list:

http://openastronomy.org/gsoc/gsoc2017/

This paper may be useful for GSOC students to learn about the full spectrum of data types and sources we have in astronomy. (via @giordano )

At the moment we include the project ideas from different pages into a single page which means that heading levels looks like:

# Ideas page

# Astropy

## Project 1

### Description

But really we want Astropy to be at a lower level. For now, for the Astropy project I lowered the levels of the projects and descriptions, to give:

# Ideas page

# Astropy

### Project 1

#### Description

but this is still not ideal. Any ideas?

There are few broken links on our site:

• ./_site/gsoc/background.html
  • External link https://mirca.github.io/gsoc-application/ 404 (@mirca)
• ./_site/gsoc/suborg_guidelines.html
  • External link https://socis.esa.int failed. Certificate expired few days ago. We've told them.
• ./_site/members/index.html
  • External link https://asaip.psu.edu/organizations/iaa/iaa-working-group-of-cosmostatistics/ 404
    To update to: http://iaa.mi.oa-brera.inaf.it/IAA/coin.html (@COINtoolbox)
• ./_site/projects/2018/poliastro/reference-frames.html
  • External link http://aa.usno.navy.mil/publications/docs/Circular_179.pdf failed: got a time out
    Probably this is only temporary.
• ./_site/projects/2019/astropy/stcs_regions.html
  • External link https://github.com/at88mph/opencadc_stc/tree/master/opencadc_stc 404
• ./_site/projects/2019/poliastro/validation-framework.html
  • External link https://blog.poliastro.space/poliastro-benchmarks/ 404 (@Juanlu001)

Add your project ideas for SunPy as comments below:

Add to the website: https://github.com/kritisingh1/numpy/wiki/Now-You-Know-It!-:-Getting-selected-in-Outreachy
Thanks @bsipocz

The page is not building properly since the merge of #158

In addition to what @bmorris3 suggested in #133 , I think it might be useful to have some overview of GSoC from previous years, especially have links or info for good previous GSoC projects somewhere discoverable for reference for potential students / mentors, but also for us to have an overview.

There is http://openastronomy.org/gsoc/ but as far as I can see that is only project ideas. There is no way to see which ones happened, who did them or info about the project. http://openastronomy.org/Universe_OA/ is nice to keep up to date with new blog posts, but again not a nice overview of previous projects.

It's probably be some work to collect that data and surface it in a good way, so definitely would suggest to focus on #133 first.

@dstansby - Could you do as done in #97 and add HelioPy to the list?? Thanks :)
Please, if possible add also some chatting channel (matrix?) and mailing list.

At @bsipocz's suggestion, we should create a calendar with upcoming events/deadlines relevant to OpenAstronomy's goals.

We probably want to differentiate the projects, so later on it would be good to use a slightly different project rather than simply re-use the astropy one. However, this is not critical and doesn't have to be done before the deadline.

I believe the related issue for ndcube's resampling project is an error. Perhaps it was supposed to be pointed at this issue instead.

The footer at http://openastronomy.org/ contains an entry [email protected]

Clicking it opens the URL mailto:[email protected] in a new browser tab, I think it should open an email with that address filled instead?

Probably needs some change here?

--

In addition, would it be possible to add a link to the openastronomy google group archive? As someone new I need to go there first and sign up, or just might want to read what's going on on that list before sending an email, no?

When a senior undergrad or junior grad student approaches this or this webpage, they're met with a wall of instructions without a clear advertisement that makes sense to a student who may be eligible to apply. Perhaps we could improve this by adding a drop-down tab on the webpage called "For Students", and the landing page for students can describe the following:

• what GSoC is (from Google's perspective)
• what OA/astropy/sunpy are (relevance to target student)
• how much experience in astronomy/physics, and software dev is necessary to apply (with emphasis on astronomy)
• for whom GSoC is a good summer salary option (senior undergrad/junior grad); examples of project scope, on the interval: [build a webpage, build a new package].
• testimonials from successful past GSoC students describing how the program fit into their career and who they'd recommend it for (I'd be happy to write the first one).
• finally, a link to the student application guidelines

Does this sound good to everyone? Ideally, in emails sent around advertising GSoC for OA, we'd send a link to this new page first.

Since I'm pitching this idea, I'd be happy to create the first PR.

It would be useful to have a better visibility to the given suborgs (and their varying application process and chat channels) in the student application guideline page.
Alternatively, those links could be repeated in every project idea page.

Looking at that guide with fresh eyes, it's not trivial to see of how to e.g. access the heliopy chat/developers, so students end up in the astropy sign up mailing list. I assume it also works the other way and astropy interests end up elsewhere.

bundle install --path vendor/bundle
The --path flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. We should use bundle config set path 'vendor/bundle', and stop using this flag.

Clicking on a mentor's name on the mentor page just leads to a blank page. Seems like it should link to a page with more info or at least their GitHub profile.

Something like this from gnome: https://wiki.gnome.org/Newcomers but for us :)

Great idea @Cadair

I think it would be a good idea - for next year for sure, to add the times avialability in UT for the mentors, so the candidates could now when they would be more likely to respond.

Would be nice to come up with a reordering of OA members, as currently it sorely depends on the location of their entry in the yaml file.

One option is to do it alphabetically. I don't like it very much as it would put one of the big members, sunpy at the end. Same with reverse alphabetical, then astropy would be at the bottom of the page.

Keep the members participating in the actual gsoc at the top of the list, and the rest afterwards. Within the two groups alphabetical might be fine.

I think this started with #64 ... I now see different backgrounds on the front page vs other pages (like "members"). Is that intended, @dpshelio and/or @Cadair ?

• define minimum details about what means open-development
• review all our members still exist and follow the practices of the community
• ...something else that I may be forgetting...

When width of the screen is between 600px and 1040px, the navigation bar is not responsive.

At the moment adding a new organisation needs to add info in the main _config.yml add a page under _includes/member/ and the logo. I believe all that info could be set inside a _members.yml file and automatically generated the members page.

As it is now it's easier to get some minor errors like wrong logos or links.

• Create mailing list for mentors discussions
• Create mailing list to all the students
• Create mailing list with accepted students (or use the above unsubscribing the non accepted)

When there are many mentors for a project or mentors with super long github name, the row is overflowing, see projects e.g.: pedal to metal, and MAST module

https://blog.github.com/2018-05-01-github-pages-custom-domains-https/

Tracker issue for stuff that may work as project ideas in future years

• astropy/astropy#8723
• asv tool to alert maintainers on performance degradation and/or comment on a PR whether the patch provides any performance changes
• specutils integration with timeseries

There is no meta tags and og tags in the header of the website. We require them for better SEO. I will like to work on it.

https://openastronomy.org/gsoc/gsoc2019/#/projects?project=incorporate_powerful_new_wcs_api_into_ndcube