Jump to content
Froxlor Forum

d00p

Administrators
  • Posts

    10327
  • Joined

  • Last visited

  • Days Won

    43

Everything posted by d00p

  1. well then sorry, you don't have 0.9.18, you have 0.9-r2
  2. Please output the result of the following sql-statement: SELECT `value` FROM `panel_settings` WHERE `varname`='version';
  3. i did that myself three times on our testserver...sorry, it does not output your error. Your error says "Update from 0.9-r0 to 0.9-r1"...read the version numbers...it's not even CLOSE to 0.9.18
  4. read your error message again, it's not the update from 0.9.18 to 0.9.18.1. You did not update from 0.9.18. I presume you upgraded from SysCP, please be sure you use the most recent SysCP version for that.
  5. Open a bug in the bugtracker
  6. No. If you use leading slashes, it always reads from the docroot. At least it did on our testservers
  7. That's one big change in two steps...
  8. there is a reason: we wanted it that way. and i don't get what you want us to tell with ...in this "short time period between the changes...." ?
  9. Thanks a lot And I agree with you, spending too much time with 'getting money' or anything will definetly lead to less progress in development.
  10. It says "down for maintenance" because of exactly that, we're switching to redmine ;-) Don't panic, it will be back online in no time
  11. Dear Froxies, as of this months, Februrary 2011, we've switched our source repository from SVN (subversion) to GIT (http://git-scm.com/). This arranges the repository as follows: Anonymous read-only access is provided via git://git.froxlor.org/froxlor.git and http://git.froxlor.org/froxlor.git'>http://git.froxlor.org/froxlor.git. The Froxlor GIT - repository may be browsed with the webinterface installed on http://git.froxlor.org If you want to contribute, you no longer need your own branch nor svn-access. Just clone our repository, make your changes, and create a patch using git format-patch origin/master. If you want to make our lives even easier, use git send-email to directly send us your patches vie e-mail. If you want to know more, join us on IRC (irc.freenode.net/#froxlor). Some more detailed information will be published on http://wiki.froxlor.org/doc/git these days. That's about it for now. d00p and the Froxlor-team
  12. no they havent and no, i dont think they have to...maybe you just use and not-yet-updated gpg-key-server
  13. there is not yet a 0.9.17 package, please read posts above
  14. key has been renewed. Packages, sorry, no info yet, Dessa seems to be sick (we haven't heard from him in four days). We'll notify you if we know more
  15. We hope you will, but it's not svn-ready yet and we don't want others to report bugs about "errors" with the new design even if it's no done (twice the work for us).
  16. no stress...it's there when it's there
  17. we're three devs short of our five-men group...we're trying our best
  18. ugh, we'll take care of this asap, sorry for any inconvenience
  19. sorry...Dessa builds the packages and he's currently a bit busy
  20. Hi Froxies, two days late (sorry) but here it is: Froxlor 0.9.17. As the team is really short with time these days, we decided to tighten up our plans. To make it short, there will be no new features in the 0.9-series except for the (re)design and multiserver-support. Which also is the roadmap, along with Froxlor-1.0, for the next months. ChangeLog for 0.9.17: Legend: ChangeLog: Download Froxlor 0.9.17 Visit www.froxlor.org or join our irc-channel #froxlor on irc.freenode.org Debian packages are in process of being built and will be available later today as usual. Thank you, your Froxlor Team
  21. Yup, we try to be backwards compatible and keep supporting the "old" theme (well, at least for a bit ) We try really hard for .17 but it's more likely to make it into .18
  22. In German (just to avoid any misunderstandings): Haben wir alles schon durchgesprochen und uns informiert, der administrative Aufwand f?r die F?hrung eines Vereins ist einfach noch zu gro? im Moment, als das es sich f?r uns lohnen w?rde. Wir sind alle freiwillig und in unserer Freizeit bei Froxlor t?tig und m?chten ungern noch mehr unserer kostbaren Zeit mit Verwaltungsaufwand f?r einen Verein einbu?en. Auch haben wir schon die M?glichkeit in Betracht gezogen uns einer externen Verwaltungsstelle f?r Open-Source-Projekte anzuschlie?en, allerdings erschien uns das zur Zeit einfach nicht notwendig. Die meisten Spender sind Privatleute oder kleine- bis mittelst?ndige Unternehmen die bisher keine Quittung verlangt haben. Wie gesagt, wir stecken unsere Energie und Zeit lieber in die Weiterentwicklung als in die Verwaltung f?r einen Verein nur um "mehr Spenden" zu bekommen. Das ist nicht unser Prim?rziel und auch nicht das, was wir mit Froxlor erreichen wollen.
  23. We discussed that. there is a lot of administrative stuff we would have to do for this (ber?hmte "Beh?rdeng?nge" usw.) which is not worth cutting of time for development. Also, we don't want to pay taxes or anything (what we surely would, cause i unsure if we would get a non-profit-organisation status). It's too complicated. On the other hand - i like the support-membership idea. We already have a company which donates on a regular basis (Bedios eBusiness Solutions)
  24. As there were some changes in the process of packaging for Debian we have to do some more work than usual. ETA is this week.
×
×
  • Create New...