Skip to content

autoformats html #262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 30, 2023
Merged

autoformats html #262

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f7d8b15
autoformats html
jzwood Mar 7, 2023
5e2f562
updates README.md
jzwood Mar 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,3 +24,4 @@ dist-newstyle/

### General ###
*~
.DS_Store
8 changes: 7 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,12 +25,18 @@ To build the project:
stack build
```

Once the project has built (which can take a while due to the dependencies for Hakyll), to generate the site use:
Once the project has built (which can take a while due to the dependencies for Hakyll), generate the site with:

```bash
stack exec -- site build
```

and for development use:

```bash
stack run -- site watch
```

The site will be build in the `_site` directory, and you can open the files in your browser of choice. Due to a Hakyll issue, some sponsor logos will not show up correctly. This is expected behavior, and should be fine for the deployed site.

For further information, please refer to the [CONTRIBUTING.md](CONTRIBUTING.md) at the root of this project.
Expand Down
258 changes: 135 additions & 123 deletions affiliates/about/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,168 +8,180 @@ <h1 class="text-2xl-5xl">What Does Affiliation Entail?</h1>
</div>
</div>

<div class="xl:max-w-screen-xl mx-auto md:px-12 lg:px-16">
<div class="bg-gray-800 shadow-lg shadow-xl shadow-md shadow-sm px-6 sm:px-12 md:px-12 lg:px-16 py-16 md:py-20">
<div class="grid gap-8 lg:grid-cols-2 lg:gap-16 lg:text-xl text-gray-300 leading-relaxed">

<div class="space-y-8">
<div>
Affiliation means that the group supports the goals of the Haskell Foundation, and, in return, the Haskell Foundation supports this group.
</div>
<div>
Different groups work in different ways, and it would be counter-productive to impose complete uniformity. However, we expect the groups that want to affiliate with the Haskell Foundation to follow a few ground rules, laid out below.
</div>
</div>
<div class="space-y-8">
<div>
Affiliation does not mean that the HF is taking over control of that group’s bailiwick. The group’s powers and responsibilities remain unchanged, although it would be reasonable to expect the group to take into account the views of the HF.
</div>
<div>
We make a distinction between projects and committees.
</div>
</div>
<div class="xl:max-w-screen-xl mx-auto md:px-12 lg:px-16">
<div class="bg-gray-800 shadow-lg shadow-xl shadow-md shadow-sm px-6 sm:px-12 md:px-12 lg:px-16 py-16 md:py-20">
<div class="grid gap-8 lg:grid-cols-2 lg:gap-16 lg:text-xl text-gray-300 leading-relaxed">

<div class="space-y-8">
<div>
Affiliation means that the group supports the goals of the Haskell Foundation, and, in return, the Haskell Foundation supports this group.
</div>
<div>
Different groups work in different ways, and it would be counter-productive to impose complete uniformity. However, we expect the groups that want to affiliate with the Haskell Foundation to follow a few ground rules, laid out below.
</div>
</div>
<div class="space-y-8">
<div>
Affiliation does not mean that the HF is taking over control of that group’s bailiwick. The group’s powers and responsibilities remain unchanged, although it would be reasonable to expect the group to take into account the views of the HF.
</div>
<div>
We make a distinction between projects and committees.
</div>
</div>

</div>
</div>

</div>

<div class="max-w-screen-xl mx-auto">
<div class="mt-16 md:mt-24">

<div class="px-4 sm:px-8 md:px-12 lg:px-16">
<div class="mx-auto prose md:prose-lg">
<div class="px-4 sm:px-8 md:px-12 lg:px-16">
<div class="mx-auto prose md:prose-lg">

<h2>Affiliated Committees</h2>
<h2>Affiliated Committees</h2>

<h3>Transparency</h3>
<ul>
<li><p>
Group must have some website that makes it clear what the goals and responsibilities of this group are
</p></li>
<li>
<p>
All technical discussions must be stored in a publicly accessible location, for example:
</p>
<h3>Transparency</h3>
<ul>
<li><p>
GitHub issues
</p></li>
<li><p>
GitLab issues
</p></li>
<li><p>
Mailing list archives There is an obvious exception for confidential matters such as financial and security related information
</p></li>
<li>
<p>
Group must have some website that makes it clear what the goals and responsibilities of this group are
</p>
</li>
<li>
<p>
All technical discussions must be stored in a publicly accessible location, for example:
</p>
<ul>
<li>
<p>
GitHub issues
</p>
</li>
<li>
<p>
GitLab issues
</p>
</li>
<li>
<p>
Mailing list archives There is an obvious exception for confidential matters such as financial and security related information
</p>
</li>
</ul>
</li>
<li>
<p>
It should be clear what decisions the group has taken, and what are under discussion (if it’s that kind of group). A good example of this are the GHC Steering Committee proposals, but a simple email to a public list can also suffice.
</p>
</li>
<li>
<p>
The group must have a voting system in place in case it cannot reach unanimity. Votes must be accompanied by reasoning, and a tie-breaking mechanism should be in place.
</p>
</li>
</ul>
</li>
<li><p>
It should be clear what decisions the group has taken, and what are under discussion (if it’s that kind of group). A good example of this are the GHC Steering Committee proposals, but a simple email to a public list can also suffice.
</p></li>
<li><p>
The group must have a voting system in place in case it cannot reach unanimity. Votes must be accompanied by reasoning, and a tie-breaking mechanism should be in place.
</p></li>
</ul>

<h3>Membership</h3>
<ul>
<li>
<p>
The group’s website should list its members (with their affiliations and terms), and the membership rules.
</p>
</li>
<li>
<p>
Groups should appoint a chair (or co-chairs) or a contact for Haskell Foundation.
</p>
</li>
<li>
<p>
Groups should ensure a turnover of membership, for example by setting terms.
</p>
<h3>Membership</h3>
<ul>
<li>
<p>
This only makes sense for "decision-making" bodies, not really for groups that just focus on doing work.
The group’s website should list its members (with their affiliations and terms), and the membership rules.
</p>
</li>
</ul>
</li>
<li>
<p>
The process for appointing new members should be clearly set out:
</p>
<ul>
<li>
<p>
There should be a “way in” for new members who are not already part of the “in crowd”; for example, a regular opportunity to self-nominate.
Groups should appoint a chair (or co-chairs) or a contact for Haskell Foundation.
</p>
</li>
<li>
<p>
Criteria for new members should be written down, so that new members can address them in writing a self-nomination.
Groups should ensure a turnover of membership, for example by setting terms.
</p>
<ul>
<li>
<p>
This only makes sense for "decision-making" bodies, not really for groups that just focus on doing work.
</p>
</li>
</ul>
</li>
<li>
<p>
A reasonably broad group of people should be involved in making appointment decisions (e.g. not just the chair). Typically the whole group votes on appointing new members.
The process for appointing new members should be clearly set out:
</p>
<ul>
<li>
<p>
There should be a “way in” for new members who are not already part of the “in crowd”; for example, a regular opportunity to self-nominate.
</p>
</li>
<li>
<p>
Criteria for new members should be written down, so that new members can address them in writing a self-nomination.
</p>
</li>
<li>
<p>
A reasonably broad group of people should be involved in making appointment decisions (e.g. not just the chair). Typically the whole group votes on appointing new members.
</p>
</li>
</ul>
</li>
</ul>
</li>
</ul>

<h3>CODE OF CONDUCT</h3>
<p>
Groups must adopt the <a href="/guidelines-for-respectful-communication">Guidelines for Respectful Communication</a>. Groups may additionally adopt other guidelines & CoCs that are stronger; as long as they do not conflict with the GRC.
</p>
<p>
Why make a code of conduct as part of HF affiliation?
</p>
<ul>
<li>
<h3>CODE OF CONDUCT</h3>
<p>
We want the Haskell community to be welcoming, diverse, and inclusive. Having explicit guidelines for respectful communication signals that desire, and makes it more explicit and concrete.
Groups must adopt the <a href="/guidelines-for-respectful-communication">Guidelines for Respectful Communication</a>. Groups may additionally adopt other guidelines & CoCs that are stronger; as long as they do not conflict with the GRC.
</p>
</li>
<li>
<p>
For all of us, as individuals and as groups, making an explicit commitment to respectful communication encourages us to review our messages to see if they meet the goals set out in the guidelines, and will give others some specifics to point to if we fail.
Why make a code of conduct as part of HF affiliation?
</p>
</li>
</ul>
<ul>
<li>
<p>
We want the Haskell community to be welcoming, diverse, and inclusive. Having explicit guidelines for respectful communication signals that desire, and makes it more explicit and concrete.
</p>
</li>
<li>
<p>
For all of us, as individuals and as groups, making an explicit commitment to respectful communication encourages us to review our messages to see if they meet the goals set out in the guidelines, and will give others some specifics to point to if we fail.
</p>
</li>
</ul>

<h2>Affiliated Projects</h2>
<h2>Affiliated Projects</h2>

<ul>
<li>
<p>
The project must have a public issue tracker and/or mailing list where discussion about the project takes place
</p>
</li>
<li>
<p>
The expectation is that the project has at least one responsive maintainer. If this is not the case, it should be clearly signalled that more resources are required.
</p>
</li>
<li>
<p>
The project must be open to community discussion about possible features and contributions.
</p>
</li>
<li>
<p>
The project should encourage new contributors and members, i.e. there should be "a way in".
</p>
</li>
<li>
<p>
Just like committees, the project must adopt the <a href="/guidelines-for-respectful-communication">Guidelines for Respectful Communication</a> as a code of conduct.
</p>
</li>
</ul>
<ul>
<li>
<p>
The project must have a public issue tracker and/or mailing list where discussion about the project takes place
</p>
</li>
<li>
<p>
The expectation is that the project has at least one responsive maintainer. If this is not the case, it should be clearly signalled that more resources are required.
</p>
</li>
<li>
<p>
The project must be open to community discussion about possible features and contributions.
</p>
</li>
<li>
<p>
The project should encourage new contributors and members, i.e. there should be "a way in".
</p>
</li>
<li>
<p>
Just like committees, the project must adopt the <a href="/guidelines-for-respectful-communication">Guidelines for Respectful Communication</a> as a code of conduct.
</p>
</li>
</ul>

</div>
</div>
</div>

</div>
</div>
Loading