[seagrant-dev] Error reporting

Kenneth Lett kennric at osuosl.org
Mon Aug 18 19:23:09 UTC 2014

On Mon, Aug 18, 2014 at 07:18:45PM +0000, Carr, Justin wrote:
> Error handling document looks good. I like that it specifically talks about how to go about examining the error.
> On the subject of communicating across the Great Library-Quad Divide: I have been looking into irc tools to allow team members to get in touch quickly without the formality of sending an email. Is there an appropriate channel we can use for this purpose or should we make a new project-specific channel on freenode?

I suggest #seagrant-dev - creating the channel is as easy as one of us
joining it, but we should register it with freenode as well.


> -----Original Message-----
> From: seagrant-dev-bounces at osuosl.org [mailto:seagrant-dev-bounces at osuosl.org] On Behalf Of Kenneth Lett
> Sent: Monday, August 18, 2014 12:09 PM
> To: seagrant-dev at osuosl.org
> Subject: [seagrant-dev] Error reporting
> I have started a very sparse draft doc to work out our error messages and levels:
> https://docs.google.com/a/osuosl.org/document/d/1ggrdeyJZLU9-d1jzP9Z5g-rqbfcKCTLZTNl800NrikU
> OSL and BSG Devs: let's collaborate on that and make sure we have something that makes sense for reporting all kinds of possible error conditions in the api.
> Ken
> _______________________________________________
> seagrant-dev mailing list
> seagrant-dev at osuosl.org
> http://lists.osuosl.org/mailman/listinfo/seagrant-dev

More information about the seagrant-dev mailing list