Add two Martin's codes

[rainwoodman]

BoxRemap and Copter.

Looks like if this page is to scale up, we need to change how the linkref and entries are separated. the current scheme separates the entry and linkref and may be difficult to maintain if we want to split the page or ask others to write pull requests (two hunks vs one)

I've put martin's other suggested link here:

https://github.com/desihub/imaginglss
https://github.com/martinjameswhite/litemangle
https://github.com/mockFactory
https://github.com/wll745881210/CLPT_GSRSD
https://github.com/martinjameswhite/recon_code

[kbarbary]

It looks like neither of these have a license. Perhaps @martinjameswhite can add a license to these? If you don't care, the MIT license is a good default choice. Or there's always www.choosealicense.com if you really want to get into it....

[kbarbary]

To scale this page up, we may want to automatically generate it from a csv or json file or similar, using (1) a script to generate rst, (2) a sphinx extensionedit: forgot this wasn't sphinx! or (3) javascript to populate a HTML table.

But let's wait on that to see how many other pieces of software we get and what the diversity is.

[rainwoodman]

Yes. This reminded me to add proper licenses to my code.

[kbarbary]

Nice 👍

[rainwoodman]

What is needed to generate the page?
"""
Project Name, Icon URL, URL, One sentence description, TAGS
"""

[rainwoodman]

I wonder if there already is a nikola plug in for this kind of things.
We need to build indices by tags as well.

[rainwoodman]

I added a stub script to build json from rst and rst from json

[kbarbary]

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the grey part).

Could also do something like

[martinjameswhite]

I think all my stuffs licensed ...

On Jun 8, 2015, at 10:56 PM, Kyle Barbary notifications@github.com wrote:

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the gre y part).

Could also do something like

—
Reply to this email directly or view it on GitHub.

[kbarbary]

Great, thanks Martin.

[rainwoodman]

@kbarbary
could you mock up an .rst entry so that I can put it in the convertor?

[kbarbary]

For now, can you just make the converter output an HTML page? e.g.,

<!--.. title: Software.. slug: software.. type: text.. hidetitle: true--><p>BCCP develops open-source software for use in cosmology. Here are some
of our projects:</p><hr><h3>SEP</h3><p>SEP is a Python and C library for source detection and photometry, adapted from the
SourceExtractor code base. It makes the SourceExtractor background and detection algorithms
available directly from Python and (eventually) Julia. &nbsp;
<ahref="http://sep.readthedocs.org">webpage</a> &nbsp;
<ahref="http://github.com/kbarbary/sep">GitHub</a></p><hr><h3>SNCosmo</h3>
...

Let's just get the links into the paragraph and prettify them in a separate step.

[rainwoodman]

BoxRemap and Copter.

Looks like if this page is to scale up, we need to change how the linkref and entries are separated. the current scheme separates the entry and linkref and may be difficult to maintain if we want to split the page or ask others to write pull requests (two hunks vs one)

I've put martin's other suggested link here:

https://github.com/desihub/imaginglss
https://github.com/martinjameswhite/litemangle
https://github.com/mockFactory
https://github.com/wll745881210/CLPT_GSRSD
https://github.com/martinjameswhite/recon_code

[kbarbary]

It looks like neither of these have a license. Perhaps @martinjameswhite can add a license to these? If you don't care, the MIT license is a good default choice. Or there's always www.choosealicense.com if you really want to get into it....

[kbarbary]

To scale this page up, we may want to automatically generate it from a csv or json file or similar, using (1) a script to generate rst, (2) a sphinx extensionedit: forgot this wasn't sphinx! or (3) javascript to populate a HTML table.

But let's wait on that to see how many other pieces of software we get and what the diversity is.

[rainwoodman]

Yes. This reminded me to add proper licenses to my code.

[kbarbary]

Nice 👍

[rainwoodman]

What is needed to generate the page?
"""
Project Name, Icon URL, URL, One sentence description, TAGS
"""

[rainwoodman]

I wonder if there already is a nikola plug in for this kind of things.
We need to build indices by tags as well.

[rainwoodman]

I added a stub script to build json from rst and rst from json

[kbarbary]

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the grey part).

Could also do something like

[martinjameswhite]

I think all my stuffs licensed ...

On Jun 8, 2015, at 10:56 PM, Kyle Barbary notifications@github.com wrote:

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the gre y part).

Could also do something like

—
Reply to this email directly or view it on GitHub.

[kbarbary]

Great, thanks Martin.

[rainwoodman]

@kbarbary
could you mock up an .rst entry so that I can put it in the convertor?

[kbarbary]

For now, can you just make the converter output an HTML page? e.g.,

<!--.. title: Software.. slug: software.. type: text.. hidetitle: true--><p>BCCP develops open-source software for use in cosmology. Here are some
of our projects:</p><hr><h3>SEP</h3><p>SEP is a Python and C library for source detection and photometry, adapted from the
SourceExtractor code base. It makes the SourceExtractor background and detection algorithms
available directly from Python and (eventually) Julia. &nbsp;
<ahref="http://sep.readthedocs.org">webpage</a> &nbsp;
<ahref="http://github.com/kbarbary/sep">GitHub</a></p><hr><h3>SNCosmo</h3>
...

Let's just get the links into the paragraph and prettify them in a separate step.

[rainwoodman]

BoxRemap and Copter.

Looks like if this page is to scale up, we need to change how the linkref and entries are separated. the current scheme separates the entry and linkref and may be difficult to maintain if we want to split the page or ask others to write pull requests (two hunks vs one)

I've put martin's other suggested link here:

https://github.com/desihub/imaginglss
https://github.com/martinjameswhite/litemangle
https://github.com/mockFactory
https://github.com/wll745881210/CLPT_GSRSD
https://github.com/martinjameswhite/recon_code

[kbarbary]

It looks like neither of these have a license. Perhaps @martinjameswhite can add a license to these? If you don't care, the MIT license is a good default choice. Or there's always www.choosealicense.com if you really want to get into it....

[kbarbary]

To scale this page up, we may want to automatically generate it from a csv or json file or similar, using (1) a script to generate rst, (2) a sphinx extensionedit: forgot this wasn't sphinx! or (3) javascript to populate a HTML table.

But let's wait on that to see how many other pieces of software we get and what the diversity is.

[rainwoodman]

Yes. This reminded me to add proper licenses to my code.

[kbarbary]

Nice 👍

[rainwoodman]

What is needed to generate the page?
"""
Project Name, Icon URL, URL, One sentence description, TAGS
"""

[rainwoodman]

I wonder if there already is a nikola plug in for this kind of things.
We need to build indices by tags as well.

[rainwoodman]

I added a stub script to build json from rst and rst from json

[kbarbary]

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the grey part).

Could also do something like

[martinjameswhite]

I think all my stuffs licensed ...

On Jun 8, 2015, at 10:56 PM, Kyle Barbary notifications@github.com wrote:

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the gre y part).

Could also do something like

—
Reply to this email directly or view it on GitHub.

[kbarbary]

Great, thanks Martin.

[rainwoodman]

@kbarbary
could you mock up an .rst entry so that I can put it in the convertor?

[kbarbary]

For now, can you just make the converter output an HTML page? e.g.,

<!--.. title: Software.. slug: software.. type: text.. hidetitle: true--><p>BCCP develops open-source software for use in cosmology. Here are some
of our projects:</p><hr><h3>SEP</h3><p>SEP is a Python and C library for source detection and photometry, adapted from the
SourceExtractor code base. It makes the SourceExtractor background and detection algorithms
available directly from Python and (eventually) Julia. &nbsp;
<ahref="http://sep.readthedocs.org">webpage</a> &nbsp;
<ahref="http://github.com/kbarbary/sep">GitHub</a></p><hr><h3>SNCosmo</h3>
...

Let's just get the links into the paragraph and prettify them in a separate step.

[rainwoodman]

BoxRemap and Copter.

Looks like if this page is to scale up, we need to change how the linkref and entries are separated. the current scheme separates the entry and linkref and may be difficult to maintain if we want to split the page or ask others to write pull requests (two hunks vs one)

I've put martin's other suggested link here:

https://github.com/desihub/imaginglss
https://github.com/martinjameswhite/litemangle
https://github.com/mockFactory
https://github.com/wll745881210/CLPT_GSRSD
https://github.com/martinjameswhite/recon_code

[kbarbary]

