On 4 Jan., 00:09, mabshoff <mabsh...@googlemail.com> wrote:
> Hi,
>
> I have been cleaning up the wiki of Spam and unfortunately on occasion
> I am removing content that isn't spam, i.e. I removed the art page.
> But fortunately none of the content is lost, so please let me know if
> anything is missing and I will restore it. The deactivated content
> isn't deleted, so it will be possible to recover that info for the
> foreseeable future. I already did so for the art page, so sorry
> mhampton :)
>
> One thing that is an issue currently is that there is no overall
> structure to the content, the "art" page being a good example. While
> some things are well organized, i.e. Sage Days, Bug Days and so on are
> all in their own directory structure the SPKG listings are a mess.
>
> We currently have the following pages:
>
> *http://wiki.sagemath.org/standard_packages_available_for_SAGE
> *http://wiki.sagemath.org/optional_packages_available_for_SAGE
> *http://wiki.sagemath.org/experimental_packages_available_for_SAGE
> *http://wiki.sagemath.org/SPKG_Audit
> *http://wiki.sagemath.org/Sage_Spkg_Tracking
>
Hi Michael,
the bulk of the information on http://wiki.sagemath.org/SPKG_Audit
went into my rewrite of Chapter 8 of the Sage Developer's Guide, see
my patch(es) at http://sagetrac.org/sage_trac/ticket/4857 from end of
December.
I wanted to ping you for a review of this only after the ReST
transition, but now that you are taking care for the spkg
documentation anyway ... there might be synergies, e.g. the SPKG.txt
Template becoming a part of the Sage distribution itself.
BTW:
There is a misnamed link in http://wiki.sagemath.org/SPKG_Audit which
should read "SPKG.txt" Template instead of "spkg-install" Template or
something very similar. I can't copy'n and paste it right now, because
I get the following error message:
{{{
Warning:
You triggered the wiki's surge protection by doing too many requests
in a short time.
Please make a short break reading the stuff you already got.
When you restart doing requests AFTER that, slow down or you might get
locked out for a longer time!
}}}
(what's that about? I certainly am not aware of producing any heavy
traffic?), but you certainly know what I mean.
Cheers,
gsw
> The information provided by all theses pages overlaps and all but the
> last two are badly outdated and link to content in the wiki I consider
> obsoleted by info linked from Sage_Spkg_Tracking in many cases. I
> would like to delete those pages like
>
> http://wiki.sagemath.org/lie
>
> for example and instead merge that info into the SPKG.txt of the
> lie.spkg which in turn will then appear in wiki.sagemath.org/spkg/lie.
> Obviously for many of the spkgs, even the standard ones, a better
> SPKG.txt needs to be written and I made that part of my ToDo List for
> SD 12. I have generally been cleaning up SPKG.txts as I go along, but
> I haven't gotten around to fixing them all. As some of you have
> experienced recently a badly formatted or incomplete SPKG.txt will get
> you a "needs work" during review, so just like "100% doctest coverage"
> I see a good SPKG.txt as mandatory to get any spkg updated.
>
> But I am also unhappy about the structure and also the name of
> Sage_Spkg_Tracking, i.e. it is a table, but should be a list of lists
> IMHO. One piece of information that could be easily added when it
> would be a list of lists is a textual description of up to a couple
> sentences for each spkg.
>
> So I propose to do the following: consolidate the above five pages
> into two:
>
> * one page with a listing of SPKGs called spkg/listing
> * one page with all the technical information called spkg/howto
>
> I would do all the work, but before I go off and do things I figured
> it would be worth it to request feedback. When those two pages are
> done I would then delete the other five pages and as things are
> incorporated into the to be written spkgs I would then also delete
> most of the current place holder wiki pages for the individual
> packages. There are some pages like the Axiom one which has more info
> than should go into the SPKG.txt of the FriCAS.spkg, so that one would
> survive.
>
> Thoughts?
>
> Cheers,
>
> Michael
>
> FYI - here is my ToDo list for SPKG.txt from all standard SPKGs - note
> that some spkgs still do not have *any* SPKG.txt at all, but those
> aren't listed:
>
> * ecm: "inital version" - needs fixing
> * genus2reduction: update missing section
> * gsl: slight restructuring is needed
> * palp - needs complete rewrite
> * pexpect - needs complete rewrite
> * polybori: small formatting issues for maintainers, Umlaut in
> Burcin's name
> * numpy: needs cleanup, "====" is used in the Changelog
> * ipython: Indentation for "== Dependencies ==", make "Mike Hanson"
> main spkg maintainer,
> formatting issue for "ipython-0.8.4.p0"
> * sphinx: trailing space at the end, dependency list needs standard
> format
> * sqlite: needs complete rewrite
> * singular: cleanup, add missing sections
> * mpfi: needs serious cleanup work
> * readline: add missing sections, cleanup
> * scipy: cleanup
> * quaddouble: clean up, but will be deprecated anyway
> * matplotlib: Changelog has some mismatched "==" vs. "==="
> * docutils: white space, changelog entries
> * pygments: white space, changelog entries
> * pynac: newlines, remove "@" to protect against Spam
> * twisted-8.1.0.p1: cleanup, missing sections
> * conway polynomials: needs complete rewrite
> * libpng: needs loads of info
> * cython: release history missing
> * libm4ri: white space issue in SPKG.txt at the bottom, "@" problems
> * libgpg_error: add missing info
> * NetworkX: add missing sections
> * clisp-2.46.p7: cleanup
> * pycrypto: complete rewrite
> * jinja: small stylistic issues
> * tachyon: cleanup
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
