The Astropy web pages
Home Page: http://www.astropy.org
License: BSD 3-Clause "New" or "Revised" License
This repository contains the Astropy web site (primary URL http://www.astropy.org).
In a previous version of this web site (on the old_site branch), this repository held the build for the site, but the content was generated from the astropy-website repository. That repo is no longer active, and issues with the astropy web site should now be reported in this repository.
I recently looked for a affiliated package, but had forgotten the name. So, I looked the the table of affiliated (and provisionally affiliated) packages in the astropy docs. That table contains a lot of info that's relevant to package contributors (code repository, name of main maintainer), but little info for somebody that's looking for a package.
I suggest to add a summary/tagline/a few keywords for each package. In turn, the column "code repository" can go. There is a link to the docs for each package and presumably the docs will explain where to get the code. (I think, the column "maintainer" is also not that important here.)
We can save even more space if we make the package name a link to its docs. So, the table would then be (using examples where I know the package well enough):
name/link - status / pipi - description
APLPy - stable - APLPy- plotting of images in WCS with lables, overlays, etc.
ginga - stable - interactive image viewer similar to ds9
phot-utils - devel - photometric functions and pipeline
From @astrofrog:
Somewhere (doesn't have to be too obvious necessarily) we should keep a list of people who were previously in roles, so that there is an official place we record this (because I think we should recognize past as well as current contributions)
Per agreement of the Coordination Committee and Brigitta, she will be taking the lead role for Core package release coordinator. Please update the Team page accordingly.
Add to Footer.
"The AstroPy project is committed to fostering an inclusive community." and link to code of conduct.
this would close astropy/coordination#22
We should either change the repo name to astropy.github.io or astropy.org - any objections? (I prefer the latter)
@eteq - FYI the tables for provisional vs accepted need to be swapped. I can try and open a PR later.
When clicking on the drop down that says "other docs", the first entry says "developer", but it doesn't link to the "documentation for developers", it links to a nightly build of the development tree...
Maybe it's just me, but I found this confusing. Maybe it should say "development" (as Python.org does) instead of "developer"? Or "In development" might be even better...
http://astropy.logosoftwear.com/ does not have a labcoat selection anymore.
Moved over from astropy/astropy#5524 as @bsipocz suggested. @perrygreenfield will look into it.
On http://www.astropy.org/about.html#acknowledge the link to the logo with white text in broken (look in the sentence under the astropy-powered image).
The broken link is: http://www.astropy.org/_downloads/astropy_powered.png
One of the items of feedback that came from ADASS (specifically @cdeil mentioned it to me) is that we should probably have the equivalent of:
http://docs.astropy.org/en/stable/stability.html
for affiliated packages. The different levels I imagine are:
We could use traffic-light colors (like in the core package) to show these in the affiliated package table.
Dear Astropy Coordinators
I have a longstanding interest in WCS and astropy.wcs and I use astropy.io.fits very extensively. Those would be big sub-packages to take on though. astropy.constants would be easier.
One caveat is that although I’ve been listed as a contributor to Astropy for a long time, I haven’t successfully contributed code yet. However, my current roles at IPAC are now half-time doing Python development for the ZTF project, and half-time working on LSST Science User Interface and Tools where I am responsible for integrating visualization tools into the LSST stack. I’m learning the LSST stack development workflow which will help in improving my skill level for Astropy contributions and I have made my first successful contribution to the stack. (I am also a big proponent of bringing more Astropy into LSST!)
Regards,
DavidDavid Shupe, Ph.D.
Staff Scientist, ZTF and LSST
IPAC/Caltech
The affiliated package info specifically mentions Python 3.x compatibility, but not Python 2.x. Is Python 2.x optional, or merely implied? I think it would be helpful to clarify that section. Personally, I would be in favor of pointing to tools like six and python-future and recommending single-codebase Python 2&3 support.
Once it has been finalized, we should add the new code of conduct to the Astropy website! :)
The Getting Started page needs to be a much higher level overview with pointers to examples and tutorials rather than just a demo for how to import.
http://docs.astropy.org/en/stable/getting_started.html
For a few long standing affiliated packages there are pages under astropy.org (e.g. http://astropy.org/astroquery and http://astropy.org/montage-wrapper and possibly others).
I propose to remove these pages and use the pointers to either point to the websites of the packages listed in the registry, or to their RTD docs page. It can be a bit fine grained, too, e.g. packages with provisional status don't get it only when they are accepted with full status, etc.
It would be useful if there were short descriptions of each affiliated package in the registry table here: http://www.astropy.org/affiliated/
I wonder if this is something we can insert automatically using the "Summary" from pypi?
Hi,
the SSL-enabled web page https://www.astropy.org/affiliated/ does not show the package registry. The table stays in the state "Loading...".
On the landing page, Ureka should be replaced with AstroConda (http://astroconda.rtfd.io). Ureka is no longer actively developed/maintained as of 04/2016. It will remain available for download indefinitely for anyone that needs it, however the packages are already >1 year out of date.
If we go ahead and merge astropy/astropy#3183 then we should add WCSAxes to the list of affiliated packages (and I will move the repo to the astropy organization).
@astrofrog @eteq @perrygreenfield I couldn't find any info on what the Astropy-APEs and astropy-api proposals are on the Astropy webpage or in the docs.
It would be very nice to have an overview table (similar to the one there is for PEPs that shows some basic info (number, title, status) and links to the document and the discussion, but that is not so easy to auto-generate.
As a start, how about adding a section describing what they are and where to find them here?
http://www.astropy.org/contribute.html
In the table of affiliated packages, there is no explanation of the "Provisional" column.
From the NumFOCUS communications director:
We'd really like to make sure that our relationship to sponsored projects is clearly delineated on each project's individual website. To that end, we're requesting all sponsored projects to take the following steps:
Please post the NumFOCUS digital stamp on the homepage of your website (at the bottom or in the footer is fine).
Link the image to this url: www.numfocus.org
At the moment, the 'About' section has information about the license, credits, citing astropy, and some high level information about the project. I wonder whether we might consider splitting into:
It would be nice to have somewhere maybe on the front page where we can show organizations that we know use Astropy (e.g. STScI/JWST, etc.)
The 'developer install instructions' link on the contribute page doesn't work, it doesn't open the right tab.
It would be nice to be able to click on section titles or on a ¶ symbol next to them (like GitHub markdown) to get a link to a section.
As discussed in #79, now that there's a "description" section in the registry, we should have this be reflected in the affiliated package pages.
The question is where. The table seems sensible, except that it already has a lot of content and long text descriptions might make it hard to read. (Although perhaps shortening some of the content in the tables would help this, as @astrofrog suggested in #79)
An alternative is an automated version of the previous "Other Packages" section.
I'll try to get to this at some point, but if someone else wants to take a stab, feel free.
The github API is really powerful and not too tough to use. It should be possible to add a script to the astropy web site that queries github for the list of APEs (from astropy/astropy-APEs), and uses that to generate a table on the astropy web site, something like what we do now for the affiliated packages.
A few minutes googling suggests that at least something of this sort is possible with jquery, which is already on our site:
http://blog.teamtreehouse.com/code-a-simple-github-api-webapp-using-jquery-ajax
If anyone wants to take a shot at this, just say so - I may get to it at some point, but unclear when...
There's a bug in the contribute page header: the "astropy" text on the left that links to the main page is duplicated.
http://www.astropy.org/contribute.html
As discussed in astropy/astropy#4673 and astropy/astropy#1457 we should add a link to http://astropy.userecho.com to the website.
This page should include a list of affiliated package contributors (we need to decide whether to duplicate names already in the list of core contributors):
As mentioned in astropy/astropy#5474, astropy.org does not currently support secure connection via https. Maybe it should?
The base CSS for astropy.org starts with a definition that basically removes useful HTML formatting tags like <it>, <sup>, <strong> etc. I understand wanting to have a highly uniform and simplified look, but it seems like this is going too far. In particular now I want to use <sup> and it isn't possible. This is something that a SO post specifically discouraged from doing with pure CSS.
Would there be a problem with liberating a few of these?
/* http://meyerweb.com/eric/tools/css/reset/
v2.0 | 20110126
License: none (public domain)
*/
html, body, div, span, applet, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, acronym, address, big, cite, code,
del, dfn, em, img, ins, kbd, q, s, samp,
small, strike, strong, sub, sup, tt, var,
b, u, i, center,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td,
article, aside, canvas, details, embed,
figure, figcaption, footer, header, hgroup,
menu, nav, output, ruby, section, summary,
time, mark, audio, video {
margin: 0;
padding: 0;
border: 0;
font-size: 100%;
font: inherit;
vertical-align: baseline;
}
@embray - since you mentioned on the list that you are no longer providing these, should we update the front page of the website?
We merged #111 from @taldcroft adding all the roles to http://www.astropy.org/team.html . One quirk there: the footnotes don't seem to be live links. Were they supposed to be, @taldcroft?
Currently the regex given by
[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4} throws a warning for Bad or unnecessary escaping. I think this should be corrected to [A-Z0-9._%+-]+@[A-Z0-9.-]+[.]{1}[A-Z]{2,4} so that the hint stops throwing this warning. Both the regex essentially convey the same meaning.
Is this a good thing to change ?
In http://www.astropy.org/affiliated/index.html it says:
That doesn't seem like an accurate description of Astropysics, but I'll leave it to @eteq!
Prompted by the discussion in astropy/astropy#6299, I figured I should start a discussion here: should we have a place where we have logos of organizations that have in some way directly supported astropy development? Some obvious inclusions would be STScI and CfA/CXC... Perhaps also LSST (depending on how @parejkoj intereprets some of his contributions). I imagine there are others that I am less familiar with, too.
In the http://www.astropy.org/about.html page we should add a mention of this:
[](http://www.astropy.org/)
which gives:
More generally, the URL http://img.shields.io/badge/powered%20by-AstroPy-orange.svg?style=flat can be used to get this image.
Affiliated packages could use this in the README
cc @eteq
Thanks for pointing this out @dfm!
Isn't regions an affiliated package? If yes, can we add it to the list?
https://github.com/astropy/regions
I think the MacOS X instructions on the home page (http://www.astropy.org/) should be updated:
Any other ways we can simplify the install instructions?
Once astropy/astropy#2562 is done, we should use the getteam.py script (or some other means, if there's some problem with that) to update the contributor list for the 0.4 release.
Right now the astropy web site doesn't have much (pretty much nothing) in the way of "look, here's some cool things astropy does" on the web site. We should add that, possibly on the main page, or possibly in the "about" section.
I'm imagining something vaguely along the lines of http://jquery.com/ , which has "A Brief Look" at the bottom showing key features.
This was prompted by @demitri suggesting it during SciCoder, after we tried to find just such a page for an intro to Astropy section.
Currently there's no link to the Astropy tutorials page (http://www.astropy.org/astropy-tutorials/) from the web page (http://www.astropy.org/), so it's hard to find.
I guess it should be added in the header, but maybe then there's too many items for mobile devices?
cc @adrn @astrofrog
React
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
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
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.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.
