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
58cff12f
Commit
58cff12f
authored
7 years ago
by
totten
Committed by
GitHub
7 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Update extend-stages.md
parent
2ccb1451
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/extend-stages.md
+10
-11
10 additions, 11 deletions
docs/extend-stages.md
with
10 additions
and
11 deletions
docs/extend-stages.md
+
10
−
11
View file @
58cff12f
...
@@ -11,21 +11,20 @@ data-management applications. As staff, volunteers, and consultants for
...
@@ -11,21 +11,20 @@ data-management applications. As staff, volunteers, and consultants for
non-profit organizations, we can share our new enhancements and extensions
non-profit organizations, we can share our new enhancements and extensions
—
and build a richer whole for the entire ecosystem.
—
and build a richer whole for the entire ecosystem.
Of course, this
sharing arrangement means that many members of the community
Of course, this
collaboration means that we're all engaged in some give-and-take.
have split roles. For examp
le:
We alternate between two ro
le
s
:
-
**Consumers**
want to quickly browse the available
-
**Consumers**
: Sometimes we're the receivers. We
want to quickly browse the available
extensions, pick the ones which look best, and install them.
They
extensions, pick the ones which look best, and install them.
We
expect the extensions to
just
work
—
both now and going forward (with
expect the extensions to work
—
both now and going forward (with
future upgrades).
future upgrades).
-
**Developers**
enjoy building great functionality, and
-
**Developers**
: Sometimes we're the providers. We
enjoy building great functionality, and
want to invite people to use
thei
r products, but need to juggle the
want to invite people to use
ou
r products, but need to juggle the
publishing tasks (like testing and maintenance releases) with the goals
publishing tasks (like testing and maintenance releases) with the goals
and resources provided by
thei
r bosses and clients.
and resources provided by
ou
r bosses and clients.
With our extension life cycle processes, we seek to build an ecosystem that
With the extension life-cycle described here, we seek to build an ecosystem that
meets the needs of both consumers and developers, while acknowledging that many
balances the needs of both consumers and developers.
people often play both roles.
## Definitions
## 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