<div dir="ltr">On Tue, Oct 8, 2013 at 7:14 AM, Christian PERRIER <span dir="ltr"><<a href="mailto:bubulle@debian.org" target="_blank">bubulle@debian.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Quoting Ralf Treinen (<a href="mailto:treinen@free.fr">treinen@free.fr</a>):<br>
<br>
> garmin-ant-downloader. Your write that the g-a-d project is currently<br>
> unmmaintained - did you try to contact the g-a-d maintainers to discuss<br>
> with them? I think you should first make an attempt to contact them and<br>
> give them a chance to react. If you don't get any answer from them in a<br>
<br>
</div>Yes, he did..:-)<br>
<br>
g-a-d is basically something that I assembled in the hope of having<br>
something that works with my 405 watch in Debian.<br>
<br>
The current course is the original work by "Paul", which got untouched<br>
for years, then got fixes by Klaus Ethgen, who had the same purpose<br>
than me(get his 405 working)...and that's it.<br>
<br>
So, I can tell that I'm mostly the "maintainer" of this and I can<br>
confirm that I don't really maintain it.<br>
<br>
And Kristof did contact me so he did indeed contact the g-a-d "maintainers"..:-)<br>
<div class="im"><br>
> > After all this said, I have the following questions to you:<br>
> > - Do you agree with my plans to extend g-a-d with ANT-FS functionality, and<br>
> > thus download capability from more GPS devices.<br>
><br>
> You should first try to get this settled upstream with the g-a-d maintainers.<br>
> There are two possible outcomes : either you join forces with the g-a-d<br>
> maintainers and create a common tool, or you do your own fork of g-a-d.<br>
> Once this is decided (and up to that point debian has no say in this)<br>
> we can work on the debian packaging. In case the old g-a-d maintainers<br>
> are not interested in a cooperation we might just switch to your fork.<br>
<br>
</div>I wouldn't call that a fork because there is nothing alive to be<br>
forked..:-). Let's call this a resurrection.<br>
<div class="im"><br>
> > - What is the preferred way to provide patches for g-a-d? (send patch to<br>
> > mailing list or provide branch for merging)<br>
><br>
> If you want to help with packaging then the best would be to create an<br>
> account on alioth, ask for inclusion in the pkg-running group,<br>
> and provide patches as branch in the git.<br>
<br>
<br>
</div>Kristof main point was that he wanted to focus on the software but<br>
have someone from our team to deal with Debian packaging...which I'd<br>
be happy to do if I knew that I'm not proposing something that I will<br>
not find time to do.<br>
<br>
<br>
</blockquote></div><br></div><div class="gmail_extra">Thank you for your replies!</div><div class="gmail_extra"><br></div><div class="gmail_extra">I've registered an account on alioth: ralovich-guest. Could you please add me to the group?</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">As I personally do not have a Forerunner 405, I can't verify protocol changes in g-a-d, thus my approach would be to keep the current g-a-d functionality and add the ANT+minus functionality, so both would co-exist for some time in the beginning. Afterwards, if protocol traces of the 405 are available we could implement that part too within ANT+minus.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Thanks,</div><div class="gmail_extra">Kristof</div></div>