[Vobject] Bug#747554: python-vobject: python3 branch

[Tobias Brox]

[Jeffrey Harris @ 2015-01-24 14:16]
> I wrote vobject a decade ago. I am, at this point, contractually forbidden to maintain it. But I’d be happy for someone else to do so!

Ok, so obviously someone needs to take the maintainer responsibility.  Adam
Tauno Williams was hinting that he could do the job - ping?

If worst comes to worst, I can take the role - but I don't have much available
time, so I will be a lousy maintainer.  Anyway, better with a lousy maintainer
than no maintainer!

Next question, how much of todays frameworks can be reused?

* Home pages at skyhouseconsulting.com - do we have access to edit it?  If
nobody at Skyhouseconsulting is involved anymore or want to be involved, it
would make sense to set up new project home pages.  Would we be allowed to get
a redirect?

* Mailing list.  It works - but as above, if there is no relationship between
skyhouseconsulting and vobject anymore, it probably makes sense to set up a new
mailing list and gradually move the traffic there.

* Subversion repository at osafundation.  Is the OSAF still operative?  It
seems like development on Chandler is more or less discontinued, and I've heard
rumors the code got so messy it's considered to be a dead end.  Anyway, that's
a digression - the questions are if we can easily control the ACLs of the
repository and, maybe more important, if we can trust this repository at all.
Probably it's better to switch to git.  I'm (like many others) more comfortable
with github than with SF, but if Someone Else wants to take over the maintainer
role and move it to SF, then let's do that.

* Bugzilla at OSAF.  SSL Cert out of date.  See the notes above ...

* pypi project page.  Whomever takes the maintainer role needs to be set up as
the project owner there, so we can roll new releases.

-- 
Tobias Brox