[Owncloud] github issues

[Thomas Müller]

Am Montag, dem 27.08.2012 um 11:39 schrieb Klaas Freitag:
> 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.
>

Thanks for your feedback - this is what I need!
 
> 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?

Which links are you referring to?
In general I'd say it'll be best to keep buggenie running in readonly mode for quite some time.

> - All comments are done by you. Not critical, but also not nice.

Hehe - github isn't perfect either. AFAIK there is no way to do this different.


> - It is still possible to file bugs on bugs.owncloud.org, no hint about 
> new bugtracking.

I think we are not yet at this stage - I was just taking care about the technical possibilities.
But I agree with you: we need to plan this properly.

> - There was no communication yet to community members
>    * that we do this move
>    * what that means
>    * how we continue from here
> 

See above.

> 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?

Yes

> - Can we set a NEEDINFO state?

Only labels are available - we can create a label NEEDINFO.

> - Can we have a "How to reproduce" field?

No - github allows no custom fields.

> - Can we have more data like versions, categories and such?

Milestones exist for release planing - meaning: the ticket x will be shipped with release y.
All the rest needs to be done with labels.

> - Is there a bug workflow which we will need such as "NEW -> ASSIGNED -> 
> CLOSED -> VERIFIED -> RELEASED" or similar?
> 

No - Github knows open and closed as states.
All the rest must be done with labels as well.

> I guess that can be configured.
> 

well actually not :-/

> 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.
> 

We can only continue to use bug genie if all know and serious issues we have with it will be fixed.
Unfortunately the community can do nothing about that as we are dependent on ownCloud Inc, 
who hosts the service for us (THX by the way ;-) ).

The move to github issues is a logical consequence if bug genie will not be fixed.

To tell the truth: bug genie is fuxxxx up for months and it looks like nobody gives a sxxx.

Take care,

Tom

> 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