[Owncloud] github issues

[Frank Karlitschek]

Hi Klaas,

thanks for the feedback.
I think it´s clear that we only move to the github issues if it is clearly superior to thebuggenie and all the migration issues are resolved.




On 27.08.2012, at 11:39, Klaas Freitag <freitag at owncloud.com> wrote:

> On 27.08.2012 11:09, Frank Karlitschek wrote:
>> That´s really awesome!!
> Yes, awesome, thanks for investigating.
> 
> But, honestly, I think thats only the half way.
> 
> Issues:
> - All links to bugs are dead from now on. That is critical imo. Could you please come up with a mapping database that redirects on bugs.o.o to the according links on github issues?
> - All comments are done by you. Not critical, but also not nice.
> - It is still possible to file bugs on bugs.owncloud.org, no hint about new bugtracking.
> - There was no communication yet to community members
>  * that we do this move
>  * what that means
>  * how we continue from here
> 
> Features of the new bugtracker:
> I don't even have permission to close a bug, so the following questions might become obsolete once I have the correct permissions, but:
> - Can we assign bugs to developers?
> - Can we set a NEEDINFO state?
> - Can we have a "How to reproduce" field?
> - Can we have more data like versions, categories and such?
> - Is there a bug workflow which we will need such as "NEW -> ASSIGNED -> CLOSED -> VERIFIED -> RELEASED" or similar?
> 
> I guess that can be configured.
> 
> If I may be honest, I am very annoyed by this uncoordinated infrastructure change activity which does not pay off in my (and others) opinion.
> It's not only that we better should care for our product instead of fiddling around with fancy web tools, this is really bad community care: People loose their links, their accounts, no clear hints where to go etc. And that is just because we're not able to fix a bug genie installation.
> 
> Moreover, we didn't have a discussion about this nor any planing. I for example spent a significant amount of time investigation WHY the buggenie performs that bad recently, lost time now.
> 
> For the github move in general: I was saying I don't care at all as long as it does not give me additional work. Now I have to migrate my branches on my own. Hmm :-(
> 
> Klaas
> 
>> On 27.08.2012, at 00:50, Thomas Müller <thomas.mueller at tmit.eu> wrote:
>> 
>>> Hi,
>>> 
>>> I spent some time to write a little script to move the issues from bug genie over to github.
>>> 
>>> The results can be seen here:
>>> https://github.com/DeepDiver1975/oc-issue-import/issues
>>> 
>>> The four labels core, apps, mirall and android represent the repos where the issues will be created.
>>> 
>>> Everybody (being member of the ownCloud organization in github) who had assigned tickets in bug genie
>>> will get the tickets assigned in github as well.
>>> 
>>> Feel free to surf through the issues on github and let me know if any valuable information got lost.
>>> 
>>> Take care,
>>> 
>>> Tom aka DeepDiver
>>> 
>>> 
>>> 
>>> Am Sonntag, dem 26.08.2012 um 17:37 schrieb Frank Karlitschek:
>>>> Hi,
>>>> 
>>>> I deactivated the github issues for now. At the moment we still use thebuggenie and it is confusing to have bugs on two places.
>>>> It we manage to migrate our data over and also make sure that it can be exported again than we enable this again.
>>>> 
>>>> I hope this makes sense for everybody.
>>>> 
>>>> 
>>>> Frank
>>>> _______________________________________________
>>>> Owncloud mailing list
>>>> Owncloud at kde.org
>>>> https://mail.kde.org/mailman/listinfo/owncloud
>> 
>> _______________________________________________
>> Owncloud mailing list
>> Owncloud at kde.org
>> https://mail.kde.org/mailman/listinfo/owncloud
>> 
> 
> 
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud