Just wondering after I saw http://code.opencv.org/projects/openc... if we are going to completely transfer error handling through github? If so, we should adapt all the existing tutorials on how to contribute.
Special issue was created to notify users about the transfer: https://github.com/Itseez/opencv/issu... together with the similar notification on the code.opencv.org: http://code.opencv.org/projects/openc...
I've already fixed some of the links on the main wiki page: http://code.opencv.org/projects/openc... and on the CONTRIBUTE page: http://opencv.org/contribute.html Please, feel free to report any other places to be updated.
As for labeling: yes, you are right, labels can be assigned only by collaborators. I think, this restriction can become very useful, because old tracker contained many incorrectly labeled issues which were hard to determine. Version information can be added in the issue body.
How about an application for official collaborator? Is that in the pipeline? Because some of us had managing rights at the dev forum and it would be good if this does not fall to some single core devs again.
Btw, does this mean that the dev forum is gone for good and that we could for example use a github.io web page to place content on?
Not sure about official collaborator applications, but I can say that GitHub does not support same user rights granularity as ChiliProject. Push access is granted along with issue edit right, and here some problems can arise, because currently all pushes are being made via pullrequests service and accidental pushes via GitHub's "Merge" button can produce conflicts. However, we will discuss this question in future.
code.opencv.org will be freezed and wiki pages will be moved to GitHub. Please, check this experimental wiki for example: https://github.com/mshabunin/test/wiki
Apparently, git mirror on code.opencv.org is not used by our infrastructure or by anyone else.
If you like, I could help design the wiki. I think that building an interface on an OpenCV specific github page could be way better than just a repo. It gives the feel of a website, but is edited by a repo. You can take a look at mine on how it feels like (tough it is far from updated ...)
Thank you for proposal, but I think in this case wiki pages are actually better, because:
In all these aspects GitHub wiki is almost the same as the current ChiliProject-based solution.
Okay seems legit :) If I find some spare time, I will have a look at it :D Still trying to figure out the issues handling now.
Asked: 2015-07-27 08:34:55 -0600
Seen: 689 times
Last updated: Jul 27 '15
@mshabunin any insights in your work?
i was just about to ask something similar.
how do we add version information / labels there ? i played a bit with my own repos , and it seems, only owner/maintainer can assign labels to an existing issue. that sounds cumbersome.
the problem I see arising now is that without a warning, people who are busy supplying fixes will not understand what happens...