On 11/29/18 12:11 AM, Vojtech Horky wrote: > Any particular reason why do you want to replace Trac? I thought that > we want eventually to have master back on helenos.org and have GH as a > backup.
Well, on GH everything is nicely integrated together - commits, pull requests and issues. It might be easier for people to use GH issues with their existing GH account than creating a dedicated HelenOS account on our trac, then going through the surprise of having their access token publicly sent to the ML. We wouldn't have to be on guard for new suspiciously looking spam accounts. Most of the time, GH would be just up and we wouldn't have to maintain it. It would be also easier to use it for us - how many time have people wanted to add a new trac ticket category, but could not because of lacking admin privileges? I have been backing most of our GH repos automatically on GitLab[1] for some time now. We could later do the same with our own Git server, maybe on a private instance of GitLab, but I am beginning to miss the point with all these backups lying around. All this experimenting and thinking is motivated by ending up with a statically generated helenos.org eventually served by HelenOS itself. Jakub [1] https://gitlab.com/HelenOS _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
