Bernard, At least, with github, you have an API available :)
https://api.github.com/repos/symfony/symfony/issues?since=2012-12-14T17:37:44Z Pascal On Tue, Dec 18, 2012 at 5:27 PM, Bernhard Schussek <bschus...@gmail.com>wrote: > One maybe not unimportant point in this regard: Javier should then start > covering current discussions on GitHub in the weekly report, which he > currently doesn't. I don't know if that's feasible without too much effort. > > -- > Bernhard Schussek > Blog: http://webmozarts.com > Twitter: http://twitter.com/webmozart > > > > 2012/12/18 liuggio <liug...@gmail.com> > >> Even if I should not have a say in the matter (I'm a passive reader), >> usually the mailing list is very important because it gives in a pull-way >> some generic information, >> but this mailing list is not so crucial, 'watch'ing the github repo is >> important but my weekly-passive source of information comes from the lovely >> weekly page in the symfony blog. >> >> so also for me +1 >> >> >> >> >> >> On Tue, Dec 18, 2012 at 11:21 AM, Bernhard Schussek >> <bschus...@gmail.com>wrote: >> >>> Even concepts and similar things can be discussed on GitHub (in fact >>> that's already the case). You simply open a ticket with a suggested change >>> and people can discuss the change with you, refining the idea before >>> actually implementing it and opening a PR. >>> >>> Example: https://github.com/symfony/symfony/issues/1341 >>> >>> Doing all of this on GitHub is very useful, because the PR can link back >>> to the ticket, which contains the full history of the discussion, and the >>> discussion can even be continued on the PR. >>> >>> -- >>> Bernhard Schussek >>> Blog: http://webmozarts.com >>> Twitter: http://twitter.com/webmozart >>> >>> >>> >>> 2012/12/18 Victor Berchet <vic...@suumit.com> >>> >>>> Thomas, >>>> >>>> I agree with that. >>>> >>>> While it's true that a lot of threads don't belong here: >>>> - did you read the doc, >>>> - go ask the user ml, >>>> - really, you should use GH >>>> >>>> The real dev subjects usually draw some attention and are active. So >>>> please once again keep this ml open. >>>> And help educating people by having a sticky post with concise, clear >>>> guidelines and a clear title. >>>> >>>> -1 >>>> >>>> >>>> On Tuesday, December 18, 2012 7:34:51 AM UTC+1, Thomas Lundquist wrote: >>>>> >>>>> On Mon, Dec 17, 2012 at 06:28:34AM -0800, Victor Berchet wrote: >>>>> > Transferring most discussion is probably a good idea however some >>>>> thread >>>>> > don't really have a place on GH, please keep this ml opened (with >>>>> some >>>>> > directions on when to use GH instead). >>>>> >>>>> Agreed. >>>>> >>>>> Simple question and argument for keeping this list: >>>>> >>>>> How can we discuss concepts and ideas on Github? >>>>> >>>>> >>>>> Thomas. >>>>> >>>> -- >>>> -- >>>> If you want to report a vulnerability issue on Symfony, please read the >>>> procedure on http://symfony.com/security >>>> >>>> You received this message because you are subscribed to the Google >>>> Groups "symfony developers" group. >>>> To post to this group, send email to symfony-devs@googlegroups.com >>>> To unsubscribe from this group, send email to >>>> symfony-devs+unsubscr...@googlegroups.com >>>> For more options, visit this group at >>>> http://groups.google.com/group/symfony-devs?hl=en >>>> >>>> >>>> >>> >>> -- >>> -- >>> If you want to report a vulnerability issue on Symfony, please read the >>> procedure on http://symfony.com/security >>> >>> You received this message because you are subscribed to the Google >>> Groups "symfony developers" group. >>> To post to this group, send email to symfony-devs@googlegroups.com >>> To unsubscribe from this group, send email to >>> symfony-devs+unsubscr...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/symfony-devs?hl=en >>> >>> >>> >> >> >> >> -- >> __________________liuggio_________________________________ >> >> __/|_ We reject kings, presidents and voting. >> /o ) \/ We believe in rough consensus >> )__ v _/\ and running code (I.E.T.F. credo) >> ______________________________________________________________ >> >> -- >> -- >> If you want to report a vulnerability issue on Symfony, please read the >> procedure on http://symfony.com/security >> >> You received this message because you are subscribed to the Google >> Groups "symfony developers" group. >> To post to this group, send email to symfony-devs@googlegroups.com >> To unsubscribe from this group, send email to >> symfony-devs+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/symfony-devs?hl=en >> >> >> > > -- > -- > If you want to report a vulnerability issue on Symfony, please read the > procedure on http://symfony.com/security > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > > > -- Pascal -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
