I want to propose that we take the time to create documentation on how our stack ticks. I'm not talking about user guides or packaging hints here, more about writing down, what we do to make foresight run. Some behind the scene documentation, services that we use, how do we set several things. What magic taghandlers do we have hidden somewhere... Unfortunatly that means we have to squeeze a lot of that out of Antonio and Ken and digging deep into that ourselves. But at the end we have a start for people who want to get a deeper understanding of fl.
-- Mark Trompell Foresight Linux Xfce Edition Cause your desktop should be freaking cool (and Xfce) _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
