[timof]

I wish to start a more technical discussion which may help a lot to build a comfortable environment for the open source community to work on coming open source Serna XML editor.

Let`s talk about technical infrastructure. Pros and contras of listed and unlisted software. Suggest another software, either open source or free for open source projects. Even commercial software may feet in some cases:

• Mailing List
  • MailMan -http://list.org/
• SVN browser (for now we are stick to SVN)
  • Sventon - http://www.sventon.org/
  • WebSVN -http://www.websvn.info/
• Issue tracker
  • Roundup - http://roundup.sourceforge.net/
  • Mantis - http://www.mantisbt.org/
  • Trac - http://trac.edgewall.org/
  • Jira -http://www.atlassian.com/software/jira/
• Blog
  • Wordpress - http://www.wordpress.org/
  • Movable Type - http://www.movabletype.org/
  • Zine - http://zine.pocoo.org/
• Wiki
  • MoinMoin -http://moinmo.in/
  • DokuWiki - http://www.dokuwiki.org/
  • MediaWiki - http://www.mediawiki.org/
• Maybe even realtime chat?

We are especially interested in integrable environment with the united authentication system.

[Susanne]

Hi Timofey,

editing this post I found a wiki really crucial

more seriously it depends on what you want to achieve...

mediawiki (the wikipedia guys) is using sourceforge:
SourceForge.net: MediaWiki

Now serna source could be fairly large --- and I think availability of the source is critical to your operations. You need to colaborate no matter if the bandwidth is available or not. If that's true it could make sense to host just the sources yourselves and use sourceforge for all the rest. git makes self-hosting fairly simple --- and it has some more advantages. for example git branch tracking is far superior to anything else and if you had oem customers oeming serna into their proprietary product, you probably wanted that to follow open source serna. In case you dual-license it under say gpl or a paid oem license.

For the single sign on I'd go with openID enabled things...


S.

[kondor]

Originally Posted by Susanne

If that's true it could make sense to host just the sources yourselves and use sourceforge for all the rest.
S.

Sourceforge and other similar services like Google Code are cool because of integrity of all used components: issue tracker, wiki, repository viewer etc. But they have some major restrictions:
1. No way to affect on installed applications. Use case: there is a need to apply some patch to issue tracker to change its some behavior.
2. No way to integrate other components such as a blog engine or a community translation system.

May be there are already existent solutions based on Open Source applications with a single identification system? Or some hosting services which allow to make flexible customizations?

[henrik]

I am working mainly with Eclipse open source as committer - and there Bugzilla and MediaWiki are used with single sign on for the public - the account is created in Bugzilla. I think that setup works really well.

[Susanne]

Originally Posted by kondor

May be there are already existent solutions based on Open Source applications with a single identification system? Or some hosting services which allow to make flexible customizations?

Obviously you'll get the full flexibility only with a self-hosted system. My concern is that this however is binding resources for security maintenance and update migration of data and patched code, resources that could be improving serna .

Maybe the key is what you really depend on: Things that are a must have for day to day operation, shared services that must have highest availability, they require a local instance. All the rest can be somewhere. For example, vlc and wordpress use pootle, but videolan.org (the vlc guys) is running their own svn and git and trac.

Don't know your order of key things, here's mine:

• mail or forum
• irc
• source code
• bug and feature tracker
• wiki
• blog
• i18n, l10n

Somewhere in there you could draw a line and host anything below on sourceforge or google or such, just pulling a local backup of the data out there.

IMHO all the tools have pros and cons, and it doesn't really matter much which one you choose as long as it's usable from windows, mac and linux clients.


Last not least, if you have an internal infrastructure in the dmz anyway, and you have experience with the tools, and they are standard tools anyway --- why not just move public with that as a starting point? You can switch to The Perfect Tool and The Best Hosting Site as needed, and add openID support as you go.


S.