New maintainer?

[guilhem]

1 year without commit.
No pull request merged.
Many forks...

Maybe it's time to have a new maintainer(s) if @seedifferently doesn't have enough time.

Without answer, maybe the community must do a "community" fork. What do you think?

[guilhem]

In #5, @seedifferently seems to encourage to pull request in @cleverdevil repository.

That's a good option, but I will try to contact boto maintainers to integrate this project in boto organisation in github.
It will give to it a better visibility.

[seedifferently]

If a credible source who knows what they're doing steps forward with interest I'm definitely game...but I don't consider this project dead. The main purpose of it works as expected for alpha software, and if life changes to where I have more time for F/OSS projects this one is definitely on my mind.

[etiennesky]

It would be great to integrate this into boto. Perhaps a first step would be to integrate outstanding pull requests. I can volunteer to do this, anyone else interested? As I mentioned in another pull request I can do it from my clone, but it would be easier from this repos.

[guilhem]

@etiennesky 👍
I can't help you to do this, but it's really a good thing.

[seedifferently]

Hi guys,

Recently the AWS team released their own tool called awscli -- http://aws.amazon.com/cli/

I am starting to think that it might be time to deprecate this project, since the S3 part of their tool provides a sync command.

What are your opinions? I have some time coming up in a bit where I thought I might revisit this and do some cleanup of the codebase, but now I'm not sure that's necessary.

Thanks,
Seth