The Future Graduates program enhances youth access to 21st Century work experience, placing local high school students in paid summer internships at innovative, San Francisco-based technology companies. – Read the full Press Release here.
AppFusions is proud to host 8 of the future graduates this summer, to make up our “AppFusions’ Future Grads Leadership Camp“. During the camp, we will be facilitating, encouraging, training, and empowering the future grads in many typical tasks found in a startup.
They will work with us on numerous efforts, learning and performing tasks such as product testing, product management reviews and inputs, marketing collateral development (printed / PDF briefs), demo video development, CRM enhancements and analysis, code analysis and reviews, and possibly other contributions depending on skills.
While we will provide positive guidance, tools and objectives, a big part of our program is about them developing their skills independently over the summer, while growing confidence through tangible results. We expect each of the future grads to come away from the program with solid skills for their “evolving resume” in life, and who knows, maybe we will hire them in the future too one day.
It was a great conference that I would highly recommend, if interested in getting up front, close, and personal with “who’s who” in the IBM Connections’ ecosystem. This includes the many folks that work daily to make IBM Connections’ customers successful: IBM developers, PMs, and IBM Collaboration Services’ (ICS) management — they were all there!
In addition, the conference was attended by a passionate group of customer end users and administrators, and dozens of expert consulting implementors from across the globe.
With a packed schedule, it was an exciting two days and we are grateful for attending!
For our part, on Thursday afternoon, AppFusions’ Patrick Li and Ellen Feaheny presented about our new AppSpokes Framework for faster development and deployment of single code-based integration applications for cloud, on-premise, hosted, or hybrid IBM Connections environments. We’ll be sharing more on that soon enough; just getting going with some initial deployments.
David then took it another level and added the header integration into AppFusions’ Immersive for Atlassian Confluence, in IBM Connections, and with a bit of additional theming, he morphed the Confluence theme to mirror the currently applied IBM Connections look and feel/theme.
For example, this:
… which looks a whole lot like the default IBM Connections theme, as shown here:
AppFusions’ Technical PM and overall great human Danielle Zhu was also with us, and AppFusions’ “Boston-camp”spin-off wouldn’t have been the same without her!
AppFusions left the conference with more knowledge than we arrived with or brought too, which to me means success. Our plate runneth over on great IBM Connections’ integrations plans and fired-up-ness — going to be a great rest of the year! THANKS to the Social Connections planning team!
For our fourth consecutive year at this IBM social business conference, AppFusions is pleased to be digging in deeper as a Silver Sponsor, further cementing our belief in connected systems and reduced silos given the social business/collaboration movement sweeping enterprises across the world.
9 of us from the AppFusions team will be attending the IBM ConnectED 2015 conference in Orlando, on January 25th-28th. We can’t wait to share our new and updated product releases with customers and IBMers alike.
This integration allows you to post your WordPress blogs directly to your IBM Connections community. Further, activity streams are logged, and IBM Connections business cards are displayed for the WordPress authors.
Immersive for Atlassian JIRA, in IBM Connections V5•Extended!
Immersive for Atlassian Confluence, in IBM Connections V5 • Extended!
Immersive for Atlassian Stash, in IBM Connections V5 • New!
Immersive for Atlassian Bamboo, in IBM Connections V5 • New!
These integrations bring your Atlassian systems into IBM Connections. All from within IBM Connections, you have powerful advanced search capabilities into all the different Atlassian applications, native IBM business cards in Atlassian applications, you can create a JIRA issue directly or share it, access and interact with Atlassian applications’ live activity streams, and more. AppFusions have been developing these integrations since 2013.
Atlassian Integrations with IBM Sametime
IBM Sametime V9 in Atlassian JIRA • Updated!
IBM Sametime V9 in Atlassian Confluence • Updated!
IBM Sametime V9 in Atlassian Stash • Updated!
IBM Sametime V9 in Atlassian Bamboo • Updated!
IBM Sametime V9 in Atlassian FishEye • Updated!
These integrations allow you to run rich IBM Sametime chat sessions, with context, from inside your Atlassian systems. These integrations have been supported since 2012.
AppFusions will have two demo pods, so we hope you will stop by to check these out and/or to discuss with us your use cases or other possibilities for IBM Connections integrations.
Note: All AppFusions’ integrations are for sale as packaged supported solutions. As you grow and evolve, as well as your systems, so also do your AppFusions’ integrations. We’re right there with you on your integrated social business/collaboration journey.
AppFusions senior integrations experts build supported use-case driven integrations between some of the most popular collaboration tools in the industry. Our integrations are not just web-links. AppFusions’ solutions bridge systems with enhanced user experiences so you can work faster and better.
With over 50 packaged integrations, and counting, AppFusions solutions quickly solve common yet tough pain point integration challenges by bridging together Atlassian Software, IBM Connections and Sametime, Jive software, Dropbox, Box, Google Drive, Egnyte, Alfresco, Microsoft OneDrive, Yammer and Parature, Lingotek (translations), single sign-on solutions (SAML2, Kerberos, OAuth2), UserVoice, and more.
The event, sponsored by IBM and hosted by AppFusions, is designed to bring together social business and platform technology development experts to discuss new strategies for standardizing technologies in support of the burgeoning adoption of social business tools. The workshop will be at Casa de la Vista on Treasure Island.
The lack of adequate standards makes it difficult to create platform bridging or application integration software that comprehensively serves mainstream social business needs of both users and organizations. The workshop will address the growing demand for interoperable social standards to solve mixed-technology challenges caused by today’s fragmented specification and technology landscape.
Workshop discussion topics include:
Key use cases and requirements driving social business
Technologies that can be standardized to solve the problems facing social business
Overall architecture of social business interoperability needs
The difference between standards inside the enterprise and across enterprises
Organic approaches that are evolving without standardization, such as user engagement and custom integration designs
Next steps for evolved social specifications, ranging from OpenSocial to the Federated Social Web
The Workshop event is free to attend, and open to social business leaders and strategists, federated and decentralized social Web technologists, security experts and developers. To register either as an attendee or as a presenter, visit the Workshop information site for instructions.
“For a long time, the W3C has thought that social standards need to be a first-class citizen on the Web. By partnering with the OpenSocial Foundation, we will lay the groundwork for this next step in the evolution of the Web, at our joint workshop in August,” said Harry Halpin, a W3C team member. “We expect that social standards will eventually have as huge an impact as HTML5 has had, both across the enterprise and for users.”
“There is a tremendous need for a standardized component model for delivery of cloud applications into the enterprise, and across many platforms. OpenSocial is the only community-led initiative working in this space to define a standard,” said Mark Weitzel, President of the OpenSocial Foundation. “In working with the W3C, we believe that we can accomplish more and reach a broader audience of developers to proliferate and optimize solutions across enterprises. We are excited to progress our objectives with these upcoming discussions in San Francisco.”
Boeing, Cisco, Dachis Group, Ford, Google, IBM, Jive Software, MIT, Mozilla, Oracle, SAP, SugarCRM, Salesforce, Telecom Italia, Tibco, UCF, W3C and many other industry leaders and social business platform corporations are anticipated at the workshop. Learn more here.
AppFusions is a leader in packaged platform-to-platform integration solutions bridging information silos, and streamlining enterprise process and data redundancies. As early development adopters, AppFusions is already deploying OpenSocial-compliant integrations with Jive Software or IBM Connections on one side, and AtlassianJIRA,Confluence, Stash, FishEye, Crucible, and/or Bamboo on the other side.
AppFusions Breaks Down Silos, Connecting Software and the Enterprise
BOSTON, June 17, 2013 /PRNewswire/ — AppFusions,a social business and engineering systems integration firm, is a Silver Sponsor and featured exhibitor at the E2 Conference, June 17-19 at the Boston Marriott Copley Place.
The E2 Conference (formerly called Enterprise 2.0) kicks off today, showcasing corporations with agendas aimed at a more connected enterprise – both culturally and system-wise. E2.0, also referred to as “Social Business,” is the concept of systems, solutions, and methodologies that encourage businesses to collaborate more openly and seamlessly, both in terms of systems and communications. One of the key goals is improved process efficiencies.
“Enterprise 2.0 is about working more fluidly at the content, data, and systems level. When done right, documented efficiency gains and streamlined business processes result,” Ellen Feaheny, AppFusions’ CEO,explains. As a movement with integrated technologies at its core, E2.0 brings game-changing innovation and performance results to businesses. “E2.0 breaks down human and systems silos inside and outside of enterprises,” Feaheny emphasizes.
Although technological seamlessness is the business and systems goal, it is not yet the norm. That’s where AppFusions steps in.
For example, with AppFusions enterprise-grade content/document management system connectors, physical document collaboration moves away from local desktops, email attachments, or siloed file repositories. Instead, “other system” document management is integrated into social business, project management, or wiki systems. When integrated, enterprise users can preview, edit, download, and embed physical documents stored in external repositories like Box, Dropbox, Alfresco, Google Docs, etc. directly from their social business platform or wiki system as native user experiences.
IT administrators appreciate such integrations to standardize business methodologies, and ward away rogue attachments/document repositories. By providing integrated “best of all worlds” solutions, document management and collaboration is managed, thus mitigating the “wild west” of systems many CIOs wrestle with these days. AppFusions’ packaged content management integrations, to date, mix together Atlassian Confluence, JIRA, IBM Connections, Jive Software, Box, Dropbox, Alfresco, and Google Docs.
Another E2.0 example of AppFusions’ integrations is “in-app/in-context” instant messaging, which allows end users to message or video chat directly from inside an enterprise social, business, or engineering system.
“At the core, these are not technical problems we are solving; these are business collaboration problems that waste crucial time, money, and – even worse – lost contextual mindshare,” Feaheny explains. “If I’m working in a wiki, bug tracker, git repository, or continuous integration server, an AppFusions connector allows me to see whether a recent contributor is online, and if so, I can connect with them instantly using IBM Sametime.” This type of integration is not only convenient, it’s smart.
“I should not have to constantly jump between systems and browsers to collaborate,” she continues. “Instead, AppFusions feels systems should all be conveniently connected, no matter where you are working.”
AppFusions’s booth in the E2 exhibit hall will focus on its 40+ packaged integration applications, bridging systems like Atlassian JIRA, Confluence, Stash, FishEye, Crucible, Crowd, IBM Connections and Sametime, Jive Social Business Platform, Google Drive and Analytics, Box, Dropbox, Alfresco, LingoTek, MixPanel, Parature, UserVoice, iRise, and others.
Come talk to us about how we can solve your application integration problems.
AppFusions is a social business, and engineering systems integrations firm offering multi-technology application solutions. By enabling enterprises to harness together key systems with “plug and play” integrations, corporations almost instantly gain improved efficiencies, faster innovation potential, and ultimately saved time and money. Its product portfolio includes packaged integrations with Atlassian, Jive, IBM, Box, Google, Dropbox, Alfresco, UserVoice, Attensa, and more. AppFusions’ development expertise in the technologies they work with is among the most technically capable in the industry. AppFusions’ customers overlap with their technology partners’ customers – from SMB to Fortune 10s, worldwide. AppFusions is based in San Francisco, and works in the U.S., Australia, and Europe.
It’s been a great last week, as AppFusions has been closing down on many preparations for the imminent IBM Connect 2013 conference in Orlando, Florida from Jan 27 – Jan 31. We are sponsoring an exhibitors booth at the event, and can’t wait – it’s going to be a great event.
Further, last Wednesday we received a mail notifying us that we’d made the cut for a stage demo at the 2nd annual “App Throwdown” event – an open demo/contest for OpenSocial application integrations into IBM platforms.
Here’s a video of last years, where we were sitting in the audience. Now, maybe we’re app integration geeks or something, not sure — but anyways, for us this event got us into quite a bit of an excited tizzy! It screamed “APPFUSIONS!”
After the session we all mutually agreed: “WE need to be on that stage next year!”
And now we will be! Yay!
In the last week, our development team has continued working hard at putting in many last minute polishes to show off IBM and Atlassian software, together, for the following integrations:
IBM Sametime in Atlassian JIRA, Confluence, Stash, Fisheye, and Bamboo
Atlassian JIRA, Confluence, and Stash in IBM Connections
Wherever a user’s name shows up in the interfaces, presence indicators tell you whether your colleague is available to chat. If green (available), right click on the presence indicator and start a chat on the fly.
Bring in other colleagues for group chat, or if your IBM Sametime subscription allows for video conferences, go ahead — launch into those too — all from right inside your Atlassian tools!
As for the IBM Connections integrations, of course these are a bit different – but also super convenient to bring together platforms, and more, workflows.
Feature highlights include:
From IBM Connections, launch the sharebox and log a JIRA issue straight-away from IBM Connections.
Atlassian JIRA, Confluence, Stash (and Bamboo, coming) activity is pushed continually in real-time into IBM Connections, with:
live contextual / actionable links back to your Atlassian systems – or,
you can launch a JIRA embedded experience for commenting or status dispositioning, from IBM Connections.
Atlassian Confluence is integrated into IBM Connections as the “wiki of choice”. (From the Apps menu, find Atlassian Confluence wiki at your fingertips.)
Finally, if you are one of those mobile types (aren’t we all?!) — we’ve got you covered there too. Directly within IBM Connections’ mobile application, find native JIRA and Confluence application nodes!
As great as all this is – it’s only the beginning!
AppFusions will be continuing to feature develop these integrations throughout 2013.
We can’t wait to see how they evolve, with the help and great ideas of IBM and Atlassian customers who in our experience, like AppFusions, simply want to “bring it together!”
I spoke with Jens Schumacher, Atlassian’s Group Product Manager for developer tools. These tools include: Bamboo, Crucible, Fisheye, and Stash. Bamboo provides continuous integration and release management. Crucible supports code review and Fisheye allows you to search out source code artifacts of various source code management flavors and browse commits, files, revisions, or related people. It also integrates seamlessly with JIRA.
Enter Stash! Stash incorporates the latest and greatest technologies in DVCS source code management and Git, allowing you to create and manage repositories, set up fine-grained permissions, and collaborate on code in a secure, fast and enterprise-grade manner.
Jens continued, providing me more background on the development of Stash.
Stash is the latest in Atlassian’s developer tools suite and was released in the Spring of 2012. Atlassian’s existing developer tools are already quite popular in development houses, but still the developers wanted more. They wanted to be able to host code in their own repository behind the firewall.
More – engineers are always pushing the envelope: they wanted Git support, a massively popular and growing DVCS approach used in code development and management these days.
To cleanly meet this need in both a tool and extensibility, Atlassian decided to build Stash from scratch including a ground up extensible API approach, rather than on top of their existing tools.
Stash incorporates code review into the development workflow so the new code gets properly reviewed before it is merged with the existing source code.
To facilitate development, Stash allows developers to set up branches, where code changes can be made in isolation and reviewed before being integrated with the mainline. This separation makes development of new features less complex.
You can easily have new code reviewed while incorporating automated testing tools as well. Stash facilitates the merging of reviewed code into the core source code. This concept of a separate workflow for development is popular with open source efforts and Atlassian has now taken a leading industry position with the Stash offering, enabling this capability inside the firewall.
Integration efforts with Stash are already supported in a number of ways.
Per Jens, 80% of the Fortune 500, as well as many many smaller firms, use Atlassian JIRA for issue tracking.Stash is fully integrated with JIRA so you can link code in Stash to a JIRA ticket and track the progress of changes.
Stash also natively integrates with enterprise user directory systems, such as Active Directory or LDAP, to make deployment easier within the enterprise.In addition, again, Stash was built with an extensive REST API to make information within Stash easily integrate-able with other tools.
Jens gave me a simple use case. Their customers often want to migrate content from one repository to another or from the cloud to within the firewall. Stash can automate aspects of this common process to simplify the effort.
In the future, Stash will be enhanced with more branch permission capabilities to better ensure that all code gets reviewed before it is merged into the core source code. They are also working hard on scalability requirements to better serve their many large customers. Currently, Stash supports up to 500 user licenses. Finally, they are working on adding enhanced collaboration capabilities for code review.
Jens noted that Atlassian has a massive ecosystem. This is helpful as there already are a number of add-ons for Stash. For example, there is a badge add-on to acknowledge developers’ efforts and skills. Another is a chart add-on to provide statistics. AppFusions built a Stash commenting add-on for Atlassian’s annual CodeGeist competition. Also, add-ons are available to help with different workflows that organizations have in place.
On top of all that, Atlassian’s very popular SourceTree DVCS client further removes DVCS source code tool complexity, and is used to support and guide the process of adding new workflows with proper controls within branching efforts, among other.
Customer response has been very positive since the release of Stash earlier this year. The timing was right for the release, as developers were ready for it.
Jens’ team is now providing new releases every 7 – 9 weeks, with many of the new capabilities coming from customer input.
New needs are always arising in enterprise software development efforts, and many organizations and third party developers want to tackle these needs. Stash provides enhanced support for these efforts.
Just received a googlegroup mail that is too good to not share, from Don Brown, Atlassian’s engineer extraordinaire, and in his current incarnation, Atlassian’s “remote app”, eh hem, PLUGINS 3 Framework Design Architect!
He and his team (including Bob, Sam, Yon) finally solved the riddle – the riddle of:
providing a single application development AND deployment framework for both on-premise and OnDemand instantiations of Atlassian’s platforms (i.e., Confluence, JIRA, etc.).
It was a riddle that rattled long and hard in recent months, and really since the release of Atlassian OnDemand (and months before … over a year ago!).
The answer: Introducing Atlassian Plugins 3 Framework!
While I could summarize, sometimes emails are left best in the perfect state that they came in as.
This is one of them.
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Don Brown Sent: Monday, August 20, 2012 3:21 PM To: firstname.lastname@example.org; email@example.com Subject: Remote Apps is now Plugins 3
Over the next few months, the Remote Apps project will be transforming into Plugins 3, which is intended to be a complete replacement for Plugins 2. The scope of Plugins 3 has expanded past just remotely hosted applications, and now brings its permissions and (now optional) sandboxing capabilities to in-process plugins as well. We expect to deliver the first developer preview of this technology at AtlasCamp 2012 in September .
The backstory here is after our Summit 2012 presentation, we’ve been having a bunch of internal discussions as well as discussions with partners and existing plugin vendors about the capabilities and future of Remote Apps, and two limitations quickly stood out:
Remote Apps isn’t on-premise friendly
The sandboxing was too restrictive for many (most?) existing plugins
The first limitation was really the showstopper – if we encourage plugin vendors to write Remote Apps that can only work for OnDemand, 85% of our current customer base, the on-premise installations, won’t benefit, and worse, it could mean fewer and fewer plugins as developers won’t want to maintain two code bases. The technical problem with Remote Apps and on-premise is that, since all the code is running on a remote server, it requires the on-premise Atlassian product to be addressable from that remote server, which almost always means the on-premise instance must be open to the Internet. The only ways to get around this – some sort of reverse HTTP firewall-poking agent or locally installed Remote Apps – are not where we want to go.
The second problem of sandboxing is because Remote Apps was an all-or-nothing proposition. Your app had to exist fully in the UI sandboxes we had in place (IFrames or strict HTML sanitization). What we wanted instead was to expand the permission system to include permissions that would allow any plugin, in-process or remote, to be written, and therefore, ensure 100% of existing version 2 plugins could migrate.
The solution we decided upon is Plugins 3. With Plugins 3, you can write a single binary (jar file) and deploy that plugin locally (in-process as you do now) or remotely in a standalone container running on a platform like Heroku. Within the plugin descriptor itself, there will be information on where the plugin is hosted remotely if that installation method is chosen. Therefore, the developer experience is like this:
Write a version 3 plugin
Deploy to Heroku (or where ever) to support OnDemand instances using the provided standalone container
Register in the Marketplace as supporting remote and local installations
When an OnDemand administrator clicks ‘Install’, they will have the plugin installed as a remote descriptor pointing at your remotely hosted instance. When an on-premise administrator clicks ‘Install’, the plugin jar will download and run in-process like before. In both cases, the same plugin jar that was registered in the Marketplace is used.
Foundational to Plugins 3 is the concept of permissions, where a plugin is required to declare what APIs, code execution privileges, or sandbox breaking capabilities it needs. In addition to the existing Remote Apps permissions, Plugins 3 includes additional ones like ‘execute_java’, ‘use_private_apis’, and ‘generate_any_html’. This provides Atlassian the ability to define which permissions are available to side-loaded plugins in OnDemand, which need curation in the Marketplace, and which are only available for on-premise installations.
In all cases, the OnDemand or on-premise administrator will have to view and explicitly approve the permissions before the installation can take place. This also means Plugins 3 will be able to support every current version 2 plugin with the quick migration step of adding permission declarations to the plugin descriptor.
However, if the migrated plugin is to be able to be executed by the container, significant effort, if not a complete rewrite, will likely be necessary.
In a nutshell, here is what has changed:
New permissions element in plugin-info in atlassian-plugin.xml
New plugin module descriptors for each Remote App extension point
Ability to use atlassian-plugin.xml instead of a Remote App descriptor, though the Remote App descriptor format is still supported
New container for running a version 3 Plugin outside the product
Set of services that are implemented in container and local versions
In the next few days, we will be merging this work, currently in the ‘p3’ branch, into master. I will also soon be publishing a Plugins 3 Tech Spec with a lot more detail than I’ve given here. I’m excited about this new direction as it will bring the benefits of Remote Apps to all plugins for both OnDemand and on-premise. Our goals are to make plugins secure, easy to write, and OnDemand-friendly, and the future looks bright.