Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
Developer Documentation
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
brienne
Developer Documentation
Commits
f1da72b7
Commit
f1da72b7
authored
8 years ago
by
Sean Madsen
Browse files
Options
Downloads
Patches
Plain Diff
extend-stages - removing intro paragraph that doesn't seem to add any
real content
parent
6722fd61
No related branches found
Branches containing commit
No related tags found
Loading
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/extend-stages.md
+1
-20
1 addition, 20 deletions
docs/extend-stages.md
with
1 addition
and
20 deletions
docs/extend-stages.md
+
1
−
20
View file @
f1da72b7
# Extension Life cycle
The CiviCRM ecosystem is built on the belief that non-profit
organizations can serve themselves best by collaborating in development of their
data-management applications. As staff, volunteers, and consultants for
non-profit organizations, we can share our new enhancements and extensions --
and build a richer whole for the entire ecosystem.
Of course, this sharing arrangement means that many members of the community
have a split role, e.g.
-
Sometimes, we are consumers. We want to quickly browse the available
extensions, pick the ones which look best, and install them. We
expect these to just work -- both now and going forward (with future
upgrades).
-
Sometimes, we are developers. We enjoy building great functionality, and we
want to invite people to use our products, but we need to juggle the
publishing tasks (like testing and maintenance releases) with the goals
and resources provided by our bosses and clients.
The purpose of this document is to describe the process of publishing
extensions through the CiviCRM ecosystem.
This document describes the process of publishing extensions within the CiviCRM ecosystem.
## Definitions
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment