Comparing revisions for ANewHomeForWikka
- [12176] 2005-12-09 13:29:19 by DarTar (unregistered user) [announcing new Wikka server - feedback welcome]
- [23473] 2016-05-20 07:38:48 by MasinAlDujaili (unregistered user) [Replaces old-style internal links with new pipe-split links.]
Additions:
{{lastedit}}
Yes, Wikka is moving to a new home! I'd like to share with the Wikka user community some thoughts about the important changes Wikka is undergoing since a couple of weeks and open a collective discussion about Wikka's future plans. Feedback from contributors, users and friends from #wikka about the changes that we plan to implement is particularly welcome.
~1)Wikka is currently hosted at [[http://www.jsnx.com jsnx.com]], i.e. JsnX's personal webserver: moving to a new server will not only free Jason from the burden of hosting Wikka on his personal resources, but will also allow a more distributed management and increase the project's visibility.
~1)The current website covers a number of different uses, in an often confusing way. It is currently used as:
~a) A **dedicated server** with a new domain name (http://wikkawiki.org) has been setup on a professional hoster ([[http://www.site5.com Site5]]).
~a) A **code repository** (SVN) and an **issue tracker** (Trac) have been opened at http://wush.net/trac/wikka (although in the future we might consider importing them on a subdomain at wikkawiki.org).
We are currently migrating feature requests and bug notifications to the tracker and we have setup a preliminary draft of a [[wush.net/trac/wikka/roadmap roadmap]], to start organizing future development in a more transparent and manageable way.
Instead of just migrating the current wiki (which suffers from the above problems), we are planning to organize the new website in a more rational way.
~a) The **main server** (**##www.wikkawiki.org##**) will be used for official announcements on new releases and important news from the development team. This server will mainly be read-only: only Wikka admins (and/or site admins) will have write-access. This part of the site need not be itself a wiki, although I think we would still be in favor of using Wikka as a backend, instead of bother with ftp sessions and static pages.
~a) The **project documentation** will have its own home in a subdomain of the new server (e.g. **##docs.wikkawiki.org##**). This -- together with some consistent naming conventions -- will allow us to build a rich and well-structured documentation for the end user and translate it in different languages. Furthermore, it will allow external wikis to refer consistently to the documentation or even to "pull" content from the documentation server using some of the syndication tool that we have started developing (remember our [[IncludeRemote FetchRemote]] action?). Only registered users will have write-access to this server, under the management of Documentation admins.
~a) A **plugin repository**: the development server will also be used to announce and discuss user-contributed add-ons. Plugins will be made available in a dedicated folder of the SVN repository, for easy tracking and downloading.
~a) Two **test servers** -- (**##demo.wikkawiki.org##**/**##beta.wikkawiki.org##**) -- will allow new users to play with a live demo of, respectively, the //latest official release// and the //latest experimental package// (fed by the SVN repository). The database will be automatically reset every week (or day?) with a cron job. This will allow users to play not only with the SandBox, but with a whole Wikka distribution, without messing up the official documentation or development pages.
Yes, Wikka is moving to a new home! I'd like to share with the Wikka user community some thoughts about the important changes Wikka is undergoing since a couple of weeks and open a collective discussion about Wikka's future plans. Feedback from contributors, users and friends from #wikka about the changes that we plan to implement is particularly welcome.
~1)Wikka is currently hosted at [[http://www.jsnx.com jsnx.com]], i.e. JsnX's personal webserver: moving to a new server will not only free Jason from the burden of hosting Wikka on his personal resources, but will also allow a more distributed management and increase the project's visibility.
~1)The current website covers a number of different uses, in an often confusing way. It is currently used as:
~a) A **dedicated server** with a new domain name (http://wikkawiki.org) has been setup on a professional hoster ([[http://www.site5.com Site5]]).
~a) A **code repository** (SVN) and an **issue tracker** (Trac) have been opened at http://wush.net/trac/wikka (although in the future we might consider importing them on a subdomain at wikkawiki.org).
We are currently migrating feature requests and bug notifications to the tracker and we have setup a preliminary draft of a [[wush.net/trac/wikka/roadmap roadmap]], to start organizing future development in a more transparent and manageable way.
Instead of just migrating the current wiki (which suffers from the above problems), we are planning to organize the new website in a more rational way.
~a) The **main server** (**##www.wikkawiki.org##**) will be used for official announcements on new releases and important news from the development team. This server will mainly be read-only: only Wikka admins (and/or site admins) will have write-access. This part of the site need not be itself a wiki, although I think we would still be in favor of using Wikka as a backend, instead of bother with ftp sessions and static pages.
~a) The **project documentation** will have its own home in a subdomain of the new server (e.g. **##docs.wikkawiki.org##**). This -- together with some consistent naming conventions -- will allow us to build a rich and well-structured documentation for the end user and translate it in different languages. Furthermore, it will allow external wikis to refer consistently to the documentation or even to "pull" content from the documentation server using some of the syndication tool that we have started developing (remember our [[IncludeRemote FetchRemote]] action?). Only registered users will have write-access to this server, under the management of Documentation admins.
~a) A **plugin repository**: the development server will also be used to announce and discuss user-contributed add-ons. Plugins will be made available in a dedicated folder of the SVN repository, for easy tracking and downloading.
~a) Two **test servers** -- (**##demo.wikkawiki.org##**/**##beta.wikkawiki.org##**) -- will allow new users to play with a live demo of, respectively, the //latest official release// and the //latest experimental package// (fed by the SVN repository). The database will be automatically reset every week (or day?) with a cron job. This will allow users to play not only with the SandBox, but with a whole Wikka distribution, without messing up the official documentation or development pages.
Deletions:
Yes, Wikka moved to a new home! I'd like to share with the Wikka user community some thoughts about the important changes Wikka is undergoing since a couple of weeks and open a collective discussion about Wikka's future plans. Feedback from contributors, users and friends from #wikka about the changes that we plan to implement is particularly welcome.
~1)Wikka was hosted at [[http://www.jsnx.com | jsnx.com]], i.e. JsnX's personal webserver: moving to a new server will not only free Jason from the burden of hosting Wikka on his personal resources, but will also allow a more distributed management and increase the project's visibility.
~1)The previous website had different uses, in an often confusing way. It was used as:
~a) A **dedicated server** with a new domain name (http://wikkawiki.org) has been setup on a new hoster ([[http://www.site5.com | Site5]]).
~a) A **code repository** (SVN) and an **issue tracker** (Trac) have been opened at http://wush.net/trac/wikka (with an alias at [[http://tracker.wikkawiki.org]]).
~a) A **test server** -- (http://demo.wikkawiki.org) allowing users to play with a live demo of the [[WhatsNew | latest official release]]. The database is automatically reset to system defaults every day. This will allow users to play not only with the SandBox, but with a whole Wikka distribution, including features that are only available to registered users.
~a) A **Wikka developer blog** (**##blog.wikkawiki.org##**), a comfortable place to keep track of important development news, especially for those among us who cannot keep an eye on the dev website on a daily basis (ahum, are there any??).
~a) The full **API documentation** (**##api.wikkawiki.org##**) for prospective developers and contributors.
~a) Several **[[WikkaMailingLists | mailing lists]]** to keep up-to-date with the latest news from the Wikka devs.
~a) The [[http://docs.wikkawiki.org | project documentation]] has been moved to a dedicated subdomain (**##docs.wikkawiki.org##**). This -- together with some consistent naming conventions -- will allow us to build a rich and well-structured documentation for the end user and translate it in different languages. Furthermore, it will allow external wikis to refer consistently to the documentation or even to "pull" content from the documentation server using some of the syndication tool that we have started developing (remember our [[IncludeRemote | FetchRemote]] action?). Only registered users will have write-access to this server, under the management of Documentation admins.
The old website has been already moved to the present domain, but we are planning to organize the new website in a more rational way.
~a) The **main server** (**##www.wikkawiki.org##**) will be completely refactored and used for official announcements of new releases and important news from the [[CreditsPage | development team]]. This server will be //read-only//: only Wikka admins (and/or site admins) will have write-access.
~a) A **support forum** (**##forum.wikkawiki.org##**) for users needing help with Wikka installation, configuration and use.
~a) A **[[PluginDirectory | plugin repository]]**: the development server will also be used to announce and discuss user-contributed add-ons. Plugins will be made available in a dedicated SVN repository (see the example of [[http://dev.wp-plugins.org | wp-plugins]]) , for easy tracking and downloading.
~~- Users will be able to suggest patches to the official repository as tickets/attachments
~~- SVN maintainers will take care of a selection and implementation of relevant modifications for the official package
~~- Other modifications will be directly maintained by contributors in the Plugin SVN repository, where these add-ons can be developed, announced and released independently from the Wikka development team.
~~-Particularly popular add-ons could be migrated to the official Wikka trunk as candidates for a release.
~a) A **test server** with the //latest unstable package// (fed by the SVN repository).
