2000-08-04: Status of http://sourceforge.net/projects/xemacs/

APA> Hello All! Here's a real short update, focused on http://xemacs.sourceforge.net/ APA> This is intended to be a bootstrapper for anybody interested in APA> getting started on the sourceforge half of XEmacs development. APA> Q: Has XEmacs development moved to sourceforge? APA> A: No. Currently there is only one CVS module on sourceforge, namely APA> xemacsweb. This is the content of APA> xemacweb＠www.xemacs.org:~/genpage which prduces most of the static APA> content of xemacweb＠www.xemacs.org:~/docs. Mailing list and their APA> archives, for one, have not been moved to sourceforge. APA> Q: Which is the offical XEmacs Website? APA> A: For a transitional period of at least two weeks it is good old APA> http://www.xemacs.org. To visit the new site (and receive bonus points APA> for testing) go to http://xemacs.sourceforge.net/, either directly, APA> or via "Project Homepage" from APA> https://sourceforge.net/projects/xemacs/. Thereafter, if all goes APA> well, http://xemacs.sourceforge.net/ will answer for APA> http://www.xemacs.org if someone puts in the work to make it so APA> (http://sfdocs.sourceforge.net/sfdocs/display_topic.php?topicid=33). APA> Q: So what's so exciting about the new site? APA> A: It is fully CVS-controlled, all HTML documents are batch-validated APA> daily using XEmacs/PSGML by xemacsweb/Makefile according to their APA> individual DTD. Alltogether there are <10 HTML errors left between APA> all .html files on the XEmacs site there! APA> Q: When can I contribute to XEmacs website content again? APA> A: Now. Get yourself a sourceforge account via APA> https://sourceforge.net/account/register.php and contact one of APA> your friendly XEmacs admins to become a developer, using APA> https://sourceforge.net/project/memberlist.php?group_id=11. Meanwhile I have added Real Name: Andrew J Cosgriff Email Addr: ajc at users.sourceforge.net and Real Name: Kevin Oberman Email Addr: koberman at users.sourceforge.net to the list of xemacs developers on sourceforge on their request. APA> Q: How do I make changes to the XEmacs CVS repository on sourceforge? APA> A: Follow instructions in https://sourceforge.net/cvs/?group_id=11 to APA> checkout (20MB after running make) and commit the sources via CVS. APA> Q: How can I keep track of changes being made to the repository? APA> A: Subscribe yourself to xemacs-checkins(a)lists.sourceforge.net[1] at APA> http://lists.sourceforge.net/mailman/listinfo/xemacs-checkins. We APA> may even subscribe xemacs-cvs(a)xemacs.org to the list, if somebody I haven't got any feedback on this. Unless people say otherwise I will subscribe xemacs-cvs(a)xemacs.org to xemacs-checkins(a)lists.sourceforge.net This makes sense since xemacsweb patches are also sent to and reviewed on xemacs-patches(a)xemacs.org. APA> can send back a confirmation reply from there. The mailing list APA> archive at APA> http://www.geocrawler.com/lists/3/SourceForge/5231/0/4114662/ is APA> actually updated quite switfy (> 30 minutes?). APA> Q: How do I inspect the state of the actual files behind APA> http://xemacs.sourceforge.net/? APA> A: Read APA> http://sfdocs.sourceforge.net/sfdocs/display_topic.php?topicid=8 APA> for reference, although steps 1 .. 7 are already done. APA> Webpage contents are physically rooted at APA> shell.sourceforge.net:/home/groups/xemacs/htdocs where htdocs is APA> currently a symlink to xemacsweb. APA> Q: How do these pages get updated? This was my most active area recently. With help from Martin R. Buchholz I was able to implement updating of the XEmacs website at http://xemacs.sourceforge.net/ via cvs commit directly! All of this is done on behalf of user xemacs and the crontab entry for adriana has been disabled. The delay in commiting is not noticable for me (takes much longer for me until the passphrase prompt appears). Due to a substancial Makefile change we can even effort to HTML-validate always after a commit. CVS update and make are kicked off by cvs commit to cvs.sourceforge.net, but these processes are run in background on shell1.sourceforge.net to avoid locking up the CVS repository (as suggested in the CVS manual). The Makefile now only validates any HTML files younger than the validate-time-stamp touched after validation. Furthermore the genpage rule is now depending on CONTENT_FILES only. Since genpage output goes to the current directory, copying of files is not needed. genpage now only takes care of those HTML files generated from .content source files. genpage had to be patched to check file mtime to the second, not just to the day to avoid needless HTML file updates causing wasteful HTML validation via XEmacs. I will submit my genpage changes (I imported genpgage 1.0.7 on a vendor branch for ease of future updates) to the author. Please send me any feedback on the current commit/update process, especially actual problems you may experience. http://xemacs.sourceforge.net/cvs-update-make.err contains site update logs, for those who know it exists :-) This can come in handy and reduces the need to login to shell1.sourceforge.net even further. APA> A: They are currently being updated a personal crontab entry of mine APA> (temporarily, until Martin hand-holds me through direct updates APA> from cvs commits). Here's[2] that crontab entry (as others may not APA> have the privelege to look at it with "crontab -u adriana -l", APA> which doesn't work even for me). This gets mailed to APA> xemacs-checkins(a)lists.sourceforge.net for now. APA> xemacs-webmaint(a)xemacs.org may be a better destination when I have APA> fixed ALL validation errors (there are still FIVE!). Above paragraph is history! APA> Q: What editor can I use on shell.sourceforge.net? APA> A: ed, when you use ssh. :-) I have installed a pretty well-featured APA> XEmacs-21.1.11 under APA> shell.sourceforge.net:/home/groups/xemacs/tools/xemacs/bin for all APA> of us to use. See ~adriana/.profile for my setup. I also had to APA> get a decent tty for Windows NT for XEmacs to run, be it -nw even. APA> I installed APA> http://www.chiark.greenend.org.uk/~sgtatham/putty/latest/putty.exe APA> and am quite happy with it. APA> Q: Can I upload big files to some kind of /pub on sourceforge? APA> A: Yes, developers can copy files to APA> <user>＠shell1.sourceforge.net:/home/groups/ftp/pub/xeemacs using APA> scp1. Anyone can download from this URL: APA> ftp://xemacs.sourceforge.net/pub/xemacs/[3] APA> Q: How much did Adrian sleep lately? APA> A: Permission denied. APA> I hope this will be helpful to others. APA> We should probably start assigning jobs between us to further APA> development on sourceforge. Trey and John have been very quiet lately. Are you guys still around? APA> A big task would be conversion of mailing list interfaces and APA> archives, although I am not sure we want to move them away from APA> xemacs.org. What's the managerial plan for the mailing list interfaces and archives? Should these move to sourceforge too? APA> Making all URLs in xemacsweb relative is on our collective to-do list. APA> genpage should come to our aid here. More on that later. Hah, I have converted all links (except for xemacsweb/FAQ) to relative. This makes links in xemacsweb/Architecing-XEmacs/ work and I can use Netscape to navigate thru the documents in my local xemacsweb working directory. This is pretty cool! Most notably the image links included via template.html are broken in all subdir HTML files generated from subdir .content files. A fix for this will be devised shortly via a genpage recipe. APA> Any comments? APA> Adrian Best regards, Adrian -- Adrian Aichner <adrian(a)xemacs.org&gt;