discuss: Thread: status update on LDP needed tasks

Hello all,

>  * Acceptable formats:  We might consider accepting alternate input formats.

Disposition:  Done.

Since January, I have expanded the format list so that there's no 
technical hurdle to accepting Asciidoc and (stock) DocBook 5.0.

And, of course, we can always consider additional accepted source 
formats.  I hope with the software architecture I have chosen, it 
will not be too tricky to support another format, if we wish.


>  * Script review: Review Martin's suggested publication script (and Makefile).

Disposition:  Done.

  https://github.com/martin-a-brown/python-tldp

This software is now rewritten in Python and "done" (as far as any 
software is ever done).  Tested, packageable and working on Debian 
and OpenSUSE platforms.

Bug reports and/or code review happily accepted!


>  * Website overhaul:  We could use a public face refresh.
>    Task deliverable:  New look and/or website.
>
>    Size:  Medium to Large.

Disposition:  Open.

We could choose to use the (already installed moin-moin) wiki, 
static files, a content management system (CMS) or even  stick 
with the static files we have today.

Whatever we end up choosing, the main files/content should probably 
be checked into a version control system or backed up from a 
wiki/CMS.  Right now, they only exist in the TLDP content area.

Is anybody interested in undertaking / sharing the website overhaul?  
I'm quite familiar with backend processing systems, networks, data 
wrangling and even sysadmin work, but the choice of tooling in the 
website creation arena is not my forte.


>  * Consistency check:  Consistency check on all LDP policy and process
>    documents.  Sources: (relative to tLDP/LDP/LDP):
>
>      faq/docbook/LDP-FAQ.xml
>      howto/docbook/LDP-Reviewer-HOWTO.xml
>      guide/docbook/LDP-Author-Guide/LDP-Author-Guide.xml
>      http://www.tldp.org/manifesto.html
>      http://www.tldp.org/jobdesc/
>      http://wiki.tldp.org/LdpStaff
>      http://tldp.org/vlist.html
>      http://tldp.org/copyright.html
>      http://tldp.org/COPYRIGHT.html
>
>    Size:  Medium to Large.

Disposition:  Open.

No change here--but, the deduplication of statements and imposition 
of consistency seems integrally tied to any website overhaul we 
would undertake.


>  * Metadata format: Open Source Metadata Framework (OMF) is defunct.
>    Size:  Large.

Disposition:  Open.

I have had a look through some of the possibilities for metadata 
formats that are used around DocBook (DublinCore/DCMI), publishing 
(ONIX, MARC, DCMI) and general web content (RDFa, other 
microformats).

None of these seem to address the LDP's main metadata questions.

I mused here aloud about what metadata we want to store.  I have 
been thinking about this myself and will bring this up in a separate 
thread.


>  * Review coordination:
>    Task deliverable:  Presence and communication!

Disposition:  Ongoing.

There are two documents that were submitted in late 2015 that have 
seen some attention recently.

  Linux Android HOWTO by Guido Gonzato
    Both JDD and Randy Kramer are having a gander at this document.

  RTC Quickstart Guide by Daniel Pocock
    I completed a markup review and also did a cursory technical 
    review.  I sent my comments along to Daniel Pocock.


>  * HTML CSS file:  Create to provide consistent look of website and docs.
>    Size:  Small?

Disposition:  Open.

I still think it might be nice to find or use some utterly basic CSS 
to style our documents the same way across our collection.  I like 
the idea of all of our documents appearing with a consistent look.

-Martin

-- 
Martin A. Brown
http://linux-ip.net/