User content is also content, thus yes.

Good question. Maybe also related to L2.

Is it assumed that using the site will automatically license the user’s content under these, or should there be a line for that?

In T15322#15031, @aklapper wrote:

+1 on Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses.

Values given in em units may produce unexpected results...

Yes. I think we should wait for a kind Administrator to implement the first one.

@aklapper @valerio.bozzolan See D25520.

BTW I like the proposed screenshot. So I also agree to: feel free to share the solution 👍

My fix would work with this css class

I did not realize you had a fix. Please share it. :)

In T15715#15174, @aklapper wrote:

I guess you could get the result that you're looking for by editing the file webroot/rsrc/css/aphront/typeahead.css and removing the line white-space: nowrap; from the definition of div.jx-typeahead-results a.jx-result. I just don't know which side effects this may have in other places...

I guess you could get the result that you're looking for by editing the file webroot/rsrc/css/aphront/typeahead.css and removing the line white-space: nowrap; from the definition of div.jx-typeahead-results a.jx-result. I just don't know which side effects this may have in other places...

Also for Archived Projects, and maybe some other objects.
I'm not sure if there's a generic way to do this, or if each search-engine needs to be updated manually.

+1 on Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses.

Completely agree on lowering their ranking as default

Since I can, thanks to that revision, at work I've put this additional CSS rule for extra nonsense scary climax.

Here's another one that I think deserves to be upstreamed: https://phabricator.wikimedia.org/T230787 adds context and search term highlights to fulltext search results. Currently Phorge and upstream Phabricator only show matching document titles with highlights on keywords in the title but not the body.
The efficiency of my solution is questionable, however, it's working well enough for Wikimedia's use of the feature.

there is a presentation from eric brechner, who was in microsofts xbox development, about kanban. he does it on whiteboard, extremely sinple:
https://www.youtube.com/watch?v=CD0y-aU1sXo

From a product POV, I agree with @valerio.bozzolan - there is (sometimes) some information on commits that would be nice to index in a search engine - comments, mostly.

Valerio: Uhm, I'm sorry, I had not seen your comment here before I landed the patch (as I had checked my Differential page instead of my notifications).

This is something that may be not appreciated by some people.

One of my favourite updates in my workplace was to store counts of feature usage per month in a table. Move forward 3 years, and whenever we need to update some code in a feature, we check for it in the table, and if it's not been used in 3 years we just scrap the feature.

I triage this to Wishlist since it's indeed useful to some people but it's somehow still controversial. In order to attract more eyes, adding also Discussion Needed.

Thanks but I don't know where that typo is, so, feel free to fix

See e.g. https://www.law.cornell.edu/wex/release why to "license under" instead of "release in"

I don't remember but that was an attempt to do not release Passphrase credentials as CC BY-SA 4.0 :D :D

Public contents are released in Creative Commons Attribution-ShareAlike 4.0.

Updated to reflect some tips from comments. Also added some "Pro / Cons"

+1 for CC BY-SA 4.0 International for content (text, images, etc) and Apache 2.0 for code.

Content is not in something, rather it's licensed under.

Thanks @aklapper, feel free to edit the Task description according to your proposal.

Public contents are in Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) and Apache 2.0 unless otherwise noted.

In T15322#11590, @valerio.bozzolan wrote:

This would also help Wikimedia volunteers to upload screenshots of Phorge to Wikimedia Commons, avoiding annoying deletion procedures for the lack of the license in the very same page etc.

Would taking care of the depreciations bump the minimum PHP version required to run Phorge?

Not in itself, but we do plan to bump the minimum to 7.1 (in T15047).

Would taking care of the depreciations bump the minimum PHP version required to run Phorge?
looks good to me otherwise

@ncoker See T15586 instead

thank you @ncoker, but:

1. This is not a task to discuss specific errors when trying to run on php 8, and
2. We don't expect arcanist to work on php 8 yet

Maybe also something for this topic!
We update php yesterday on our WSL2 (Ubuntu 22.04) clients to 8.1.22 and pulled the latest arcanist from git after the commit
Now we facing this problem on starting arcanist:

D25386 and D25387 provide the big "do not crash on deprecation warning", and are probably enough to declare "experimental support for php 8.2" on their own.

I was thinking "out out", but only visible to admins - and then, only as a yellow notice at the top of the page:

This is a good plan. Would this be opt-in, e.g. this Phorge instance would be the main one with this on but other installs wouldn’t see this by default?

Another problem dramatically frequent for newcomers (at least in my office).

(Implementation notice: in both phorge and arc, this is handled in PhutilErrorHandler::handleError(), and the check is simply $num === E_DEPRECATED), and maybe E_USER_DEPRECATED.

+1

I agree that Phorge should not fall over because of a deprecation warning.

I've extracted T15535: Using Differential with plain Git, without requiring Arc for the git-push-for-revision.

In T15096#11546, @avivey wrote:

Interesting.... Herald could probably start the flow, but there's still more parts needed (update vs create revision, extract summary and test plan)

( The CLA → https://secure.phabricator.com/L28 )

If it's urgent, we can apply a strict CLA now (basically copy Phacility), and soften it later, once we've had legal counsel.

Has anyone experimented with using arcanist in a docker container? I see two people have published these on dockerhub:

• https://hub.docker.com/r/nasqueron/arcanist
• https://hub.docker.com/r/adlogix/arcanist

It's all a matter of risks after all. Keeping everything as-is ("all rights reserved") just increases risks for every contributor, including Administrators.

yeah, well, we still can't afford legal advice. If some funded organization is willing to donate some, we'll appreciate it.

At the moment, if somebody makes a comment in the website with a creative snippet, that is "all rights reserved" from that author. Same on Differential, since volatile patches can be somehow considered as out of the repository.

@valerio.bozzolan I think you're confusing this task ("website content") and T15121 (contributor agreement).

Since I am not currently authorized to make changes on other people's code from comments or Differential and I don't want to be vulnerable to copyright trolling.

Interesting.... Herald could probably start the flow, but there's still more parts needed (update vs create revision, extract summary and test plan), and it technically can't delete the branch (it can prevent it from being created, but that shows up as an error in the user-side).
But it should be able to at least trigger the flow and provide a URL for the user to click on.

Could this be solved with a Herald action?

I suspect there's also a problem of motivation: These things are lots of work, and the people who are capable of performing them - people who are comfortable with working with these tools - will not personally benefit from this stuff. The people who would benefit the most are people who are not involved in the project at all...

Uhm. Have we any idea about how to unlock this situation?

I think the current actionable steps we can take are:

I posted this in a separate thread, but it is definitely related: https://we.phorge.it/T15524

How would we as phorge upstream use the info? Would it inform development? Be just informational?

How would we as phorge upstream use the info? Would it inform development? Be just informational?