It looks like neither of these have a license. Perhaps @martinjameswhite can add a license to these? If you don't care, the MIT license is a good default choice. Or there's always www.choosealicense.com if you really want to get into it....

[kbarbary]

To scale this page up, we may want to automatically generate it from a csv or json file or similar, using (1) a script to generate rst, (2) a sphinx extensionedit: forgot this wasn't sphinx! or (3) javascript to populate a HTML table.

But let's wait on that to see how many other pieces of software we get and what the diversity is.

[rainwoodman]

Yes. This reminded me to add proper licenses to my code.

[kbarbary]

Nice 👍

[rainwoodman]

What is needed to generate the page?
"""
Project Name, Icon URL, URL, One sentence description, TAGS
"""

[rainwoodman]

I wonder if there already is a nikola plug in for this kind of things.
We need to build indices by tags as well.

[rainwoodman]

I added a stub script to build json from rst and rst from json

[kbarbary]

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the grey part).

Could also do something like

[martinjameswhite]

I think all my stuffs licensed ...

On Jun 8, 2015, at 10:56 PM, Kyle Barbary notifications@github.com wrote:

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the gre y part).

Could also do something like

—
Reply to this email directly or view it on GitHub.

[kbarbary]

Great, thanks Martin.

[rainwoodman]

@kbarbary
could you mock up an .rst entry so that I can put it in the convertor?

[kbarbary]

For now, can you just make the converter output an HTML page? e.g.,

<!--.. title: Software.. slug: software.. type: text.. hidetitle: true--><p>BCCP develops open-source software for use in cosmology. Here are some
of our projects:</p><hr><h3>SEP</h3><p>SEP is a Python and C library for source detection and photometry, adapted from the
SourceExtractor code base. It makes the SourceExtractor background and detection algorithms
available directly from Python and (eventually) Julia. &nbsp;
<ahref="http://sep.readthedocs.org">webpage</a> &nbsp;
<ahref="http://github.com/kbarbary/sep">GitHub</a></p><hr><h3>SNCosmo</h3>
...

Let's just get the links into the paragraph and prettify them in a separate step.

[rainwoodman]

BoxRemap and Copter.

Looks like if this page is to scale up, we need to change how the linkref and entries are separated. the current scheme separates the entry and linkref and may be difficult to maintain if we want to split the page or ask others to write pull requests (two hunks vs one)

I've put martin's other suggested link here:

https://github.com/desihub/imaginglss
https://github.com/martinjameswhite/litemangle
https://github.com/mockFactory
https://github.com/wll745881210/CLPT_GSRSD
https://github.com/martinjameswhite/recon_code

[kbarbary]

It looks like neither of these have a license. Perhaps @martinjameswhite can add a license to these? If you don't care, the MIT license is a good default choice. Or there's always www.choosealicense.com if you really want to get into it....

[kbarbary]

To scale this page up, we may want to automatically generate it from a csv or json file or similar, using (1) a script to generate rst, (2) a sphinx extensionedit: forgot this wasn't sphinx! or (3) javascript to populate a HTML table.

But let's wait on that to see how many other pieces of software we get and what the diversity is.

[rainwoodman]

Yes. This reminded me to add proper licenses to my code.

[kbarbary]

Nice 👍

[rainwoodman]

What is needed to generate the page?
"""
Project Name, Icon URL, URL, One sentence description, TAGS
"""

[rainwoodman]

I wonder if there already is a nikola plug in for this kind of things.
We need to build indices by tags as well.

[rainwoodman]

I added a stub script to build json from rst and rst from json

[kbarbary]

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the grey part).

Could also do something like

[martinjameswhite]

I think all my stuffs licensed ...

On Jun 8, 2015, at 10:56 PM, Kyle Barbary notifications@github.com wrote:

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the gre y part).

Could also do something like

—
Reply to this email directly or view it on GitHub.

[kbarbary]

Great, thanks Martin.

[rainwoodman]

@kbarbary
could you mock up an .rst entry so that I can put it in the convertor?

[kbarbary]

For now, can you just make the converter output an HTML page? e.g.,

<!--.. title: Software.. slug: software.. type: text.. hidetitle: true--><p>BCCP develops open-source software for use in cosmology. Here are some
of our projects:</p><hr><h3>SEP</h3><p>SEP is a Python and C library for source detection and photometry, adapted from the
SourceExtractor code base. It makes the SourceExtractor background and detection algorithms
available directly from Python and (eventually) Julia. &nbsp;
<ahref="http://sep.readthedocs.org">webpage</a> &nbsp;
<ahref="http://github.com/kbarbary/sep">GitHub</a></p><hr><h3>SNCosmo</h3>
...

Let's just get the links into the paragraph and prettify them in a separate step.

[rainwoodman]

BoxRemap and Copter.

Looks like if this page is to scale up, we need to change how the linkref and entries are separated. the current scheme separates the entry and linkref and may be difficult to maintain if we want to split the page or ask others to write pull requests (two hunks vs one)

I've put martin's other suggested link here:

https://github.com/desihub/imaginglss
https://github.com/martinjameswhite/litemangle
https://github.com/mockFactory
https://github.com/wll745881210/CLPT_GSRSD
https://github.com/martinjameswhite/recon_code

[kbarbary]

It looks like neither of these have a license. Perhaps @martinjameswhite can add a license to these? If you don't care, the MIT license is a good default choice. Or there's always www.choosealicense.com if you really want to get into it....

[kbarbary]

To scale this page up, we may want to automatically generate it from a csv or json file or similar, using (1) a script to generate rst, (2) a sphinx extensionedit: forgot this wasn't sphinx! or (3) javascript to populate a HTML table.

But let's wait on that to see how many other pieces of software we get and what the diversity is.

[rainwoodman]

Yes. This reminded me to add proper licenses to my code.

[kbarbary]

Nice 👍

[rainwoodman]

What is needed to generate the page?
"""
Project Name, Icon URL, URL, One sentence description, TAGS
"""

[rainwoodman]

I wonder if there already is a nikola plug in for this kind of things.
We need to build indices by tags as well.

[rainwoodman]

I added a stub script to build json from rst and rst from json

[kbarbary]

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the grey part).

Could also do something like

[martinjameswhite]

I think all my stuffs licensed ...

On Jun 8, 2015, at 10:56 PM, Kyle Barbary notifications@github.com wrote:

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the gre y part).

Could also do something like

—
Reply to this email directly or view it on GitHub.

[kbarbary]

Great, thanks Martin.

[rainwoodman]

@kbarbary
could you mock up an .rst entry so that I can put it in the convertor?

[kbarbary]

For now, can you just make the converter output an HTML page? e.g.,

<!--.. title: Software.. slug: software.. type: text.. hidetitle: true--><p>BCCP develops open-source software for use in cosmology. Here are some
of our projects:</p><hr><h3>SEP</h3><p>SEP is a Python and C library for source detection and photometry, adapted from the
SourceExtractor code base. It makes the SourceExtractor background and detection algorithms
available directly from Python and (eventually) Julia. &nbsp;
<ahref="http://sep.readthedocs.org">webpage</a> &nbsp;
<ahref="http://github.com/kbarbary/sep">GitHub</a></p><hr><h3>SNCosmo</h3>
...

Let's just get the links into the paragraph and prettify them in a separate step.

[rainwoodman]

BoxRemap and Copter.

Looks like if this page is to scale up, we need to change how the linkref and entries are separated. the current scheme separates the entry and linkref and may be difficult to maintain if we want to split the page or ask others to write pull requests (two hunks vs one)

I've put martin's other suggested link here:

https://github.com/desihub/imaginglss
https://github.com/martinjameswhite/litemangle
https://github.com/mockFactory
https://github.com/wll745881210/CLPT_GSRSD
https://github.com/martinjameswhite/recon_code

[kbarbary]

It looks like neither of these have a license. Perhaps @martinjameswhite can add a license to these? If you don't care, the MIT license is a good default choice. Or there's always www.choosealicense.com if you really want to get into it....

[kbarbary]

To scale this page up, we may want to automatically generate it from a csv or json file or similar, using (1) a script to generate rst, (2) a sphinx extensionedit: forgot this wasn't sphinx! or (3) javascript to populate a HTML table.

But let's wait on that to see how many other pieces of software we get and what the diversity is.

[rainwoodman]

Yes. This reminded me to add proper licenses to my code.

[kbarbary]

Nice 👍

[rainwoodman]

What is needed to generate the page?
"""
Project Name, Icon URL, URL, One sentence description, TAGS
"""

