RFC: documenting PureScript's governance/structures/policies/processes

f-f · February 7, 2020, 11:09am

@hdgarrood I accepted the invitation to the org, but it seems like I don’t have permission to create new repos, which is necessary to move other repos too. Here’s how to enable that

garyb · February 7, 2020, 1:56pm

@f-f done! But also I’ve given you full admin rights now so you can set up anything that might be required without being hindered again.

hdgarrood · February 7, 2020, 2:33pm

Yeah, it only gave me the option to invite you as a member in the first instance, I think you have to wait until the person has accepted the invitation to make them an admin.

f-f · February 10, 2020, 1:33pm

Thanks @garyb and @hdgarrood! I managed to finally fix CI and publish a new release from the new location

At this point there should be only two things to fix:

@hdgarrood could you delete your AppVeyor build for Spago? It looks like both mine and yours are building against the repo, but only mine has the right tokens
I wanted to downgrade my status from “owner” to “member” of the org as agreed, but GitHub doesn’t seem to let me do that, does anyone know how to do it?

garyb · February 10, 2020, 2:32pm

I’ve downgraded you to “member”, but also made a Spago team which you’re a member of, and given that team admin rights to spago - hopefully that’ll mean you can change anything that might need changing in the future.

hdgarrood · February 10, 2020, 11:09pm

Good to hear! The appveyor project should be deleted now.

chexxor · February 11, 2020, 4:41am

In case there is need for details of governance models, the people behind the Core Infrastructure Initiative’s best practices and badge system have spent a lot of time defining criteria and conversing with a variety of projects to ensure they are correct, appropriate, and fair.

This document discusses the basic requirements of a project’s governance model for the Silver badge, amongst other things like essential documentation:

github.com

coreinfrastructure/best-practices-badge/blob/master/doc/other.md

# Other criteria for higher-level badges

<!-- SPDX-License-Identifier: (MIT OR CC-BY-3.0+) -->

## Introduction

This document describes the criteria for badges beyond the "passing" level
(the "silver" and "gold" levels).
Please
[post an issue](https://github.com/coreinfrastructure/best-practices-badge/issues)
if you have comments on these criteria.
These criteria build on the
<a href="./criteria.md">criteria for the "passing" level</a>.
Note that passing is by itself an achievement; at the time of this writing
only about 10% of projects that are pursuing a badge achieve the
passing level.

These higher levels are named "silver" and "gold":

* Silver (formerly "passing+1") is a more stringent set of criteria

This file has been truncated. show original

As a side-note, the requirements for the “basics” badge is documented here, for those interested:

github.com

coreinfrastructure/best-practices-badge/blob/master/doc/criteria.md

# Best Practices Criteria for Free/Libre and Open Source Software (FLOSS)

<!-- SPDX-License-Identifier: (MIT OR CC-BY-3.0+) -->
<!-- DO NOT EDIT generated file criteria.md !! -->
<!-- The actual criteria and detail text are in config/locales/en.yml -->
<!-- while rationale and other info is in locale/criteria/criteria.yml . -->
<!-- See also files criteria-header.markdown and criteria-footer.markdown . -->

## Introduction

This is a set of best practices
for Free/Libre and Open Source Software (FLOSS) projects.
Projects that follow these best practices
will be able to voluntarily self-certify and show that they've
achieved a Core Infrastructure Initiative (CII) badge.
Projects can do this, at no cost,
by using a web application (BadgeApp)
to explain how they meet these practices and their detailed criteria.

There is no set of practices that can guarantee that software

This file has been truncated. show original