Dear ruby wizards,
As of now, there are some open bugs in fedora-review's ruby plugin [1]
Basically, we need some input on these to sort out how this should work.
However, here is also a more basic issue: who should maintain the ruby
plugin? Frankly, keeping track of all upcoming changes isn't that easy
when lacking specific ruby skills (which is what the open bugs are all
about).
Since some releases we have "outsourced" the java plugin to the java
SIG; the fedora-review-plugin-java is now part of javapackages-tools. I
think we have now stabilized the plugin interface. Basically, this has
made life easier both for me (no java wizard) and for the java SIG which
can enforce their packaging rules by modifying or adding tests.
From my perspective it would be nice to apply this organization also to
the ruby plugin i. e., create a fedora-review-plugin-ruby package
somehow maintained by the ruby SIG.
Thoughts?
--alec
[1]:
https://bugzilla.redhat.com/show_bug.cgi?id=1128094
https://fedorahosted.org/FedoraReview/ticket/225
https://fedorahosted.org/FedoraReview/ticket/238