DynamoDB

[Paddy Foran]

Is support for DynamoDB planned for GoAMZ? Is there some way I can help contribute code to support DynamoDB in Go?

Thanks,

Paddy Foran

[Gustavo Niemeyer]

Hey Paddy,

On Wed, Jan 18, 2012 at 17:40, Paddy Foran <foran...@gmail.com> wrote:
> Is support for DynamoDB planned for GoAMZ? Is there some way I can help
> contribute code to support DynamoDB in Go?

Absolutely. Someone will definitely put this in, and if you're
interested, I'll be of course glad to take your contributions.

--
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/plus
http://niemeyer.net/twitter
http://niemeyer.net/blog

-- I'm not absolutely sure of anything.

[Matthew Moore]

Hey there,

Just wondering if there have been any updates here?  I'd love to do my DynamoDB work in Go :)

[Gustavo Niemeyer]

hi Matthew,

No updates yet. I don't depend on DynamoDB myself at this point, so
we're waiting for someone to step up to push it forward.

> --
> You received this message because you are subscribed to the Google Groups
> "goamz" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to goamz+un...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--

gustavo @ http://niemeyer.net

[Matthew Moore]

Gotcha.  I have a version in github that is working reasonably well at https://github.com/crowdmob/goamz.  It could probably be cleaned up to align with the general goamz format in terms of code layout.

I did a bzr push to github first, so it should be sync'ed with your changes.

[Gustavo Niemeyer]

Neat, that'd certainly be welcome.

[Matthew Moore]

Just let me know how you'd like to proceed!  I'm not sure I have much time to clean it up in the next couple weeks, but would love to have someone on your team give any recommendations as to what to clean up :)

[Gustavo Niemeyer]

On Wed, Apr 3, 2013 at 1:55 PM, Matthew Moore <ma...@crowdmob.com> wrote:
> Just let me know how you'd like to proceed! I'm not sure I have much time
> to clean it up in the next couple weeks, but would love to have someone on
> your team give any recommendations as to what to clean up :)

The proper way to do this would be to break down the whole module in
small increments, ensure that every piece is well tested, and pay
attention to conventions on coding and documentation as present in the
other packages. Submit each piece for inclusion, and we'll review
them. The small increments ensure that we're always on the same page.


gustavo @ http://niemeyer.net