JanZerebecki added a comment.
In https://phabricator.wikimedia.org/T74907#1483021, @Tpt wrote:
But I believe that if we move some of these libs out of GitHub we will maybe
miss contributions of external users that may use this libs for other use
cases than Wikibase itself and that may be
Tpt added a comment.
I am myself not against a move of all these libs to Gerrit or Phabricator as I
already have to use these tools. But I believe that if we move some of these
libs out of GitHub we will maybe miss contributions of external users that may
use this libs for other use cases than
JeroenDeDauw added a comment.
I strongly dislike moving all repositories used by Wikidata to Gerrit. The same
goes for any such general policy, such as forcing people to use a particular OS
or IDE. If the people that contribute to a repository most want to have it at a
given location, than let
JanZerebecki added a comment.
We had a discussion about this:
Decision:
- We will gradually move our repositories to gerrit.
- We will start with WikimediaBadges and Wikidata.org
- We are OK with loosing the feature of coverage before merge, but want to
implement it in Wikimedia CI afterwards.
mmodell added a comment.
In https://phabricator.wikimedia.org/T74907#1218316, @mmodell wrote:
Last time I checked, arcanist/differential do not have any have explicit
support for chains of dependent patches.
I was wrong, it does have dependencies now. One differential revision can
depend
Addshore added a subscriber: Addshore.
Addshore added a comment.
Well something that might be interesting (from the phab site)
Phabricator can host Git, Mercurial and Subversion repositories. It also
works well with existing repositories (like GitHub, Bitbucket, or other
repositories you
mmodell added a comment.
In https://phabricator.wikimedia.org/T74907#1109504, @thiemowmde wrote:
Erm, not what I meant. Will Phabricator support chains of patches and if it
does, how?
In https://phabricator.wikimedia.org/T74907#1109505, @Qgil wrote:
@mmodell, @chasemp, please check
JanZerebecki added a comment.
That is a good idea as those two are not registered at packagist.org so for
them the blocker task is not one.
TASK DETAIL
https://phabricator.wikimedia.org/T74907
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or
aude added a comment.
WikimediaBadges and Wikidata.org would be good to start with and can't imagine
objections to moving those. I would also like PropertySuggester in gerrit.
we haven't yet converted the PropertySuggester's api module to use i18n, but
should do that soon. and then how do we
thiemowmde added a comment.
@Qgil, how will the chain aspect mentioned above work then? How to submit a
patch to Phabricator that depends on an other patch that's still in review?
TASK DETAIL
https://phabricator.wikimedia.org/T74907
REPLY HANDLER ACTIONS
Reply to comment or attach files,
thiemowmde added a comment.
I just wrote this as an email to wikimedia-de-tech. As a reference:
GitHub does have two major problems:
1. It's not possible to add people for review. There is no review board. You
can ping people via email, which usually gets lost. You can assign one person,
thiemowmde added a comment.
Erm, not what I meant. Will Phabricator support chains of patches and if it
does, how?
TASK DETAIL
https://phabricator.wikimedia.org/T74907
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL
Qgil added a comment.
Clearly, there is no chain unless everything is either in Gerrit or in
Phabricator.
TASK DETAIL
https://phabricator.wikimedia.org/T74907
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
Legoktm added a comment.
How about we start small and begin with the Wikidata.org and WikimediaBadges
extensions that are currently packaged in the Wikidata build:
- https://github.com/wmde/WikimediaBadges
- https://github.com/wmde/Wikidata.org
Both would benefit from being on gerrit and being
JeroenDeDauw added a comment.
Thank you Dereckson for writing down your concerns and observations, I share
many of them. I do not expect constructive discussion to happen here, and just
get one-sided repeats of arguments already covered in the past. If we want to
improve things, then IMO we
JanZerebecki added a comment.
Could you list your concrete pain points?
TASK DETAIL
https://phabricator.wikimedia.org/T74907
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
Tobi_WMDE_SW added a comment.
Some additional discussion is happening on wikidata-l:
https://lists.wikimedia.org/pipermail/wikidata-l/2015-February/005421.html
TASK DETAIL
https://phabricator.wikimedia.org/T74907
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim,
17 matches
Mail list logo
