I wouldn't change that design constraint to support this, but publican could provide the capability to link in to external feedback-capturing mechanisms. Off the top of my head, one approach would be to conditionally allow books to be configured as feedback=mechanism, where mechanism is a pluggable option. For Red Hat use, we could build a bugzilla feedback extension, which would inject code into the output (probably just for html) allowing you to leave feedback for a particular chapter/section. This would be static output, providing a deep link into bugzilla with the appropriate component, version etc. to match the book filled out. Plugins could be developed for any other feedback mechanism people want to use.
David ----- Original Message ----- From: "Jeffrey Fearn" <jfe...@redhat.com> To: spa...@fedoraproject.org, "Publican discussions" <publican-list@redhat.com> Sent: Thursday, October 21, 2010 4:03:31 PM GMT +10:00 Brisbane Subject: Re: [publican-list] Open Feedback Publishing System (OFPS) Eric "Sparks" Christensen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jared pointed out a neat "feature" O'Reilly is trying out called Open > Feedback Publishing System (OFPS)[1]. This allows readers to leave > comments on a particular paragraph of a document. > > Contrary to its name, OFPS is NOT open source. There are other projects > that are open source that do the same thing. The one I saw listed was > called Wooki[2]. > > I'm wondering if something similar could be implemented within Publican > to be used, at a minimum, in our draft documentation. It might make it > easier for people to let us know of problems without filing a bug. > Because it would take less time to leave feedback we might find that we > receive more than we currently do through BZ. > > [1] http://labs.oreilly.com/ofps.html > [2] http://wookicentral.com One of the founding constraints to Publican design is that there is no server side scripting. I don't see how you could do this without doing server side scripting and processing of some kind. It would require a major change in direction for Publican to become a web service instead of a static content provider. Cheers, Jeff. -- Jeff Fearn <jfe...@redhat.com> Software Engineer Engineering Operations Red Hat, Inc Freedom ... courage ... Commitment ... ACCOUNTABILITY _______________________________________________ publican-list mailing list publican-list@redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican _______________________________________________ publican-list mailing list publican-list@redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican
