<span style="font-family: verdana,sans-serif;" dir="ltr">2008/10/31 Dagobert Michelsen <<a href="mailto:dam@opencsw.org">dam@opencsw.org</a>></span><br style="font-family: verdana,sans-serif;"><div style="font-family: verdana,sans-serif;" class="gmail_quote">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
> * **Source**.<br></blockquote><div><br>(*) The project should formally adopt GAR for Sol 9 and 10 builds and make use of GAR mandatory for all packages. Future Solaris packaging standards might mean a switch to pkgbuild or something else entirely. Incidentally, not all my packages are in GAR and I don't like it as a tool, however, maintainers having private scripts to build stuff is untransparent and makes taking on the maintenance of an existing package very difficult in some cases.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> * **Key**.<br></blockquote><div><br>(*) The Key should be owned by all of and only the board members.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> * **Board**.<br>For me this is the most important point. The<br>
nomination/election is one of the keys on the meeting.</blockquote><div><br>(*) Can maintainers who don't attend vote?<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> * **Release Process**.<br></blockquote><div><br>You might want to take a look at Hudson, which is a nice Continuous Integration server that I've used for automated builds in the past.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> * **Distributed**.<br><br>
I don't know if distribution is really that good</blockquote><div><br>+1<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">. ... It may be sufficient to replicate the server<br>
backups to different people so the infrastructure can be<br>
rebuild quickly if anything happens. </blockquote><div><br> (*) The board members should maintain the infrastructure (delegating to corporations or people as they see fit). Everything should be replicated in two places, ideally I guess one in Europe and one in North America. LDAP, SVN, DNS, web servers, wiki servers... all of these things can be made to work in a fully redundant fashion across a WAN. NFS might be a struggle though.<br>
</div>(*) I've got one more, and this is probably going to be a little controversial... we should move out of /opt/csw and into /opt/opencsw. Blastwave Inc is still distributing into /opt/csw and the scope for end user confusion and incompatible software releases is huge. Although this sounds like a lot of work, if everything is in GAR, and everything needs to be rebuilt for Sol 9 in the next six months, it's really not a lot of extra work. I've got big reservations about maintaining stuff through opencsw that installs into /opt/csw.<br>
</div><br style="font-family: verdana,sans-serif;"><span style="font-family: verdana,sans-serif;">-- </span><br style="font-family: verdana,sans-serif;"><font size="1"><span style="font-family: verdana,sans-serif;">Gary Law</span><br style="font-family: verdana,sans-serif;">
<span style="font-family: verdana,sans-serif;"><a href="mailto:glaw@opencsw.org">glaw@opencsw.org</a></span></font>