Giter Site home page Giter Site logo

foundation's Introduction

foundation's People

Contributors

domenkozar avatar edolstra avatar fricklerhandwerk avatar raitobezarius avatar rbvermaa avatar thufschmitt avatar zimbatm avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

foundation's Issues

Spending Request: Upgrades to the the macOS builders

What I want to spend money on

In short, I propose we buy 9x Samsung 860 EVO 250GB hard drives (none of the macOS builders use more than 100G.)

I also propose upgrading mac1 from 4G of RAM to 8G of DDR3L 1600 (PC3L 12800), which matches the other mac builders.

How much it will cost

what cost quantity link
Samsung 860 EVO 250GB $60 9 https://www.newegg.com/samsung-860-evo-series-250gb/p/N82E16820147676
8G of DDR3L 1600 (PC3L 12800) (2x4GB) $52 1 https://www.newegg.com/crucial-8gb-204-pin-ddr3-so-dimm/p/N82E16820148608
Mac Mini Logic Board Removal Tool $5 1 https://www.ifixit.com/Store/Tools/Mac-mini-Logic-Board-Removal-Tool/IF145-159?o=3
iFixit Tool Kit $60 1 https://www.ifixit.com/Store/Tools/Pro-Tech-Toolkit/IF145-307?o=4

Total: $680

(Note: the iFixIt tool kit contains all the tools we need and more, plus a case to put them all in.)

Why

I was curious why our macs are so slow to use interactively. It didn't take me long to find some answers.

Passmark says this about our current drives and my proposed drive:

image

Background

Some info about our hardware:

Implementation

I will bug and bother @rbvermaa until he does it. Also, I will link him to these three helpful guides:

Some system info

mac1

00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
Model name:          Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz

              total        used        free      shared  buff/cache   available
Mem:              3           3           0           0           0           0
Swap:            15           0          15

mac2-mac8

00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
Model name:          Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz

              total        used        free      shared  buff/cache   available
Mem:              7           6           0           0           0           0
Swap:            15           0          15

Some SMART info:

mac1

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi/HGST Travelstar Z5K500
Device Model:     APPLE HDD HTS545050A7E362
Serial Number:    TEG5193RKSDAJG
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches

mac2

=== START OF INFORMATION SECTION ===
Device Model:     APPLE HDD HTS541010A9E662
Serial Number:    JD8002D82KZSGD
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches

mac3

=== START OF INFORMATION SECTION ===
Device Model:     APPLE HDD HTS541010A9E662
Serial Number:    JD8002D82L08DD
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches

mac4

=== START OF INFORMATION SECTION ===
Device Model:     APPLE HDD HTS541010A9E662
Serial Number:    JD8002D82D1TVD
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches

mac5

=== START OF INFORMATION SECTION ===
Device Model:     APPLE HDD HTS541010A9E662
Serial Number:    JD8008D828X4XS
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches

mac6


=== START OF INFORMATION SECTION ===
Device Model:     APPLE HDD ST1000LM024
Serial Number:    S35RJ9DGA08673
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches

mac7

=== START OF INFORMATION SECTION ===
Device Model:     APPLE HDD HTS541010A9E662
Serial Number:    JD8002D801SJGD
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches

mac8

=== START OF INFORMATION SECTION ===
Device Model:     APPLE HDD HTS541010A9E662
Serial Number:    J88000D80AAJ6B
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches

Subscription for newsletter

Hi from the marketing team!

We are currently working on reviving a NixOS newsletter (what was previously called weekly.nixos.org). But it is going to be called newsletter and we are going to be posting once a month.

We are using mailchimp. A "problem" (a good problem to have) is that we are not starting from scratch since we already have ~2400 subscribers in the newsletter. Since we are over 2000 subscribers we need to upgrade.

Pricing from what I can see it for next (they call it "Essentials") tier is:

  • 1501-2500 subscribers => $40/month
  • 2501-5000 subscribers => $69/month

If we launch the newsletter I'm sure we will quickly reach the 2500 subscribers.

Can we get the funds to support this idea moving forward.

Thank you, Danke, Grazias, Dziekuje, Hvala, ...

Offering services for NixCon and other events

I want to figure out how we could better use the foundation for NixCon. And hopefully be able to re-use that work for other events like Ocean Sprint, Nix Camp, ...

Having a framework like that in place is a requirement for NixCon 2023 to happen. We need to have something in place before the end of February so we have enough time to book the event, ...

Problem statement

Events require money to function (sorry to be crude). On the input, you typically have sponsors and tickets. On the output; venue, catering, swag, AV equipment, ...

The foundation is a financial vehicle registered in NL and that can be used to fund various efforts (and people?).

