Hi,
I would like to change basic packaging from that random mess we have
to CPack: http://www.cmake.org/Wiki/CMake:Packaging_With_CPack
This would make it super easy to package huggle on any platform,
especially on Mac properly, with all dependencies so that it works to
every user.
Is there someone who knows this, or can help?
Hi,
I just released huggle 3.1.6, have fun.
This version contains a number of major changes, including update of
Qt libs for windows and fully working extension system. It may not
work as no beta tester responded to beta version I released earlier.
So if it doesn't, don't blame me :P
Thank you all who worked on it
Hi,
I created a windows installer for 3.1.6, you can find it at
http://tools.wmflabs.org/huggle/files/huggle_beta_3.1.6.exe
Please test it, especially if both plugins work. Linux and MacOS users
should be able to install these using --extension option for configure
script.
Hi Andre,
Sorry i didn't have much time, is there still time for us? So far I
got only few categories of easy tasks, which on other hand are really
easy, so maybe not even suitable (they don't really require much
thinking). These are:
Localization in source code - find elements which have hardcoded
english and implement localization macros on them, so that they are
retrieved by key from xml files (basically replacing hardcoded strings
with some C++ code) this can be more complicated for gui elements,
where new functions may need to be created, but it's still very
trivial task, that requires beginner c++ knowledge.
Update of deprecated code - we have some nice functions, that could be
used on many places, so basically rewriting some parts of code
utilizing them.
Update of deprecated API calls - some MW api's were deprecated in
recent days, queries used in huggle need to be updated.
I believe all these categories are suitable for newbie programmers,
but I don't really know if it's kind of tasks you would like to have
at code in. What do you think? Should I create bugs for these?
If someone has an idea for other easy tasks, let me know.
P.S. I have a number of harder tasks as well, but these may require
deep knowledge of C and C++.
On Fri, Nov 7, 2014 at 2:25 PM, Andre Klapper <aklapper(a)wikimedia.org> wrote:
> On Fri, 2014-11-07 at 13:22 +0100, Petr Bena wrote:
>> This is a good idea, I will try to get some easy tasks and will list
>> myself there. Thanks
>
> That's awesome, thank you, Petr! Plus we'll have another interesting
> programming language in the mix!
>
> Feel free to drop your rough ideas on
> https://www.mediawiki.org/wiki/Google_Code-in_2014#Proposed_tasks
> (as Google will take a look at that list on Monday).
> We can still polish them until Dec 01st when Code-In starts.
> Also, it probably makes sense to have a Huggle section under
> https://www.mediawiki.org/wiki/Google_Code-in_2014#Common_instructions_for_…
> with general information and links (where to find the code, how to
> compile, etc).
>
> Cheers & thanks!
> andre
> --
> Andre Klapper | Wikimedia Bugwrangler
> http://blogs.gnome.org/aklapper/
>
Hey folks,
I posted to this list in August with an idea for a generalized revision
quality classification service. Well, I have been hard at work writing
code[1] and organizing a project[2]. Today, I'd like to call your
attention to a grant proposal to fund some work on the project. See
https://meta.wikimedia.org/wiki/Grants:IEG/Revision_scoring_as_a_service
*TL;DR: *You should be able to request
http://revscores.wmflabs.org/enwiki?rev_id=4567893 and get back {"text_svm":
{"damage": 0.65273, "good-faith": 0.74527}} This service could be used in
tools like Huggle and vandal bots to flag edits that are likely to be
damaging.
Please review the proposal and endorse it if you see fit. I'd also
appreciate if anyone on this list would be able to spare the time to advise
us and work with us on developing formats/standards that will be generally
useful.
1. https://github.com/halfak/Revision-Scoring
2. https://meta.wikimedia.org/wiki/Research:Revision_scoring_as_a_service
Thanks!
-Aaron
Ahoj Petr,
On Thu, 2014-09-25 at 09:05 +0000, Petr Bena wrote:
> Bugzilla is going to be shut down
> --------------------------------------------------------
>
> Unfortunately, my favorite BT is going to be replaced with
> phabricator, it will happen soonish and for 3 days we are going to be
> without a bug tracker, you can use the tracker we have on github in
> case you needed to report any issues meanwhile.
>
> I will give you more information as soon as I get more information :)
> I can't really get much out of Andre regarding how the migration is
> going to work.
You might want to consider contacting me if you'd like to get something
out of me? :)
Please do ask all the things which feel unclear to you, preferably on
https://www.mediawiki.org/wiki/Talk:Phabricator
And in general, there's some information that can be found on
https://www.mediawiki.org/wiki/Phabricator - but it's work in progress
and we are very happy to improve it based on feedback!
Cheers,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Hi folks,
There are 2 things I want to tell you:
Bugzilla is going to be shut down
--------------------------------------------------------
Unfortunately, my favorite BT is going to be replaced with
phabricator, it will happen soonish and for 3 days we are going to be
without a bug tracker, you can use the tracker we have on github in
case you needed to report any issues meanwhile.
I will give you more information as soon as I get more information :)
I can't really get much out of Andre regarding how the migration is
going to work.
3.1.4 release
-------------------------
I would like to release 3.1.4 soon but there is a number of HEAVY
changes, which should be beta tested. So do that please :) thanks