For how to go about discussion: would a google group work?
Or possibly an organization on github? Personally I could go with almost anything. On Wednesday, August 10, 2016 at 11:09:12 PM UTC-4, Jonathan Pittman wrote: > > For some reason I did not get the last 3 updates until this one. Weird. > > So, I have looked over a number of packages that parse tiff files. While, > at the most basic level, they all have to do the same sort of things, each > one also approaches the situation a little differently. And more so, the > end result tends to be for custom use cases. > > I already have code up on github > <https://godoc.org/jonathanpittman.com/tiff>. You will have to excuse my > lack of good documentation and tests. I was originally planning to just do > a proof of concept for how this might work. So, it needs some cleaning up. > I am also in the process of making some changes to it including the > LICENSE. No pull requests at this time please, but do have a look if you > like. > > I would like to see some real discussion about the approach before writing > any more code. I am not sure the best way to go about this discussion. > Does email work for everyone? Should we use the go proposal method? A > shared google doc? I would like this to eventually make its way to the > golang.org/x/image repo. I would like to see a collection of use cases > that we can include when trying to solve this in an appropriate and general > way. > > On Wednesday, August 10, 2016 at 6:08:00 PM UTC-4, jonathan...@gmail.com > wrote: >> >> I would be interested in seeing this happen. >> >> On Tuesday, July 26, 2016 at 7:36:31 PM UTC-7, Jonathan Pittman wrote: >>> >>> Well me too! I am looking to see what level of interest there is in the >>> Go community to see this happen. I am also looking for people who are >>> interested in working on this. >>> >>> Figuring out how to handle this problem for one specific camera's raw >>> files is not too difficult. Figuring out how to do this to handle the >>> majority of cases requires a bit more work. >>> >>> To be clear, I am wanting a pure Go solution that is better thought out, >>> better laid out, and better to use than the existing C/C++ options. >>> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
