Atlassian offers returns on licenses within 30 days of purchase. Customers who purchase Atlassian licenses from //SEIBERT/MEDIA have this period of time to reimburse us for the licenses. This is how we conduct the licensing process: When you order a license for an Atlassian product from us, we cover the fees for you. As soon as we receive the license code, we use our credit card to make an advance payment directly to Atlassian for the license fees. We then send you a normal invoice that you must pay within two weeks.
In our article, “Enterprise Wikis: Criteria and important topics in the evaluation of wiki software” we discussed the diverse and unique requirements an enterprise wiki needs to meet. Decisions about choosing the right wiki system cannot be made using generalizations, but rather only by taking into account the specific needs of the company. In this article, we will draw a concrete comparison between the approaches of the Atlasssian Confluence commercial system and the open source systems Foswiki and MediaWiki. What are the strengths of Confluence compared to Foswiki and MediaWiki?
Wikis for intra-company usage are becoming well established as both commercial and open source applications. This article gives an overview of criteria and requirements involved in the decision making process, along with a comparison of our proprietary Wiki Confluence System and its open source competitors, Foswiki and MediaWiki.
All wiki systems have the same basic functions: opening, editing and saving documents. These functions can be covered in a single Wikipedia paragraph. The functions of a more advanced business wiki, however, are more complex. A business wiki is not simply a web lexicon, but rather is intended to systematically handle a variety of processes in the company.
Wikipedia is by far the best-known example of a wiki. This web lexicon is what most people immediately think of when they hear the word wiki. It’s not surprising, since the online encyclopedia is used by millions of people every day. However, Wikipedia is something completely different from a wiki that is used in a corporate intranet.
Martin Seibert and Eric Klein present the news module within the LINCHPIN suite. The module will cater to your personal needs for information, as it allows you to subscribe to different news channels. Your personalized news will then appear on your dashboard.
In the first article on the differences between a company’s intranet and website, we addressed organizational questions and described how these systems differ conceptually. From a technical perspective as well, intranet and web projects must be approached differently to meet the various needs of the user groups.
You do not need to be an Internet professional to recognize the basic difference between a company’s intranet and its online presence. An intranet, the internal system, is protected against external access and contains non-public information. Online content, however, can be accessed by anyone. If you take a closer look, it’s clear that many different aspects must be considered and play an important role. We will therefore turn our attention in these two articles to the question of how to differentiate between an intranet and a website. First, we will look at the organizational aspects before dealing with the technical aspects in the following article.
You are a teacher or student at a university and want to gain practical experience working with Atlassian tools? Atlassian offers you the opportunity to use numerous products with the Classroom License – free of charge. All you have to do is submit an application. Why use Atlassian tools in your project? For budding software developers in particular, using Atlassian products during their studies is a great way to start working early on with tools designed for use in professional enterprises.
Git Essentials is the new Atlassian product suite that completely and seamlessly displays the development workflows with Git in software development teams – from agile issue management and repository management to software releases for continuous integration.