[MEI-L] Where to report customization service bugs?

[Raffaele Viglianti]

+1 to having separate tool in separate GitHub repo. Makes it somewhat
easier to contribute to :)

Raffaele


On Sun, Aug 4, 2013 at 11:52 AM, TW <zupftom at googlemail.com> wrote:

> Good question ;-)  My thought was that the tools directory might be a
> good place for the customization service, but on the other hand, a
> separate repository would make the Google Code repository less
> crowded.
>
> 2013/8/4 Daniel Röwenstrunk <roewenstrunk at edirom.de>:
> > Let me ask you in return, what would be a good reason to have it in the
> Google Code repo and not on GitHub?
> >
> > Daniel
> >
> >
> > Am 04.08.2013 um 17:25 schrieb TW <zupftom at googlemail.com>:
> >
> >> Hallo Daniel,
> >>
> >> before submitting the issue to the new repository:  Is there a
> >> specific reason not to have the customization service code in the
> >> Google Code repository?
> >>
> >> Thomas
> >>
> >> 2013/8/4 Daniel Röwenstrunk <roewenstrunk at edirom.de>:
> >>> Hi Thomas,
> >>>
> >>> I'm not quite sure what plans Johannes is talking about… My plan with
> the service is to keep it most separate from other services and thus most
> flexible in regards of integration and use. I intend to publish the code on
> GitHub and so reporting errors at Google Code wouldn't be very helpful.
> Actually, I created a repository on GitHub just a second ago:
> https://github.com/Edirom/custoMEIzation (the code will follow soon…).
> So, please report the issue there.
> >>>
> >>> Greetings,
> >>> Daniel
> >>>
> >>>
> >>> Am 04.08.2013 um 11:07 schrieb Johannes Kepper <kepper at edirom.de>:
> >>>
> >>>> Hi Thomas,
> >>>>
> >>>> I admit that this is somewhat tricky. All references should be
> relative to the driver.xml file in the repository, but when checking the
> current situation, I just noticed that the CSS is not contained in the zip
> you get from custom.music-encoding.org. So the current behavior is
> definitely faulty, and you should report that an Google Code. However, we
> already planned to revise the service and integrate it better with the
> website itself. Looking at our current schedule, this won't happen before
> September, and even September is pretty dense already… You may have to be
> patient, or you could volunteer ;-)
> >>>>
> >>>> Best,
> >>>> Johannes
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Am 04.08.2013 um 07:11 schrieb TW:
> >>>>
> >>>>> Hi all,
> >>>>>
> >>>>> would it make sense to report problems with the customization service
> >>>>> via the Google Code issue tracker?
> >>>>>
> >>>>> The problem:  When generating guidelines, the CSS files are missing
> >>>>> and the image links point to the wrong directory (or the images are
> in
> >>>>> the wrong directory, depending on what perspective you take).
> >>>>>
> >>>>> Have a nice Sunday!
> >>>>> Thomas
> >>>>>
> >>>>> _______________________________________________
> >>>>> mei-l mailing list
> >>>>> mei-l at lists.uni-paderborn.de
> >>>>> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> mei-l mailing list
> >>>> mei-l at lists.uni-paderborn.de
> >>>> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> >>>
> >>>
> >>> _______________________________________________
> >>> mei-l mailing list
> >>> mei-l at lists.uni-paderborn.de
> >>> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> >>>
> >>
> >> _______________________________________________
> >> mei-l mailing list
> >> mei-l at lists.uni-paderborn.de
> >> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> >
> >
> > _______________________________________________
> > mei-l mailing list
> > mei-l at lists.uni-paderborn.de
> > https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20130804/ac1fec65/attachment.html>