(ack, resending form the proper email account, apologies if this duplicates, moderators feel free to delete the other one)
Hello All, at TPAC Mike Smith indicated to me that he wants to decommission the server at dvcs.w3.org. Given that it’s an old machine running an old, insecure OS and an old version of Mercurial, I agreed (not to mention that the machine hasn’t been entirely stable). So, starting immediately, the official repository for FXTF editor’s drafts is now: https://hg.fxtf.org/drafts/ The old repository at https://dvcs.w3.org/hg/FXTX has been deleted. If you have an existing clone of the repo, you can simply edit the file ‘.hg/hgrc’ in the repo and change the [path] default = url to the new one (and the default-push url if you have one in there). Alternatively you can simply start with a fresh clone of the repo from the new URL. Since I don’t have access to the W3C account database, the login username and password you’ll have to use will be the same as your account oncsswg.org (wiki, Shepherd, etc). If you’re already set up for access to the CSSWG test repository, you should be good to go. If not, see the instructions on the wiki: https://wiki.csswg.org/tools/hg#setting-up-mercurial-preferences Please note: be sure that the username configured in your Mercurial .hgrc file contains the same email address (or alternate email address) you have set in your account on csswg.org. All CSSWG members with write access to the wiki should also have write access to the FXTF draft repo. If you have any difficulty accessing the new repo, please contact me, not W3C. While I was at it, I wrote a new web app to manage serving the draft pages (from dev.w3.org/fxtf which actually just proxies drafts.fxtf.org). The new app has the following features: 1) automatically syncs the repo bi-directionally with the mirror at GitHub (like the test repo has been doing). This means that there's now a GitHub mirror (https://github.com/w3c/fxtf-drafts/ ) available for push access as well as merging PullRequests online. If you want write access to the GitHub repo, email me or ping me on IRC. 2) should be much faster updating the served drafts after pushes. 3) automatically runs Bikeshed for any documents in the repository that have the '.bs’ file extension and do NOT have a corresponding ‘.html’ file. If the Bikeshed run fails with errors, the most recent good version will be served. 3a) all the current automatically generated Bikeshed drafts will re-update every time the spec database is updated. This will keep all cross-spec links fresh. 4) automatically generates a clean index page for the drafts at http://dev.w3.org/fxtf/ 5) automatically manages URL rewrites and redirects for old spec names as well as versioned vs unversioned spec shortnames. So no more maintaining redirect files (I’ve removed some from the repo already). NOTE: the information to do this comes from the spec database, if you find a missing or wrong redirect, please let me know. 6) displays a history view of spec updates (from the index page) and serves old versions via a dated URL. This includes old versions of automatically generated Bikeshed output. 7) displays status of automatic Bikeshed runs as well as any Bikeshed warning and error output, linked from both the Bikeshed icon on the index page as well as an automatically injected Bikeshed icon on automatically generated pages. 8) sends email to offenders if automatic Bikeshed runs produce warning or error output. The last person editing the relevant file(s) as well as the person pushing the changes (if different) will get notified with the name of the file in question and the Bikeshed output. Both myself and Tab will also receive a copy of these emails to keep track if anything goes south. 9) Bikeshed status updates are live via server push notifications. The icon colors will change as generation happens on the server and reflect the status of the last run. When new versions are successfully generated, the spec will automatically reload. Note if you want a static version of the spec, without the Bikeshed icon, (for example, to have a copy to publish on /TR) simply shift-click the Bikeshed icon in the spec and it will go away. A note about the draft history views. The app tracks draft history based on the date which the changes were pushed to the server, not the date the changes were committed. This way, if you commit a change locally today, but don’t push it to the server until next week. In the future, historical views of this week will not show your changes (although a historical view of the repository will). Unfortunately Mercurial doesn’t store any information about when previous pushes happened, so the app is only tracking history starting now. As always, if you notice any issues, please let me know. Peter
signature.asc
Description: Message signed with OpenPGP using GPGMail
