2011/2/13 Bryan Tong Minh bryan.tongm...@gmail.com:
This has gotten better lately, WMF created a bugmeister position and
the bugmeister tries to respond to most if not all bugs after being
reported. We should definitely keep up with this and try to at least
confirm every problem that is being
On 13/02/11 11:54, Roan Kattouw wrote:
Bugzilla patches are another matter, yes, but I think making sure
patches get reviewed can be a Bugmeister task. We get relatively few
patches through Bugzilla these days anyway.
Maybe once 1.17 is released, we should focus on the bugzilla patch queue
Maybe we can make the bugathon part of the Berlin hackaton?
On Sun, Feb 13, 2011 at 4:03 PM, Ashar Voultoiz hashar+...@free.fr wrote:
On 13/02/11 11:54, Roan Kattouw wrote:
Bugzilla patches are another matter, yes, but I think making sure
patches get reviewed can be a Bugmeister task. We
These have been circulating in the open source Twitterspere today.
They struck me as apposite to discussions on these topics around
MediaWiki.
How to write a roadmap:
http://blogs.gnome.org/bolsh/2011/02/07/drawing-up-a-roadmap/
How to grow your contributor community (and how to decimate it):
On Samstag, 12. Februar 2011 at 17:55, David Gerard wrote:
How to grow your contributor community (and how to decimate it):
http://www.codesimplicity.com/post/open-source-community-simplified/
and imo, wikimedia fails at a lot of these points:
*Quote: Respond to contributions immediately.
For the last months I have been going through Bugzilla and what strikes me
is that we are not using it as efficiently as other communities do. In
particular, there is little follow up to reported problems (as Leo mentioned
as well). On the short term, I think we can have a bugathon to clean up
Have a bugathon where we label a lot of bugs as appropriate bugathon bugs
that need either:
a) test patch / update patch to recent svn version
a) confirmation / replication of new / unconfirmed bugs
We can provide a simple ready to go Wiki installation for people to use for
bug triaging and
I think one way that non technical people can help is by trying to replicate
bugs, if they follow the steps as described in the bugreport Do you get the
same malfunction or not. That would be a great help as it weeds out invalid
bugreports
Sent from my iPhone
On 2011-02-12, at 17:26, phoebe
On Sat, Feb 12, 2011 at 1:11 PM, Ryan Lane rlan...@gmail.com wrote:
Have a bugathon where we label a lot of bugs as appropriate bugathon bugs
that need either:
a) test patch / update patch to recent svn version
a) confirmation / replication of new / unconfirmed bugs
We can provide a simple
On Sat, Feb 12, 2011 at 9:41 PM, Leo diebu...@gmail.com wrote:
*Quote: Respond to contributions immediately.
This is what I think bugs me the most. There are heaps of bugs which have had
patches attached for month or years. For newcomers, who maybe spent a lot of
time on these, it's just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In article AANLkTi=nq2tookvgmhrxbegvr6fzxe1wzv9dbzde4...@mail.gmail.com,
Ryan Lane rlan...@gmail.com wrote:
Have a bugathon where we label a lot of bugs as appropriate bugathon bugs
that need either:
a) test patch / update patch to recent svn
I believe the next hack-a-ton is in Berlin, soon.
Perhaps requiring people to travel to another country to participate in
this is part of the problem. I don't doubt that real-life meetings are
useful for Wikimedia Foundation employees and existing MW contributors,
but it doesn't do much to
Leo diebu...@gmail.com writes:
*Quote: Respond to contributions immediately.
This is what I think bugs me the most. There are heaps of bugs which
have had patches attached for month or years. For newcomers, who maybe
spent a lot of time on these, it's just rude to neither commit them
nor
13 matches
Mail list logo
