his package !
>
> On Thu, Jan 19, 2012 at 7:04 AM, Michael van der Kolff
> wrote:
>> Dear mentors,
>>
>> I am looking for a sponsor for my package "jbigkit".
>>
>> * Package name : jbigkit
>> Version : 2.0-9+1
>> Upstream
IANAL, etc., but how about getting some legal advice on this? It
seems to me it wouldn't be nearly as cut and dried as all that; have
you examined whether or not such a scheme could be set up in such a
way that makes it a DMCA safe harbour?
Cheers,
Michael
On Sat, Jan 21, 2012 at 7:47 AM, Russ
But in setting it up in the US, don't you only have to care about US law?
Cheers,
Michael
On Sat, Jan 21, 2012 at 9:06 AM, Russ Allbery wrote:
> Michael van der Kolff writes:
>
>> IANAL, etc., but how about getting some legal advice on this? It seems
>> to me it wouldn
OK, I've simplified and renamed the debian revision to 2.0-1 (Yeah, I
know, the history went backward...)
Is anything else required?
Cheers,
Michael
On Thu, Jan 19, 2012 at 10:33 PM, Jakub Wilk wrote:
> * Michael van der Kolff , 2012-01-19, 20:19:
>
>> What do you mean by
Can I please get a mentor, reviews, anything for jbigkit 2.0-1?
Cheers,
Michael
On Sat, Jan 21, 2012 at 9:33 AM, Michael van der Kolff
wrote:
> OK, I've simplified and renamed the debian revision to 2.0-1 (Yeah, I
> know, the history went backward...)
>
> Is anything else req
I can't tell if you're serious or not... but in any case, a cursory
review of the code reveals that if it's an April Fool's, it's a bit
early.
This is basically a segfault generator, nothing to see here...
But if you were serious, I'd say that this is where software that has
been written comes to
Neither github.com nor gitorious.org are owned by MS. Anyone may host
whatever they like, so long as it's in accordance with the law.
On 20/02/2012 11:45 PM, "SchmiTTT" wrote:
> Am 2012-02-16 10:28, schrieb Michael van der Kolff:
>
>>
>> But if you were se
Are there any best practices when packaging where upstream only has a
git repo? I was thinking of forking it and tagging it, and so on;
does that make sense as a means of "maintaining" an upstream?
I wish to package gedit-code-assistance, found at
https://github.com/jonocodes/gedit-code-assistanc
Never mind, I found a real upstream. Turned out the author moved
development from github, but left no pointer :(
Warmest regards,
Michael
On Sun, Apr 22, 2012 at 1:50 PM, Michael van der Kolff
wrote:
> Are there any best practices when packaging where upstream only has a
> git repo?
9 matches
Mail list logo
