On Nov 1, 8:24 am, llbbl <[email protected]> wrote: > github is a great tool for collaborative development. Although the GUI > tools aren't up to par with SVN tools so you will most likely be using > the command line to make your commits and push origin to master.
We don't have any plans move from Subversion to github. We are discussing options, but I would have to have a lot more positive experience with github first. > > I have been using FF4 beta and the Development tools are not anywhere > near as useful as firebug. It has like 5 windows all displaying > different things. Their UI is annoying. Also another thing that I > don't like about it is that it doesn't seem to have all the features > that Firebug does (console, net panel, awesome plugins). Of course these are things you should bring up with them. > > Please, please don't let your long term goals of multibrowser support > and a new versioning system interfere with development efforts of a > firebug support for FF4. We are committed to Firebug support in Firefox. jjb > > On Oct 28, 9:40 pm, Leeoniya <[email protected]> wrote: > > > other tools have nothin' on fbug. github is the way to go for sure, it > > is a huge step up from google code for collab. maybe not so much for > > issue tracking. > > > On Oct 27, 1:00 pm, Steven Roussey <[email protected]> wrote: > > > > > 1. Adopting things that all the other competitors have and developers > > > > are requesting. This one is a good example of > > > > that:http://code.google.com/p/fbug/issues/detail?id=1811 > > > > Just curious, but with the latest Firebug 1.6 or 1.7, what happens if > > > you use the toString() function set on the function of interest? I > > > haven't tested it, but try using a myFunc.toString=function(){return > > > "Some name";}. > > > > > 2. Switching to github, yes it's extra work etc, but it makes > > > > collaboration whole lot easier and a lot of projects gained more > > > > contributors just by doing this. (I guess official mirror and > > > > accepting pull requests will be good start) > > > > I'm an advocate of that idea. But there is a lot of work to: > > > > 1. Set things up. Code and Issues, etc. I know you can use svn2git or > > > similar, and you can copy issues out of Google Code and put them in > > > GitHub programatically, but it is a lot of work to do *correctly*. > > > > 2. Get Firebug devs up to speed on git. I'm only so far as commit/pull/ > > > push. To use it correctly, we would have to learn it really well. > > > > 3. Deal with pull requests. Have pull requests automatically trip a > > > run of all tests with the proposed patch, etc. Of course, there may > > > not really be many pull requests, but if that is so, then why move in > > > the first place? > > > > -steve-- -- You received this message because you are subscribed to the Google Groups "Firebug" 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/firebug?hl=en.
