Also me, in projects related to Wikimedia Phabricator:
While I wish again to give all my support to the author and be friendly with this difficult topic, I do not sincerely believe that striking "closed source" would better describe the official statement, which is "I have no plans to release the source code".
Grazie! 🏆
Marking this as "waiting for approval", as I've submitted 13 proposals though the form, but now I guess I must wait something.
Uh. I noticed that I can propose myself a capacity from the web UI from this page:
Well, let's remove Phorge from the list.
FabLab Messina is online!
It's alive!
I've shared another comment as I believe that maybe the author was not aware of the right to fork or maybe needs an help to use git.
lol
I was trying to describe the situation using only Free licensed images, but it was difficult to find a compass suitable for background purposes. Now this category exists:
Maybe relevant: today, on Meta, I've done section editing using the "[edit source]" link and it resulted in an undesired added newline after pressing "Publish changes":
a2ensite itwikicon.2026 apache2ctl graceful certbot certonly --webroot --webroot-path=/var/www/html -d 2026.itwikicon.org apache2ctl graceful
DNS deployed.
(@Ladsgroup Maybe last file F101159597 is private)
I was browsing this Puppet page: https://gerrit.wikimedia.org/g/operations/puppet/+/production/modules/phabricator/data/fixed_settings.yaml#200 and there was a link leading here.
As I see the thing could really means one dollar,
I mean, I was* going to rollback. Now I'm stalled trying to understand if you want to keep it here and why.
You may then argue that the red bell is too much scaring. That could be improved too in my opinion https://we.phorge.it/T16754
Ah. lol. I was sure the Bulk Editor was able to move columns, but it can't 🥶 Here current situation, as memo:
Do you propose a wontfix? That's fine for me
Hello :) I was spawned here from the kind code patch from aklapper, but I failed in understanding why moving tasks is not sufficient for this workflow. One step back:
Nice, thanks. Anyway, this is the classic "somebody should do something" situation, as anybody in the world could try to improve the source code:
Not implemented during the hackathon :3 maybe next one
I shared the above comment in the assumption that current server limits were selected to consume less resources, but if I'm wrong and if somebody is telling me that the server actually consumes less resources by specifying bigger limits, then I wonder why we have such small default limits 🤯 I'm interested in such discussion.
The workround is also a performance optimization
🤩
P.S. I'm in medical permission this week, and I was in permission also the previous 3 weeks. I'm sorry for this unfortunate delay. I come back next Monday and this has mac priority.
Credo ci sia ancora da creare una "issue" sul tema dei tag:
For historical records, currently the BotCancellazioni has 2148363 edits.
I've updated the bot to use your Lua feature:
Related commit: