Universal Blue•3y ago

" There are four hard things in computer science: - Counting - Cache invalidation - Naming things "

"
There are four hard things in computer science:
- Counting
- Cache invalidation
- Naming things
"

j0rge•3/1/23, 3:35 PM

@.jstone after the rename marco wants to finish animesh's PR so we can do versioned containerfiles

CChaiQi " There are four hard things in computer science: - Counting - Cache invalidatio...

dreamyuki•3/1/23, 3:42 PM

true
i just naming my project with something random

j0rge•3/1/23, 6:01 PM

@.jstone I was thinking, can we just rename ublue-os/base the repo from base to main?

j0rge•3/1/23, 6:02 PM

and change the package name?

Marco (马可)•3/1/23, 6:05 PM

We could do that, I'd suggest we start with a branch for the changes. Alternatively, start a new repo and when ready archive this one with a new readme

Jj0rge @.jstone I was thinking, can we just rename ublue-os/base the repo from base to ...

jstone•3/1/23, 6:07 PM

That might be one way of doing it, provided it's also coordinated with moving the ublue first-run functionality into another repo

j0rge•3/1/23, 6:08 PM

right

j0rge•3/1/23, 6:08 PM

actually, we should create a new one so we're not in a rush to "flip a switch"

jstone•3/1/23, 6:09 PM

Yeah

xyny•3/1/23, 6:29 PM

I think we should steer the current base towards being the startingpoint image (as proposed in my graph). Strip it down, and make it a custom image starting point intended to be based on the -main, with more customizability in mind.

j0rge•3/1/23, 10:44 PM

@.jstone is there anything I should be doing to prep for the image restructuring?

j0rge•3/1/23, 10:46 PM

also I'd like for us to figure out what the scope of images is on the -main image

Jj0rge @.jstone is there anything I should be doing to prep for the image restructuring...

jstone•3/2/23, 12:14 AM

I think the easiest thing to do would be to create a ublue-os/mainublue-os/main repo so that we have a clean slate to play with, and ensure that cosign is set up

j0rge•3/2/23, 12:18 AM

ok so not a copy

j0rge•3/2/23, 12:18 AM

base is set to be a template anyway

jstone•3/2/23, 12:19 AM

The scope should be A) one parameterized Containerfile for multiple Fedora releases and DEs B) limit the Containerfile defintion to essential rpm-ostree installs with QoL package inclusion/exclusion lists. This will give downstream maintainers a simple path for consuming images and ensuring that they're only adding features and not taking them out

jstone•3/2/23, 12:21 AM

I think anyone submitting package inclusion requests should be asking themselves if what they're requesting will be generally useful for everyone and won't benefit just one subset of users. If the feature is too specific, then it should instead exist in a downstream image

j0rge•3/2/23, 12:26 AM

oh I know!

j0rge•3/2/23, 12:26 AM

Issue template!

jstone•3/2/23, 12:28 AM

Ooohhh yes please!

jstone•3/2/23, 12:29 AM

I'd love a template that lets users select versions and whatnot

j0rge•3/2/23, 12:29 AM

https://github.com/ublue-os/main

GitHub

GitHub - ublue-os/main: A base image with batteries included

A base image with batteries included. Contribute to ublue-os/main development by creating an account on GitHub.

j0rge•3/2/23, 12:29 AM

working on template now

jstone•3/2/23, 12:31 AM

Permission to start placing files in the repo?

j0rge•3/2/23, 12:32 AM

lazy concensus!

j0rge•3/2/23, 12:33 AM

don't add any packages though if you can help it, like add the minimum so we can all use the templates

jstone•3/2/23, 12:34 AM

What do you mean by that?

j0rge•3/2/23, 12:40 AM

let me make a template so we can use the templates to add packages

j0rge•3/2/23, 12:41 AM

so I can test the wording, etc. of the template and we can practice

jstone•3/2/23, 12:41 AM

Ack

j0rge•3/2/23, 12:42 AM

I have fancy work templates I can reuse

j0rge•3/2/23, 12:42 AM

I'll be done in a few minutes

рибаня•3/2/23, 12:45 AM

how do you guys feel about feature branches instead of repos? It would conflate issues and PRs into one place but it also might be easier for users to work with

j0rge•3/2/23, 12:45 AM

I kind of kept it split on purpose for a few reasons

j0rge•3/2/23, 12:46 AM

say in a few months ribbanya-linux blows up and everyone loves it and you have thousands of new fans and admirers

j0rge•3/2/23, 12:46 AM

and my ubuntu image does the same thing but it's a different community, though a subset of this one

j0rge•3/2/23, 12:48 AM

https://github.com/ublue-os/main/pull/3

GitHub

feat: add initial issue template by castrojo · Pull Request #3 · ub...

j0rge•3/2/23, 12:48 AM

This is going to be :lit:

j0rge•3/2/23, 12:48 AM

j0rge•3/2/23, 12:49 AM

^^^ can someone review that PR?

Jj0rge and my ubuntu image does the same thing but it's a different community, though a...

рибаня•3/2/23, 12:50 AM

well in that scenario the fork would be ribbanya/ribbanya-linux which is a fork of ublue/main, and so my fork would have its own PRs, issues, and discussions

(not that I think separate repos are a bad idea, was just wondering)

j0rge•3/2/23, 12:50 AM

oh, I meant within the org itself

j0rge•3/2/23, 12:50 AM

assuming a ublue-os/ribbanya

j0rge•3/2/23, 12:50 AM

didn't we try a dev branch in nvidia and then end up regretting it?

рибаня•3/2/23, 12:51 AM

I mentioned this in the discussions but I do think, since we are starting from scratch with ublue/mainublue/main, all of the derivative repos should be git clones so they can merge upstream

j0rge•3/2/23, 12:53 AM

What commands do we want run in a bug report, I'm thinking rpm-ostree status -vrpm-ostree status -v at a minimum

Ррибаня how do you guys feel about feature branches instead of repos? It would conflate ...

jstone•3/2/23, 12:53 AM

I have very mixed feelings about the mono repo model for our needs because we already have a protected branch model to ensure that people must have a pull request, which means more branches, and making sure we don't end up rebasing and merging onto the wrong branch can be a management nightmare

j0rge•3/2/23, 12:54 AM

for sure reinvestigate when we're larger though

Jjstone I have very mixed feelings about the mono repo model for our needs because we al...

рибаня•3/2/23, 12:54 AM

I think it definitely comes down to your social structure of maintainers which I'm not familiar with

jstone•3/2/23, 12:55 AM

Having feature branches does work in certain contexts like for managing very similar files across a release branches https://src.fedoraproject.org/rpms/kernel

" There are four hard things in computer science: - Counting - Cache invalidation - Naming things "

Similar Threads

Similar Threads

Similar Threads