We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-04-15 15:56:17 +0200

What is the participation and contribution policy for Jolla's open source contributors in open source projects?

Version: 15 April 2014

This is a copy of Jolla's Participation and contribution policy for Jolla's open source contributors in open source projects. It is taking effect as of 15th April 2014 but may take some time to fully show its full effects within the open source projects that Jolla employees are participating in.

It's meant as both an internal policy and something for community members and participants of open source projects to better understand how to deal with Jolla employees, their actions, statements, etc. where they're encountered, in and outside official communication channels.

When you as a Jolla employee are participating in open source projects, you are participating as yourself. You have your own opinions and do not speak on behalf of the company unless explicitly stated in your statements. If an official response from Jolla is needed, request to contact Jolla through established communication channels listed at jolla.com and sailfishos.org.

As a Jolla employee participating/contributing as part of your work in open source projects or maintaining open source projects you are however expected to - based on a subset of Jolla values:

  • Be transparent externally - be active in communication channels of the projects you are part of, maintain public roadmaps, respond to bug reports, make others aware of your work and activities in public.
  • Jolla is open source driven -- to respect open source community contribution. Jolla originates from open source and is built on open source.
  • Respect other people’s work and expertise - be meritocratic in commit privileges, be open to other views despite disagreements
  • Respect customers and partners - our open source contributors are also our customers and partners, or our future customers. Likewise don't disclose partners data that you have no permission to disclose.
  • DIT – doing it together - to actively pursue and nurture community/customer involvement in your open source projects
  • Be diplomatic in your daily communication, resolve disagreements and conflicts using the methods of the given open source project. If problems escalate or pre-exist, seek advice and guidance before taking hard action.

If you are participating in official communication channels related to developer and/or open source communication (such as sailfishos.org, related official IRC channel, social media, etc), understand that you are representing Jolla as part of your work. Please consult with the owner of the communication channel for guidance on behaviour and in case of problematic situations. Exercise caution in what you say, and promise.

As a open source contributor, if you experience that the employees of Jolla when contributing as part of their work are not adhering to these expectations, contact developer-care at jolla.com for a discussion about the problem at hand.

We ask that you attempt to resolve personal disagreements and conflicts using discussion, diplomacy and the methods of the given open source project that you are both participating in first as Jolla employees are first and foremost participating as their personal selves in open source projects.

What is the participation and contribution policy for Jolla's open source contributors in open source projects?

Version: 15 April 2014

This is a copy of Jolla's Participation and contribution policy for Jolla's open source contributors in open source projects. It is taking effect as of 15th April 2014 but may take some time to fully show its full effects within the open source projects that Jolla employees are participating in.

It's meant as both an internal policy and something for community members and participants of open source projects to better understand how to deal with Jolla employees, their actions, statements, etc. where they're encountered, in and outside official communication channels.

When you as a Jolla employee are participating in open source projects, you are participating as yourself. You have your own opinions and do not speak on behalf of the company unless explicitly stated in your statements. If an official response from Jolla is needed, request to contact Jolla through established communication channels listed at jolla.com and sailfishos.org.

As a Jolla employee participating/contributing as part of your work in open source projects or maintaining open source projects you are however expected to - based on a subset of Jolla values:

  • Be transparent externally - be active in communication channels of the projects you are part of, maintain public roadmaps, respond to bug reports, make others aware of your work and activities in public.
  • Jolla is open source driven -- to respect open source community contribution. Jolla originates from open source and is built on open source.
  • Respect other people’s work and expertise - be meritocratic in commit privileges, be open to other views despite disagreements
  • Respect customers and partners - our open source contributors are also our customers and partners, or our future customers. Likewise don't disclose partners data that you have no permission to disclose.
  • DIT – doing it together - to actively pursue and nurture community/customer involvement in your open source projects
  • Be diplomatic in your daily communication, resolve disagreements and conflicts using the methods of the given open source project. If problems escalate or pre-exist, seek advice and guidance before taking hard action.

If you are participating in official communication channels related to developer and/or open source communication (such as sailfishos.org, related official IRC channel, social media, etc), understand that you are representing Jolla as part of your work. Please consult with the owner of the communication channel for guidance on behaviour and in case of problematic situations. Exercise caution in what you say, and promise.

As a open source contributor, if you experience that the employees of Jolla when contributing as part of their work are not adhering to these expectations, contact developer-care at jolla.com for a discussion about the problem at hand.

We ask that you attempt to resolve personal disagreements and conflicts using discussion, diplomacy and the methods of the given open source project that you are both participating in first as Jolla employees are first and foremost participating as their personal selves in open source projects.

What is the participation and contribution policy for Jolla's open source contributors in open source projects?

Version: 15 16 April 2014

Edit on 16 April 2014: Adjust language a little bit to make it clearer

This is a copy of Jolla's Participation and contribution policy for Jolla's open source contributors in open source projects. It is taking effect as of 15th April 2014 but may take some time to fully show its full effects within the open source projects that Jolla employees are participating in.

It's meant as both an internal policy and something for community members and participants of open source projects to better understand how to deal with Jolla employees, their actions, statements, etc. where they're encountered, in and outside official communication channels.

When you as a Jolla employee are participating in open source projects, you are participating as yourself. You have your own opinions and do not speak on behalf of the company unless explicitly stated in your statements. If an official response from Jolla is needed, request to contact Jolla through established communication channels listed at jolla.com and sailfishos.org.

As a Jolla employee participating/contributing as part of your work in open source projects or maintaining open source projects you are however expected to - based on a subset of Jolla values:

  • Be transparent externally - be active in communication channels of the projects you are part of, maintain public roadmaps, respond to bug reports, make others aware of your work and activities in public.
  • Jolla is open source driven -- to To respect open source community contribution. Jolla is open source driven, originates from open source and is built on open source.
  • Respect other people’s work and expertise - be meritocratic in commit privileges, be open to other views despite disagreements
  • Respect customers and partners - our open source contributors are also our customers and partners, or our future customers. Likewise don't disclose partners data that you have no permission to disclose.
  • DIT – doing it together - to actively pursue and nurture community/customer involvement in your open source projects
  • Be diplomatic in your daily communication, resolve disagreements and conflicts using the methods of the given open source project. If problems escalate or pre-exist, seek advice and guidance before taking hard action.

If you are participating Understand that participation in official Jolla communication channels related to developer and/or open source communication (such as sailfishos.org, related sailfish.org, official IRC channel, channels, social media, etc), understand media presence, etc) does mean that you are representing Jolla as part of your work. Please consult with the owner of the communication channel for guidance on behaviour and in case of problematic situations. Exercise caution in what you say, say and promise.

As a open source contributor, if you experience that the employees of Jolla when contributing as part of their work are not adhering to these expectations, contact developer-care at jolla.com for a discussion about the problem at hand.

We ask that you attempt to resolve personal disagreements and conflicts using discussion, diplomacy and the methods of the given open source project that you are both participating in first as Jolla employees are first and foremost participating as their personal selves in open source projects.

What is the participation and contribution policy for Jolla's open source contributors in open source projects?

Version: 16 April 2014

Edit on 16 April 2014: Adjust language a little bit to make it clearer

This is a copy of Jolla's Participation and contribution policy for Jolla's open source contributors in open source projects. It is taking effect as of 15th April 2014 but may take some time to fully show its full effects within the open source projects that Jolla employees are participating in.

It's meant as both an internal policy and something for community members and participants of open source projects to better understand how to deal with Jolla employees, their actions, statements, etc. where they're encountered, in and outside official communication channels.

When you as a Jolla employeeemployee are participating in open source projects are participating in open source projects, , you are participating as yourself. You have your own opinions and do not speak on behalf of the company unless explicitly stated in your statements. If an official response from Jolla is needed, request to contact Jolla through established communication channels listed at jolla.com and sailfishos.org.

