S h i v wrote:
> On 10/27/07, *Tim Spriggs* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
> wrote:
>
>
> I chatted with Shiv and there is a short deadline for topics. It seems
> that there is a technical group that could potentially be
> interested in
> Nexenta but we need to come up with a list of projects that can be
> handed to someone or maybe even a small group to accomplish. I would
> appreciate any ideas from the community that I can formalize and
> can be
> presented. Some ideas:
>
> (advanced elements) Nexenta autobuilder
> - script to "Nexentize" an existing Ubuntu/Debian package
>
> (easy-moderate) Port packages that do not currently compile directly
> from Ubuntu/Debian sources:
> - gcc/gcj
> - some kind of full java sdk
> - db4.6 (and other versions)
> - others?
>
> (advanced) Enhance the zones script to support installing:
> other forms of linux
> other forms of OpenSolaris
>
> (Very advanced) Enhance dpkg/apt to support shared filesystems in
> a zone
>
> (easy) Test packages/file reports
> (moderate) submit patches
>
> I'm sure there is a lot more but I'm hoping others will help fill this
> list in so we can pick/choose. Also, if you feel like
> mentoring/overlooking a project then that would be appreciated. The
> topic deadline is Monday Oct 29 (this coming Monday). The final
> (detailed) deadline is Monday Nov 5.
>
>
>
> The dates of the program are revised to 3-Nov for initial inputs (it
> would help if I can get the input 1day earlier). Final deadline is
> 14-Nov.
>
> The list above looks good. The qualifiers easy, moderate, advanced are
> helpful.
> A couple of them is not evident, ex: what is it about Nexentizing the
> ubuntu packages. Is it picking the ubuntu source packages and applying
> nexenta specific patches to come up with binaries for nexenta ?
> Any sort of regression test suites for NCP release?
> Are there other forms of contributions required - website
> maintenance/administration, art-work, documentation.
>
> ~Shiv
>
Nexentize is my own lingo for taking a Ubuntu package and making it
conform to Nexenta. This is trivial for a large number of packages as it
is mostly changing version information and recompiling the package.
There are some packages that require a lot more than that.
Regression testing would be a great idea. Maybe we could have a zone
project that attempts to install packages to verify their dependency
lists and ultimately check for basic package conflicts. We could put a
pass/fail state into a database table and then roll the zone back to a
pre-installation state and start over again on the next package in a list...
I'm happy doing administration, Martin is heading up website and art
work, documentation is always needed. I'll be writing some documentation
soon, it could always be added to. Some kinds of documentation that we need:
blog entries of how to do basic things in Nexenta or even experience
with Nexenta
package system documentation
installation system documentation
Also, another great project would be to either fixup the Nexenta
installer or even rebuild it if someone has enough ambition.
Sorry for the late notice, I had to go on a trip on short notice. I just
got back. If you pick and choose from these I can try to write some
longer explanations of each one so interested parties can read more
about a potential project.
Thanks,
-Tim
_______________________________________________
gnusol-users mailing list
[email protected]
http://lists.sonic.net/mailman/listinfo/gnusol-users
