Our mission is to engage a broad community into ownership of software and other projects. The resources of project contributors are limited and new demands are not easy to fulfill. Fortunately, this can be aided by the substantial community of specialists that permeates the web. They publish blogs, answer questions, and offer free and paid consulting services. Simply, ApiFusion connects project's demands and supply from community.
Here, online communities are formed around projects to unite all aspects of project support: documentation, public Q&A, commercialization, and even evolution into new projects. This engagement creates immortality potential for these Egregores and their associated projects, countering even the eventual and unavoidable abandonment of projects by their founders.
Modern applications comprise multiple independent modules, internal and from outside. They are connected by APIs.
API is the highest level of reusable software module formalization. Any change to the project eventually will be reflected in API SDLC. This level of abstraction is a pain point for the majority of software projects.
The limit of (mostly human) resources leaves most support layers under-server. This means that documentation, development, questions, tests, samples, and all other aspects of the SDLC do not receive sufficient resources.
The compatibility matrix for any API has virtually infinite variations which the API owner cannot possibly cover. There are simply too many users with their own specific environments. To make matters worse, the conditions where APIs are used are increasingly dynamic. This is driven by an expanding global audience and constant developments in hardware, OS-es, browsers and standards. The only way to bring API user needs under control is to utilize community expertise. API oriented communities are agile over time; they remain relevant to each API's actual current state and usage. These communities will respond to respective APIs' market needs.
ApiFusion facilitates this by creating a place for those in the know to provide free and commercial support to whoever needs it. In the other direction, it provides a place for those in need of support to reach those who wish to provide it. It opens and manages a feedback loop for APIs across all SDLC aspects, taking their support beyond the intial team in an unprecedented way.
This platform serves as an online API registry for open and closed source software libraries and services. With an emphasis on social coding, it streamlines content generation for and by different groups involved: developers, project managers, business analysts, designers, lawyers, security professionals, and so on. Individual views are provided for each category of specialists, while maintaining a unified project structure.
Platform and Service
The areas covered by ApiFusion include compatibility, support, and documentation. Compatibility is covered in all its form, from legal to platform. Support is provided for everything from new feature requests to implementation offers. Documentation is synced live with project code. It extends well beyond developer-only needs to include the needs of other fields: marketing, design, etc. This paints a complete image of the project for varied specialists.
As with all other areas of the knowledge base, this is assembled through collaboration in the community. Ideas, requests, proposals, solutions with feedback and traceable certifications are brought together under the same platform. ApiFusion is a reactive knowledge base, animated by community collaboration, and an organization tool for people-driven projects. It is a unified mega-market for projects.
ApiFusion.org is an open source platform which may be deployed in its own environment and synchronized with this ApiFusion.com service.
ApiFusion.org initially was developed to serve an open source project, API documentation and community comments. As main project contributors will not necessarily be maintaining it, we have opened writing privileges to everyone. While the primary documentation will remain the product of a consensus, yet the alternative opinions shall be honored. They will persist in the comments/discussions and in related alternative implementations pages.
Additionally, API documentation will be available in different languages. The whole ApiFusion knowledge base will be segmented by locale, including the UI and discussions.
The documentation pages will be available via major IDEs as help and inline suggested content.
API documentation could be parsed from sources and pages will have a direct relation with generated documentation tree making the ApiFusion pages an extension for embedded within code.
The work is in progress.
The primary grouping will be done by organization/site and by projects inside of it.
- Consult the User's Guide for information on using the wiki software.
- Use Cases
- Design:ApiFusion.org/wiki Wiki relations design
- ApiFusion environment Setup docs
- MediaWiki FAQ
- Localize MediaWiki for your language
The ApiFusion site is a public place and is not responsible for each contributor's actions and/or content provided or viewed. By posting on ApiFusion, you agree to take full responsibility for the content of your post. ApiFusion reserves the right to block and remove inappropriate content at its own digression. Please keep your feelings and non-project related content separate from ApiFusion. Voting and rating features for different categories will be provided for contributor and user convenience.