Samuel, After some more discussion with Martin, we've decided maybe it would best if you take over the crary project, since there is a low probability we will ever use it for Erlware again. You still interested?
Thanks! JW On Sun, Feb 13, 2011 at 10:31 AM, Samuel <[email protected]> wrote: > I used crary for some projects at work in the past. That means that > any bug we find will be corrected (and obviously contributed back). We > don't plan to develop it further, it does pretty much what we need. > Also, I cannot guarantee that we can't take a look to possible > contributions to merge them (There wasn't any contribution apart from > ours during last years, so that is not likely to happen). > > Now that I know it's officially orphaned, I see two possibilities. > > * You drop the project and my company takes it over. As I said that > only means "fixing bugs that get in our way," not evolving the > project. I don't think we will use it in any new products, since there > are other solutions more widespread such as mochiweb. That also means > we will enforce our own versioning system and coding standards. > * It stays as an erlware product. We'll contribute any bugfix, but > won't enforce our standards, nor our versioning system. Anyone from > erlware will have to take care of versioning and testing the patches > since our tests will be on a slightly different source. (The erlware > maintainer could be me anyway, but as myself, not as part of my > company's work). > > Both are ok for me. > -- > Samuel > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
