a) I dont think overworking yourselves will benefit Pharo. I have to only take a look at my father whos even at the age of 70 is still a workaholic to see the negative side of things. And believe me things can seriously get bad. You health is 1000 times more important than Pharo.

b) I think its a bad idea that Pharo keeps including new libraries. I dont believe there is enough manpower to maintain a large array of Pharo libraries inside the image. I fear that Pharo is going the direction of Java but you are not Oracle or Sun and we are no Java community to support you. Its my opinion there must be a discussion of cleaning the code and reducing the size and complexity of the existing libraries instead of keep adding new exciting cool features. I love Pharo but I would like to see it doing a similar clean up and reduction as Cuis. I think it will reduce your work. I am closely following your modularation efforts and the effort to make removable part of Pharo that were not removable in the past. We all want a better Pharo but its more important to have an easy to manage Pharo.

c) Issue tracker wise, since you already considering moving to Git, I think that Github could make an excellent place for issue reporting. I see amber people using it to a great effect so far. And why not even bring support ( outside pharo as third party library) for bitbucket etc.