- User Since
- Jun 10 2021, 11:53 (67 w, 5 d)
Mar 1 2022
I've been think about what to do with this for a while, and I have to say, it's a hard one.
Aug 17 2021
Jul 23 2021
It is a step forward, but considering how the URL could be factorized would be a plus, IMO.
Jul 13 2021
Jul 12 2021
I sent @ toward 18.104.22.168 too.
Jul 9 2021
Are we supposed to make a similar lengthy statement?
Jul 7 2021
Jul 6 2021
- Fix error mssage in HarbormasterCircleCIBuildStepImplementation
- Add some comments explaining what's up in HarbormasterExternalBuildableInterface
Thanks for the review @speck , I'll rebase this and update.
Jul 2 2021
Jun 30 2021
The vision statement really is fantastic.
Jun 28 2021
Jun 27 2021
Jun 26 2021
Jun 25 2021
So I setup an instance and a dummy project with CircleCI integration.
Jun 24 2021
Great! Thanks @Matthew .
@speck What you have here seems reasonable to me. Can you propose this upstream and see how it goes?
How many of them are there? Eyeballing P2, it's of the order of 500. There are 5 people in this task, we can do 15/day and be done in a week. That doesn't sound intractable if we are all willing to chip in.
Jun 23 2021
Do lint and fix error raised by the linter
A few things on here.
Jun 22 2021
I would like to note that France has what the local law calls association loi 1901, which is very advantageous for a open source projects. In short it is an entity that can own stuff, accept donation, but cannot do for profit operations. Projects such as VLC and ffmpeg are using this. The requirement are very lax (you basically need to have an address somewhere in France for administrative bullshit) and have at least 3 founders. They don't need to be French or live in France, in fact, last time I checked, you could even do one as an illegal emigrant, which I found funny. I had a long chat with Jena Baptiste Kempf who created VLC about this for the last big open source project, but we ended up going for a structure in HK because we had Chinese users and donors and that was easier administratively this way. Chinese special case excluded, this was by far the best option we had.
@chris Option 3: when upgrading an existing instance, and *IF* the storage.default-namespace is not set explicitly, prompt the user.
Jun 21 2021
I see that this has been added to the changelog already here: https://we.phorge.it/w/changelog/2021.25/ . Fantastic!
I landed the code, but leaving the task open because we need to add a release note whenever we know where they go.
I'm going to land this one as to not wait on things that are not sorted out, with the obvious note that a release note would be advantageous.
Jun 20 2021
Jun 19 2021
TBH, I don't think we need to revise it, especially not at this time. It's been working. If we find there are problems with it later down the road, we can revise.
As an asside, you might want to split up the logo rename part of that diff in another diff, this should be able to get in eight away, and there is no reason to wait on a resolution for the translation business to move on with it.
While I'm not super familiar with this setup, it is customary in the node space to commit package-lock.json int he repository. If it is intended to put stuff in there which are not to be committed at all - the folder is a placeholder - then it is best to ignore the whole folder. If committing what's in there is intended, then package-lock.json should be included.
Jun 15 2021
Jun 13 2021
No need to apologize, i wasn't super clear myself, so let me try to make my point in a more cogent manner. The main thing that bothered me with what happen is that our default should be to use the phorge's default (that I happen to find good myself, but it is not super relevant to the point). This comes down to dogfooding. The default configuration is what we are going to put into people's hand. We must ensure this is as good as possible for as many users as possible right out of the bat. This will never happen if the standard phorge install doesn't use the default, because what's out of sight also typically is out of mind.
Jun 12 2021
Jun 11 2021
Also, S1 isn't public, contrary to what the name says, so this effectively just changes the error message at the moment.
This nevertheless regressed the dashboard for everybody vs what was before. I'm sorry but I don't want to be welcome to create my own dashboard with the information I see fit on it, because I had one that was pretty good to begin with. You just broke everybody's dashboard. If it is for logged out users, and you don't want to put it up now, then just park it somewhere.
- differential: default view policy: public
- diffusion: default view policy: public and default push policy; blessed committers
- maniphest: default view policy: public and default edit policy: task author or trusted contributors.
- project: default view policy: public
- paste: default view policy; public
- countdown: default view policy; public
So I edited policy.allow-public and set it to true in the DB.
I'm going to have to be honest here. While this is more appropriate for logged out users, this is a net regression for a regular user.