Category: Collaboration and workplace(Page 26 of 94)
This category is focused on enterprise / workplace collaboration tools and strategies, including office suites, intranets, knowledge management, and enterprise adoption of social networking tools and approaches.
Amazon Web Services and Slack Technologies announced a new multi-year agreement to deliver solutions for enterprise workforce collaboration. Slack and AWS will strategically partner to help distributed development teams communicate and become more efficient and agile in managing their AWS resources from inside Slack. Slack will migrate its Slack Calls capability for all voice and video calling to Amazon Chime, AWS’s communications service that lets users meet, chat, and place business calls. Slack is also leveraging AWS’s global infrastructure to support enterprise customers’ adoption of its platform and to offer them data residency – the ability to choose which country or region their data is stored at rest in while fulfilling compliance requirements. Slack continues to rely on AWS as its preferred cloud provider and will use a range of AWS services, including storage, compute, database, security, analytics, and machine learning, to develop new collaboration features. Additionally, AWS has agreed to use Slack to simplify the way teams at AWS communicate and work together.
Slack and AWS will also extend product integration and deepen interoperability. These integrations include:
Amazon Chime infrastructure with Slack Calls
AWS Key Management Service with Slack Enterprise Key Management (EKM)
Atlassian announced 12 new collaboration features, automations and integrations in order to help developers take their time back and ship better code, faster. There are too many disconnected tools, manual processes, and constantly changing collaboration practices are blocking developers from reaching the full promise of DevOps. Developers need less context switching. Fewer meetings. Fewer pings from IT about security incidents. Just more time to code and deliver value to customers. The goal is to help developers focus on their code with connected development, IT operations, and business teams with automation that spans Atlassian products and third-party tools. With Jira as the backbone and ultimate source of truth, Atlassian unifies all of DevOps work to reduce collaboration overload. There are deep integrations between Jira Software Cloud and Bitbucket Cloud, GitHub, and GitLab so that issue tracking and project updates happen right where you code, automatically. No need to go back to Jira. And your project manager won’t have to ping you for updates and interrupt your coding flow, because your project board will automatically update based on your work in Bitbucket, GitHub, or GitLab.
EditShare’s new Flow panel for Adobe Premiere Pro is designed to simplify content management, proxy and remote editing, and review and approval workflows for editors. For open storage, EditShare’s EFS enhances collaborative editing with support for project-locking for Productions in Premiere Pro. With the Productions feature set, Premiere Pro can now handle projects with “an extraordinary number of assets” while maintaining peak performance. Sharing and organizing those assets is also simplified. Flow manages the entire media technology stack with tools to orchestrate assets and workflows across tiered on-premise, nearline and cloud storage environments. A secure platform for remote, collaborative productions, Flow offers an advanced proxy-based workflow with support for more than 500 codecs. Its enhanced Premiere Pro panel connects individual editors and production teams directly to the Flow media asset management and its productivity-focused toolset including extensive asset tracking, collaborative proxy editing workflow, and review and approval workflows across cities, countries and continents. EFS scalable storage enables media organizations to build extensive collaborative workflows on premise, in the cloud, or in hybrid installations, shielding creative personnel from the underlying technical complexity while equipping administrators and technicians with storage management tools. For Adobe editors, EFS is fast and flexible collaborative storage that supports Productions in Premiere Pro for project sharing.
An article on The Verge and quotes from Microsoft’s Jared Spataro about Fluid reminded Thompson of OpenDoc and he begins his own thoughts on Fluid with a bit of history on Steve Jobs decision to kill OpenDoc in 1997. Thompson suggests the reason was that a combination of Microsoft’s dominant marketshare, and
that the application model was simply a much better approach for the personal computer era. Given the lack of computing power and lack of connectivity, it made much more sense to have compatible documents made by common applications than to try and create common documents with compatible components — at least with the level of complexity implicit in OpenDoc.
Thanks to Thompson for giving me an excuse to indulge in a little history of my own, which largely supports his view. Below is what I shared with him. The history is fun, but the new Fluid Framework is also worth a closer look.
———————-
Fluid also reminded me of the competing OpenDoc and OLE approaches in the early 90s. To supplement your history…
At the first Documation conference in February 2004 1994 I moderated a session that included Apple Chief Scientist Larry Tesler, and Tony Williams, Microsoft Software Architect and Co-creator of COM. I had asked each of them to discuss requirements for and their approaches to building a “compound document architecture”. OpenDoc was naturally appealing to me (and many of my subscribers) at the time, but Tony made a strong case for OLE. Tony’s argument for OLE was technical but he also addressed the issue from a business point of view, and argued that OpenDoc was too much of a radical change for both developers and end users. While this was more of an issue for Microsoft with their large developer community and installed base, OpenDoc was radical, and I expect that was the reason OpenDoc languished at Apple and for Jobs’ ultimate rejection.
On Wednesday the general session was divided into two sections. One covered new technologies being developed to enhance document computing and document management. The other presented senior managers from large corporations who described their own document management needs.
Your editor opened the technology session by describing three components of current document management systems, each of which presage future developments. Objects — whether in terms of object-oriented databases, object-oriented programming, or multimedia document component “information objects” — play a big role in making systems more flexible and capable of dealing with complexity. Building an architecture to manage and share distributed objects, and to link and assemble them into document form are requirements of many enterprise-wide document management solutions. Finally, the document metaphor is increasingly seen as the most effective and friendly way to interface not only with document management systems, but with information in general.
Today, these capabilities are built either at the application level, or as “middleware”. For many reasons (e.g., application interoperability, performance, and ease of application development), it would help instead to have support for these capabilities at the operating environment level.
Previous attempts at compound document architectures to provide such an environment have failed. But this is clearly something we need, and eventually will get. Whoever defines and builds such an architecture will be in a powerful position to dominate the IT market. We can expect fierce battles among the platform and architecture vendors to control this architecture . The two leading candidates today are Microsoft’s OLE, and the Component Integration Lab consortium’s OpenDoc (based on Apple technology).
Larry Tessler from Apple described the “Information Tidal Wave” (his alternative to “superhighway”) coming with the growth of electronic multimedia documents, and with the rapid building of electronic document repositories. IS managers will face severe new problems arising from the need to manage these repositories. Larry positioned OpenDoc as a core technology for supporting the management and assembly of these new kinds of documents.
Microsoft’s Tony Williams focused on user requirements for a compound document architecture. Compound documents should be thought of as “compound views” of information, and documents are just one form of information, and thus need to be handled as part of an information architecture. Information architectures in turn need to be able to manage many different types of multimedia data for both document and data applications.
A standard “containment model” is needed, Williams said, to allow applications to share and organize information objects. Previous attempts at standard compound document architectures, e.g., ODA (Office, or Open Document Architecture) failed because they attempted to define a too restrictive representation. Such systems also need to handle ad hoc information (for example, that created with a personal information manager) as well as structured documents.
Tony emphasized the need to protect both user investments in information and developer investments in applications. While a compound document architecture environment is a requirement of any new operating environment, there must be an evolutionary path provided — a compound document architecture that forces a radical change too quickly will not gain acceptance. Tony positioned OLE as the technology that meets these requirements.
When asked, both Tony and Larry Tessler claimed that OpenDoc and OLE should work together and described generally — each in terms of the architecture they were promoting — how that could happen. However, this is definitely an area where there needs to be continued and aggressive vigilance on the part of corporate users to ensure that operating environment interoperability results. It would certainly not be wise — at least not yet — to assume that one of these approaches will become dominant.
Automattic, the open source force behind WordPress, WooCommerce, Longreads, Simplenote and Tumblr, has made a $4.6M strategic investment into New Vector — the creators of an open, decentralized communications standard called Matrix. New Vector also developed a Slack rival (Riot) which runs on Matrix. Matrix is an open source project that publishes the Matrix open standard for secure, decentralised, real-time communication, and its Apache licensed reference implementations.
New Vector’s decentralized tech powers instant messaging for a number of government users, including France — which forked Riot to launch a messaging app last year (Tchap) — and Germany, which just announced its armed forces will be adopting Matrix as the backbone for all internal comms; as well as for KDE, Mozilla, RedHat and Wikimedia, and others.
Microsoft introduced the first way for end users to experience the Fluid Framework in Microsoft 365 with the upcoming availability in preview of Fluid Workspaces and Fluid Components. Fluid Workspaces and Components work like the web to bring the right level of context and connection as well as seamlessly capture follow-ups in-line and edit action items with an entire team. Fluid Components and Fluid Workspaces will become available in more places over time. This initial public preview includes basic text, tables, lists, agendas and action items. These Fluid components will be available for creation in Outlook for the web and Office.com. Microsoft also announced the Fluid Framework will be made open source and hosted as a repository available on GitHub in the next month, allowing developers and creators to use infrastructure from Fluid Framework in their own applications. Coupled with the release of additional developer documentation and tooling, developers can work alongside Microsoft to create and evolve Fluid Framework as it is developed. Developers can take advantage of JavaScript APIs that give them access to collaborative, shared data structures which can be used to power collaborative experiences. They also can create Fluid components — elements that can be reused within Microsoft 365 and across applications.
The Gilbane Report on Open Information & Document Systems (ISSN 1067-8719) was periodical launched in March, 1993 by Publishing Technology Management Inc. which was founded by Frank Gilbane, its president, in June, 1987.
The Gilbane Report was sold to CAP Ventures Inc in December 1994, who published it until May, 1999, when it was bought by Bluebill Advisors, Inc. a consulting and advisory firm founded by Frank Gilbane. Bluebill Advisors continued to publish the Gilbane Report until March, 2005. The Gilbane Report issues from 1993 – 2005 remain available in either HTML or PDF (or both), on the Gilbane Advisor website, which is owned by Bluebill Advisors Inc.
Below is a link to the first issue of the Gilbane Report. There is also a PDF version.
Enterprise social software (also known as or regarded as a major component of Enterprise 2.0), comprises social software as used in “enterprise” contexts. It includes social and networked modifications to corporate intranets and other classic software platforms used by large companies to organize their communication. In contrast to traditional enterprise software, which imposes structure prior to use, enterprise social software tends to encourage use prior to providing structure.
