I think Google Sites is a different to hosting a development project at code.google.com? -- I suspect the latter would be a better environment for development Wiki. Unfortunately I'm not familiar with either wiki to say for sure.
Joe. On Fri, Jun 20, 2008 at 7:29 PM, Larry Becker <[EMAIL PROTECTED]> wrote: > Google Sites looks acceptable. According to : > http://googleblog.blogspot.com/2008/05/google-sites-now-open-to-everyone.html > > "Similar to Google Docs, built-in editing tools allow for popular text and > formatting changes to be made in a straightforward, WYSIWYG manner. Once > your site is up and running, inviting people to edit or view your content is > as simple as entering in their email address (of course, you can change > access levels at any time). And you (or anyone who has editing privileges) > can add or edit information whenever you'd like." > > The big issue will be porting over the content from the old Wiki. This will > be difficult, I think. > > Larry > > On Fri, Jun 20, 2008 at 1:15 PM, Joe Desbonnet <[EMAIL PROTECTED]> wrote: >> >> The Wiki at code.google.com? (Hosting, backups and maintenance taken >> care of by Google). >> >> Joe. >> >> >> On Fri, Jun 20, 2008 at 7:07 PM, Stefan Steiniger <[EMAIL PROTECTED]> >> wrote: >> > Dear users and developers, >> > >> > due to maintenance difficulties of our current Wiki (openjump.org) but >> > also >> > with the aim to release Jon Aquino from his duties we decided to move >> > the >> > Wiki. >> > >> > The question is where to host it? That is, we need a service, as we have >> > no >> > servers for hosting [not sure if OSGEO can help here]. So if you have >> > suggestions, then please let us know! (I know there was a discussion a >> > while >> > ago on that topic, with respect to Google-sites.) >> > >> > Ideally the new Wiki should fulfill these requirements: >> > >> > . editing for every person who wants to edit (i.e. at least the people >> > registered to our mail lists should be allowed to edit) >> > . some type of spam-filter [e.g. a captcha], so that we avoid/identify >> > bad >> > edits >> > . it should allow to pull a backup >> > . we should be able to delete single, unwanted, very old pages (this is >> > a >> > problem right now, as the backup is currently 715MB large!) >> > >> > Any suggestions? >> > >> > As a fall-back strategy we may use possibility to add pages on the >> > OpenJUMP-users Google group, use Google Sites, or use the Wiki that >> > comes >> > with our SourceForge account (i.e. the account we use for code and >> > project >> > management, but this wiki ) >> > >> > best regards >> > Stefan >> > >> > PS: Sunburned: I think you already did a test with Google Sites. Can you >> > check if one can add a Google-group to the list of people for editing? >> > _______________________________________________ >> > jump-users mailing list >> > [email protected] >> > http://lists.refractions.net/mailman/listinfo/jump-users >> > >> _______________________________________________ >> jump-users mailing list >> [email protected] >> http://lists.refractions.net/mailman/listinfo/jump-users > > > > -- > http://amusingprogrammer.blogspot.com/ > _______________________________________________ > jump-users mailing list > [email protected] > http://lists.refractions.net/mailman/listinfo/jump-users > > _______________________________________________ jump-users mailing list [email protected] http://lists.refractions.net/mailman/listinfo/jump-users
