Hi Guys, Google Doc = Google Drive, about a year ago Google messaged all existing Users that Docs would be deprecated, renamed Drive. Although it doesn't seem to have happened fully yet (Everything is still labeled Docs although technology migration has likely completed). Opening a text document from Google Docs/Drive is the same as etherpad/piratepad. Google bought the technology, IMO the main diff is that if you use Google Docs/Drive, then there is a bit of accountability for changes (Who did what?). The re-launched etherpad and piratepad don't require anyone to identify themselves. http://www.tech.slashdot.org/story/09/12/19/0059221/google-open-sources-ethe... If you don't need real time collaboration or file management, ie you just want everyone to get copies of what is available, I highly recommend deploying as a torrent (the actual torrent file can be publicly or privately deployed for easy access, or both, or distributed as a file link or mail attachment, etc). Anyone can change a file and the changed file would be automatically replicated to all others. If you want file change management, I highly recommend Github. Free for any fully public repositories and easy for anyone to grab copies of individual files or entire repositories. No limits on storage or bandwidth. But, IMO the biggest mistake I always see is lack of planning of how many repositories to make downloads somewhat granular, eg if you only want artwork, you shouldn't have to download all the printed material, too. And, of course because GIT stores not only the new file but every previous version of the file (with the same name) you can always revert to a previous version (especially good for docs, but can be useful for other file types as well). Although Google Docs/Drive also has this functionality, AFAIK it's very limited in comparison. If we want to use Github, I can create a simplified instruction page for how to setup, check out a page, then upload the changes merging with the existing pages on the Server. Optionally, I can also create a separate page which can describe the most common Admin type tasks that might be encountered for our purposes. Also, with Github, wiki(s) are supported for free. More specifically, <any> kind of static website (ie billboard type which does not require login). Similar to the openSUSE wiki, editing is completely unrestricted to everybody unless someone wants to pay (but IMO it's not needed). The advantage of building a wiki on Github is to more easily reference files stored there... Although with a little more effort, it doesn't really matter if the Wiki might for instance be located on openSUSE (links would have to be created and maintained manually). Speaking of which, I highly recommend using the openSUSE Wiki as a Wiki platform. Although the GUI editing tool is somewhat limited, it does support the full MediaWiki syntax, so it's possible to do much more than many people might think. The only think that can't be changed is the overall theme (but likely isn't an issue for us). Lastly, re: Connect although I haven't looked at it recently I imagine that if we use any existing openSUSE/SUSE web resources that Connect should support it. Tony On Wed, Dec 11, 2013 at 6:27 PM, Rajko <rmatov101@charter.net> wrote:

On Wed, 11 Dec 2013 11:43:19 +0100 Joerg Stephan <osml@johest.de> wrote:

...

maybe it could be idea to setup an etherpad for sharing the information and working on texts or maybe include etherpad in connect (?).

Good idea, but until someone creates such plugin for connect, or someone creates our own etherpad, we are better off not to be too particular and just get job done: * using docs as temporary draft place when expected frequency of edits is high, which makes wiki unsuitable, * create and update wiki page, lets say daily, until number of edits slows down. * when editing frequency drops, keep and update wiki page.

Once someone finds time to analyze connect and see how it can be organized, some other makes plugins, then we can switch to in-house solutions.

BTW, wiki article http://en.opensuse.org/openSUSE:Marketing_priorities is on its way :) ... and it is not the same as a table.

-- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-marketing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-marketing+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-marketing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-marketing+owner@opensuse.org