Update ecosystem upload docs (CPAN).

As explained here: https://rakudo.party/post/CPAN6-Is-Here

Author: Patrick Sebastian Zimmermann

doc/Language/modules.pod6

@@ -423,21 +423,29 @@ If you've written a Perl 6 module and would like to share it with the
 community, we'd be delighted to have it listed in the L<Perl 6 modules
 directory|https://modules.perl6.org>. C<:)>
 
-For now, the process requires that you use git for your module's version
-control.
+Currently there are two different module ecosystems (module distribution
+networks) available:
 
-The instructions herein assume that you have a
-L<GitHub|https://github.com> account so that your module can be
-shared from its GitHub repository, however another provider such as
-L<GitLab|https://about.gitlab.com/> should work as long as it works in
-a similar way.
+    =item B<CPAN>
+    This is the same ecosystem Perl5 is using. Modules are uploaded as I<.zip>
+    or I<.tar.gz> files on L<PAUSE|https://pause.perl.org/>.
 
-To share your module, do the following:
+    =item B<p6c>
+    Up until recently the only ecosystem, but soon to be deprecated. It is based
+    on Github repositories which are directly accessed. It has only limited
+    capability for versioning.
+
+The process of sharing your module consists of two steps, preparing the module
+and uploading the module to one of the ecosystems.
+
+=head2 Preparing the Module
+
+For a module to work in any of the ecosystems, it needs to follow a certain
+structure. Here is how to do that:
 
     =item Create a project directory named after your module. For
     example, if your module is C<Vortex::TotalPerspective>, then create a
-    project directory named C<Vortex-TotalPerspective>. This project
-    directory name will also be used as the GitHub repository name.
+    project directory named C<Vortex-TotalPerspective>.
 
     =begin item
     Make your project directory look like this:
@@ -447,14 +455,13 @@ Vortex-TotalPerspective/
 |-- lib
 |   `-- Vortex
 |       `-- TotalPerspective.pm
-|-- doc
-|   `-- Vortex
-|       `-- TotalPerspective.pod6
 |-- LICENSE
 |-- META6.json
 |-- README.md
 `-- t
     `-- basic.t
+
+
 =end code
 
     If your project contains other modules that help the main module do
@@ -504,15 +511,23 @@ lib
     https://design.perl6.org/S26.html> markup inside your modules. Module
     documentation is most appreciated and will be especially important once
     the Perl 6 module directory (or some other site) begins rendering Pod docs
-    as HTML for easy browsing.
+    as HTML for easy browsing. If you have extra docs (in addition to the
+    Pod docs in your module(s)), create a C<doc> directory for them. Follow
+    the same folder structure as the C<lib> directory like so:
+
+    =begin code :skip-test
+    doc
+    `-- Vortex
+        `-- TotalPerspective.pod6
+    =end code
+
     N«
         Note, described above is a minimal project directory. If your project
         contains scripts that you'd like distributed along with your module(s),
-        put them in a C<bin> directory. If you have extra docs (in addition to the
-        Pod docs in your module(s)), create a C<doc> directory for them. If you'd
-        like a graphical logo to appear next to your module at the module
-        directory, create a C<logotype> directory and put into it a C<logo_32x32.png>
-        file. At some point, you might also consider adding C<CONTRIBUTORS>, C<NEWS>,
+        put them in a C<bin> directory. If you'd like a graphical logo to
+        appear next to your module at the module directory, create a
+        C<logotype> directory and put into it a C<logo_32x32.png> file. At some
+        point, you might also consider adding C<CONTRIBUTORS>, C<NEWS>,
         C<TODO>, or other files.
     »
 
