![]() Two people really helped get the 0.7.x release done and once 0.7.4 was released the two contributors felt they had finished what they wanted to accomplish and moved on. At that point I said that I couldn’t continue at the rate I had been developing and I needed help. A contributor can work on what ever they want, that’s the point of open source software. ![]() That’s fine and perfectly natural and acceptable. There were a few contributors over the years but they few 3-4 people total and they all wanted to work on specific things. I needed a break and in late 2013 simply stopped coding. With very few contributors I ended up doing the vast majority of development nearly full time (like Strahinja had). Knowing C++ and Qt (which Sigil is written in) I decided to finish the 0.4.0 release and get it out the door. At the time of transition the 0.4.0 release was nearly ready. Very few contributors came forward to help which has always and still is a problem for Sigil. My goal for Sigil was to keep it moving forward from a project manager standpoint and continue coding for calibre. My goal was to manage releases, help contributors, evaluate code but not actually write code myself. When I (John Schember) took over I was planning on being a project manager for Sigil. He basically handed me the keys to his classic Mustang and said it’s yours do what you want even if you wreck it I won’t mind. Giving someone full control over your project, a project you started and were basically the sole developer on is very difficult. I really want you to know you’d have full autonomy to do whatever you feel is necessary. I’m not going to interfere in any way, shape or form. If you decide to take over the project as the maintainer, you’d have free reign over any aspect of Sigil development you’d become “the boss” and how you decide to evaluate future contributions from others (and yourself) is up to you. Other people could then contribute under whatever level of supervision you deem necessary.”Ģ) “Like I said, I’m not going to lay down any expectations/requirements. Specifically he said these two things that have stuck with me (because I highly respect him as developer).ġ) “Frankly, even if someone comes forward who’s willing to devote more time to Sigil than you, I’d still probably tap you for the PL/gatekeeper role because I know I can trust your judgment. His trust in me made me feel I was right for the role. Strahinja said some very kind things to me during the transition. By July of 2011 I was the official maintainer of the code base. I (John Schember) who had been developing for calibre decided to step up and offered to becoming the maintainer of Sigil. In June of 2011 Strahinja made a post on the then Sigil development blog stating that he was leaving and a new maintainer was needed. Strahinja leaving Sigil and the transition to new maintership 3) He felt it was time to move on and contribute to other projects and use his free time in a more free manner such as working on other open source projects. His exact words were “I’ve been looking at this codebase for over two years now, and frankly I’ve grown weary of it.”. 2) After two years of working on the same code day in and day out he got tired of it. Simply put he was done with Sigil for a few reasons: 1) he got a job which took away most of his free time. Once Strahinja graduated the magnitude of keeping a project like Sigil wasn’t as simple. While it was a school project there was plenty of time to devote to working on Sigil full time. It started as a school project as part of his computer science course work and was the basis of his Bachelor’s and Master’s thesis. Sigil was started by Strahinja Marković in 2009. Sigil has been around for a number of years so and changed hands during that time. Most of this is from memory and looking back though emails. This is the boring part so that’s why it comes after the features which is what people really care about. Strahinja leaving Sigil and the transition to new maintership.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |