Good day. 1) Is there a reason that the wiki is still residing where it is, vs. being migrated over to the [sqlite]docsrcs or [sqlite]src fossil repos. Is it that someone just hasnt taken the time to get the cvstrac wiki pages migrated over to one of the fossil wikis?
2) I suspect I can guess the answer to this one, but wanted to throw it out there for review, consideration, and comment. I understand that the value of a fossil repo is the ability to have a web-server content, versioned project source code, versioned documentation, issue tracking/reporting, and a wiki, all integrated into a single file. However with SQLite, it presents that there are at least three different repos a fossil repo for the source code, a second fossil repo for the documentation, and the third being a cvstrac repo for the wiki. Is it intended to eventually get everything into a single fossil repo sqlite source, sqlite docs, sqlite bug tracking, and sqlite wiki? If not, please elaborate so that he who is ignorant (me) can gain an understanding. TIA. What spurred my initial query is that I am making a FTS searchable sqlite info tool that is not reliant on any one particular external entity. Ive got all 300+ doc pages (v3.7.4) (from docsrc fossil repo), all >62000 user mail-list emails (from gmane and the sqlite listserv), and all developer and announcement mail-list emails (from sqlite listserv). The last meaty info repo that Id like to integrate into the tool is the sqlite wiki contents. I can clone and get the sqlite docsrc repo, but cant seem to do the same with the Wiki cvstrac repo. Id surely like to migrate that useful information into the tool -TodWulff _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