As a Jolla employee employee participating/contributing as part of your work in open source projects or maintaining open source projects projects you are however expected to - based on a subset of Jolla values:

  • Be transparent externally - be active in communication channels of the projects you are part of, maintain public roadmaps, respond to bug reports, make others aware of your work and activities in public.
  • To respect open source community contribution. Jolla is open source driven, originates from open source and is built on open source.
  • Respect other people’s work and expertise - be meritocratic in commit privileges, be open to other views despite disagreements
  • Respect customers and partners - our open source contributors are also our customers and partners, or our future customers. Likewise don't disclose partners data that you have no permission to disclose.
  • DIT – doing it together - to actively pursue and nurture community/customer involvement in your open source projects
  • Be diplomatic in your daily communication, resolve disagreements and conflicts using the methods of the given open source project. If problems escalate or pre-exist, seek advice and guidance before taking hard action.

Understand that participation in official Jolla communication channels (such as sailfish.org, official IRC channels, social media presence, etc) does mean that you are representing Jolla as part of your work. Please consult with the owner of the communication channel for guidance on behaviour and in case of problematic situations. Exercise caution in what you say and promise.

As a open source contributor, if you experience that the employees of Jolla when contributing as part of their work are not adhering to these expectations, contact developer-care at jolla.com for a discussion about the problem at hand.

We ask that you attempt to resolve personal disagreements and conflicts using discussion, diplomacy and the methods of the given open source project that you are both participating in first as Jolla employees are first and foremost participating as their personal selves in open source projects.

What is the participation and contribution policy for Jolla's open source contributors in open source projects?

Version: 16 April 2014

Edit on 16 April 2014: Adjust language a little bit to make it clearer

This is a copy of Jolla's Participation and contribution policy for Jolla's open source contributors in open source projects. It is taking effect as of 15th April 2014 but may take some time to fully show its full effects within the open source projects that Jolla employees are participating in.

It's meant as both an internal policy and something for community members and participants of open source projects to better understand how to deal with Jolla employees, their actions, statements, etc. where they're encountered, in and outside official communication channels.

When you as a Jolla employee are participating in open source projects, you are participating as yourself. You have your own opinions and do not speak on behalf of the company unless explicitly stated in your statements. If an official response from Jolla is needed, request to contact Jolla through established communication channels listed at jolla.com and sailfishos.org.

As a Jolla employee participating/contributing as part of your work in open source projects or maintaining open source projects you are however expected to - based on a subset of Jolla values:

  • Be transparent externally - be active in communication channels of the projects you are part of, maintain public roadmaps, respond to bug reports, make others aware of your work and activities in public.
  • To respect open source community contribution. Jolla is open source driven, originates from open source and is built on open source.
  • Respect other people’s work and expertise - be meritocratic in commit privileges, be open to other views despite disagreements
  • Respect customers and partners - our open source contributors are also our customers and partners, or our future customers. Likewise don't disclose partners data that you have no permission to disclose.
  • DIT – doing it together - to actively pursue and nurture community/customer involvement in your open source projects
  • Be diplomatic in your daily communication, resolve disagreements and conflicts using the methods of the given open source project. If problems escalate or pre-exist, seek advice and guidance before taking hard action.

Understand that participation in official Jolla communication channels (such as sailfish.org, official IRC channels, social media presence, etc) does mean that you are representing Jolla as part of your work. Please consult with the owner of the communication channel for guidance on behaviour and in case of problematic situations. Exercise caution in what you say and promise.

As a open source contributor, if you experience that the employees of Jolla when contributing as part of their work are not adhering to these expectations, contact developer-care at jolla.com for a discussion about the problem at hand.

We ask that you attempt to resolve personal disagreements and conflicts using discussion, diplomacy and the methods of the given open source project that you are both participating in first as Jolla employees are first and foremost participating as their personal selves in open source projects.