RFE: Add tool for documentation's catalog on reviewing documentation



16 years ago
12 years ago


(Reporter: WeirdAl, Assigned: WeirdAl)





16 years ago
I have an idea for an enhancement to www.mozilla.org/catalog which places a
database underneath the catalog and allows us to track when a document was
reviewed for accuracy and what Bugzilla bug number applies to that bug.

This bug is for creating the database layer in the catalog.  The first phase of
this bug is for me to create a proposed MySQL database and PHP/XHTML scripts for
that database.  The second phase of this bug is for jkeiser to translate the PHP
scripts into Perl scripts for inclusion as a new tool for mozilla.org.


16 years ago
Blocks: 151952

Comment 1

16 years ago
Well, I've got a broken setup.  But hopefully it'll be a good starting point for

http://jslab.org/mozcatalog/addPage.php.txt -- the script dies in the first
MySQL query.  Something is not working right.

http://jslab.org/mozcatalog/addPage.html -- for an HTML template (missing a
submit button)
http://jslab.org/mozcatalog/addPage.js -- the JavaScript
http://jslab.org/mozcatalog/mysql.php.txt -- for connecting to the MySQL db
(it's written for my machine, not yours)
http://jslab.org/mozcatalog/mozcatalog.mysql -- a MySQL query for creating the

Comment 2

16 years ago
Reassigning to jkeiser:  this has to be written in Perl, my insert query is
broken for reasons I don't understand, he's motivated and understands what needs
to be done.
Assignee: jscript → jkeiser

Comment 3

16 years ago
Okay, quick summary of a hot debate:

It seems better to track our documentation via Zope, except dawn is requiring
CVS blame tracking.  So our current consensus may be to hack Zope to log into
the CVS tree that Mozilla uses, and track our documentation through Zope, with
comments showing who's actually doing the changes via CVS.

Comment 4

16 years ago
jkeiser thinks it would be easier and better to build cvs blame natively into
Zope.  Opinions?

Comment 5

16 years ago
<irc:quote author="jkeiser">
Make Zope Work. runyaga is asking about the easiest way to do the cvs mirroring
we want, but given that there are existing CVS impls out there cvsblame should
not be a problem.

runyaga is going to set some things up on his server, and I'm going to test an
install of bonsai to see if I can get it to work. Hmm, mozwebtools would know
who knows how to set that up, maybe they could help.

The long and short of it--well the short anyway--is that we want to get cvs
blame up to keep existing functionality, and that Zope can do everything all of
us wants with existing Zope functionality, so we should Go There.

Comment 6

16 years ago
jkeiser:  mind if I take this bug back from you? :) I've recently started 
reworking my PHP/MySQL approach to the catalog.  I currently have a script to 
dump the current catalog to a MySQL database, and I'm working on tools to 
maintain it and output the catalog (both in a static page set for those who 
won't be logging in, and in dynamic pages for those who do log in).

Comment 7

16 years ago
w/ jkeiser's permission.

Comment 8

16 years ago
Really reassigning.
Assignee: jkeiser → ajvincent
This isn't really a server ops bug.  There's nothing for ops to do until someone
has an app written and you need somewhere to install it.  Until such time this
is just tracking a generic project.
Component: Server Operations → Miscellaneous
Updating QAContact of all Miscellaneous bugs to miscellaneous@mozilla-org.bugs. If this particular bug should have a different QAContact, please change it and accept my apologies.
QA Contact: myk → miscellaneous

Comment 11

12 years ago
This bug is dead, obsolete and buried.  ->WONTFIX.
Last Resolved: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.