@@ -523,7 +538,7 @@ lib
     {
         "perl" : "6.c",
         "name" : "Vortex::TotalPerspective",
-        "version" : "0.1.0",
+        "version" : "0.0.1",
         "description" : "Wonderful simulation to get some perspective.",
         "authors" : [ "R<Your Name>" ],
         "license" : "Artistic-2.0",
@@ -560,7 +575,7 @@ lib
     C<%?RESOURCES> Hash indexed on the name provided.
 
     The L<Test::META module | https://github.com/jonathanstowe/Test-META/>
-    can help you check the correctness of the META.info file.
+    can help you check the correctness of the META6.json file.
 
     There are more fields described in the L<META design documents |
     https://design.perl6.org/S22.html#META6.json>, but not all of these are
@@ -570,10 +585,70 @@ lib
 
     =end item
 
+    =begin item
+    To test your module you can use the following command to install the
+    module directly from the module folder you just created.
+
+    =for code :lang<shell>
+    zef install ./your-module-folder
+
+    =end item
+
+=head2 Upload your Module to CPAN
+
+Uploading a module to CPAN requires having a L<PAUSE|https://pause.perl.org/>
+user account. If you don't have an account already go there and apply for an
+account. The process takes about 5 minutes and some e-mail back and forth.
+
+    =begin item
+    Create a package of your module:
+
+    =begin code :lang<shell>
+    cd your-module-folder
+    tar czf Vortex-TotalPerspective-0.0.1.tar.gz --transform s/^\./Vortex-TotalPerspective-0.0.1/ --exclude-vcs --exclude=.[^/]*
+    =end code
+
+    If you use git you can also use the following command to create a package directly for a given commit.
+
+    =for code :lang<shell>
+    git archive --prefix=Vortex-TotalPerspective-0.0.1/ -o ../Vortex-TotalPerspective-0.0.1.tar.gz HEAD
+
+    =end item
+
+    =item Go to L<PAUSE|https://pause.perl.org/>, login and click on
+    L<Upload a file to CPAN|https://pause.perl.org/pause/authenquery?ACTION=add_uri>.
+
+    =item Make sure you select C<Perl6> in the select input box.
+
+    =begin item
+    Select your file and click I<Upload>!
+
+    N«
+        Make sure you have a META6.json file in your dist and that the dist
+        version you're uploading is higher than the currently uploaded version.
+        Those are the most common upload errors.
+    »
+
+    =end item
+
+=head2 Upload your Module to p6c
+
+N«
+    The I<p6c> ecosystem is soon to be deprecated, so you should consider
+    using the I<CPAN> ecosystem instead.
+»
+
+If you want to use the I<p6c> ecosystem you need to use git for your module's
+version control. The instructions herein assume that you have a
+L<GitHub|https://github.com> account so that your module can be shared from its
+GitHub repository, however another provider such as
+L<GitLab|https://about.gitlab.com/> should work as long as it works in a
+similar way.
+
     =item Put your project under git version control if you haven't done so
     already.
 
-    =item Once you're happy with your project, create a repository for it at GitHub.
+    =item Once you're happy with your project, create a repository for it on GitHub.
     See L<GitHub's help docs|https://help.github.com/> if necessary. Your
     GitHub repository should be named the same as your project directory. Immediately
     after creating the GitHub repo, GitHub shows you how to configure your
@@ -612,26 +687,6 @@ know where to look for the module file(s).
 You can find a list of modules and tools that aim to improve the experience of
 writing/test modules at L<Modules Extra|/language/modules-extra>
 
-=head1 The Future of the Ecosystem
-
-L<https://modules.perl6.org> and github-based infrastructure is temporary. The
-plan is to establish something similar to Perl 5's PAUSE/CPAN/MetaCPAN
-infrastructure. B<Volunteers needed!>
-
-The rough plan is:
-
-=for code :skip-test<should be numbered items>
-1. fix EVAL precomp bug (nine)
-2. get Repository API straight
-3. get zef up to speed
-4. continue with the metacpan fork for perl6 (jdv79)
-
-The repository with jdv's fork can be found at L<https://github.com/jdv/metacpan-web>
-
-You can also already upload your Perl 6 modules to
-L<Perl 5's PAUSE|https://pause.perl.org/>, selecting `Perl6` directory during the
-upload. That will ensure your module is indexed in Perl 6's space and not Perl 5's.
-
 =head2 Contact Information
 
 To discuss module development in general, or if your module would