On 2/28/07, mpb <[EMAIL PROTECTED]> wrote: > I might be willing to volunteer to manage/edit the wiki. I've been > using Gobo (Rootless) for under 2 weeks and have 9+ years experince > with a variety of Linux distributions and also with FreeBSD. > > But I have a few questions: > > 1) What is the roadmap for Gobo 014?
We're focusing on stability for this release. We're doing a huge work trying to fix all reported bugs since 013, which include problems in the installer, the live cd, adding facilities for compiling kernel modules and installing new kernel images and printing support. NTFS-3G is also going to debut, so that full NTFS write support can be there for those sharing the disk with a Windows OS. There were also many, many fixes and enhancements in Compile, Scripts and Manager since then, as reported in the mailing lists and in the bugtracker. Of course we're also going to need more documentation, so I think we cannot avoid dedicating some weeks to reorganize the wiki. However, this is a subject for another thread. > 2) What is the roadmap for Compile and Scripts? Compile and Scripts had both *a lot* of work since 013. Support for package signature is finally well implemented on Scripts, and many bugs were fixed in the meantime. Talking about Compile, we need to dedicate some time to fix some UnionSandbox issues that still exist; some might be unionfs' problems, but that demands some debugging and testing before saying anything else. I would still like to have one more feature in Compile, and I'd love to see it ready for 014: automatically ask the user after he/she created a new recipe to have it submitted to the gobolinux-recipes list, without requiring he/she to do the process of writing an email, attaching the recipe and sending it to the list. I think that this can increase the number of contributed recipes a lot, just because users sometimes forget to send their recipes or don't want to switch applications just to do that. > 3) What is the roadmap for Rootless? Well, Rootless roadmap is basically the same. It should "just work", and then use the infrastructure provided by Compile and Scripts. So, if I would need to define a roadmap for it, I would just say "fix known bugs", which for now are none (all rootless bugs reported were fixed since 013). > (Aside: If you want to recruit new users, these roadmaps should be > cleary published on the Gobo web-site.) Or in the wiki? > 4) Does the Gobo devel team have a common Social Contract (a la > Debian), a core Philosophy (a la Gentoo and Ubuntu), a shared Goal (a > la openSUSE), or a shared vision of why users should choose Gobo (a la > Fedora)? > > http://www.us.debian.org/social_contract > http://www.gentoo.org/main/en/philosophy.xml > http://www.ubuntu.com/ubuntu/philosophy > http://en.opensuse.org/Welcome_to_openSUSE.org > http://fedora.redhat.com/About/ - Social contract: no, we're just a group of friends/partners doing something in common - Core philosophy: given that we all were *greatly* influenced by the free software movement, I think I can say for us all when I say that we're trying to bring back to this same community all we received from it. And this comes in the form of our shared goal.. - Shared goal: to bring new ideas and to show that *NIX can be more intuitive and better. Just take a look at the revolution being made by the guys from the Plan-9 project to have an idea on what "a better *NIX" looks like. - Why users should choose Gobo: We don't want to enforce anyone to use it. People should come and use because they're interested by it, or because they want to try something different, or because they feel this different organization can be of some benefit for them. I just don't take these as "an official view on core philosophy and in shared goal". These are just some snippets of things that I'm pretty sure we all aggree, but they might not be the ideal thing to put as a picture in the wall. > On the following page I can find Roadmaps for 007, 011 and 012. > However, they are explicitly labeled as "Outdated documents, of > historical interest only." Why is there no current roadmap? Only because we really didn't took a time to sit down and write it. I know you're new to the Gobo community, but if you follow the development list you'll see that there is only a small group of people working on the project. We have a real problem of man power, which only gets saned when interested users start to help on the development of some pieces of the puzzle. This doesn't happen all the time, unfortunately, as even our user base is small. > > I have two items I want to have in the 013 release. > > * Linux-pam as primary authentication > > * LVM > > I did not find any replies to Jonas's email. (Perhaps there was IRC > discussion.) LVM support went in 013, with Device-Mapper and support in the kernel for that. A reply was probably forgot to be sent due to activities in the development. > I think there is a Gobo Philosophy, and I think it is a compelling > philosophy. I just don't think it has been written down and published > on the web-site. In my opinion, the Gobo web-site does not clearly > explain to potential new users what the (very compelling) advantages > of Gobo are. Yes, you're right here. Feel free to send suggestions on how to turn the texts better, or just use the wiki for that (which might be used as reference to update the static messages in the main page). > And in the short term I believe that Gobo should certainly NOT try to > compete with Ubuntu in terms of ItJustWorks usability. Sure. Ubuntu has a huge community of developers. I really appreciate the big job they're doing, and certainly would love to be able to dedicate myself full time on this together with many other guys. But let's face the reality and try to do the best we can ;-) Cheers, -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
