I agree with the change, we don't use the irc channel at all and I am sure it creates a bad impression. I say we can it. Also, yes, the dev process is no longer applicable, we don't send patches anymore. I think using github pull requests and reviews works well. Each dev can fork from the main at github erlware and then send pull and review requests. Thoughts?
Cheers, Martin On Sun, Jun 28, 2009 at 1:23 PM, Samuel<[email protected]> wrote: > > Guys, > > I polled the IRC archives, no one of the days I looked at had > anything. I suggest removing the link from the developers page, since > it may create a bad impression for possible newcomers. > > The patch is in erlware-site's next branch if any one wants to review > it: 158acf7535e2d2b02656b0a256b8f2d91d1b8ee3. If no one complains, > I'll push it to master on Wednesday (1th of Jul). > > BTW, now that we have git-hub, it may be worth revisiting the > development process (we are not following right now anyway). Maybe it > is more convenient to ask for reviews before pushing something to > master instead of the former idea of sending all the patches to the > list? > > Best regards > -- > 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 -~----------~----~----~----~------~----~------~--~---
