Alex,
More power to you for sticking your head above the parapet in relation to
this.
Marcin
On Saturday, June 16, 2012, Alex Gaynor wrote:
>
>
> On Mon, May 28, 2012 at 12:39 PM, Simon Bächler
>
> > wrote:
>
>> I was just checking on github if there was a new version of django-taggit
>> and
On Mon, May 28, 2012 at 12:39 PM, Simon Bächler wrote:
> I was just checking on github if there was a new version of django-taggit
> and was quite shocked what I saw. The original repository had not been
> updated for over a year. Yet there are 41 issues and 12 pull requests.
> There are 114 fork
Open Letters scare me ... They remind me of the pseudo-beginning of
mainstream, non-free software :)
I'd say just do like Russ mentioned. Try to pull everything together
in one repository. Then when it's mature and you still want to take
over the project, contact the original author and see if he/
It does if anyone wants to be able to find the code.
On Tue, May 29, 2012 at 4:01 PM, Daniele Procida wrote:
> On Tue, May 29, 2012, Marcin Tustin wrote:
>
> >That's not quite right. Once you build up a reputation as the package to
> >have, if you don't at least hand over the project, you expos
On Tue, May 29, 2012, Marcin Tustin wrote:
>That's not quite right. Once you build up a reputation as the package to
>have, if you don't at least hand over the project, you expose everyone to
>the pain of figuring out how to either use your code, or which is best
>place to get a forked version. I
That's not quite right. Once you build up a reputation as the package to
have, if you don't at least hand over the project, you expose everyone to
the pain of figuring out how to either use your code, or which is best
place to get a forked version. It's certainly not hard to see that there
are peop
On Tue, May 29, 2012 at 2:46 AM, Simon Bächler wrote:
> I believe that if you publish a repo and you are the main contributor then it
> is your responsibility to maintain it.
that's not how it works, fortunately.
if you (or anybody) write something, you're free to share it. that's
it. no resp
On Tue, May 29, 2012, Simon Bächler wrote:
>I believe that if you publish a repo and you are the main contributor
>then it is your responsibility to maintain it.
That seems to be asking a bit much, frankly.
Don't forget that one way for Alex (or whoever) to meet the obligations you set
out fo
Hi Russ
I understand that Alex is busy doing other things now. But he is the owner of
the django-taggit repo. If someone is searching for django-taggit it's his repo
that shows up.
What you are suggesting, creating my own fork and fixing my issues there is not
the solution. It would only lead
Hi Simon,
On Tue, May 29, 2012 at 1:39 AM, Simon Bächler wrote:
> I was just checking on github if there was a new version of django-taggit
> and was quite shocked what I saw. The original repository had not been
> updated for over a year. Yet there are 41 issues and 12 pull requests. There
> are
I was just checking on github if there was a new version of django-taggit
and was quite shocked what I saw. The original repository had not been
updated for over a year. Yet there are 41 issues and 12 pull requests.
There are 114 forks, 17 of which had commits within the last month.
Shortly, i
11 matches
Mail list logo
