While editing the configuration and having other users pull it is fine for actual configuration changes, some things, like updating the list of project numbers, should be easier to update. This type of information is normally controlled by the project managers, who have already stated they will not touch anything that even remotely looks like code.
One idea I thought of, create a dedicated list editor in Javascript to edit a Fossile wiki page. At least 2 problems with this: Writing the needed Javascript (we could do it, just requires the time to put in the effort). And needing the ability to fetch the raw wiki page from Fossil, which, as far as I know, is not yet available. I am planning to look into enhancing Fossil, myself, to allow serving raw wiki pages, but I do not yet know how much effort this will be. Another idea I thought of is to define a special ticket type to hold the list of project numbers in the comment field. This would require being able to do an SQL query from TH1. Again, I plan to look into this, but do not yet know the effort required. (The ticket idea occured to me because if we rely on a developper to maintain the list of project numbers in Fossil, the project managers will just write tickets asking us to update the list. So, I figured, why not store the list in a ticket (or even multiple tickets, but I see no need for that).) Thoughts? Does anyone have a better idea/suggestion? _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
