point at pyramid_viewgroup, todo gardening

2 files changed, 18 insertions, 20 deletions

diff --git a/TODO.txt b/TODO.txt
index 49fbc3425..1953d5382 100644
--- a/TODO.txt
+++ b/TODO.txt
@@ -67,7 +67,8 @@
 
 - ``handler`` ZCML directive.
 
-- Try to get rid of Mako Beaker dependency.
+- Try to get rid of Mako Beaker dependency.  Mail sent to
+  http://groups.google.com/group/mako-discuss (was put into moderation).
 
 - ``docs`` directory for each paster template.
 
@@ -82,8 +83,6 @@
 - Do something about ZODB session chapter: either remove or create a
   pyramid_zodbsessions package.
 
-- repoze.bfg.viewgroup in CMF tutorial
-
 - translationdir ZCML directive use of ``path_spec`` should maybe die.
 
 - Make settings an attribute of.. registry?  request?  Ugh.
diff --git a/docs/tutorials/cmf/actions.rst b/docs/tutorials/cmf/actions.rst
index 8af8e5fd4..a6e33fa59 100644
--- a/docs/tutorials/cmf/actions.rst
+++ b/docs/tutorials/cmf/actions.rst
@@ -4,25 +4,24 @@
 Actions
 =======
 
-In CMF, the "actions tool" along with "action providers" create an
-extensible mechanism to show links in the CMF management UI that
-invoke a particular behavior or which show a particular template.
+In CMF, the "actions tool" along with "action providers" create an extensible
+mechanism to show links in the CMF management UI that invoke a particular
+behavior or which show a particular template.
 
-:app:`Pyramid` itself has no such concept, and no package provides
-a direct replacement.  Actions are such a generic concept that it's
-simple to reimplement action-like navigation in a different way within
-any given application.  For example, a module-scope global dictionary
-which has keys that are action names, and values which are tuples of
-(permission, link).  Take that concept and expand on it, and you'll
-have some passable actions tool replacement within a single application.
+:app:`Pyramid` itself has no such concept, and no package provides a direct
+replacement.  Actions are such a generic concept that it's simple to
+reimplement action-like navigation in a different way within any given
+application.  For example, a module-scope global dictionary which has keys
+that are action names, and values which are tuples of (permission, link).
+Take that concept and expand on it, and you'll have some passable actions
+tool replacement within a single application.
 
-The `repoze.bfg.viewgroup
-<http://svn.repoze.org/repoze.bfg.viewgroup/trunk/>`_ package provides
-some functionality for creating "view groups".  Each view in a
-viewgroup can provide some snippet of HTML (e.g. a single "tab"), and
-individual views (tabs) within the group which cannot be displayed to
-the user due to the user's lack of permissions will be omitted from
-the rendered output.
+The `pyramid_viewgroup <https://github.com/Pylons/pyramid_viewgroup/>`_
+package provides some functionality for creating "view groups".  Each view in
+a viewgroup can provide some snippet of HTML (e.g. a single "tab"), and
+individual views (tabs) within the group which cannot be displayed to the
+user due to the user's lack of permissions will be omitted from the rendered
+output.
 
 The :term:`repoze.lemonade` package provides "list item" support that
 may be used to construct action lists.