Bjørn Mork [2022-01-23 14:26:18]:
Hi,
> OpenWrt is a rather small project, so it would make sense to piggy-back
> on someone with a bit more manpower. salsa.debian.org comes to mind...
IIRC it was already proposed in the past already. I'll include following note
for future myself:
Sun, 27
At least for sure it must be two separate sites: one for code hosting
and one for downloads.
Because it looks like chances to be blocked are higher for the
downloads site than for the source hosting.
For example VPNs and Tor websites are getting blocked in Russia
On Thu, Jan 20, 2022 at 10:42:15AM +0100, Paul Spooren wrote:
>> Must confess: I was unaware of the ~16k issue body character limit...
>
> I discussed this with Drew (sourcehut developer)
Thanks! That means there's a chance it will be documented and, if
possible, fixed/improved.
Incidentally,
On Tue, Jan 25, 2022 at 09:45:52PM +0200, Sergey Ponomarev wrote:
> Well, we may *speculate* and try to minimise risks but that's what I
> tried to say: it's counterproductive.
Avoiding unnecessary risks is productive. It's one of the ways in which
projects and organisations stay afloat.
>
Well, we may *speculate* and try to minimise risks but that's what I
tried to say: it's counterproductive.
For example, did you know that GitHub was blocked in Ukraine for one day?
As far as I remember, literally some small court in a village said to
block four hundred sites with GH and
On Tue, Jan 25, 2022 at 06:56:04PM +0200, Sergey Ponomarev wrote:
> Speaking about GitHub and access to it from sanctioned territories
> this is a really big concern. [..]
Thank you for corroborating that concern.
Some news reports, think-tank analysis, and legal guidance providers
suggest the
+1 for a GitHub
+1 for GitLab
+1 for a self hosting GitLab
+1 for joining to any existing OS hosting
-1 for plain emails.
As a contributor but not a core developer I would like to ask. Please
tell me honestly. Is the send-patch approach just an IQ test?
Because I failed it :)
My few patches that
Paul Spooren writes:
> None of the OpenWrt project members is willing to setup and maintain a
> GitLab instance and there were multiple vetos again gitlab.com.
I'll take advantage of not being a member and throw out a crazy question
here:
Did anyone reach out to other open source projects wrt
> ## Conclusion
>
> From a FOSS perspective I’d skip GitHub entirely and move to Codeberg or
> sr.ht. Codeberg (Gitea) is a fine clone of GitHub and sr.ht comes with a great
> _no bloat_ attitude and priority on email integration for tickets and git
> (they
> created git-send-email.io).
Hi,
On 22/01/2022 14:37, Petr Štetiar wrote:
> Paul Spooren [2022-01-07 10:34:34]:
>
> Hi,
>
> (adding openwrt-adm@ into the loop)
>
>> None of the OpenWrt project members is willing to setup and maintain a
>> GitLab instance
> so what about having that GitLab instance prepared and co-maintained by
Paul Spooren [2022-01-07 10:34:34]:
Hi,
(adding openwrt-adm@ into the loop)
> None of the OpenWrt project members is willing to setup and maintain a
> GitLab instance
so what about having that GitLab instance prepared and co-maintained by some
trusted 3rd party? I mean, define our needs, find
Etienne Champetier [2022-01-20 14:56:28]:
Hi,
> Any chance you can update the buildbots docker images ?
> (I see only you 2 listed as admins here: https://openwrt.org/infrastructure)
should be done.
Cheers,
Petr
___
openwrt-devel mailing list
Paul Spooren wrote:
>> "Codeberg e.V. is a registered non-profit association based in Berlin,
>> Germany" So, this makes me feel better.
> I’ll write them an email asking for their long term ideas of
> maintaining Gitea. Just because is a “e.V.” and in Germany doesn’t make
>
Hi Petr & Jow
Le jeu. 20 janv. 2022 à 09:10, Paul Spooren a écrit :
>
> Hi Etienne,
>
> >>
> >> Currently we’re facing an issue[1] from our heterogeneous buildbot
> >> setup[2] that partly uses outdated runners missing packages installed host
> >> packages, causing them to upload broken SDKs
Hi Etienne,
>>
>> Currently we’re facing an issue[1] from our heterogeneous buildbot setup[2]
>> that partly uses outdated runners missing packages installed host packages,
>> causing them to upload broken SDKs at random.
>
> My understanding is that buildbot runner are docker containers now
Hi Paul,
Le jeu. 20 janv. 2022 à 05:04, Paul Spooren a écrit :
>
> Hi Florian,
>
> > I have now been persuaded to share my thoughts on the subject as well.
>
> Thank you.
>
> > Why not gitlab?
> > Here we can take the services (GIT, CI/CD, ISSUE-Tracking) from them.
>
> Some people don’t like
Hi Florian,
> I have now been persuaded to share my thoughts on the subject as well.
Thank you.
> Why not gitlab?
> Here we can take the services (GIT, CI/CD, ISSUE-Tracking) from them.
Some people don’t like the particularly “bloated” interface of GitLab but I
agree, they offer the stuff
Hi Michael,
> "Codeberg e.V. is a registered non-profit association based in Berlin,
> Germany"
> So, this makes me feel better.
I’ll write them an email asking for their long term ideas of maintaining Gitea.
Just because is a “e.V.” and in Germany doesn’t make it super sustainable,
Hi Sam,
>
> A big thank you for doing this.
Half the fun.
>
> Must confess: I was unaware of the ~16k issue body character limit when
> I proposed SourceHut. Did you find a public bug report or feature
> request about that? (I looked just now. Could not find one myself, but
> perhaps my
I have now been persuaded to share my thoughts on the subject as well.
Since this is a major change.
In itself, I think it is good that thought is being given to
unification.
Github was the first web-based source code management tool.
So I think it's just that most of user are also on github.
Thank you for this great report!
I did not know codeberg existed, but when I looked, discovered I already had
a login!
I would go with codeberg.
It's okay that many community repos are on git, git makes cloning easy.
Who is funding codeberg, and how stable is that funding?
"Codeberg is not a
On Tue, Jan 18, 2022 at 03:38:43PM +0100, Paul Spooren wrote:
> ## Bug Tracker
>
> I looked today into migrating issues from bugs.openwrt.org over to
> GitHub.com, codeberg.org (GiTea) and todo.sr.ht (Sourcehut). [..]
>
> While sr.ht allows to import the large collection of issues, each
> message
Hi all,
Thanks for the active discussion. My thoughts on the three topics bug tracker,
CI and Git _root_.
## Bug Tracker
I looked today into migrating issues from bugs.openwrt.org over to GitHub.com,
codeberg.org (GiTea) and todo.sr.ht (Sourcehut). The migration path is somewhat
easy
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Op 9 jan. 2022, om 19:16 heeft
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Op 9 jan. 2022, om 19:16 heeft
On 1/7/22 10:34, Paul Spooren wrote:
Hi all,
Back at the Hamburg meeting in 2019 and a succeeding vote we decided to migrate
over to a self-hosted GitLab instance. Some years passed and nothing really
happened so I’d like to give this another go.
None of the OpenWrt project members is
Hi Hauke,
On 1/9/22 17:55, Hauke Mehrtens wrote:
The criteria from gnu.org are irrelevant to me and I agree with Rosen and Bjørn
on that topic.
I would prefer a vote like this, this is just an example not the official vote:
-
Migrate bug reporting from bugs.openwrt.org to
On 1/7/22 10:34, Paul Spooren wrote:
Hi all,
Back at the Hamburg meeting in 2019 and a succeeding vote we decided to migrate
over to a self-hosted GitLab instance. Some years passed and nothing really
happened so I’d like to give this another go.
None of the OpenWrt project members is
>> You must be
>> a) human,
>> b) age 13 or older, and
>> c) obey US law.
>>
>> So who exactly can have a SourceHut account but not a Github account?
>At least anyone who:
>- doesn't run proprietary JavaScript; or
>- boycotts PRISM participants (e.g. Microsoft); or
>- boycotts GitHub or Microsoft
On Sat, Jan 08, 2022 at 08:02:30PM +0100, Bjørn Mork wrote:
> Sam Kuper writes:
>> Not everyone has, or can have, a Microsoft (GitHub) account.
>
> Please explain.
>
> These terms are pretty much identical:
>
>
>
Sam Kuper writes:
> Not everyone has, or can have, a Microsoft (GitHub) account.
Please explain.
These terms are pretty much identical:
https://docs.github.com/en/github/site-policy/github-terms-of-service#b-account-terms
https://man.sr.ht/terms.md#account-terms
You must be
a) human,
b)
On Sat, Jan 08, 2022 at 10:31:01AM -0600, Lao Shaw wrote:
> github is used by so many open source projects and it becomes the de
> facto git repo platform for many,
This is a tragedy.
> what makes openwrt so special to the point that github is not good
> enough and your idea will do better (for
>
> Hi all,
>
> Back at the Hamburg meeting in 2019 and a succeeding vote we decided to
> migrate over to a self-hosted GitLab instance. Some years passed and nothing
> really happened so I’d like to give this another go.
>
> None of the OpenWrt project members is willing to setup and maintain a
Rosen Penev writes:
> https://www.gnu.org/software/repo-criteria-evaluation.html seems to be
> complete garbage. Seems the higher the criteria, the less users.
Yes, I encourage everyone to read that page. Personally, it made me
worry more about the FSFs definition of freedom than using
On Fri, Jan 7, 2022 at 1:38 AM Paul Spooren wrote:
>
> Hi all,
>
> Back at the Hamburg meeting in 2019 and a succeeding vote we decided to
> migrate over to a self-hosted GitLab instance. Some years passed and nothing
> really happened so I’d like to give this another go.
>
> None of the
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Indeed, so +1
Paul
> Op 7 jan.
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Indeed, so +1
Paul
> Op 7 jan.
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
On 07/01/2022 12:07, Sam Kuper
On Fri, Jan 07, 2022 at 12:07:38PM +, Sam Kuper wrote:
> On Fri, Jan 07, 2022 at 10:34:34AM +0100, Paul Spooren wrote:
> > Instead of maintaining flyspray and the server, I’d like to export all
> > flyspray issues, migrate them to GitHub and open GitHub issues for
> > openwrt/openwrt to the
On Fri, Jan 07, 2022 at 10:34:34AM +0100, Paul Spooren wrote:
> Instead of maintaining flyspray and the server, I’d like to export all
> flyspray issues, migrate them to GitHub and open GitHub issues for
> openwrt/openwrt to the public.
Please don't do this. GitHub has substantial accessibility
40 matches
Mail list logo
