[pkg-fso-maint] I need a DD to upload libfsoresource :-)

[Heiko Stübner]

First, I did rename the branches of the libfsoresource git according to the 
last mails as a test, so gbp-clone is happy now and you will need to reclone 
it.

Am Montag 15 März 2010 14:36:57 schrieb Jonas Smedegaard:
> Yes, I do understand this.  We have an important role as distributors,
> which is to *distribute* code written by others.  When weget more
> enthusiastic and participate in the coding (which is to some extend what
> is happening when we cherry-pick code not yet approved for release by
> our upstreams) then we should IMO be *very* transparent about it.
here our beliefs about transparency differ. I think current Freerunner-users 
that use Debian on it are somewhat familiar and follow fso-developments.
So it could be easier for them to see on in the current form what commit a 
snapshot package was based on by simply looking at the history which is also 
in our git and compare with upstreams git.


> Yes, it is more work to prepare patches. On the other hand, later bug
> tracking can be helped when both yourself, downstream users and upstream
> developers can very clearly see not only the upstream internal reference
> number (i.e. the commit ID) of our snapshot but more details on changes
> between that and upstream latest release (which non-Debian users can be
> expected to base their user experiences on).
For cornucopia bugtracking is at the moment mostly packaging a new snapshot, 
as the code which contains the bugs is most of the time already obsolete when 
the bug is discovered.

To conclude, I don't think it's necessary to change the packaging at the 
moment as the cornucopia stuff changes very frequently and real releases won't 
happen this often. Also we need the snapshots just to improve the user 
experience - or create one at all.


At this point opinions of other pkg-fso members would also be helpful, as we 
will be running in circles here. 
For example fso-frameworkd, fso-gpsd and fso-gsm0710muxd by other DDs also use 
a similar packaging style (with master = upstream-git too) where nobody 
complained about this since 2008 - so it seems not to be completly wrong to me 
but more a matter of personal preference/opinion.


Heiko