Hello, I just started working on this project this week-end (BTW, I'm alien_ on IRC), and I already have a few 'fundamental' noob questions or concerns regarding the way this infrastructure is built and on how we use our tools such as osc, OBS, gerrit and git :-)
-I noticed we store the full tarballs inside our repos and in OBS. git is not good at it and there's a lot of wasted space because of this. Could we just have the sources fetched during compile time and tracked by the build scripts similar to the way Gentoo's portage works? I know that this might mean we should rewrite OBS or ask the OBS developers to do it for us. Are they accepting feature requests from us? -I find it a bit awkward to use two versioning tools for development, can't osc just reuse the local git repo instead of implementing its own versioning. I'm thinking about our git repo having a remote inside OBS and one in our gerrit, and using just git for all the versioning instead of osc. -is the mer infrastructure opened for stuff belonging more to the UX projects, such as ex-meego packages and so on? could we have our gerrit and git repos shared with anyone willing to be a part of this 'ecosystem' and having the same review process, source repo for package data, documentation and so on for all of them? I find it hard to find various UX packages spread out all over the OBS, many in abandonware state, when it would be much easier to find their latest version in our gerrit. -is there a way to get OBS to integrate better with a workflow that is a bit more into work with upstream projects? I am thinking about having it support transparently source directories checked out from all over the internet, such as from gitorious, instead of pre-built source archives for everything. I know that many projects are only available as source tarballs, but there are quite a lot of them who use git now and we should do better for them if possible. -I would appreciate some documentation on the way we're supposed quickly iterate on development of applications running inside the mer/nemo image, perform debugging and deploy quick fixes and not only for interpreted languages which can be written on the device, but for example by using the image and the osc/OBS toolchain from whithin the QtSDK. Is there any and I am just too blind to see it? I'm looking forward for your feedback, and thanks for the patience to read this, it got longer than I expected :-) Cheers, Cristian
