Hey,
I just read the announcement, and want to come with a suggestion.
Since the community have pretty much figured out how to set up Jenkins and get everything to build locally, would it be an idea for us to document it? (And would it be okay to create a pull request for that documentation, so it can be hosted as part of the official VyOS documentation).
If so, I will be creating a ticket in vyos.dev, to have a place to track it all.
Also, it seems a few changes to some packages might be needed - would you guys accept pull requests for the packages, so they can be built locally? (While still allowing them to build in your system like they always have).
I’m also thinking about a way to include both the official and unofficial branding into the package that contains it, and then having the home made stuff use the unofficial, so the ISO’s people build thenselves won’t have the official VyOS graphics and ascii art.
What do you guys think?
I think going this way, if possible, would result in the community seeing that you guys don’t mind us building our own ISOs - and it would solve the problem of bandwidth for the mirror, and the problem with people releasing home built ISO’s to others (they can still do that, but the branding will indicate that it isn’t anything official)
Well… Dont ask to ask…
Normally I would agree.
However, my idea require the VyOS team to be onboard with it, since it require them to approve of it.
I am willing to spend the time on getting the ball rolling, but if all it results in is silence, I won’t.
I really want the issue to be resolved in a way that works for everyone, and if the reasons they say are true, we should be able to work it out. (I hope they are true, since the alternative would mean that they don’t want anyone to have access to the stable branch without playing)
My hope is that, that isn’t the case.
And if we can get it resolved, it would make it really easy for them to say: “See, we do want the community, we cannot provide hosting for the packages, here is a guide on how to set everything up yourself. Branding will indicate it isn’t official, but please play around with it and report back any finding”
That would give a huge amount of goodwill - but it requires teamwork.
So, are you guys (VyOS team) up for it?
So start by creating a task over at https://vyos.dev and then you will get an official reply.
Some parts of this are in the feature requests created by me:
âš“ T6450 Use http instead of https for rolling apt repo access - closed wontfix, but discussion indicates it should be possible to use apt-mirror to create mirrors of the original https repo to create mirrors accessible for http
âš“ T6451 Please consider removing trademarked logo/artwork in public build scripts - open wishlist, so there is some hope
âš“ T6483 Please include corresponding source packages for all .deb packages in APT repo - open wishlist, so there is some hope
But even if promises are made, remember Sentrium is a company that could be acquired by some other company, then the new owners can say that the promises of the previous owners are no longer valid. Google too said “don’t be evil” in the beginning…
1 Like