Hi Jiri,
I really aplaud your achievements and I am looking forward to trying it out :-D. On the other hand I really don't understand your separatist tendencies. Why use a separate private issue tracker on GitHub and a separate private repo on GitHub? IMO coastline should be either merged to mainline. Even in the case we actually decided to keep it in a separate repo (why?) then why not host it on the official server along mainline. And why not use the projects main issue tracker?
I certainly cannot speak for Vojta, but in my opinion it is OK to have the coastline separated as long as it is in an alpha/beta stage (I know that it is funny to use these terms in context of HelenOS, but I hope you understand what I want to say).
Now, as the coastline is getting mature, let's discuss how exactly should we integrate it -- both from the point of view of the sources and from the point of view of hosting it on HelenOS project's infrastructure.
M.D. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
