One problem is that the necessity to link to a working test environment
does not allow to develop ideas with the community before they are
implemented.
2013/4/9 Amir E. Aharoni amir.ahar...@mail.huji.ac.il
2013/4/9 Steven Walling steven.wall...@gmail.com:
One system that I find a lot of
Those are very good points, both of them. Thanks.
2013/4/9 Matthew Flaschen mflasc...@wikimedia.org
On 04/09/2013 12:18 PM, Denny Vrandečić wrote:
I thought that in order to discuss these design decisions with the
community before hand, telling them on their respective village pump is
On Apr 15, 2013 5:06 PM, Denny Vrandečić denny.vrande...@wikimedia.de
wrote:
One problem is that the necessity to link to a working test environment
does not allow to develop ideas with the community before they are
implemented.
Nobody is asking of you to have a testable with every idea you
On Mon, Apr 15, 2013 at 1:32 PM, Martijn Hoekstra
martijnhoeks...@gmail.com wrote:
In other words, all discussion is welcome, with or without proto, but don't
expect final community buy in before we have been able to toy around with
it.
And even then, some people will ignore the prototype and
On Mon, Apr 15, 2013 at 8:06 PM, Brad Jorsch bjor...@wikimedia.org wrote:
On Mon, Apr 15, 2013 at 1:32 PM, Martijn Hoekstra
martijnhoeks...@gmail.com wrote:
In other words, all discussion is welcome, with or without proto, but
don't
expect final community buy in before we have been able to
Technical changes on the Wikimedia projects can be hairy. We are currently
having a discussion about the Wikidata deployment to the Wikipedias, and
there have been many examples in the past of deployments that raised
discussions.
One of my statements in this discussion is that the a priori
What kind of changes are we talking about here? What exactly falls under
the category of design decisions? Because, for example, my Gerrit change
that converts Special:Userlogin into a FormSpecialPage is a design change
(in the software sense of the word), but the change based on it to add the
On Tuesday, April 9, 2013, Denny Vrandečić wrote:
Technical changes on the Wikimedia projects can be hairy. We are currently
having a discussion about the Wikidata deployment to the Wikipedias, and
there have been many examples in the past of deployments that raised
discussions.
One of my
On Tuesday, April 9, 2013, Tyler Romeo wrote:
What kind of changes are we talking about here? What exactly falls under
the category of design decisions? Because, for example, my Gerrit change
that converts Special:Userlogin into a FormSpecialPage is a design change
(in the software sense of
2013/4/9 Steven Walling steven.wall...@gmail.com:
One system that I find a lot of potential value in is the Wikitech
Ambassadors mailing list. I hope that mailing list grows and can be the
place where we make announcements that should be communicated widely.
Yes, that, but to make it really
On 04/09/2013 12:18 PM, Denny Vrandečić wrote:
I thought that in order to discuss these design decisions with the
community before hand, telling them on their respective village pump is
sufficient. Not so it seems. No single channel would find acceptance to
communicate with the community.
On Tue, Apr 9, 2013 at 9:48 AM, Steven Walling steven.wall...@gmail.comwrote:
On Tuesday, April 9, 2013, Denny Vrandečić wrote:
Technical changes on the Wikimedia projects can be hairy. We are
currently
having a discussion about the Wikidata deployment to the Wikipedias, and
there have
On 04/09/2013 12:57 PM, Amir E. Aharoni wrote:
2013/4/9 Steven Walling steven.wall...@gmail.com:
One system that I find a lot of potential value in is the Wikitech
Ambassadors mailing list. I hope that mailing list grows and can be the
place where we make announcements that should be
13 matches
Mail list logo
