However, considering that MP1 code base sometimes acts like a Pandora's box, not many developers are willing to put a lot of effort in it, or are experienced enough to handle such a challenge. I think that everyone in the team agrees that MP1 needs to keep advancing until MP2 reaches a state of development where it can start replacing its predecessor. I felt I could help better in MP1 Development than in the early stage of MP2.Īrion: Yes, It was Simone that dragged me into this! Joking aside, this was not an easy decision. They asked us if one was the 'vice' or “deputy” of the other, but I immediately said we share it fifty-fifty.

So I announced to the Team that we were going to share the chair. However, since no one else was moving to do something, I contacted Arion and asked him to share the responsibility and balance the knowledge - him on the code side and me on the Team rules and management. I have been working in IT for fifteen years but not at all as a developer. I was not at all convinced to take the ‘job’ because of my limited coding knowledge. What inspired you to agree to become MP1 Development Manager?Ĭhemelli: The idea came to my mind after some team members spoke with Infinityloop and he told me that my name was quite frequently suggested by them. So here is the Inside Scoop from our new Managers about MP1 Developmentġ. However, with the recent successful release of RC3, I finally managed to catch up with them and ask them about their new roles, and the future of MP1. These guys are not easy to catch, they work almost every spare minute on MP1 these days, trying to get MP 1.1.0 released.

As many of you know from a recent news release, arion_p and chemelli have taken on the task of managing MP1 development.

Mediaportal webepg duplicate names