How can we make those work together to:

  • promote more Nix-related events by reducing the financial overheads
  • funnel excess profit from sponsors back to the foundation
  • improve the transparency around event costs, ...

Naive first proposal

The NixOS Foundation would provide a form that event organizers have to fill, with some required information like location, organizers, ...

The NixOS Foundation would provide the Pretix platform, pre-configured with a Stripe account, to provide ticket sales. I'm assuming we want to use the hosted Pretix version so that some of the proceedings maintain that valuable software and don't have to burden the infra team.

The NixOS Foundation would send invoices to sponsors that agree to fund a specific event.

The NixOS Foundation would handle the invoices to pay for the venue, ...

For any events smaller than 100.- EUR (something that can pay pizzas and beer) and that happens less than 12 times per year for a given region; the foundation would only require minimal inputs.

For larger events, the organizers would be responsible for finding the sponsors (although the foundation can help communicate with/provide repeat sponsors).

TODO: How to deal with insurance?

TODO: How to deal with VAT? (see #10)

TODO: Should we hire a temp. secretary?

Create report of spending

Once we start spending money, we should have a report about how much we are spending and on what, so that people donating money can see what we are using the donations for.

Clearly establish the roles of the chairman, treasury and secretary

What are the duties and legal obligations of the new members?

There are some legal duties that we have to fulfill with the NL government, and then a set of expectations that we have internally.

If I get access to the founding document I can get them translated, and then take a look at the NL laws as well, and come up with a proposal.

Empower and structure the teams in the community

What are we trying to solve here?

  1. The Nix ecosystem is unified by an overarching vision of what we value and where we want to go, but that vision is very rough and implicit;
  2. We generally don't know how to target our efforts, even when there's a clear common goal. Because of that, the Nix ecosystem could be described as a very rich galaxy of half-baked projects;
  3. Even when we can have a targeted effort towards a common goal (works like the Infrastructure team or the Marketing team for example), these still tend to happen in silos. They are seldom visible to the rest of the community, and don't communicate or collaborate with each other.

Figure out NixCon VAT

Two issues:

  • We probably need to pay VAT in France for the tickets.
  • And we need to pay VAT for the sponsors, probably also in France.

So we probably need to register with the French tax authorities and pay VAT for 2022.

@armijnhemel is going to ask his tax advisor about this.

Set up a credentials scheme for the marketing team

The Nix marketing team needs a way to handle credentials to the various communication channels they work with.

Specifically and immediately, the team needs

Generally, the marketing team (and supposedly other teams in the future) needs

  • a predictable scheme of obtaining and handling credentials
  • a process for creating or claiming accounts on communication platforms
  • a way to keep track of who has access to what.

This was discussed with @garbas and @tomberek on the Nix marketing meeting 2023-03-15.

Establish a Cloudflare Pages account at the Foundation level

At the moment, nix.dev uses Domen's personal CloudFlare Pages account for publishing the site. As nix.dev is currently a semi-official information outlet under the Foundation, it would be best to have an account managed by the Foundation instead.

The practical issue that brought this up is that nix.dev doesn't currently have per-pull-request deploy previews, which is a feature provided by CloudFlare Pages. Some members of the Nix docs team (including myself) would like to see that enabled and would currently need to go through Domen for that. Nothing against the lovely Domen, of course, but a Foundation-level account would enable us to distribute admin capabilities across select members of the Foundation/docs team.

In terms of cost, the free plan would likely suffice to begin with. In the event that a higher plan is needed, multiple projects could likely be covered by a pro plan simultaneously.

image

Create the process of establishing new teams

Team work is essential for efficient use of available human resources. For example, splitting packaging work on Nixpkgs in to domain specific teams can have very positive impact on packages quality, can rapidly speed up their development and maintenance and can be motivating factor for existing and new contributors. Unfortunately, there is no official process or guideline for creation and bootstrapping of new teams.

Team creation process should provide information such as:

  • complete list of already existing teams
  • list of minimal human resources requirements (for example: team lead + 2 other members)
  • requirements for declaration of some scope of interest/motivation (for example: the team is interested in geospatial packages development and maintenance)
  • exact process of team infrastructure creation and configuration (creation of GitHub team, adding members, setting all permissions, creation of home page, creation of matrix channel)
  • list of available founding for team (for example: covering expenses for team sprints)
  • recommendations for assets (for example Nixpkgs packages) adoption (how to migrate packages from single/multli person maintenance to team)
  • recommendations for best practices to operate

Finish the transfer of nix.dev

It would be good to finish the transfer of ownership of nix.dev to the foundation and the documentation team. I noticed some uncertainty because the documentation is halfway in the org, but still contains the copyright notice to Domen. I suppose that documentation team members want to know that their work is held in good hands.

@domenkozar, what are the requirements on your side for this to happen?

Documentation: Apply to Google Season of Docs

The Nix documentation team is preparing an application for Google Season of Docs. The deadline is Friday 2023-03-24.

The plan is to make a project draft to be approved by the board until the next board meeting (Tuesday 2023-03-21) and then either provide all data for a board member to submit the form or do it on the board's behalf.

It would be great if the foundation could support a successful grant with additional funds, e.g. by matching the grant amount.

project domain name

we observe that people are confused about names in the Nix ecosystem and find it hard to distinguish between its components.

given the goal of easing learning Nix, we should reduce that confusion as much as possible.

proposal:

  • match domain names to component names

considerations:

  • Nix and Nixpkgs are not used separately at large
    • its possible though and some do it
  • NixOS covers a distinct use case, and only ~half of the 2022 survey respondents use NixOS daily
    • @MMesch reports that most business users are not on NixOS
  • Nix is at the core of the ecosystem, everything builds on top and around it

current state:

options:

related:

@garbas this is a responsibility of the marking team, but intimately concerns documentation w.r.t. consistency and avoiding confusion

Formalize a funding/grants program

  • Official sponsorship program plan
  • Transparent budget reports
  • Improve the grant program as we just kicked it off (note from myself: I copy-pasted this from the last meeting notes, but I'm not sure what it means. I'll let another board member refine this point)

Formalize community teams with GitHub teams

GitHub offers a mechanism to group people together to assign them to issues or pull requests, and provide contact and other information. Currently we don't use it in any structured fashion, which makes discoverability of team members and their activities unnecessarily hard.

Registering the NixOS Trademark

There is a lengthy legal process to register the NixOS trademark.

What's the process?

  • Eelco, Ron and Armijn have interviewed multiple trademark registering teams and began engagement
  • We've worked with the trademark team based on their guidance to define the wording of it.
  • Define what we are registering : Nix + logo
  • Initiate registration process and pay fees for each country (each registration process will take 3 - 6 months)
    in UE € 1850,00
    in UK € 950,00
    in US € 1990,00
  • Work across the community to define the trademark policy based on issue #36

Setup the Pretix shop for NixCon

NixCon has a Pretix shop they use to sell tickets.

In order to have the Foundation be the fiscal host for the event, we will need to:

  • Give access to the Pretix shop to the foundation members
  • Create a Stripe account for the Foundation if it doesn't already exists
  • Have the Foundation set some rules in regard to the use of their accounts, to avoid misunderstanding.
  • Setup the IBAN and Stripe accounts, so the amounts are forwarded to the Foundation

Apply for eHerkenning for ED

Needed to submit taxes etc. Rob currently does that but since he's leaving the board, we need another board member to be authorized.

decide what is an official project in the Nix ecosystem

There is no clear definition of what firmly belongs to the Nix ecosystem, what is "official" or merely "associated", and what is considered third-party.

Tasks

  • decide on criteria
  • define processes for state transitions
  • take inventory
  • update status

Proposal

  1. Mentioned (third party): Code that works and solves a known problem
  2. Endorsed (third party): Significant user base; software is usable and approachable (don't have to read the code to work with it)
  3. Recommended (community project): Large user base; maintained and accepting contributions
  4. Official: Vital to the ecosystem; actively developed by at least two people and with enough resources in the long run; high standards of code quality, collaboration, and documentation

Publish Nix Financials and Budget to Community

Create a public report that covers all the donations and expenses operated by the NixOS foundation that is shared with the community.
The goal is part of our larger effort to make more parts of the foundation transparent.

Define a permission scheme for maintainers

For the few formal teams we have as well as generally on NixOS/nixpkgs the process is mostly implicit and unstructured.

Nixpkgs uses a magic issue where @domenkozar essentially hands out commit bits based on comments. The Nix team got into working mode after pestering @edolstra into setting up permissions. This

We are currently blocked on that in the @NixOS/documentation-team where we have to make up the process as we go, and have to resort to ask org owners ad hoc. It would be good to have something written down that the next generation of community members and team leads can refer to.

Proposal

  1. Implement #21 and make team leads maintainers for their GitHub team
  2. Give team leads merge access to all repositories their team is concerned with
  3. Give each team triage access to the same repositories
  4. Give team leads write access to the NixOS Calendar
  5. Use teams for CODEOWNERS and establish the practice of team leads merging PRs approved by team members

The advantage of this is what amounts to a hierarchy of responsibilities, where team leads can decide themselves who they trust with curating project boards and how much energy to spend on double checking their team members' reviews, but are ultimately responsible for merging changes.

Related:

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.