Re: [Owncloud] Move to GitHub
For the record I'm still against a move to GitHub, and I don't think that the decision should be made by vote. Such a move concerns business strategy and politics and must be decided by the project / company leaders. Best, Sam. signature.asc Description: This is a digitally signed message part. ___ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud
Re: [Owncloud] Move to GitHub
For me it's not that gitorious is really bad... but that i am already on github for other projects and it's simpler to have everything there... (username eMerzh btw ;-) ) On the issue tracker topic, i have some things that i want to get fixed on the genie and it's ok for me (downtime / maintenance pbm a-side) but i think the main issue is that on genie or on github we need to organise ourself a bit : how to classify things, what informations are important / need tags ... what does things mean (testing / assigned /... ) The problem, i think, will specially raise with github issue (tagging style instead of list of fields) so we have to be careful and to define some way-to-go (don't get me wrong ... i like the flexibility of Github but it can lead to some disorganization :p ) about the split of repos, we may want to be careful about providing core apps compatible with the core code (manage compatibility issues at least for core ..) Regards, eMerzh ___ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud
Re: [Owncloud] Move to GitHub
Am 23.06.2012 um 22:21 schrieb eMerzh: For me it's not that gitorious is really bad... but that i am already on github for other projects and it's simpler to have everything there... (username eMerzh btw ;-) ) On the issue tracker topic, i have some things that i want to get fixed on the genie and it's ok for me (downtime / maintenance pbm a-side) but i think the main issue is that on genie or on github we need to organise ourself a bit : Better organization is another reason for GitHub Issues. We would have separated bug tracker for every single repo. It makes it all a bit cleaner. how to classify things, what informations are important / need tags ... what does things mean (testing / assigned /... ) we can create as many labels as we like ;) The problem, i think, will specially raise with github issue (tagging style instead of list of fields) so we have to be careful and to define some way-to-go (don't get me wrong ... i like the flexibility of Github but it can lead to some disorganization :p ) about the split of repos, we may want to be careful about providing core apps compatible with the core code (manage compatibility issues at least for core ..) Regards, eMerzh ___ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud
Re: [Owncloud] Move to GitHub
Hehe, yes, but do we have the ability to transfer an issue from one to another? (just asking) and yes we can have as many label as needed but it's better if everyone use at least some equivalent labels :) ___ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud
Re: [Owncloud] Move to GitHub
Am 23.06.2012 um 22:54 schrieb eMerzh: Hehe, yes, but do we have the ability to transfer an issue from one to another? (just asking) and yes we can have as many label as needed but it's better if everyone use at least some equivalent labels :) https://github.com/blog/967-github-secrets Cross-Repository Issue References might be the best solution___ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud
