Manish Chakravarty wrote: > Hi All, > > > my two cents: > > > *How easily can a new developer join the BeleniX project? > - We'll be moving to SFE.. where will the belenix sources be hosted? > - Are we setting up rules to give contributor status? > - Is there a need for a constitution for the belenix community? > > *Building BeleniX > - We had discussed checking the performance of a gcc-built belenix > prototype and going ahead with it. Is this still in the plans? > This was discussed due to the inablity to redistribute Sun Studio > freely. It's currently only freely downloadable. > > > I we cant redistribute BeleniX freely. But there is no problem in > distributing binaries compiled from Sun Studio.
BeleniX is freely re-distributable. We had an intention to bundle SUN Studio with BeleniX but, SUN Studio can't be re-distributed. Essentially the point is the toolchain used to build BeleniX components is not completely free. However a gcc-built BeleniX distro from ground up is a massive proposition requiring a complete distro-specific build system and a separately maintained package repository. It is not practical given the limited resources of the BeleniX team. Rather it will be practical to base as much of BeleniX work based on existing community effort as possible. Leverage off Indiana and existing Pkg repositories etc. will avoid having to separately maintain a complete distro stack and better participate in OpenSolaris community developments and contributions. > > How about we try a quick and dirty build of KDE4 on belenix? > It already builds well on S10. > I am upbeat about KDE4 because KBE ( the build system) is designed to > work on S10, has very few requirements (it pulls all the stuff it > needs from the net ) and should work without a problem > I would be interested in trying this out. Fantastic. There will be a Native Zone based build environment available for BeleniX quite soon, based off the distro constructor. I will send out a notification once that is available for download on Genunix. In the meantime I am getting KDE3 spec files into the SFE repository. These are gcc-built and I am quite happy with the performance I am getting. I am on KDE 3.5.8 right now and it's stable. > > Since the build system is being migrated to .spec files, we would end > up with a scenario like > > ON ==> OpenSolaris > X ==> OpenSolaris The plan is to pull all OpenSolaris consolidations and community contributions from pkg.opensolaris.org saving a huge amount of effort. Whatever is not on pkg.opensolaris.org is to be built out of SFE which includes the KDE stuff below. In the longer run the intention is to have a pkg.belenix.org that is synced up with pkg.opensolaris.org and contains additional packages, some BeleniX-specific. > KDE ==> SpecFiles > other Software ==> SFE > > Which would reduce effort required for maintenance , help us > concentrate on the branding, look and feel and general end-user > experience of belenix. > > How does this sound? Precisely. That is the intention to leverage OpenSolaris community efforts as much as possible and concentrate on value-addition. > > Can I have a copy of the belenix sources in the next BOSUG meet? Let > me try and build KDE4 on this. May be "borrow" a few Sabayon tricks > for belenix? Sure. > > > *Website issues > - The website needs to be upgraded. How do we find new artwork. > - How good is the current bugs database? > - Can we have all the links resolve to belenix.org > <http://belenix.org>? (and not to > sarovar or genunix) > > * An alpha release > -Can we have a quick alpha release before the 0.7? This could be > distributed minimally on the list and we can try it out on as many > different types of hardware to clean up issues that linger on after > release (like the math library issue in 0.6 and install issue in 0.6*) > > > BeleniX 0.7 Alpha (or call it Belenix KDE4 Developer Preview ;) if you > so wish ) makes sense. Belenix is of course a KDE based distribution. > > Can we sync up at the next BOSUG meet? I'd like to take the last > Belenix build, put SunStudio and KBE on it and give KDE4 a try on Belenix. Better to use the Indiana environment since that is what BeleniX 0.7 will be based on. Use distro constructor and rebuild a new Indiana ISO based off the current pkg repo. Glyn sent out instructions on how to setup a JDS CBE in Indiana, KBE should be no different. > > > > * Other topics? > > Let's take cues from Sabayon and make the end-user experience a little > more polished. Yes. > > > If you are willing to take up one of the tasks, join into this > discussion with your thoughts. > One way to contribute to BeleniX right now is to contribute to the Spec Files Extra (SFE) repository. Add new packages to that or build and debug existing packages on Solaris Express or better Indiana. Regards, Moinak. > > Regards > Anil > _______________________________________________ > belenix-discuss mailing list > http://mail.opensolaris.org/mailman/listinfo/belenix-discuss > <http://mail.opensolaris.org/mailman/listinfo/belenix-discuss> > http://groups.google.com/group/belenix-discuss > > > > > -- > Warm Regards, > Manish Chakravarty > ---- > Associate Software Developer > Spike Source > +919980250606 > --- > ------------------------------------------------------------------------ > > _______________________________________________ > belenix-discuss mailing list > http://mail.opensolaris.org/mailman/listinfo/belenix-discuss > http://groups.google.com/group/belenix-discuss >
