Ben
- creating a company
- being the head of a research group
- HDR of noury
- PhD of Nick
- Papers there and there
- admin there and there
- dealing with people
- dealing with people
- dealing with people
- having a door always open
- having a door always open
- being second of a lab of 300 researchers
- coding on boring stuff
- working on projects
- thinking about money for the team
is a long list of duties before even thinking about Pharo.
So we must evaluate our energy before changing to a new architecture.
And there are always pros and cons.
Evaluating for REAL a new bugtracker is not something that we do in one
afternoon.
And we do not do that two months before a release. We do not change the commit
tools
either. This is like that.
Stef
On 29 Jan 2014, at 12:44, Benjamin <benjamin.vanryseghem.ph...@gmail.com> wrote:
> I actually proposed few replacement one month ago inside the RMoD team,
> nobody answered except “Fogbugz is bad” , and nobody tried what I proposed.
>
> Exactly what happened when we had to choose a replacement for Google Issue
> Tracker.
>
> Ben
>
> On 29 Jan 2014, at 08:33, Marcus Denker <marcus.den...@inria.fr> wrote:
>
>>
>> On 29 Jan 2014, at 11:32, Sebastian Sastre <sebast...@flowingconcept.com>
>> wrote:
>>
>>> I hope we’re not making it harder than it should for fear to feedback
>>>
>>>
>>
>> It has already been concluded that fogbugz was a mistake. It’s just not made
>> for an open source project.
>>
>> Now moving will be *a lot* of work and we have not even found a replacement
>> that is scriptable.
>>
>> We first need to release Pharo3 before we sink indefinite amounts of time
>> into this.
>>
>> Marcus
>
