BTW, I gather from examples on the page like "wikimedia-roadmap-updater" that we're doing away with subpaths in the git clone url ?
I just want to make sure that people are aware that using the "Clone/Checkout As" option allows you to specify whatever you want, including paths (I use this myself).
So, both of these are possible: git clone ssh:// git@phabricator.wikimedia.org/diffusion/CALLSIGN/wikimedia-roadmap-updater.git git clone ssh:// git@phabricator.wikimedia.org/diffusion/CALLSIGN/wikimedia/roadmap-updater.git
Respectively resulting in the directories: wikimedia-roadmap-updater.git roadmap-updater.git
I just wanted to make sure that people were aware of that, it's an interesting way to namespace on url, but not on checkout directory.
DJ
On Wed, Nov 26, 2014 at 12:07 PM, Derk-Jan Hartman < d.j.hartman+wmf_ml@gmail.com> wrote:
Yes they are tied together.
There are some really good explanations about the reasons and history of phab callsigns in https://secure.phabricator.com/T4245 I'm not a big fan of them either....
DJ
On Wed, Nov 26, 2014 at 10:51 AM, Gilles Dubuc gilles@wikimedia.org wrote:
Is there a length limit to call signs? I imagine that the answer is yes, at least in terms of how hashes are displayed on that page, I would imagine that anything above 11 characters would make the shortened display of hashes unusable.
I'm personally not a fan of abbreviations like "VE" to begin with, although I do unfortunately use them sometimes in public content like commit messages. They're alienating to casual code contributors who should be dealing with unified naming for a given component and shouldn't need to learn our insider jargon. If the extension is called VisualEditor, so should the rest. For example in the diffusion page you've linked to, the fact that the URL is /VE/ is a bad idea, imho. I understand the challenge for hash display, but there's no reason to make the URL shorter. Are the two tied together in Phabricator? I.e. does the callsign define the diffusion URL?
On Wed, Nov 26, 2014 at 9:10 AM, Antoine Musso hashar+wmf@free.fr wrote:
Le 26/11/2014 03:45, James Forrester a écrit :
A handful of repos are so important and high-profile that we can use
an
acronym without too much worry, like "MW" for MediaWiki or "VE" for VisualEditor.
What is the point of opening a discussion if some people already rushed/enforced their decisions ?
For the rest, we need to make sure we've got a good enough name that won't cause inconveniences or confusion, and doesn't repeat
the
mistakes we've identified over time. We've learnt since the SVN to git migration a few years ago that calling your repository "/core" is a
bad
plan, for instance.
{in your opinion}, I think `/core` is just fine.
[[mw:Phabricator/Diffusion/Callsign_naming_conventions]] <
https://www.mediawiki.org/wiki/Phabricator/Diffusion/Callsign_naming_convent...
Can we take sometime to clean up the repositories, there are a lot of obsolete/abandoned ones that I would love to see disappear or archived somewhere else.
For the Gerrit hierarchy 'integration/*', please have who ever is leading the project to fill a task for the #contint project. Some repos need to be renamed / changed.
-- Antoine "hashar" Musso
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l