diff --git a/pages/consulting/index.md b/pages/consulting/index.md index ffd15921..53a68583 100644 --- a/pages/consulting/index.md +++ b/pages/consulting/index.md @@ -1,342 +1,432 @@ --- title: Consulting description: > - Discuss consulting for open-source software, scientific and research - workflows, technical education, and community-focused projects. -date: 2026-08-06 + Find professional support for open-source software, research software, + scientific computing, technical education, and related projects through the + Open Science Labs consulting partner network. +date: 2026-10-02 authors: ["OSL Team"] template: main.html section_label: Work with OSL page_theme: consulting -hero_words: ["Discuss", "Scope", "Deliver"] +hero_words: ["Connect", "Collaborate", "Deliver"] --- # Consulting -Open Science Labs (OSL) welcomes consulting enquiries from research -institutions, nonprofits, companies, open-source projects, community -organisations, and other groups working in open science and technology. +Open Science Labs (OSL) connects organisations with independent partners that +provide professional support for open-source software, research software, +scientific computing, technical education, and related projects. -A consulting engagement is formal, scoped work. Before work begins, the parties -must agree on the intended outcomes, responsibilities, timeline, budget, -delivery structure, and an approved contracting and payment route. - -Open Science Labs is a fiscally hosted project of Open Source Collective (OSC). -OSL coordinates technical discussions, preliminary scoping, contributors, and -delivery. Formal agreements involving OSL are subject to OSC review and -approval. +Our role is to help bring the right people together. -## Areas of interest +Rather than operating as a traditional consulting company, OSL is building a +network of consulting partners that can evaluate projects, define a scope of +work, and deliver professional services directly to clients. -The following examples describe areas in which OSL is interested in -contributing. They are not commitments that a particular service, specialist, or -delivery schedule will be available. +If your university, research group, nonprofit, company, open-source project, or +community needs technical support, tell us what you are trying to accomplish. -- **Open-source project strategy:** repository assessment, project planning, - contribution workflows, maintainership practices, and sustainability. -- **Scientific and technical software:** architecture, implementation, testing, - packaging, releases, and maintenance planning. -- **Research workflows:** reproducibility, data and computational workflows, - research software practices, and technical documentation. -- **Documentation and contributor experience:** onboarding, contribution guides, - tutorials, developer documentation, and release processes. -- **Education and mentorship:** workshops, learning materials, mentoring - workflows, and open-source contributor programmes. -- **Community and programme development:** project incubation, affiliation, - community participation, and responsible collaboration practices. +We can help identify an appropriate path and, when possible, connect you with a +partner that has relevant expertise. -The final scope depends on the project's needs, available expertise, risk, -capacity, and the appropriate legal and delivery arrangements. + +Discuss your project -## Ways to work with us +## How our consulting network works -### Defined consulting engagement +### 1. Tell us what you need -A defined engagement has an agreed scope, deliverables, schedule, budget, and -review process. It may be appropriate for an assessment, implementation, -maintenance project, documentation project, workshop, or another time-limited -body of work. +Contact OSL with a short description of your project, repository, research +workflow, or technical problem. -When an external organisation is purchasing defined services, deliverables, -deadlines, continuing support, confidentiality, or other contractual -commitments, OSL discusses the request and may prepare a preliminary scope. +Helpful information includes: -Before OSL accepts the engagement or makes a binding commitment, the proposed -arrangement must be sent to OSC for review. OSL will contact OSC as part of this -process; prospective clients can continue to use OSL as their point of contact. - -For an approved formal engagement involving OSL, OSC is the legal organisation -entering into and signing the agreement on behalf of the hosted Open Science -Labs project. - -[Learn how Open Source Collective handles legal agreements](https://docs.oscollective.org/for-hosted-member-projects/signing-and-entering-into-legal-contracts) +- the project or repository; +- what you would like to accomplish; +- important technical or scientific requirements; +- your preferred timeline; +- your approximate budget or funding constraints; +- whether the work needs to be public; +- whether confidential information or restricted systems are involved. -### Continuing support +You do not need to prepare a complete specification before contacting us. -Some projects may need maintenance, technical advice, documentation, training, -or community support over a longer period. Any continuing arrangement must -define priorities, response expectations, available capacity, and how either -party may change or end the work. A continuing arrangement involving paid -deliverables, response commitments, reserved capacity, confidentiality, or other -enforceable obligations follows the formal OSC contract-review process. +### 2. We explore the right route -### Paid open-source contributions +OSL reviews the enquiry at a high level and considers whether one of our +consulting partners may be a suitable fit. -When sufficient funds are available in OSL's Open Collective budget, OSL may -compensate individuals for approved work that directly supports its open-source -projects and programmes. +When appropriate, we can make an introduction. If an existing partner does not +match the request, we may explore other organisations or specialists in our +network. -Examples may include: - -- mentoring; -- project maintenance; -- bug investigation and bug fixes; -- documentation; -- packaging and distribution; -- testing and continuous integration; -- implementation of new features; -- research software improvements; -- public bug-bounty programmes. +We cannot guarantee that a suitable provider will be available for every +project. -A separate formal consulting contract is not necessarily required for each -OSL-funded contribution task. After the approved work has been completed, the -contributor may submit an expense of type **Invoice** through OSL's Open -Collective page. +### 3. Meet the consulting partner -The invoice should clearly describe: +The consulting partner evaluates the project with you and determines whether it +can take on the engagement. -- what work was completed; -- when it was completed; -- how it supported the relevant open-source project or programme; -- the approved payment amount; -- links to issues, pull requests, commits, releases, documentation, reports, or - other evidence where practical. +Depending on the project, the partner may discuss: -An authorised OSL administrator reviews the expense. OSC then performs its own -compliance review and processes an eligible payment. +- scope and deliverables; +- milestones and acceptance criteria; +- technical approach; +- timeline and budget; +- intellectual property; +- confidentiality; +- maintenance and support; +- other project-specific requirements. -Paid tasks may only be offered when: +### 4. Agree on the delivery and administrative structure -- sufficient funds are available in OSL's hosted budget; -- the work supports OSL's open-source mission; -- the expected work and payment are documented; -- the completed work can be reviewed; -- the resulting expense complies with OSC policies. +In many cases, the client and consulting partner will contract and manage the +engagement directly. -[Read Open Source Collective's payment and expense guidance](https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid) +For some projects, however, the engagement may benefit from fiscal, +administrative, payment, or contracting infrastructure. When appropriate, OSL +may explore whether one of its fiscal hosts can support the arrangement. -[Review Open Source Collective's expense policies and limitations](https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid/expense-policies-and-limitations) +The appropriate structure is determined case by case. Fiscal-host support is +not automatic, and OSL cannot guarantee that a particular client, partner, or +engagement will be eligible. Any such arrangement remains subject to the +relevant fiscal host's scope, review, approval, fees, compliance requirements, +and contractual terms. -#### Invoice or Reimbursement? +When no fiscal-host arrangement is used, the client and partner establish their +own contractual, financial, legal, tax, confidentiality, intellectual-property, +and delivery arrangements. -An **Invoice** is used to request payment for completed work or services. A -**Reimbursement** is used when someone has already paid an eligible project cost -personally and is requesting repayment. Professional services must not be -submitted as reimbursements. +Open Science Labs is not automatically a party to agreements between a client +and an independent consulting partner. -Invoices must be for completed work, and expenses cannot normally be paid in -advance. Invoice descriptions should be specific and itemised rather than vague -or undetailed lump sums, and relevant evidence should be included where -practical. +### 5. Build something useful + +The partner delivers the agreed work in collaboration with the client, +maintainers, researchers, or other stakeholders involved in the project. + +OSL encourages approaches that strengthen open-source ecosystems, promote +maintainability, and contribute improvements upstream whenever practical. -[Review the difference between invoices and reimbursements](https://docs.oscollective.org/for-hosted-member-projects/spending-money-and-getting-paid/invoice-and-reimbursement-examples) +## Optional fiscal-host support + +OSL has established fiscal-host relationships that support different parts of +its mission. When an engagement would benefit from additional financial or +legal infrastructure, OSL may be able to help explore an appropriate +fiscal-hosted route. + +Depending on the project and the fiscal host, this may include support such as: + +- receiving and managing project funds; +- invoicing and payment processing; +- paying eligible contributors or service providers; +- financial administration and compliance; +- where permitted by the fiscal host, review and signature of formal + agreements. + +OSL currently works with **Open Source Collective** for open-source initiatives +and with **The GRAPH Network** for certain non-open-source projects. The +appropriate route depends on the nature of the engagement and the eligibility +requirements of the relevant fiscal host. + +Fiscal-host support is an optional, case-by-case arrangement. Becoming an OSL +consulting partner does not automatically provide access to a fiscal host, and +clients or partners should not assume that OSL or a fiscal host will become a +party to an engagement until the proposed structure has been reviewed and +approved. -Paid contribution programmes and bug bounties are mechanisms through which OSL -can fund approved open-source work. They are not an alternative contracting -route for an external organisation purchasing a defined result. When payment is -exchanged for client-specific deliverables or other contractual commitments, the -formal OSC review and contracting process applies. +[Learn more about OSL's fiscal hosts](/about/fiscal-sponsor/). -### Partner-supported engagement +## Areas our partners may support -When the work would benefit from complementary expertise or delivery capacity, -OSL may explore an engagement involving an appropriate partner, affiliated -project, or independent specialist. Participation is conditional on fit, -availability, and the necessary review and approvals; it is not guaranteed. +Capabilities vary between partners and projects, but consulting engagements may +include areas such as: + +### Open-source maintenance -The appropriate contracting and payment arrangement will be discussed before any -commitment is made. Depending on the engagement, OSL may coordinate work through -an Open Source Collective (OSC)-approved agreement, participate in an approved -collaboration, or introduce the client to an independent provider contracting -separately. OSC does not automatically become the contracting party for -independently delivered work. +- bug investigation and fixes; +- dependency updates; +- compatibility work; +- test improvements; +- continuous integration; +- technical debt reduction; +- issue and pull-request workflows; +- release preparation; +- maintenance planning. + +### New features and integrations + +- new library functionality; +- APIs and command-line interfaces; +- integrations with external tools and services; +- import and export formats; +- workflow automation; +- prototypes; +- upstream contributions. + +### Packaging, releases, and distribution + +- Python packaging and PyPI releases; +- conda and conda-forge; +- R packaging; +- containers; +- release automation; +- version and dependency management; +- installation testing; +- release documentation. -A referral is an introduction, not a guaranteed placement, endorsement, -warranty, or promise about an independent provider's quality or availability. -OSL may not be involved in the resulting contract, delivery, payment, or -supervision. +### Research and scientific software -Any formal agreement in which OSL participates remains subject to OSC review. -When an independent provider contracts directly with the client, OSL and OSC may -not be parties to that agreement. +- turning scripts and notebooks into reusable software; +- research software architecture; +- reproducible computational environments; +- scientific testing and validation infrastructure; +- research data pipelines; +- interoperability; +- performance optimisation; +- software citation metadata; +- archival releases; +- sustainable research software practices. + +Software engineering can improve reliability, reproducibility, transparency, +and maintainability, but does not replace scientific, clinical, regulatory, or +domain-specific validation. -### Other consulting and collaboration needs +### Documentation and contributor experience -The services described on this page represent the areas in which OSL is most -interested in contributing, but they are not an exhaustive list. +- user and API documentation; +- tutorials; +- developer guides; +- contribution guidelines; +- maintainer documentation; +- onboarding; +- release processes; +- architecture documentation; +- project roadmaps. -You are welcome to contact us if your project requires a different type of -open-source, scientific, technical, educational, or community-focused support. +### Open-source strategy and sustainability -Depending on the request, available expertise, and the appropriate contracting -structure, OSL may be able to: +- upstream contribution strategy; +- project sustainability; +- maintenance planning; +- contributor workflows; +- governance; +- reducing single-maintainer dependencies; +- release and compatibility policies; +- long-term planning for grant-funded software. -- develop a customised scope; -- collaborate with an affiliated project or community; -- bring together contributors with complementary expertise; -- explore delivery alongside a research institution, nonprofit, company, or - other partner; -- connect you with an independent specialist or organisation that may be better - suited to the work. +### Mentoring, workshops, and training -Partner-supported and customised engagements are considered individually. -Availability is not guaranteed, and any formal involvement by OSL or Open Source -Collective remains subject to the applicable review and approval process. +Depending on the partner and available expertise, engagements may include: -Contact: [team@opensciencelabs.org](mailto:team@opensciencelabs.org) +- open-source contribution training; +- developer workshops; +- research software practices; +- technical mentoring; +- packaging and release training; +- contributor onboarding; +- training around specific open-source technologies. -[Discuss another consulting need](mailto:team@opensciencelabs.org?subject=Open%20Science%20Labs%20custom%20consulting%20inquiry) +These examples are not a fixed catalogue. If your need is not listed, contact +us and tell us about it. -## Consulting, support, and paid contribution programmes +## Our first consulting partner -### Formal consulting arrangements +### SciStitch -Formal consulting is used when an external organisation expects defined -deliverables, a delivery schedule, dedicated capacity, confidentiality, -maintenance obligations, or other enforceable commitments. It requires OSC -review and, when approved, an agreement signed by OSC. +**SciStitch is the first consulting partner in the Open Science Labs consulting +network.** -### General community or financial support +SciStitch began as OSL's initial internal structure for professional consulting. +As the initiative evolved, we decided to move toward a decentralised partner +model: dedicated organisations can focus on professional consulting and service +delivery, while Open Science Labs continues focusing on its broader mission +around open source, open science, community, education, mentorship, and social +impact. -Questions and discussions in OSL's public community channels are informal and -provided on a best-effort basis; they do not include agreed deliverables, -response times, confidentiality, or an obligation to continue support. +This structure also allows OSL to collaborate with multiple consulting +organisations over time instead of limiting the initiative to a single internal +team. -General financial support does not purchase defined services or create a -guaranteed client-specific deliverable. OSL allocates it according to its -mission, available budget, priorities, and OSC policies. Organisations -interested in general support can learn more about -[sponsoring OSL](/about/sponsorship/). +- [Visit SciStitch](https://scistitch.com/) +- [Learn about the SciStitch partnership model](https://scistitch.com/partnership/) -### Paid contribution programmes +Services, availability, pricing, project acceptance, and delivery are normally +determined directly by SciStitch. If a specific engagement would benefit from +OSL's fiscal-host infrastructure, OSL and SciStitch may explore an appropriate +fiscal arrangement, subject to the relevant host's review and approval. -When funds are available, OSL may pay contributors for completed, approved, -mission-aligned open-source work through **Invoice** expenses. A paid -contribution opportunity is not automatically created when someone contacts OSL: -it depends on available funding and an approved, documented task, and it remains -subject to OSL and OSC review. +## Why a partner network? -Paid internships, fellowships, and other contributor opportunities are separate -programmes with their own eligibility, selection, funding, and supervision -requirements. Contacting OSL about consulting does not create a paid -contribution opportunity, and participation in a community or contributor -programme does not create a consulting relationship. +Open Science Labs is a community, not a conventional software agency. -Volunteer work, internships, fellowships, paid open-source contributions, and -formal consulting are separate programmes and workflows. +A partner-based model keeps that distinction clear while still helping +organisations find professional support. -When a request needs accountable delivery, a defined schedule, confidential -handling, or dedicated capacity, the work should be discussed as a formal -consulting engagement before it begins. +It also gives OSL the flexibility to build relationships with organisations and +specialists with different areas of expertise. -## How the workflows differ +Over time, we hope this can create a broader ecosystem connecting: -### Formal consulting +**organisations that need help → professional service providers → open-source +projects → maintainers and contributors** -Client inquiry → preliminary OSL discussion and scope → OSC review and -signature → delivery → approved contributor or provider invoices +This can create value across the ecosystem: -### OSL-funded open-source work +- organisations gain access to specialised expertise; +- consulting partners find meaningful projects; +- open-source projects receive professional engineering and maintenance; +- where appropriate, eligible engagements may be able to use fiscal + infrastructure facilitated by OSL; +- maintainers and contributors may gain new opportunities to collaborate and + grow professionally. -Available OSL budget → documented task or bounty → completed -contribution → OSL review → **Invoice** expense → OSC compliance -review and eligible payment +Participation in paid work is never automatic and depends on the consulting +partner, project requirements, funding, contributor readiness, and the +arrangements established for each project. -### Independent partner referral +## Our principles -Client inquiry → possible introduction → independent provider and -client determine their own agreement +### Open whenever practical -These workflows are not interchangeable. In particular, the OSL-funded -contribution workflow must not be used to avoid a formal agreement when an -external client is purchasing defined services. +We encourage upstream contributions, open standards, reusable solutions, +documentation, and public technical knowledge whenever the project allows it. -## How an engagement is considered +### Respect project communities -OSL considers each enquiry individually. An initial discussion usually covers: +Existing maintainers, governance structures, contribution processes, and +community decisions should be respected. -1. the problem, intended outcome, and people affected by the work; -2. the repository, documentation, data, infrastructure, and relevant - constraints; -3. the proposed scope, responsibilities, deliverables, and review process; -4. technical, scientific, ethical, privacy, security, or regulatory - requirements; -5. the timeline, budget, available expertise, and delivery capacity; -6. whether OSL should deliver directly, explore a partner-supported engagement, - make a referral, or recommend another route; -7. the contracting and payment structure that would need approval. +### Build for maintainability -An initial conversation is exploratory. No work, partnership, referral, or -contract is promised until the appropriate parties have reviewed and approved -the arrangement. +Professional delivery should consider what happens after the initial task is +completed. Tests, documentation, packaging, release processes, and handover can +be as important as the feature itself. -## Fiscal hosting and contracting +### Support people as well as software -Open Science Labs is a [fiscally hosted project](/about/fiscal-sponsor/) of Open -Source Collective. +Open source is sustained by people. We are particularly interested in +relationships that can strengthen maintainers, researchers, contributors, +communities, and the long-term sustainability of the projects involved. -OSL coordinates project discussions, preliminary scoping, technical planning, -contributor participation, and delivery. +### Keep relationships clear -When a formal agreement involving OSL is required, OSC reviews the proposed -arrangement and, if approved, is the legal organisation entering into and -signing the agreement on behalf of the hosted project. +OSL, consulting partners, clients, and community programmes have different +roles. -OSL may also use available project funds to compensate contributors for -completed, approved open-source work through **Invoice** expenses administered -by OSC. +Professional consulting should not depend on unpaid volunteers or create +commercial delivery obligations for participants in OSL internships, mentorship +programmes, or community activities. -The precise contract, payment, intellectual-property, confidentiality, -acceptance, and delivery terms are determined for each engagement. +## Looking for something different? -## Start a conversation +Our current partners may not cover every technology, scientific discipline, +country, or type of engagement. -Tell us about the project, repository, research workflow, or technical problem -you would like to discuss. +That should not stop you from contacting us. -You are also welcome to contact us when your needs do not fit neatly into one of -the services described on this page. We can discuss whether OSL can support the -work directly, develop a customised engagement, collaborate with an appropriate -partner, or suggest another route. +If you need a different type of consulting or professional support, we may be +able to: -Prospective clients may contact OSL about standard consulting services, unusual -or custom technical needs, research software, educational or community work, and -possible partner-supported arrangements. You do not need to determine the -contracting route before contacting us; OSL and OSC will identify the -appropriate route after the initial discussion. +- identify another potential partner; +- connect you with an affiliated project or specialist; +- explore collaboration with another organisation; +- introduce you to someone in the wider open-source or research software + ecosystem; +- suggest a different route when OSL is not the appropriate place for the + request. -Helpful information includes: +An introduction from OSL does not guarantee that a provider will accept the +project, and clients remain responsible for evaluating whether an independent +partner is appropriate for their needs. -- a link to the repository, project, or relevant documentation; -- a short description of the problem; -- the outcome you would like to achieve; -- important technical, scientific, ethical, or regulatory requirements; -- your preferred timeline; -- your approximate budget or funding constraints; -- whether the work must be public; -- whether confidential information or restricted data is involved; -- whether you need a defined project, continuing maintenance, or another form of - support; -- whether you are open to an engagement involving an appropriate partner, - affiliated project, or independent specialist. +[Discuss another consulting need](mailto:team@opensciencelabs.org?subject=Open%20Science%20Labs%20consulting%20partner%20inquiry) + +## Become a consulting partner + +We would like this initiative to grow beyond a single organisation. + +Companies, cooperatives, research software groups, independent specialists, +nonprofits, and other organisations with professional expertise in open source, +science, research software, education, or related technical areas are welcome to +discuss becoming part of the OSL consulting network. + +We are particularly interested in partners that: + +- understand open-source communities; +- respect upstream projects and their maintainers; +- value transparent and maintainable engineering; +- are comfortable collaborating across organisations; +- support open science, education, research, or social-impact work; +- can provide professional services through an appropriate legal and financial + structure, either independently or, where eligible and approved, with + fiscal-host support facilitated by OSL. + +Partnership does not mean that OSL guarantees projects, revenue, clients, or +exclusive access to opportunities. + +Our goal is to build a network in which organisations can discover appropriate +expertise and collaborators more easily. + +[Contact Open Science Labs about becoming a consulting partner](mailto:team@opensciencelabs.org?subject=OSL%20consulting%20partnership) + +## For the OSL community + +This initiative is also part of a broader goal: creating more pathways between +community participation and professional open-source work. + +Consulting engagements are managed by the partner delivering the service, +including decisions about staffing, compensation, contracting, and contributor +participation. + +Where appropriate, a partner may decide to collaborate with contributors from +the OSL ecosystem. + +However: + +- community participation does not create an entitlement to paid consulting + work; +- internships and volunteer programmes are separate from commercial + engagements; +- contributors should not be expected to fulfil client obligations without an + appropriate professional arrangement; +- each consulting partner determines how it selects and works with + contributors. + +We hope that, as the partner network grows, it can create more opportunities for +people to gain experience, collaborate across organisations, and build +sustainable careers around open source and research software. + +## Start a conversation + +If your organisation needs help with open-source software, research software, +scientific workflows, technical education, or another related challenge, +contact us. + +You can come to OSL even if you do not know which partner would be the best fit. + +Tell us about: + +- your organisation or project; +- the problem you are trying to solve; +- the technologies involved; +- your expected outcome; +- your timeline; +- your approximate budget; +- whether you already have a contracting and payment structure or may need + fiscal-host support; +- any scientific, security, privacy, or regulatory requirements. -A complete specification is not required before contacting OSL. An initial -discussion can help determine the appropriate workflow, delivery structure, and -whether the request is a suitable fit. +We will review the enquiry and, when possible, help identify an appropriate next +step. -Primary contact: [team@opensciencelabs.org](mailto:team@opensciencelabs.org) +Primary contact: +[team@opensciencelabs.org](mailto:team@opensciencelabs.org) Discuss your project -[Discuss another consulting need](mailto:team@opensciencelabs.org?subject=Open%20Science%20Labs%20custom%20consulting%20inquiry) +You can also explore our first consulting partner: +[SciStitch](https://scistitch.com/).