Hey, I ain’t dead yet! I know I haven’t posted for a loooong time, but that’s just because I’m really busy with lots of different projects…
Anyway, people keep asking where DevAssistant is going in 0.9.0, so here it is:
- We’ll introduce Central Assistant Index (not sure if this is the final name, though), where people will be able to share their own assistants.
- We’ll use the Index so much ourselves, that we’ll even drop the default assistant set and leave everything up to the index – we’ll most likely upload most of our default set assistants there, though.
- To have a nice systematic way to upload assistants, we’ll introduce a simple packaging format for assistants.
- We’ll introduce dependency versioning.
- We’ll introduce appendable snippets, which will allow combining any type of snippet-like code (e.g. creating Github repos) with any assistant.
- We’ll try to add some nice support for building Docker images and working with containers (this includes work in both DevAssistant core and some actual assistants – the core will provide functionality to conveniently do some Docker operations and the assistant authors will have to actually use it to make it available to end-users).
- And we’ll clean-up the Yaml DSL to make it more consistent and powerful.
- We’ll introduce project types concept.
- … and as usual, tons of smaller improvements and bugfixes.
Sounds good? I certainly hope it does!
That’s right, DevAssistant is now 0.7.0 with 0.8.0 comming with tons of improvements. In short, we rewrote command line interface, we have GUI, assistant DSL is more and more powerful and… And the code is a bit cleaner. DevAssistant is the reason why I haven’t written any post for quite a while, it just seems to consume my time faster than I consume my chocolate.
I’ll probably not be writing much to this blog about DevAssistant (that’s the official name now), since we have DevAssistant blog on our new homepage. We also have mailing list, G+ community and Twitter… And we are also at freenode #devassistant channel. Quite a lot of communication channels, right? Well, we just want everyone to be able to reach us easily. So please come to us with your use cases and what DevAssistant can do for you. I’m sure we’ll be able to help (we just don’t know how to write an assistant that would make a nice cup of coffee for you, but anything else should be doable).
Just yesterday, I released version 0.4.0 of Developer Assistant with tons of improvements and new features, that I’d like to introduce here. Since not many people know how devassistant works, I’ll briefly go through all the functionality that was there in previous versions, too.
It’s been a few days since RHSummit has come to an end, but I still remember that good feeling I had when Jim Whitehurst shown the “Open or Die” slide.
For me, this years RHSummit was a great conference. My talks about Software Collections went pretty well, people were asking questions and shown lots of interest. The talks were even more actual because RHSCL Beta was released few days prior and it had some serious buzz going around. And of course, I got my T-shirt, so I really can’t complain…
Because of the conference and other things at work, my two main projects – Devassistant and Copr – did not get the attention they deserve in the past few weeks. Fortunately, we’re getting some strong manpower for Copr (Mirek Suchy already started digging into the code), so everything will hopefully start moving forward as it should in the following days and weeks.
Just remember: Open or Die
So Dave Malcolm (yes, that great guy from Fedora who knows everything about Python) is reassigning most of his Python packages in Fedora, including the interpreters. Incidentally, I’m supposed to step up and take most of the work (to be fair, I’ll definitely not be alone, we’re a community after all).
So what’s this going to mean? Less time for my other projects, like Copr, Devassistant and Software Collections. And I’ll probably give up all the Ruby stuff, too. The last part feels to be the most saddening for me, as I feel I did a good deal of work on Ruby and Fedora integration and going on with that would be nice. But it seems it’s time for me to move on (I’ll still keep some RubyGems, just to follow where Ruby packaging is going).
On the other hand, I always wanted to contribute to Python itself (I already have few patches there, but just tiny bits) and this means a great chance to get closer to upstream and contribute more.
In Fedora, I’d like to push the community to migrate to Python 3 – by that, I mean making Python 3 the only Python runtime in minimal installation. It does not mean enforcing migration of everything immediately without a pardon (and it also does not mean migrating the Fedora infrastructure). This alone will take a lot of time and convincing and helping people, but it will be needed eventually – sooner rather than later. Python 2 is old and tired and it won’t be getting any new features and improvements. After all, Fedora claims to be close to upstream and first in innovations, so it’s time to finally say our goodbyes to Python 2 and welcome Python 3.
I’m also planning to look into packaging extension libraries/frameworks for other Python interpreters in Fedora like Jython and PyPy, but that’s probably even further in the future.
All in all, these are big shoes to fill. I promise I’ll do my best