We had some participation in the MeeGo project in the past before intel cancelled it for Tizen...
Tizen just now after four year has just got their first product to market way too late, too expensive for the only first place just launched; India. For those following Jolla & SailfishOS, they should know that Jolla has made some huge deals in some BRIC countries.. We need to pick up the work from where MeeGo was left, integrating new stuff for providing same functionality, and then further on moving as close to as possible for full compatibility between the two distros on distro level.. so people must help try get our stuff into their Mer distro (which is the community successor to the Meego/harmattan/maemo distro). I have two items on my TODO list related to this that I will for sure do most of myself, first one requiring major cpu power, is integrating their libhybris android compatibility layer, requiring a full android build... A third item that is not dependent on me, is for us to join the SailfishOS Alliance, I wouldn't be the right person at this moment to be fully responsible, as I'm in no legal position currently to represent on the behalf of our only formal organization supporting development, which currently is OMA... So anyone involved with the more biz/administrative side of association/project with interest in this, do please approach Sailfish Alliance and make yourself useful in this are and make sure for us to be part of it. It's nice to do such huge builds and test them the same day, so related to this I myself mainly plan on really get started on this when bigberta-moondrake.org is up again... For those of you who don't know, it's my 64 core, 256GB RAM, 8xSSD hardware raid 0, Opteron system, it's been out of commission for almost a year, and with my procrastrination and difficulties hauling my ass to RMA it and financially related difficulties getting in the way... (and to try make it public so people without previous access will know about new (although just personal) sponsoring is coming their way, and this will come as a kenobi cluster (and former klamah) replacement, it being both pretty much able to push away all of existing work that ABF servers do, reducing the cost of renting/hosting by removing the need, while still provide a solid enough virtual environment to provide it as just as much test and build platform as back then, which we now unfortunately all have to do locally. I think I should have it up and running again at full capacity and full/stable uptime within the next two months, I'll be getting back to work after my several weeks absence outside of cooker list activity next week after having some medical difficulties sorted out finally... >From brief discussions with bero regarding this, he's expressed interest in this and I hope for him to help out, especially considering android is especially his field.. ;) Second major and likely most controversial item on my list is RPM... Considering the advantage we had by having free playground within the RPM project and better collaboration with other distros, this hasn't been the case for years now due to diffficult upstream.. We considered (together with PLD) first just maintaining a cvs git clone repo of rpm5.org where we could follow upstream and do our own work in common branches again where we pulled it all in easily. Then we considered perhaps fork rpm5 and gradually transform it to become compatible with rpm.org, but the heavy amounts of refactoring done within rpm.org makes this a very time consuming, tedious and wasteful job... So easier is it that we move back to rpm.org, ie. with their distro-ecosystem (orwhatever the list was named), most other distros of interest that's still around and having an interest in the golden arch (that I actually was hired initially for working on, as part of my master studies), namely a cleaner, saner, easier, more automatic, more compatible with far less maintenance for the RPM distros to finally share, just like .deb based distros has been since the early morning... So I have like over 300 patches maintained locally since 2011 with pretty much all of my work which hasn't gone upstream meanwhile and all the work invested into it earlier over the years before my cvs commit access was cut off back in nov 2011. So I have quite a large and lonely task cut out for me this time, only help I'm making some hopes of is PLD helping porting parts of their relevant code and functionality parts to rpm.org... If anyone would like to help me out with the job, even rookie apprentices would be accepted, please let me know! ;) So yes, for the next release (not upcoming), the official plan of mine (probably a bit perplexing to some;) is for us to move back to rpm.org... So yeah, I just felt like giving some news, advice, thoughts and meaningful and really important stuff to work on while I just for once felt like making some posts and broaden the perspective related to not strictly packaging and releasing, but thread onto other parts related to governance, our obviously not so bright future and what's needed to ensure our actual survival... I hope to be back to roughly full pace next week, will get back to other posts I've left unreplied sometime next week, might even communicate some more on this list. And for others who wants to reach me, help with stuff etc., if you post the issue on cooker list, the problem, reproducer, etcetcetc. on list, rather than just reporting on IRC that something is broken and I need to fix, then I can probably way more easily help you diagnose and fix the issue yourself in much shorter time, while everyone learns something and doesn't miss out on important stuff because they weren't present on IRC that exact time, TC meetings at fixed times always crashing with other stuff etcetcetc... It's fucking impossible for anyone to follow anything unless they live on IRC and have the same dedicated amount of time and hours, same level of participation or what not... So many stupid decissions even gets both raised during these TC (which we all rejected two years ago in advance after several discussions with all having outcome in favour against having a TC), voted on and decided during these meetings with no trace of any previous or later information about them beyond what the meeting log (which you just don't feel like reading through whole of at once on a regular basis, especially not when it's all already has taken place and you have limited ability to even comment on it... Well, I wasn't meaning to write much at all, so let's hope what I wrote was coherent, sane and not coming off as insulting anyone or leave too many holes in my loud thinking for now... Cya next week or something... ;) -- Kind Regards, Per Øyvind
_______________________________________________ OM-Cooker mailing list [email protected] http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
