Re: bug updating a bug in your issue tracker

Vladimir> For example, in your latest message about Mercurial revision Vladimir> numbers, I see that you, in a previous message, provided a Vladimir> recipe for setting the menubar font. That belongs under the Vladimir> topics "The Menubar", "Fonts", and "X Defaults and xrdb". (Of Vladimir> course, any information entered should be entered in *one* Vladimir> place only, and all other entries should be links.) I was going to suggest adding this to EmacsWiki, but reading http://www.emacswiki.org/emacs/AppropriateMedia reminded me that the Info pages would be a better place for user how-to documentation. It's more work to add little nuggests, but in the long run I think it's better to have a simple model for where and how to find information. If we have multiple information collections, each of which may or may not have the information someone is looking for, people will just end up using Google. And in that case we might as well just leave the information in the mailing list archives. (I'm assuming that the archives are indexed; I haven't checked.) Vladimir> Another example: Once the whole Mercurial revision number Vladimir> topic settles down, whatever is decided should be captured in Vladimir> the wiki as well. Yeah, I could see this going into a wiki or someplace on xemacs.org. I see that http://www.xemacs.org/About/Website.html does have information on how to contribute website patches. It looks a little intimidating to me, but I haven't actually tried to contribute website patches yet. I don't have strong opinions about using a wiki versus using the CVS-based workflow that the website uses. A wiki makes it easier for people to contribute, but it's harder to use offline. mike _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta