Skip to content

Commit

Permalink
Merge pull request #312 from publiccodenet/release-20231107
Browse files Browse the repository at this point in the history
Release 20231107
  • Loading branch information
ericherman authored Nov 7, 2023
2 parents 40154e0 + bc98c5e commit 820648e
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 68 deletions.
4 changes: 4 additions & 0 deletions OSPO.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,10 @@
# SPDX-License-Identifier: CC0-1.0
# SPDX-FileCopyrightText: 2022-2023 The Foundation for Public Code <[email protected]>
type: Resource
redirect_from:
- ospo
- ospos
- OSPOs
---

# Government OSPOs: let's work together
Expand Down
69 changes: 3 additions & 66 deletions careers/intern.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,74 +2,11 @@
# SPDX-License-Identifier: CC0-1.0
# SPDX-FileCopyrightText: 2019-2023 The Foundation for Public Code <[email protected]>
type: Position
excerpt: Join us as either a junior codebase steward or general intern (Flexible, Amsterdam or remote)
excerpt: Not currently accepting internships.
---

# Internship program

Our program offers you the opportunity to work on high value public code projects used around the world, and improve the role of technology in society. You'll help to make public-purpose software and policy – used for example in cities and other public organizations – more open and collaborative.
At this time, the Foundation for Public Code is not accepting new internships.

[The Foundation for Public Code](https://publiccode.net) helps public organizations develop and maintain software and policy together. We provide review of codebases that are in our stewardship to help developers build trusted and reliable software that can be widely reused and foster a strong community around it.

We test against the [Standard for Public Code](https://standard.publiccode.net/) to make codebases understandable, reusable and community based. Our standards are high, as well as opinionated, to ensure codebases can be trusted as the infrastructure of society. The Standard supports continual improvement of codebases and helps policy makers keep technology and architectural choices open.

## What interns do

We have two types of internships: codebase steward and general. Please send us a proposal on how you would fit within the Foundation's activities, based on the information below, your skills and your interests.

### Join as an intern codebase steward

As an intern [codebase steward](https://publiccode.net/codebase-stewardship/) you will be paired with and mentored by one of our codebase stewards to make the Foundation's codebases more trusted, reliable and reusable.

For more information on our four types of codebase stewards please see:

* [Quality - help make codebases more reusable](quality.md)
* [Community - help people work together on codebases](community.md)
* [Product - help make codebases more attractive](product-marketing.md)
* [Support - help people reuse existing codebases](support.md)

### Join as a general intern

As a small but growing organization we also regularly need help from talented indivudals on various issues. Examples include:

* researching and developing case studies on the economics of open source for public use
* improving how we measure impact
* organizing epic events
* supporting ongoing operations in an open-by-default and community-driven organization

You'll get the chance to learn from and work with everyone at the Foundation.

For the latest list of things we are solliciting from contributors, please check out our [GitHub repositories](https://github.com/publiccodenet) or our [individual contributors](https://about.publiccode.net/contributor-guides/for-individuals) page. You can also send us a proposal that you think can benefit us as well as fulfull your internship requirements.

## What we expect from all of our team members

You should:

* share our core values: openness, quality, trust, community, helpfulness
* understand the value of and be experienced with open source products and communities
* want to work for the public good
* have a collaborative work attitude and take pride in making things together
* be able to work independently
* be a strong communicator in English
* have international experience
* be an active participant in the codebase community you support

## More information about this position

We expect interns to join us for at least 3 months, and at least 3 days per week. We are looking for interns to join us from September 2019 onwards.

We are open to all types of applications, including as part of your studies (like a thesis or final project), as a student placement before or after graduation, or independently of an educational program. We will provide some financial compensation for people not covered by their institutions or training program.

The position of intern codebase steward can be fulfilled either in our Amsterdam office or remotely, with trips to our head office in Amsterdam for training and important events. General interns are based in our Amsterdam office.

## More about the application process

We enthusiastically encourage people underrepresented in the worlds of technology and government to apply.

If you want to know more about the position, please get in touch with via [email protected] with:

* your internship prososal
* a cover letter
* a resume or a short explanation of your relevant work experience

We will review applications on a rolling basis.
The program may open again in the future.
2 changes: 1 addition & 1 deletion codebases/openzaak.html
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ <h3>Find out more</h3>
<li><a href="https://github.com/open-zaak/open-zaak" target="_blank">Github repository</a></li>
<li><a href="https://openzaak.org" target="_blank">Product website</a></li>
<li><a href="https://www.youtube.com/playlist?list=PL_5ziu2gADmCnEhBPf2KXXjGqaAdI3epJ" target="_blank">Meet the community</a></li>
<li><a href="https://github.com/open-zaak/open-zaak/blob/main/docs/introduction/open-source/public_code.md">Assessment towards the Standard for Public Code</a>
<li><a href="https://open-zaak.readthedocs.io/en/latest/introduction/open-source/public_code.html">Assessment towards the Standard for Public Code</a>
</ul>
</div>
</div>
3 changes: 2 additions & 1 deletion standard-for-public-code/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,8 +43,9 @@ For the codebase to be completely certified every meaningful line of code, and t

If codebases have been completely audited from the first merge request they can be immediately certified as compliant with the Standard for Public Code.

If the audit process is added to an existing codebase, the new merge requests can be certified, but the existing code cannot be certified.
If the audit process is added to an existing codebase, the new merge requests can be certified, but the existing code will not be automatically certified.
By auditing every new merge request the codebase can move incrementally towards being completely certified.
The codebase stewards can also do a complete audit of a codebase, at the current commit, and start applying the process from then on to ensure that a codebase stays certified.

## The goals for the Standard for Public Code

Expand Down

0 comments on commit 820648e

Please sign in to comment.