So we're supposed to sit around and wait? At a minimum we need to build our defenses and resources. Show TUBITAK how many people are wanting to be involved in a community maintained Pardus.
They act like waiting is no big deal but in the real world, we cannot trust using completely unsupported software. MANY users will abandon Pardus out of fear if nothing happens soon. Maybe that is what TUBITAK is wanting...
Right now many have signed our community commitment form:
(
https://docs.google.com/spreadsheet/viewform?hl=en_US&formkey=dC1mZm12b1laYlZpTzYySjZzQllYT1E6MQ)
...and according to our friends on Facebook we have a server on the way from the Pardus Users Association (
http://www.pkd.org.tr/) that will be set up as a build farm. I believe their goal is to work with TUBITAK as well (as much as possible) to arrange some sort of agreement to continue Pardus as it is (without an official fork) but, if TUBITAK is unwilling then Pardus will be forked by the community.
So, we do not wait. We aid others who are willing to work with us. I think this means we need to get a new repo online with updates and bug fixes while we wait. We will need a bug tracker as well (redmine would work really well for this actually).
Right now I have been talking with Hamit Giray Nart who is helping with communication in organizing this build farm.
Also, I am still interested in working out of github if the above plan does not succeed in the end. Since Ozan does not respond to our messages we can still fork his github with a click of a button.