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 people who want to take this over, and it's better to let *someone* do that then leave the project to moulder and splinter.
On Tue, May 29, 2012 at 3:00 PM, Javier Guerra Giraldez <jav...@guerrag.com>wrote: > On Tue, May 29, 2012 at 2:46 AM, Simon Bächler <s...@feinheit.ch> 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 responsibilities. > > if sharing code had such "responsibility to maintain", nobody would > share anything. > > -- > Javier > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- Marcin Tustin Tel: 07773 787 105 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
