[Mailman-Developers] Mailman-Developers Digest, Vol 286, Issue 7

[Chris Cargile]

To pair with Sandesh's sharing that the python-version-requirement in the
documentation needed updating and to coincide with Paul's (brave :)
commitment, I would like to know what the "must-do"s are, and later more
specifically, the processes for updating the build documentation in its
various places:

- while each component of MM3 )archiver, UI...) should be entitled to its
own separate documentation for modularity and sanity of the developers,
what would be considered the best practices for documentation as a whole?
 This is one of my first dives into software development in a
group-oriented/open-source env't but in non-profit organizations I
volunteer-served and administrated, clear and systematic process flows were
helpful (to help me stay focused)

- IOW, could we assume the wiki.list.org is the de facto location for
overall MM3 documentation and that bzr or pythonhosted.org would be where
the individual component's documentation should be maintained for now?

At minimum, I think it is important to get confirmation whether the
confluence snapshot (wiki.list.org) is just a snapshot and we can direct
our efforts at updating the documentation there? also, on that note, what
would be the sphinx documentation role in all this and/or how necessary is
it to understand that system?

Finally, for the confluence system, I noticed there is more of a total CMS
offering vs. just the wiki functionality and wanted to know will the blog
etc be maintained disparately after we move to a moin system?

This is a lot but I'm trying to get to speed - on the fun side, I'm making
my first update to add me on the remote-attendees list for the upcoming
pysprints

Cheers,
Chris


On Mon, Feb 25, 2013 at 6:00 AM, <mailman-developers-request at python.org>wrote:

> Send Mailman-Developers mailing list submissions to
>         mailman-developers at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mail.python.org/mailman/listinfo/mailman-developers
> or, via email, send a message with subject or body 'help' to
>         mailman-developers-request at python.org
>
> You can reach the person managing the list at
>         mailman-developers-owner at python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Mailman-Developers digest..."
>
>
> Today's Topics:
>
>    1. Wiki Migration Update (Paul Boddie)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 25 Feb 2013 00:01:17 +0100
> From: Paul Boddie <paul at boddie.org.uk>
> To: mailman-developers at python.org
> Subject: [Mailman-Developers] Wiki Migration Update
> Message-ID: <201302250001.18261.paul at boddie.org.uk>
> Content-Type: text/plain;  charset="us-ascii"
>
> Hello,
>
> This is really just a quick mail to let you know that I haven't forgotten
> about my promise to look into migrating the Wiki content to MoinMoin. As
> always, you can monitor the status of the work here:
>
> http://hgweb.boddie.org.uk/ConfluenceConverter/
>
> I aim to upload a snapshot of the translated content to a demonstration
> site
> (as I did before) in the next few days, and hopefully will have improved
> the
> output a bit by then. Although I have mostly been focusing on the old
> Confluence Wiki markup in the past couple of days, I think that the recent
> changes have improved the "fidelity" of the old page revisions somewhat,
> and
> with the new XHTML-style markup being somewhat easier to deal with, I aim
> to
> have parity between the two formats fairly soon.
>
> If there's anything in particular beyond basic content migration that you'd
> like to see in MoinMoin, please let me know. The markup mapping page...
>
> http://moinmo.in/ConfluenceConverter/DevelopmentNotes/MarkupMapping
>
> ...describes some macros and other features that should be reproduced in
> the
> Moin-based solution, and I've attempted to incorporate existing page
> comments
> (as I described before) and page navigation features, but it would be
> useful
> to know what people currently depend upon so that any extra macros or
> extensions can be written.
>
> I'll send another update soon. Thanks for being patient!
>
> Paul
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
>
>
> ------------------------------
>
> End of Mailman-Developers Digest, Vol 286, Issue 7
> **************************************************
>