-
Notifications
You must be signed in to change notification settings - Fork 1
Glossary Definitions - Terminology of DevRel #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
j12y
wants to merge
6
commits into
main
Choose a base branch
from
dev/137/terminology-of-devrel
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
23b575d
added the glossary defination
pratik-mahalle 4449d42
Merge pull request #1 from pratik-mahalle/main
j12y fcc641a
incorporated edits, added version, iterated on definitions
j12y 125cfd1
propose replacing technical support in devrel definition
j12y a8166d8
amended definitions of community manager and developer advocate to in…
j12y 499a23a
reworded a few sentences for clarity
j12y File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| term: Community Manager | ||
| version: 1.0.0 | ||
| --- | ||
|
|
||
| A Community Manager is a typical role within Developer Relations programs that has responsibility for maintaining the health of a Developer Community. | ||
|
|
||
| Community Managers will use strategies that are aimed at achieving successful outcomes for a community -- both for its individual members and represented organizations. Common objectives include the growth of the community through new members, establishing processes for how members of the community behave and engage with each other, and facilitating participation between members of the community for mutual benefit. | ||
|
|
||
| Some common tactics of Community Managers include welcoming people into the community, facilitating networking activities, sharing information, moderating discussions, organizing events, and establishing ties between the community members and organizations represented. | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| term: Developer Advocate | ||
| version: 1.0.0 | ||
| --- | ||
|
|
||
| Advocacy is the public support or recommendation of a particular action, cause, or policy. A Developer Advocate is a role that advocates for the use of a specific set of technologies or services publicly on behalf of an organization. | ||
|
|
||
| Developer Advocates often have a cross-functional skillset and act as a public figure to lead within a community through their expertise and by becoming a liasion or bridge to gather feedback from members of the community for their organization. | ||
|
|
||
| Common objectives include generating awareness and setting an example for other members on the successful adoption of the technology. Some common tactics of Developer Advocates include creating technical content, representing an organization at events, gathering developer usage feedback, and engaging in technical discussions with the public. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| term: Developer Community | ||
| version: 1.0.0 | ||
| --- | ||
|
|
||
| A community is a group of people who come together online or in-person because they share a common interest, goal, or trait. A developer community is a community that forms around a specific technology or product that is used by software developers. | ||
|
|
||
| People may seek community for peer-to-peer recommendations and support, collaboration on achieving outcomes, sharing knowledge, extending the original technology, or purely a sense of belonging. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| term: Developer Educator | ||
| version: 1.0.0 | ||
| --- | ||
|
|
||
| A Developer Educator is a typical role within Developer Relations programs that has responsibility for the learning and training programs on behalf of an organization. | ||
|
|
||
| Developer Educators have skills and strategies that include technical writing, editing, information architecture, curriculum development, learning pedagogy, video production, and classroom experience. | ||
|
|
||
| Some common tactics of Developer Educators include providing different modalities of content including reference documentation, frequently asked question knowledge bases, tutorials, how-to videos, and learning guides. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| term: Developer Evangelist | ||
| version: 1.0.0 | ||
| see: | ||
| - developer-advocate | ||
| --- | ||
|
|
||
| Evangelism is the act of sharing the message and teachings of a faith. A Developer Evangelist is a role that evangelizes for the use of a specific set of technologies or services on behalf of an organization. | ||
|
|
||
| Developer Evangelists often have a cross-functional skillset but primarily act as a public spokesperson on behalf of an organization. Common objectives include generating awareness of a product or service and creating demand among technical members of an organization to adopt it. | ||
|
|
||
| Some common tactics of Developer Evangelists include creating technical content, representing an organization at events, and engaging in promotional programs through social media and public discussion. | ||
|
|
||
| Developer Evangelism was a term commonly used in Developer Relations programs where the mission is primarily based on public outreach and promotion, using technical knowledge and skill to excite, inspire and educate. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| term: Developer Experience Engineer | ||
| version: 1.0.0 | ||
| --- | ||
|
|
||
| A Developer Experience Engineer is a typical role within Developer Relations programs that has a responsibility for providing resources that aid with the successful adoption of a developer product. | ||
|
|
||
| Developer Experience Engineers are typically engineering roles that focus on the creation of SDKs, CLIs, UIs, Docs, etc. that are important for software developers to succeed in adopting a technology but may be accessories to the core product. | ||
|
|
||
| Often synonymous with Developer Relations Engineer. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| term: Developer Experience | ||
| version: 1.0.0 | ||
| --- | ||
|
|
||
| Developer Experience is the user experience of a technology, product, or service where the user is a software developer. | ||
|
|
||
| The experience of an individual in the adoption and use of a technology is important to Developer Relations because friction that prevents the realization of value is an obstacle or barrier to a successful outcome for the organization. | ||
|
|
||
| It is also common for this term to be used to indicate the collective experience of software developers internal to an organization with the set of tools used in the production of a software product. This is not the meaning typically used within the context of DevRel. | ||
|
|
||
| Commonly abbreviated as DX or DevEx. | ||
|
|
||
| Contributors to a positive developer experience include well designed and intuitive APIs, comprehensive and accurate documentation, ease of use with developer tools (Client SDKs, CLIs), and a welcoming community with support. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| term: Developer Relations Lead | ||
| version: 1.0.0 | ||
| --- | ||
|
|
||
| A Developer Relations Lead is a role responsible for the overall Developer Relations program and objectives. | ||
|
|
||
| * Developer Relations Manager is often an individual contributor role within an organization with leadership responsibility for the Developer Relations program. | ||
|
|
||
| * Head of Developer Relations is frequently synonymous with a position that has budget and resources within an organization to achieve its objectives. | ||
|
|
||
| DevRel Leaders are responsible for the strategy, execution, and day-to-day management of the program to align initiatives with broader business objectives. | ||
|
|
||
| Leveling as a Sr. Manager, Director, VP, and beyond indicate the size of the team and management reporting hierarchy. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,5 @@ | ||
| term: Developer Relations | ||
| version: 1.0.0 | ||
| --- | ||
|
|
||
| # Developer Relations | ||
|
|
||
| Developer Relations is the practice of building and nurturing relationships with external and internal teams through community engagement, technical support, education, and advocacy to enable the successful adoption of an organization’s developer products and drive business value. | ||
| Developer Relations is the practice of building and nurturing relationships with external and internal teams through community, advocacy, education, and developer experience to enable the successful adoption of an organization’s developer products and drive business value. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.