General repo
openastronomy / openastronomy.github.io Goto Github PK
View Code? Open in Web Editor NEWThe web site for the Open Astronomy effort.
Home Page: http://openastronomy.org
License: BSD 2-Clause "Simplified" License
The web site for the Open Astronomy effort.
Home Page: http://openastronomy.org
License: BSD 2-Clause "Simplified" License
At @bsipocz's suggestion, we should create a calendar with upcoming events/deadlines relevant to OpenAstronomy's goals.
Post your 2020 GSOC project ideas here.
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.
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?
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.
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.
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
It needs to be added to the list in the config yaml file.
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:
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.
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
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.
The page is not building properly since the merge of #158
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.
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:
There is no favicon which should be there in the title bar. I will like to work to include a favicon in the site.
Add to the website: https://github.com/kritisingh1/numpy/wiki/Now-You-Know-It!-:-Getting-selected-in-Outreachy
Thanks @bsipocz
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.
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.
The application asks for a webpage where to explain how to join to an IRC or mailing list.
- 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
- /css/bootstrap/bootstrap.css
- /css/bootstrap/bootstrap-responsive.css
- /css/swc.css
- ajax.googleapis.co[...]n.js (78.5KiB)
- https://openastronomy.org/ (180B of inline JavaScript)
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)
meta http-equiv
or by adding custom headers to _config.yml
# 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
We could use this for caching:
https://github.com/benbalter/jekyll-include-cache
We should define a lang
attribute on the html root
I believe the related issue for ndcube's resampling project is an error. Perhaps it was supposed to be pointed at this issue instead.
Something like this from gnome: https://wiki.gnome.org/Newcomers but for us :)
Great idea @Cadair
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:
Add your project ideas for SunPy as comments below:
Tracker issue for stuff that may work as project ideas in future years
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?
How to get in touch with organisation may have changed. Also now we have matrix connected with all.
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.
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 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.
There are few broken links on our site:
./_site/gsoc/background.html
./_site/gsoc/suborg_guidelines.html
./_site/members/index.html
./_site/projects/2018/poliastro/reference-frames.html
./_site/projects/2019/astropy/stcs_regions.html
./_site/projects/2019/poliastro/validation-framework.html
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.
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
assigned to: @RafaelSdeSouza @emilleishida @migueldvb
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.
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.
We should be explicit about the CoC when students apply.
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.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.