Compare commits
37
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
5e41cdb5be | ||
|
|
c148d8b4d4 | ||
|
|
8b0831378e | ||
|
|
4f7547f29d | ||
|
|
4be21e63d6 | ||
|
|
da603b1809 | ||
|
|
ca7da7d1b6 | ||
|
|
4997bbb1b3 | ||
|
|
83b85bf2ec | ||
|
|
599cf0bb46 | ||
|
|
81d622f081 | ||
|
|
e56f37a08d | ||
|
|
8fb1273bcb | ||
|
|
2c9089e8dc | ||
|
|
7240cfb29d | ||
|
|
28311bef1d | ||
|
|
89312c13c7 | ||
|
|
f334f0816e | ||
|
|
b06d31906b | ||
|
|
45ae3195d5 | ||
|
|
5bdd0602be | ||
|
|
bdc3d45717 | ||
|
|
09121fd419 | ||
|
|
46ccf7a1f4 | ||
|
|
b312fbadd1 | ||
|
|
16216aecfe | ||
|
|
175ac74c42 | ||
|
|
ce427fc471 | ||
|
|
4299bf664f | ||
|
|
4a29ffd658 | ||
|
|
de5beca1b4 | ||
|
|
29ed1b66b1 | ||
|
|
8fae2d4f39 | ||
|
|
1c3b994d1c | ||
|
|
d3bb6e63fe | ||
|
|
6eaaaa14be | ||
|
|
6611c8757b |
@@ -0,0 +1 @@
|
||||
|
||||
@@ -0,0 +1,37 @@
|
||||
# How to request goods or services for the organization
|
||||
|
||||
Status is a rapidly growing organization with multiple moving parts. As a result, core contributors may need to utilize new tools, technologies, or seek support from consultants and other service providers to support our expansion journey.
|
||||
|
||||
To ensure that these needs align with the organizational strategy, priorities, and established policies, it is crucial that each core contributor follows the standard process for requesting goods/services.
|
||||
|
||||
Please carefully read the following instructions to ensure a smooth and timely process:
|
||||
|
||||
1. When you need to request goods/services falling under the categories listed below, please raise a [request for goods/services](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4) in [SpiffWorkflow](https://prod.mod.spiff.status.im/).
|
||||
- **Software & Licenses**: (new tools, apps, subscriptions, etc.)
|
||||
- **Consulting fees**: (consultants, freelancers)
|
||||
- **Other fees**: (bounties)
|
||||
|
||||
> For instructions on how to raise a request, please refer to this [guide](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#3ef6bd6141f84ff496cfea785a514a5a).
|
||||
|
||||
If you are unsure about the categories or how to proceed with your specific case, you can get in touch with the Finance team.
|
||||
|
||||
2. Your request will be reviewed by a Budget Owner (usually the Project Lead) and, where required, by the relevant Service Units. The approval process will be handled automatically. Please ensure that you provide all necessary details regarding your request, as these are crucial for the Project Leads and Service Units to review and make the necessary arrangements.
|
||||
|
||||
> Note: The [Approval strategy](https://www.notion.so/Approval-strategy-9c15269bbb184ec9909dfd900bcf0b91?pvs=21) for each request may vary based on several variables:
|
||||
> - **Category/sub-category**: Different sets of approvers may be required based on the category/sub-category of the request. For example, PeopleOps partners need to review requests for learning & development but not for consulting fees or software & licenses.
|
||||
> - **Amount**: In some cases, a simplified approval strategy may be triggered if the amount is below a certain threshold.
|
||||
> - **Project**: The Budget Owner is determined based on the selected project in the request. If the Budget Owner is the one raising the request, the L2 Budget Owner will be required to provide approval.
|
||||
> - **Requestor name**: The approval process ensures that Requestors cannot approve their own requests.
|
||||
|
||||
3. You can monitor the progress of the approval process in SpiffWorkflow. For instructions on how to check your process instances, please refer to this [guide](https://www.notion.so/Quick-start-user-guide-SpiffWorkflow-0e2dd1fbe3584a8981b3acb36834b2c2?pvs=4#caff0b729d2246dc8b80a30c274a7dd9).
|
||||
|
||||
4. To stay informed about the approval outcomes, please check your StatusApp Desktop notifications from the [SpiffWorkflow contact](https://join.status.im/u/zQ3shqpayoq1MeWZK8XkEsD6fECvnWzBZAPmV5DwgxnexkKgu). Reviewers may request additional information about your request, so please be prepared to address their questions.
|
||||
|
||||
> How to submit additional information - pls refer to this[ guide](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#307fa3bb9d4241da955aeeb6e534f21d).
|
||||
|
||||
5. Once your request is approved, you can proceed with the purchasing and payments. To access the approval history and other details regarding your request, please navigate to your request in SpiffWorkflow.
|
||||
|
||||
6. When Finance processes your payment requests or third-party invoices, they will check for approved requests in SpiffWorkflow. If there are no approved requests or if the amounts differ, they may request additional approval from the Budget Owner and Service Units.
|
||||
|
||||
|
||||
If you are a Budget Owner or a member of the Service Units team, you may find the [report](https://superset.infra.status.im/superset/dashboard/p/W351qlbzmdj/) useful.
|
||||
@@ -0,0 +1,30 @@
|
||||
# SpiffWorkflow
|
||||
|
||||
### What is SpiffWorkflow
|
||||
SpiffWorkflow is a workflow engine which enables our organisation to define their processes in [BPMN format](https://www.ibm.com/cloud/blog/bpmn) (looks like a flowchart) and then allows the orchestration and execution of these processes within the platform. The workflow orchestration can be simple such as allowing multiple people to review and approve a request within the platform, or it could also be super complex orchestration integrated with multiple systems and driving a workflow between them. SpiffWorkflow has a simple interface for the end user to interact with and raise requests.
|
||||
|
||||
|
||||
### When to use SpiffWorkflow
|
||||
Most of the time, you will be using the platform to raise requests which need to be reviewed and approved. E.g. requesting a laptop, hardware/software, permission to travel etc. The full list of processes that are active in the platform can be found [here](https://www.notion.so/SpiffWorkflow-9873a17b6cb744ef996d860e27b774eb?pvs=4#59c2e4b668b046a6a3f2acefcaf5c37c).
|
||||
|
||||
|
||||
### Getting setup with SpiffWorkflow
|
||||
As a new joiner, you will have received an email in your status inbox from "[Logos.co](http://logos.co/) Keycloak" which will get you to set your password and OTP. You will have 5 days to action this otherwise the link in the email will expire. If this happens, please contact PeopleOps and they will send you a new email. Once you have logged in, let's make sure that you can receive notifications to your Status Desktop app.
|
||||
|
||||
1. Login to [SpiffWorkflow](http://prod.mod.spiff.status.im)
|
||||
2. Go to “Start New+” and click “start” button on “Set up Status App (Desktop) notifications”
|
||||
3. Follow the instructions and then accept the contact request from SpiffWorkflow. That's it.
|
||||
|
||||
You can read the full instructions with images [here](https://www.notion.so/0e2dd1fbe3584a8981b3acb36834b2c2?pvs=21).
|
||||
|
||||
|
||||
### How to raise a request in SpiffWorkflow
|
||||
1. On the home page of SpiffWorkflow, navigate to "Start New+". Here you will find all the processes which you have permission to start
|
||||
2. Click "start" button on the process you wish to start. You will be redirected to a form which you can fill out and submit
|
||||
|
||||
If you are halfway through a process and are not sure what you need to fill in the field, you can come back to this process later. Just go down the bottom and "Save and Close". To come back to this process later, you can see this on your home page under "In Progress" -> "Started by me". To resume the process, click the "Go" button.
|
||||
|
||||
|
||||
### Useful links
|
||||
1. [SpiffWorkflow landing page](https://www.notion.so/SpiffWorkflow-9873a17b6cb744ef996d860e27b774eb)
|
||||
2. [User guide](https://www.notion.so/0e2dd1fbe3584a8981b3acb36834b2c2?pvs=21)
|
||||
@@ -0,0 +1,56 @@
|
||||
# Superset
|
||||
### Basics Tutorial
|
||||
|
||||
Superset is an open-source data exploration and visualization platform powered by Apache Superset. It provides a user-friendly interface for data analysts and business users to interact with their data and create interactive visualizations, charts, and dashboards. With Superset, users can connect to various data sources, including databases, and more, to explore and analyze their data in a visually appealing and intuitive manner. Superset offers a wide range of visualization options, such as bar charts, line charts, maps, and heatmaps, allowing users to gain valuable insights and make data-driven decisions. It also supports the use of filters and drill-down capabilities to dive deeper into the data. Overall, Superset empowers users to effectively explore and communicate their data through interactive and dynamic visualizations.
|
||||
|
||||
Step 1: Accessing Superset
|
||||
|
||||
- Open your web browser and enter the URL Superset is hosted. https://superset.infra.status.im/superset/welcome/
|
||||
- Enter your Github username and password to log in to Superset. If this is your first time using Superset it will create a brand new user for you
|
||||
- If this is your first time, you'll need access to dashboards you need. You can contact laloanaya through discord or at lalo@status.im to get access to these resources.
|
||||
|
||||
Step 2: Exploring the Superset Home Page
|
||||
|
||||
- After logging in, you'll be directed to the Superset home page.
|
||||
- The home page contains a menu bar at the top and various sections with options to explore dashboards.
|
||||
|
||||
Step 3: Navigating the Menu Bar
|
||||
|
||||
- The menu bar at the top provides different options for managing and exploring data.
|
||||
- Click on the "Dashboards" option in the menu bar to access the available dashboards.
|
||||
|
||||
Step 4: Viewing a Dashboard
|
||||
|
||||
- On the Dashboards page, you'll see a list of available dashboards.
|
||||
- Click on the name of the dashboard you want to visualize.
|
||||
|
||||
Step 5: Interacting with Filters (if available)
|
||||
|
||||
- If the dashboard has filters, you can interact with them to refine the displayed data.
|
||||
- Look for filter options on the dashboard interface, such as drop-downs, sliders, or text inputs.
|
||||
- Select the desired options or adjust the filters as necessary.
|
||||
|
||||
Step 6: Exploring the Dashboard
|
||||
|
||||
- Once the filters are set (if applicable), explore the dashboard to view the visualizations.
|
||||
- The dashboard will display various charts, graphs, and data visualizations relevant to the chosen topic.
|
||||
|
||||
Step 7: Analyzing the Dashboard
|
||||
|
||||
- Take time to analyze and interpret the visualizations on the dashboard.
|
||||
- Pay attention to trends, patterns, and any insights the data may reveal.
|
||||
- Use the interactive elements (if available) to drill down into specific data points or explore different dimensions.
|
||||
|
||||
Step 8: Navigating Between Dashboards (if applicable)
|
||||
|
||||
- If there are multiple dashboards available, you can navigate between them using the menu or designated links.
|
||||
- Go back to the Dashboards page or use the provided navigation options to switch between different dashboards.
|
||||
|
||||
### Requesting Changes or New Dashboard
|
||||
|
||||
- If you need to request changes to an existing dashboard or create a new one, please reach out to Lalo Anaya.
|
||||
- You can contact Lalo Anaya through Discord by sending a message to his username (laloanaya) or email him at [lalo@status.im](mailto:lalo@status.im).
|
||||
- Clearly communicate your requirements, including the specific changes or details for the new dashboard you would like to create.
|
||||
- Lalo will assist you in making the necessary updates or work with you to design and develop a new dashboard based on your needs.
|
||||
|
||||
That's it! You've now learned how to access Superset, navigate the home page, view dashboards, interact with filters (if available), explore the visualizations, and analyze the data presented on the dashboards. Enjoy exploring the insights provided by the visualizations! If you have questions or suggestions you can contact laloanaya through discord or at lalo@status.im
|
||||
@@ -0,0 +1,5 @@
|
||||
# Playbook
|
||||
|
||||
In this section, you will find information and guides on platforms, processes and frameworks we have at Status.
|
||||
|
||||
If you have any questions, please reach out to People Ops who can help navigate your questions.
|
||||
+4
-1
@@ -36,7 +36,10 @@
|
||||
- [Expense reimbursements](./finance/expense-reimbursements.md)
|
||||
- [Offboarding](./offboarding/index.md)
|
||||
- [Device Logistics](./offboarding/device-logistics.md)
|
||||
|
||||
- [Playbooks](./Playbooks/index.md)
|
||||
- [How to request goods and services](./Playbooks/How-to-request-goods-or-services.md)
|
||||
- [Spiffworkflow](./Playbooks/Spiffworkflow.md)
|
||||
- [Superset](./Playbooks/Superset.md)
|
||||
|
||||
*****
|
||||
|
||||
|
||||
@@ -34,9 +34,11 @@ As per our transparency and resourcefulness principles, we ask everyone to post
|
||||
|
||||
Here's an event [post example](https://discuss.status.im/t/ethdenver-feb-15-17-2019/922).
|
||||
|
||||
## If it falls outside your project's budget
|
||||
## Once you have your travel details ready
|
||||
|
||||
Submit the request in the #travel-requests channel and tag (as cc) your project lead. From there, your project lead can give a simple 👍 to confirm the request makes sense or ask additional questions; and People Ops & Finance can ask any necessary questions or suggest adjustments.
|
||||
Submit your individual travel request via [SpiffWorkflow](https://prod.mod.spiff.status.im/).
|
||||
|
||||
Here's the instructions on [how to create a travel request](https://www.notion.so/Request-Travel-06db3450784e4320adb425688d8dbe3f?pvs=4#ceb64c141032482cbf5b2b5642414e76).
|
||||
|
||||
## Related articles
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ Core contributors have the potential option of leasing devices from Status to en
|
||||
|
||||
While Status provides you the flexibility to purchase the appropriate devices in line with the capped amounts stated in this section, Status ultimately owns such devices. Following your purchase, Status will subsequently lease you back the device which you have purchased.
|
||||
|
||||
For the purposes of purchasing devices, you can expense up to the below amount but just let your project lead know about your device purchasing plans.
|
||||
For the purposes of purchasing devices, you need to raise the request via [SpiffWorkflow](https://prod.mod.spiff.status.im/) to get okays from your Project Lead and PeopleOps partner.
|
||||
|
||||
The standard setup for everyone includes a laptop, a Keycard, a Yubikey, and a Ledger.
|
||||
|
||||
@@ -22,18 +22,19 @@ For each item we have defined a budget. Your spend will stay below the defined b
|
||||
* Yubikey: you can reimburse one (approx USD 50)
|
||||
* Ledger: you can reimburse one (approx USD 80)
|
||||
|
||||
> Most contributors should be able to effectively perform their work using standard equipment, but if you're struggling to participate or you need other equipment to perform your role successfully (for example, you need a better quality webcam to record videos or a higher quality mic to record demos for Status) then please speak to your project lead and People Partner and they can support you with your needs on a case by case basis. For those that are approved to receive higher quality equipment, we recommend the **Logitech Brio 4K Webcam** and the **Rode NT-USB USB Condenser Microphone**.
|
||||
> Most core contributors should be able to effectively perform their work using standard equipment, but if you're struggling to participate or you need other equipment to perform your role successfully (for example, you need a better quality webcam to record videos or a higher quality mic to record demos for Status), then please raise the request via [SpiffWorkflow](https://prod.mod.spiff.status.im/) and People Partner can support you with your needs on a case by case basis. For those that are approved to receive higher quality equipment, we recommend the **Logitech Brio 4K Webcam** and the **Rode NT-USB USB Condenser Microphone**.
|
||||
|
||||
Following the cessation or termination of your services to Status, you have the option of purchasing from Status any equipment you purchased in accordance with this section.
|
||||
Following the cessation or termination of your services to Status, you have the option of purchasing from Status any equipment you purchased in aordance with this section.
|
||||
|
||||
## 🏪 How to get your devices
|
||||
|
||||
1. Let your project lead & People Partner know prior to purchasing the devices
|
||||
2. Choose official or trusted vendors to buy your devices.
|
||||
3. Go to your `profile > assets` in BambooHR and `Add assets,` filling all device information.
|
||||
4. Once registered, [request a refund](../finance/expense-reimbursements.md) by adding the expense to Expensify and your next invoice.
|
||||
5. You can reimburse custom expenses. Try to avoid international shipping when possible. Buy from vendors within your country or economic area.
|
||||
6. Enter into a leasing agreement with Status in respect of the device you have purchased.
|
||||
1. Choose official or trusted vendors to buy your devices
|
||||
2. Raise a request for goods/services via [SpiffWorkflow](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#3ef6bd6141f84ff496cfea785a514a5a) prior to purchasing the devices.
|
||||
3. Upon getting okays from your Project Lead and PeopleOps partner, proceed with the purchase.
|
||||
4. Go to your `profile > assets` in BambooHR and `Add assets,` filling all device information.
|
||||
5. Once registered, [request a refund](../finance/expense-reimbursements.md) by adding the expense to Expensify and your next invoice.
|
||||
6. You can reimburse custom expenses. Try to avoid international shipping when possible. Buy from vendors within your country or economic area.
|
||||
7. Enter into a leasing agreement with Status in respect of the device you have purchased.
|
||||
|
||||
## ℹ️ FAQ
|
||||
|
||||
@@ -43,11 +44,11 @@ Following the cessation or termination of your services to Status, you have the
|
||||
|
||||
* __What if I don't have enough funds to buy the device before reimbursement?__
|
||||
|
||||
If cash flow is an issue, please ping your People Partner and we'll help come up with a solution!
|
||||
If cash flow is an issue, please mention it in the request (select "Payment method" <> "Reimbursement") and ping your People Partner and we'll help come up with a solution!
|
||||
|
||||
* __What if my devices becomes outdated?__
|
||||
|
||||
At the 3 year mark, if your device needs an upgrade, ping your People Partner.
|
||||
At the 3 year mark, if your device needs an upgrade, just raise a new request via [SpiffWorkflow](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#3ef6bd6141f84ff496cfea785a514a5a).
|
||||
|
||||
* __What happens if I accidentally damage a device?__
|
||||
|
||||
|
||||
@@ -6,9 +6,9 @@ Here you'll find helpful information to make your travel abroad experience more
|
||||
|
||||
Some of these points might not apply to offsites as they're usually centrally organised with their particular budget.
|
||||
|
||||
Your travel budget comes from your project's budget. If you don't have previous approval or haven't posted your travel plans yet, check out [Events and meetups](../contributing-to-status/events-and-meetups.md) before booking your trip.
|
||||
Your travel budget comes from your project's budget. Raise a travel request [SpiffWorkflow](https://prod.mod.spiff.status.im/) and check out [Events and meetups](../contributing-to-status/events-and-meetups.md) before booking your trip.
|
||||
|
||||
If the travel falls outside your project's budget, talk with your project lead about the event or meeting you're attending and [create a travel request](../contributing-to-status/events-and-meetups.md).
|
||||
Here's the instructions on [how to create a travel request](https://www.notion.so/Request-Travel-06db3450784e4320adb425688d8dbe3f?pvs=4#ceb64c141032482cbf5b2b5642414e76).
|
||||
|
||||
|
||||
## Before travelling abroad:
|
||||
@@ -49,7 +49,7 @@ Don't go overboard with spending on bookings, food, and drinks. Keep accountabil
|
||||
|
||||
If there are any issues or you believe that you should get reimbursed for any of the expenses above, please speak to your People Partner, who can review your request on a case by case basis. Ultimately, it will be in Status’ sole discretion to determine whether an expense is a “reasonable expense” and whether it will be reimbursed.
|
||||
|
||||
Whether using a card or requesting reimbursements, you're responsible for submitting your expenses correctly as a traveller. We currently process expenses together with payroll or invoices. When you're back from your trip, follow the instructions on [How to file expenses or get reimbursed](../expense-reimbursements.md) for uploading your receipts in a compliant and timely manner to keep our finances healthy.
|
||||
Whether using a card or requesting reimbursements, you're responsible for submitting your expenses correctly as a traveller. We currently process expenses together with payroll or invoices. When you're back from your trip, follow the instructions on [How to file expenses or get reimbursed](../finance/expense-reimbursements.md) for uploading your receipts in a compliant and timely manner to keep our finances healthy.
|
||||
|
||||
## 🛩 Getting there
|
||||
|
||||
|
||||
@@ -4,6 +4,8 @@ Status' Contributors Guide is an open living repo built for you. The truth is, S
|
||||
|
||||
Here you'll find helpful guidelines on how to contribute to this guide and make it yours!
|
||||
|
||||
_Note: You can start contributing only once access to status-im organization is provided to you by people-ops. Prior to that, the github link will not be working._
|
||||
|
||||
## 👾 Contributing with pull requests
|
||||
|
||||
Whether you'd like to fix typos, update information, add sections, or build new content, you can create a pull request to contribute to the guide.
|
||||
|
||||
@@ -5,10 +5,14 @@
|
||||
You can request a reimbursement for reasonable expenses incurred on behalf of Status during the project's development. You can read about some of these expenses at:
|
||||
* [Computers and devices](../contributing-to-status/laptops-and-devices.md)
|
||||
* [Events and meetups](../contributing-to-status/events-and-meetups.md)
|
||||
* [Travelling for Status](../contributing-to-status/traveling-for-status.md)
|
||||
* [Travelling for Status](../contributing-to-status/travelling-for-status.md)
|
||||
* [Essential reading](../fundamentals/essential-reading.md)
|
||||
|
||||
It's essential that you carefully read the following instructions to get reimbursed and so we can file expenses correctly. In order to get your expenses reimbursed correctly and in time you will need [Expensify](https://www.expensify.com/) to report and store the expense receipts, and add these expenses to your monthly invoice sent to `billing@status.im`.
|
||||
It's essential that you carefully read the following instructions to get reimbursed and so we can file expenses correctly.
|
||||
In order to get your expenses reimbursed correctly and in time:
|
||||
- ensure that your purchase or travel request in [SpiffWorkflow](https://prod.mod.spiff.status.im/) gets approved before you purchase goods or services
|
||||
- after the purchase or travel, submit the expense receipts to [Expensify](https://www.expensify.com/)
|
||||
- add these expenses to your monthly invoice sent to `billing@status.im`
|
||||
|
||||
In addition to these notes, you can find a guide [here](https://docs.google.com/document/d/1UX9uizHnJDXZjghiXiBGUexrQxxaiyv3-KpyKfHYJKU/edit#) and you can also view our video walkthrough [here](https://youtu.be/04YB_Xz48E8).
|
||||
|
||||
@@ -66,6 +70,8 @@ Go to the `Expense` tab on either the web or mobile apps to upload expenses manu
|
||||
|
||||
Uploading expenses and submitting an expense report are different actions within Expensify. Once you've uploaded all your receipts, it's fundamental that you submit the report for Finance's review and approval.
|
||||
|
||||
Finance checks the submitted expenses against your purchase/travel requests raised in [SpiffWorkflow](https://prod.mod.spiff.status.im/), and if the expenses follow the approved by Project Leads amounts, no additional approval will be required.
|
||||
|
||||
You must submit the expense report and get it approved before being able to include it in your invoice. To do that, click the `Reports` tab and `Submit` your report.
|
||||
|
||||
> ⚠️ Only **approved** expense reports should be included in the monthly contributor invoice.
|
||||
|
||||
@@ -0,0 +1,31 @@
|
||||
# Guidance from Legal perspective regarding (potential) disputes
|
||||
|
||||
## Background
|
||||
|
||||
* While we hope that you may never have to run into this issue, and for the most part it is relatively exceptional, Status, like any other organisation, faces the risk of entering into disputes, whether they are arising from internal or external events, within or outside of Status’ control and with different types of counterparties, from service provides to (former) CCs (“Counterparty”).
|
||||
* Therefore we have developed this guidance for CCs on how you can help prevent and mitigate potential disputes, protect Status’ interests and how to best collaborate with Legal to resolve any disputes in the most peaceful and amicable manner possible.
|
||||
|
||||
## Guidance
|
||||
|
||||
#### When to involve Legal - the earlier the better. However, please contact Legal immediately if:
|
||||
* It is more than likely that Status will fail to fulfil its obligation(s) towards a Counterparty or if Status has already failed on its obligation(s) towards a Counterparty (doesn’t matter if the Counterparty is aware about this or not). For example,
|
||||
* Status failed to pay, or failed to pay on time any amounts due (e.g. an invoice has been unpaid past the stated due date);
|
||||
* Breached a term of a contract in any way, for example, by inappropriate use of services (e.g. a service is being used contrary to a service’s acceptable use policy); or
|
||||
* Breached confidentiality (e.g. a CC inadvertently shares confidential information with another third party that is not compliant with the contract).
|
||||
* If a Counterparty claims that Status is not fulfilling its obligations (whether this is accurate or not) or threatens legal action against Status in this respect; or
|
||||
* if a legal counsel or a law firm has taken over communications with Status;
|
||||
|
||||
#### If any of the above takes place - the following should be observed:
|
||||
* Follow good practices: Preserve all communications with the Counterparty, such as discord chats, emails, any social media chats (e.g. Telegram), calls and meeting notes.
|
||||
|
||||
## After you contact Legal:
|
||||
|
||||
* Do not let the Counterparty know you are involving Legal, (for example, do not include Legal in -cc to an email with a Counterparty) unless Legal has advised you to do so. In our experience, if a Counterparty becomes aware that Legal is being involved, it may escalate an already sensitive situation or unnecessarily provoke hostility.
|
||||
* Communicate with the Counterparty only in consultation with Legal and other internal stakeholders as relevant, for example, your team lead.
|
||||
* Any communication with the Counterparty must be screened and approved by Legal.
|
||||
* Any strategy or potential proposals/compromises must also be discussed with Legal.
|
||||
|
||||
## After the dispute has been resolved:
|
||||
|
||||
* Rectify/Monitor - Legal and CC should continue to monitor for any potential signs that the dispute may resume or re-escalate and ensure that events or factors which led to the dispute have been adequately addressed (e.g. has Status’ failure to perform an obligation now being rectified?)
|
||||
* Lessons learned - Legal, CC, relevant team lead and any other relevant internal stakeholders should form a “lessons learned” group to review the events and factors, which led up to the dispute and determine whether any changes to procedure or practices should be made to prevent or mitigate the chance of such a dispute arising again. Notes and conclusions should be well documented for future reference
|
||||
@@ -2,7 +2,9 @@
|
||||
|
||||
We encourage using some time to learn about things related to your tasks and our collective mission. Make your fellow project core contributors aware of you being on/offline and that the project's progress doesn't get hindered. Feel free to discuss it openly and agree on timing with everyone involved.
|
||||
|
||||
We offer an annual learning budget of USD 170 for each core contributor. You can use this budget towards things like books, conferences, or online courses. Speak with your project lead to request additional funding if needed.
|
||||
We offer an annual learning budget of USD 170 for each core contributor. You can use this budget towards things like books, conferences, or online courses.
|
||||
|
||||
For the purpose of purchasing learning & development items (learning platforms, courses, online conferences), you need to raise the request via [SpiffWorkflow](https://www.notion.so/Request-Goods-or-Services-9891dc90f4424a0ebd3407db1991c203?pvs=4#3ef6bd6141f84ff496cfea785a514a5a) to get okays from your Project Lead and/or PeopleOps partner.
|
||||
|
||||
If you need a reference, a core contributor could spend their first 1-3 weeks spending 50% of their billed hours to learn and ~2 hours p/w after that on an ongoing basis. This is just an example, and we encourage you to figure out a learning cadence that best helps you succeed in contributing to Status.
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 82 KiB After Width: | Height: | Size: 82 KiB |
@@ -2,7 +2,7 @@
|
||||
|
||||
## 📥 Downloading Status
|
||||
|
||||
First you will need to download the latest release of Status Desktop from [https://status.im/get/](https://status.im/get/)
|
||||
First you will need to download the latest release of Status Desktop from [here](https://github.com/status-im/status-desktop/releases).
|
||||
|
||||
### On Windows:
|
||||
- Locate and double-click the .exe file. (It will usually be in your Downloads folder.)
|
||||
@@ -13,7 +13,7 @@ First you will need to download the latest release of Status Desktop from [https
|
||||
- Run the extracted `StatusIm-Desktop-<version>.AppImage`
|
||||
|
||||
### On Mac:
|
||||
- Open Status.dmg and
|
||||
- Open Status.dmg
|
||||
- Copy Status.app to the Applications folder
|
||||
- You will need to "right click -> open" when running it for the first time (due to new Apple requirements for notarization). You may need to "right click -> open" twice.
|
||||
|
||||
@@ -41,7 +41,7 @@ When choosing a username, it is recommended that you use the same username you a
|
||||
|
||||
3. Status should recognize this key is Iuri’s and immediately open the "send contact request" dialog so you can send a contact request to him:
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
4. Send Iuri a nice message while you’re at it, something that will make him smile. Also let Iuri know you’re a new Status CC and mention your full name and the name of the team you have just joined. Click the “Send Contact Request” button to send the contact request.
|
||||
@@ -50,7 +50,7 @@ When choosing a username, it is recommended that you use the same username you a
|
||||
5. Iuri should have a pending contact request from yourself. You need to wait for Iuri to accept your request.
|
||||
|
||||
|
||||
6. Once Iuri has accepted your request (congrats, you’re now friends with Iuri), he will send you a link to Status Internal community (if you don’t receive this link, ping @helium on Discord).
|
||||
6. Once Iuri has accepted your request (congrats, you’re now friends with Iuri), he will send you a link to Status Internal community (if you don’t receive this link, ping @helium__ on Discord).
|
||||
|
||||

|
||||
|
||||
@@ -109,7 +109,7 @@ Because Status is a fully p2p network that is not under the control of any autho
|
||||
|
||||
One of these mechanisms is ‘mutual contacts’. What this means is that in order to start a 1on1 conversation with another person, or to add somebody to an ad-hoc group chat, you first need to be a mutual contact with that person. So it is recommended that you send ‘Contact requests’ in Status to all the other CCs that you may need to chat with outside of the Status Internal community space.
|
||||
|
||||
Here is a useful link to the Status CC’s contact list which contains everyone's chat keys (and names/emails etc): [https://contacts.status.im](https://contacts.status.im)
|
||||
[Here](https://contacts.status.im) is a useful link to the Status CC’s contact list which contains everyone's chat keys (and names/emails etc).
|
||||
|
||||
Like Discord, Status also supports small ad-hoc group chats. Unlike Discord, which only supports 10 participants in each ad-hoc group chat, Status currently supports 20 participants and hopefully we can further increase this number in the future. So if you need to have a small private group chat about something, give this functionality a try!
|
||||
|
||||
@@ -120,7 +120,7 @@ Like Discord, Status also supports small ad-hoc group chats. Unlike Discord, whi
|
||||
|
||||
One of the reasons we dogfood is to identify bugs! So if you think you have run into a bug, it would be much appreciated if you follow these instructions to report the issue:
|
||||
|
||||
1. Go to [https://github.com/status-im/status-desktop/issues](https://github.com/status-im/status-desktop/issues) and have a quick look to see if the issue has already been reported. If you see that the issue has already been reported, you can leave a comment on the issue saying “I’ve experienced this bug” and add any additional information (if any) from your experience that’s not already in the bug report.
|
||||
1. Go to the [Status Desktop repo](https://github.com/status-im/status-desktop/issues) on GitHub and have a quick look to see if the issue has already been reported. If you see that the issue has already been reported, you can leave a comment on the issue saying “I’ve experienced this bug” and add any additional information (if any) from your experience that’s not already in the bug report.
|
||||
|
||||
Don’t worry about accidentally creating a duplicate bug, this happens all the time and the Desktop team will deduplicate any duplicate bugs reported.
|
||||
|
||||
@@ -134,8 +134,6 @@ Don’t worry about accidentally creating a duplicate bug, this happens all the
|
||||
|
||||
And that’s it, if you follow these steps you’ve written a highly descriptive and informative bug report that’s better than 95% of bug reports 🙂
|
||||
|
||||
[https://github.com/status-im/status-desktop/issues](https://github.com/status-im/status-desktop/issues)
|
||||
|
||||
|
||||
## ⬆️ How to request a new feature or an improvement to an existing feature
|
||||
|
||||
@@ -145,6 +143,6 @@ To gather and prioritise this feedback, we have set up a ‘User Voice board’
|
||||
|
||||
The idea behind a user voice board is simple - anybody can post an improvement idea or feature request, everybody can upvote requests that are important to them, and designers and developers working on the desktop product can respond to these suggestions.
|
||||
|
||||
Give it a go 🙂 Just upvoting (or not upvoting) requests helps build a prioritised backlog to feed into the product development roadmap.
|
||||
Give [Feature UpVote](https://status-desktop.featureupvote.com) a go 🙂 Just upvoting (or not upvoting) requests helps build a prioritised backlog to feed into the product development roadmap.
|
||||
|
||||
|
||||
[https://status-desktop.featureupvote.com](https://status-desktop.featureupvote.com)
|
||||
|
||||
Reference in New Issue
Block a user