#1751: Links to DEPRECATED.pod et al
-------------------------------------+--------------------------------------
Reporter: Paul C. Anagnostopoulos | Owner: jkeenan
Type: todo | Status: assigned
Priority: normal | Milestone:
Component: docs | Version: 2.6.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
-------------------------------------+--------------------------------------
Changes (by jkeenan):
* cc: cotto, Coke (added)
Comment:
Replying to [comment:2 Paul C. Anagnostopoulos]:
> I'd go a little more radical.
Well, note that I recommended proceeding step-wise. It may ultimately
prove beneficial to merge all those pages into one. But let's first get a
single page that describes what has been deprecated when, and get other
people's reactions to that.
>
> I'd change DEPRECATED.pod so it simply refers to the wiki page.
[snip]>
> Is it possible to make the wiki page part of the source and install it
after each official build? If so, then that would solve the wiki versus
DEPRECATED.pod duplication.
I believe ''DEPRECATED.pod'' should remain the official source for what is
scheduled for deprecation. In part, this is for historical continuity: I
think most of our core developers think first in terms of going to the
source code and only secondarily of going to the wiki.
(kid51 is more skeptical than others of the usefulness of wikis. I've
found them useful when preparing for events to be held at a specific point
in time, such as YAPCs and F2F hackathons. I find them less useful for
ongoing project documentation for reasons very similar to those which
generated this ticket: Wikis sprawl. Individual pages are not kept up-
to-date. Links are not kept up-to-date. And you spend a lot of time
typing formatting instructions and previewing pages -- a lot more
keystrokes than simply typing in source code files. But setting my
personal opinions aside ...)
So I'd like first to see what content from [wiki:Deprecation] can be moved
over to [wiki:ParrotDeprecations]. Then we should here from other
committers, particularly from people who have been more involved in
setting up these pages than I have, e.g., cotto and Coke.
Thank you very much.
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1751#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
