Le 02/12/2014 23:55, Chad a écrit :
Yes, the repo will also have a path for cloning (at a later time) and
a name (which is arbitrary and can be changed by repo owners
whenever they want).
Great, that works for me so :-]
--
Antoine hashar Musso
On Tue Dec 02 2014 at 2:23:49 PM James Forrester jforres...@wikimedia.org
wrote:
On 2 December 2014 at 13:51, Chad innocentkil...@gmail.com wrote:
So I'm thinking people are liking where we've ended up on callsigns...at
least I haven't seen any major objections in the last day or so.
Do
On 2 December 2014 at 13:51, Chad innocentkil...@gmail.com wrote:
So I'm thinking people are liking where we've ended up on callsigns...at
least I haven't seen any major objections in the last day or so.
Do we have a rough consensus? If so, could we move Merlijn's table
over the messy
Le 02/12/2014 22:51, Chad a écrit :
Do we have a rough consensus? If so, could we move Merlijn's table
over the messy original one and update the guidelines to match the
new plan? Once that's done I'd be glad to close out T1314 and we can
start importing repositories.
I have a last minute
On Tue Dec 02 2014 at 2:25:20 PM Antoine Musso hashar+...@free.fr wrote:
Le 02/12/2014 22:51, Chad a écrit :
Do we have a rough consensus? If so, could we move Merlijn's table
over the messy original one and update the guidelines to match the
new plan? Once that's done I'd be glad to close
Brad Jorsch (Anomie) wrote:
I can't find documentation anywhere for what's valid in callsigns besides
uppercase, but seeing feature requests for stuff like Allow digits in
callsigns and allow hyphens in callsigns I'm suspecting the character
set is literally [A-Z]. Which means a lot of the
On Thu, Nov 27, 2014 at 3:02 PM, Merlijn van Deen valhall...@arctus.nl
wrote:
I've fiddled a bit with this in the style of tail numbers / actual
radio call signa: first letter is a category (country in a call sign),
the rest is assigned as a number, unless someone wants a specific one.
The
On Sat, Nov 29, 2014 at 6:26 PM, Merlijn van Deen valhall...@arctus.nl
wrote:
- The G-prefix has on major advantage: it keeps the 'root namespace'
(i.e. the first letter) clean: at the moment only A C E G L M O P S W
are in use, so adding another prefix 'B' is easy. If we already have
On 27 Nov 2014, at 20:02, Merlijn van Deen valhall...@arctus.nl wrote:
On 26 November 2014 at 23:29, MZMcBride z...@mzmcbride.com wrote:
If we're stuck with using callsigns, the idea of using the shortest
possible strings (a four-character hash?) appeals to me.
If
particular repos want
On Mon Dec 01 2014 at 8:28:50 PM Krinkle krinklem...@gmail.com wrote:
On 27 Nov 2014, at 20:02, Merlijn van Deen valhall...@arctus.nl wrote:
On 26 November 2014 at 23:29, MZMcBride z...@mzmcbride.com wrote:
If we're stuck with using callsigns, the idea of using the shortest
possible
On Fri, Nov 28, 2014 at 6:15 PM, MZMcBride z...@mzmcbride.com wrote:
Chad wrote:
On Fri Nov 28 2014 at 2:41:00 PM Bartosz Dziewoński matma@gmail.com
wrote:
On Thu, 27 Nov 2014 21:02:39 +0100, Merlijn van Deen
valhall...@arctus.nl wrote (roughly):
On Fri Nov 28 2014 at 6:15:44 PM MZMcBride z...@mzmcbride.com wrote:
Chad wrote:
On Fri Nov 28 2014 at 2:41:00 PM Bartosz Dziewoński matma@gmail.com
wrote:
On Thu, 27 Nov 2014 21:02:39 +0100, Merlijn van Deen
valhall...@arctus.nl wrote (roughly):
On Sat, 29 Nov 2014 17:51:11 +0100, Chad innocentkil...@gmail.com wrote:
The only exception I'd make is MediaWiki. Under this
scheme the callsign is MWMW. MediaWiki should be
just plain MW.
Feels slippery. Next thing you know, someone will want VE and SMW. :)
--
Bartosz Dziewoński
On 29 November 2014 at 09:13, Bartosz Dziewoński matma@gmail.com
wrote:
On Sat, 29 Nov 2014 17:51:11 +0100, Chad innocentkil...@gmail.com wrote:
The only exception I'd make is MediaWiki. Under this
scheme the callsign is MWMW. MediaWiki should be
just plain MW.
Feels slippery. Next
On the talk page I suggested dropping the G prefix for top-level
repos, and just giving them an unprefixed callsign. I think that would
fix the ugliness of some of the frequently used names.
On Sat, 29 Nov 2014 17:51:11 +0100, Chad innocentkil...@gmail.com wrote:
The only exception I'd make
On Nov 29, 2014 1:58 PM, Legoktm legoktm.wikipe...@gmail.com wrote:
On the talk page I suggested dropping the G prefix for top-level
repos, and just giving them an unprefixed callsign. I think that would
fix the ugliness of some of the frequently used names.
On Sat, 29 Nov 2014 17:51:11
Three short notes:
- The G-prefix has on major advantage: it keeps the 'root namespace'
(i.e. the first letter) clean: at the moment only A C E G L M O P S W
are in use, so adding another prefix 'B' is easy. If we already have
repositories that start with a B, it's more confusing.
- Being a
On Thu, 27 Nov 2014 21:02:39 +0100, Merlijn van Deen
valhall...@arctus.nl wrote:
I've fiddled a bit with this in the style of tail numbers / actual
radio call signa: first letter is a category (country in a call sign),
the rest is assigned as a number, unless someone wants a specific one.
On Fri Nov 28 2014 at 2:41:00 PM Bartosz Dziewoński matma@gmail.com
wrote:
On Thu, 27 Nov 2014 21:02:39 +0100, Merlijn van Deen
valhall...@arctus.nl wrote:
I've fiddled a bit with this in the style of tail numbers / actual
radio call signa: first letter is a category (country in a call
Chad wrote:
On Fri Nov 28 2014 at 2:41:00 PM Bartosz Dziewoński matma@gmail.com
wrote:
On Thu, 27 Nov 2014 21:02:39 +0100, Merlijn van Deen
valhall...@arctus.nl wrote (roughly):
https://www.mediawiki.org/wiki/Special:Permalink/1287943
I definitely like this proposal a lot more than the
On 26 November 2014 at 23:29, MZMcBride z...@mzmcbride.com wrote:
If we're stuck with using callsigns, the idea of using the shortest
possible strings (a four-character hash?) appeals to me.
If
particular repos want specific available hashes (, ), I'm fine
with allocating on a
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
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
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 gil...@wikimedia.org wrote:
Is there a length
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).
I think that is a bit sad. Not tearing of cloths or gnashing of teeth sad.
Maybe stare whistfully into the sunset and think of what could have been
bad.
I'd prefer not to have them but I ultimately don't care that much. It does
provide a fun bikeshedding opportunity I guess.
Nik
On Nov 26, 2014
On Tue, Nov 25, 2014 at 9:45 PM, James Forrester jforres...@wikimedia.org
wrote:
and in particular the plan for what we'll call the existing repos
https://www.mediawiki.org/wiki/Phabricator/Diffusion/Callsign_naming_conventions/Existing_repositories
I can't find documentation anywhere for
On Wed Nov 26 2014 at 7:27:20 AM Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
On Tue, Nov 25, 2014 at 9:45 PM, James Forrester jforres...@wikimedia.org
wrote:
and in particular the plan for what we'll call the existing repos
https://www.mediawiki.org/wiki/Phabricator/Diffusion/
Hi,
On Thu, 27 Nov 2014, at 02:26, Brad Jorsch (Anomie) wrote:
[...]
If we can't -2 the whole idea of required callsigns,
Why can't we?
--
svetlana
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Wed Nov 26 2014 at 1:22:59 PM svetlana svetl...@fastmail.com.au wrote:
Hi,
On Thu, 27 Nov 2014, at 02:26, Brad Jorsch (Anomie) wrote:
[...]
If we can't -2 the whole idea of required callsigns,
Why can't we?
Because Phabricator requires them for all repositories as a
unique
Chad wrote:
On Wed Nov 26 2014 at 1:22:59 PM svetlana svetl...@fastmail.com.au
wrote:
On Thu, 27 Nov 2014, at 02:26, Brad Jorsch (Anomie) wrote:
[...]
If we can't -2 the whole idea of required callsigns,
Why can't we?
Because Phabricator requires them for all repositories as a
unique
Sadly this is carved from the fires of Mt Doom.
-Chad
On Wed, Nov 26, 2014, 2:30 PM MZMcBride z...@mzmcbride.com wrote:
Chad wrote:
On Wed Nov 26 2014 at 1:22:59 PM svetlana svetl...@fastmail.com.au
wrote:
On Thu, 27 Nov 2014, at 02:26, Brad Jorsch (Anomie) wrote:
[...]
If we can't
Hello all,
*TL;DR*: Reminder to please bike-shed at
[[mw:Phabricator/Diffusion/Callsign_naming_conventions]]
https://www.mediawiki.org/wiki/Phabricator/Diffusion/Callsign_naming_conventions
before
December.
Just when you thought it was safe, there's the next stage in our migration
of developer
James Forrester wrote:
We need to agree how we are going to name our repos, and much more
importantly because it can't change, what their callsign is. These will
be at the heart of e-mails, IRC notifications and git logs for a long
time, so it's important to get this right rather than regret it
No we can't not.
-Chad
On Tue, Nov 25, 2014, 9:11 PM MZMcBride z...@mzmcbride.com wrote:
James Forrester wrote:
We need to agree how we are going to name our repos, and much more
importantly because it can't change, what their callsign is. These will
be at the heart of e-mails, IRC
35 matches
Mail list logo
