Hi Dietrich, don¹t worry, your English is fine; mine probably isn¹t better either ;-)
The important fact is IMHO, that now the qooxdoo open-source project has the opportunity to open-up and directly involve collaborators in a well-organized way. As a largely company-provided OSS there simply is too much of a single dependency and only limited ways of participation. Lets improve on that! Putting it onto a broader foundation of project contributors certainly is the better way to go. 1&1 is actively supporting and driving this next step of the open-source project, so we can ensure there¹s uninterrupted availability and eventually a more user-/maintainer-friendly infrastructure without legacy (e.g. wiki, etc.). Certainly, there are benefits and disadvantages of both, i.e. more company-provided vs. more community-driven, so lets not waste time in debating. There are so many talented and active contributors in the community already, it¹s not about the ³if", but the ³how" to get them involved in the ongoing evolution of the qooxdoo project. Stay tuned, Andreas PS: Dietrich, we count you in. :-) ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
