Omim: [unofficial] This bugtracker is not actively monitored, [email protected] could be used for reporting

[dbf256]

As mentioned here: http://forum.openstreetmap.org/viewtopic.php?pid=595981#p595981, this place is not actively tracked by dev team, so email could be used instead.

[utack]

it used to be, any information what changed?

[dbf256]

utack, in a link from my first message there is a comment from maps.me developer (in russian): "Developers read all email in [email protected] and check github bugtracker very rare ". Recently I reported several bugs here and there are no any comments from maps.me devs, so I decided to create this placeholder bug to save time of other reporters. Once again, I don't work in maps.me so my comments are not an official position of the team.

[burivuh]

Currently the best way to communicate for us is [email protected] as it aggregates several channels and is monitored on a daily basis by our QA team.

[vincentdephily]

I've just sent an email to [email protected] asking them to make github their primary bugtracker, we'll see.

[Zverik]

Alas, we cannot make this the primary bugtracker, since our workflow depends on other tools and services in the intranet. But I've partially solved this issue with a script: from now on all new github issues will be forwarded to [email protected].

[utack]

Thanks for solving this
Should any existing bugs we opened be emailed to [email protected] again or did you run the script for all existing bugs too?

[Zverik]

I plan to categorize the existing issues in a week or so, and then share the result with the development team.

[vincentdephily]

Thanks for working on integrating github with your internal tools. But forwarding issues (and their comments) from github to [email protected] is only half the job : updates must flow the other way too, otherwise [email protected] remains like a blackbox.

[Zverik]

Open source does not mean transparent development. Why do you need to read everything that people report? Do you also want us to open our roadmap, budget, event plan, employee information?

For developers that are considering participating, the already open list of issues is full of reasonably simple to implement features.

[vincentdephily]

IMHO open source _does_ mean transparent development. Not everything needs to be available, but a bugtracker is a key part of the system. Suggesting the sharing of budget, event plan, and employee information must be rhetoric hyperbole on your part, but roadmaps are useful to both users and contributors, and many projects share theirs.

I'm not going to read everything that people report, but I keep close tabs on bugs or feature requests that affect me. Before reporting a bug, I'll search the current issues for duplicates. If a bug has been open for a long time, I want to know if it's being worked on, or if I need to dig into the code myself (hopefully the bug discussion has some pointers). Etc.

Bug triaging is real work, help us help you. If posting issues on github is just another way to email b@mm, you're missing out on what the community can give you, and you're not getting the full benefit of open source.

[matkoniecz]

Open source does not mean transparent development. Why do you need to read everything that people report? Do you also want us to open our roadmap, budget, event plan, employee information?

Is budget, event plan and employee information really kept on the bug tracker?

[richlv]

@burivuh is reacting on issues very timely - is all good here, can this issue be closed ?