Re: Syck, fork, hosting

"Alexey Zakhlestin" <[email protected]>
Newsgroups gmane.text.yaml.general
Message-ID <[email protected]>
On 2/27/08, Ingy dot Net <[email protected]> wrote:
>
> I have no problem with you being the maintainer of the legacy libsyck,
>  but that's not my call to make. Have you contacted Why? I bet he would
>  let you take it over.
>

I did contact him several times (sometimes he answered, sometimes he didn't…)

de-facto I am already maintaining syck-code in why's subversion
repository. But there's no way for me to make release, as releases are
to be put on why's web-server and he is the only person who has access
to that.

Last drop is, that 2 months ago Why was doing some upgrades and broke
syck's bugtracker and never answered my emails regarding that. I can't
be sure, that he would not break subversion next time. :-/

last time I heard from Why was in november, when he promised me to
sort the release schedule in several days and let me know (he told,
that, he is going to fix something during ruby-1.9 process). He didn't
make a single svn commit since then and ignored my further messages

so, my options are:
1) wait some more time
2) maintain the fork at something like googlecode
3) maintain the fork at yaml.org

I like (3) more than (2) because it would be easier to switch
maintainers again, if I have to step away too, at some point

p.s. I still like (1) the most, but, well, in april it will be year,
since I first asked Why to start the release-process.

-- 
Alexey Zakhlestin
http://blog.milkfarmsoft.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Yaml-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yaml-core
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.