[rainwoodman]

I wonder if there already is a nikola plug in for this kind of things.
We need to build indices by tags as well.

[rainwoodman]

I added a stub script to build json from rst and rst from json

[kbarbary]

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the grey part).

Could also do something like

[martinjameswhite]

I think all my stuffs licensed ...

On Jun 8, 2015, at 10:56 PM, Kyle Barbary notifications@github.com wrote:

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the gre y part).

Could also do something like

—
Reply to this email directly or view it on GitHub.

[kbarbary]

Great, thanks Martin.

[rainwoodman]

@kbarbary
could you mock up an .rst entry so that I can put it in the convertor?

[kbarbary]

For now, can you just make the converter output an HTML page? e.g.,

<!--.. title: Software.. slug: software.. type: text.. hidetitle: true--><p>BCCP develops open-source software for use in cosmology. Here are some
of our projects:</p><hr><h3>SEP</h3><p>SEP is a Python and C library for source detection and photometry, adapted from the
SourceExtractor code base. It makes the SourceExtractor background and detection algorithms
available directly from Python and (eventually) Julia. &nbsp;
<ahref="http://sep.readthedocs.org">webpage</a> &nbsp;
<ahref="http://github.com/kbarbary/sep">GitHub</a></p><hr><h3>SNCosmo</h3>
...

Let's just get the links into the paragraph and prettify them in a separate step.

[rainwoodman]

BoxRemap and Copter.

Looks like if this page is to scale up, we need to change how the linkref and entries are separated. the current scheme separates the entry and linkref and may be difficult to maintain if we want to split the page or ask others to write pull requests (two hunks vs one)

I've put martin's other suggested link here:

https://github.com/desihub/imaginglss
https://github.com/martinjameswhite/litemangle
https://github.com/mockFactory
https://github.com/wll745881210/CLPT_GSRSD
https://github.com/martinjameswhite/recon_code

[kbarbary]

It looks like neither of these have a license. Perhaps @martinjameswhite can add a license to these? If you don't care, the MIT license is a good default choice. Or there's always www.choosealicense.com if you really want to get into it....

[kbarbary]

To scale this page up, we may want to automatically generate it from a csv or json file or similar, using (1) a script to generate rst, (2) a sphinx extensionedit: forgot this wasn't sphinx! or (3) javascript to populate a HTML table.

But let's wait on that to see how many other pieces of software we get and what the diversity is.

[rainwoodman]

Yes. This reminded me to add proper licenses to my code.

[kbarbary]

Nice 👍

[rainwoodman]

What is needed to generate the page?
"""
Project Name, Icon URL, URL, One sentence description, TAGS
"""

[rainwoodman]

I wonder if there already is a nikola plug in for this kind of things.
We need to build indices by tags as well.

[rainwoodman]

I added a stub script to build json from rst and rst from json

[kbarbary]

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the grey part).

Could also do something like

[martinjameswhite]

I think all my stuffs licensed ...

On Jun 8, 2015, at 10:56 PM, Kyle Barbary notifications@github.com wrote:

Are all the new codes licensed now?

I agree with the removal of the SNCosmo icon. It was out of place given that no other package has an icon. However, I'm not a big fan of the move to lists of links. The list is almost always one item long. If you don't want the title to be the link, I'd suggest putting the links in boxes after the blurb, like

(but without the gre y part).

Could also do something like

—
Reply to this email directly or view it on GitHub.

[kbarbary]

Great, thanks Martin.

[rainwoodman]

@kbarbary
could you mock up an .rst entry so that I can put it in the convertor?

[kbarbary]

For now, can you just make the converter output an HTML page? e.g.,

<!--.. title: Software.. slug: software.. type: text.. hidetitle: true--><p>BCCP develops open-source software for use in cosmology. Here are some
of our projects:</p><hr><h3>SEP</h3><p>SEP is a Python and C library for source detection and photometry, adapted from the
SourceExtractor code base. It makes the SourceExtractor background and detection algorithms
available directly from Python and (eventually) Julia. &nbsp;
<ahref="http://sep.readthedocs.org">webpage</a> &nbsp;
<ahref="http://github.com/kbarbary/sep">GitHub</a></p><hr><h3>SNCosmo</h3>
...

Let's just get the links into the paragraph and prettify them in a separate step.