[Vobject] Reviving vobject maintainership

[Pierre-Yves Chibon]

On Sun, 2015-01-25 at 12:05 -0500, Adam Tauno Williams wrote:
> > 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?
> 
> It seems to me the simplest solution - and what would happen if I was
> maintainer - is that everything would move to SourceForge where there is
> a complete stack of applications for doing everyone necessary running on
> a solid Open Source foundation [Allegra]. 

Amen to that!

> > * 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.

If it is possible to get the archive, we could also ask the new provider
(sf?) to import them.

> > Probably it's better to switch to git.  
> 
> Yep, subversion is fading.

+1

> > 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.

Note though that there are a few forks of the vobject code laying around
in github with more or less patches which might be interesting to
integrate.
Most forks seems to originate from this one:
https://github.com/adieu/vobject/
(which lead me to start the discussion with that person about their
thoughts on the future of vobject
https://github.com/adieu/vobject/issues/5#issuecomment-71381551
discussion which lead to this fork: https://github.com/tBaxter/vobject/
which seems also pretty advanced)

So there is definitely interest in keeping vobjects alive and the future
maintainer should know that he/she will not be alone in this task.

Regards,
Pierre