Zope-Announce

zope-announce@zope.dev

January 2011

2 participants
2 discussions

Announcement: 2011 Zope Foundation Board Elections and General Meeting
by Tres Seaver 27 Jan '11

27 Jan '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (apologies in advance for the cross-post: we need this to reach the whole Zope community). The Zope Foundation board is pleased to announce that the regular 2011 general meeting of the foundation will be held on Wednesday, 16 March 2011, at 15:00 UTC. The meeting will be conducted via IRC at the following channel: irc://irc.freenode.net/#zope-foundation Prior to that meeting, the current board will conduct an elections in which foundation members will select seven (7) board members in accordance with the foundation bylaws[1]. Summary - ------- - - Nominations open via the foundation(a)zope.org mailing list until Friday, 2011-02-11. - - Voting via e-mail to a closed mailing list, from Wednesday, 2011-02-16 through Friday, 2011-03-04. - - Votes tallied by representatives of the current board, using "Meek and Warrent STV" method using OpenSTV software. - - General meeting and seating of the new board, Wednesday, 2011-03-16. Procedure for Elections - ----------------------- The procedure for the elections is as follows: - - Foundation members may nominate any member by responding to the board's announcement on the foundation(a)zope.org mailing list. Nominations will remain open until Friday, 2011-02-11, 23:00 UTC. - - At the close of the nominations period, the board will create a new mailman list, 'zf-elections-2011', and approve all ZF members to post to the list.. In order to preserve anonymity of votes, foundation members will not be subscribers to the list; access to the list archives will be restricted to the "tellers" appointed by the board. - - On Wednesday, 2011-02-16, the Secretary will send an e-mail announcing the opening of the voting period. This e-mail will contain the ballot, with careful instructions about how to rank preferences in the reply. The Reply-to header of this e-mail will be set to the 'zf-elections-2011' list. - - ZF members will vote by replying to that e-mail. Voting will remain open until Friday, 2011-03-04, 23:00 UTC. - - At the close of voting, the board will appoint two of its members as "tellers." The tellers will use the list archive to tabulate the members' votes, using the OpenSTV application[2] configured to use the Meek and Warren STV method[3]. The tellers will report the election results, along with the raw tallies, at a special board meeting to be held on Tuesday, 2011-03-15, 15:00 UTC. - - After canvassing the results from the tellers, the board will notify all nominees of the success / failure of their candidacy, thanking them for their willingness to serve. - - At the general meeting, the last item on the agenda will the announcement of the election results, including a vote to "seat" the board. An online version of this announcement is available at: http://foundation.zope.org/news/2011_election_and_general_meeting/ References - ---------- [1] http://foundation.zope.org/bylaws/zope_foundation_bylaws.pdf [2] http://stv.sourceforge.net/aboutopenstv [3] http://stv.sourceforge.net/votingmethods/meek Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1B8owACgkQ+gerLs4ltQ7OaACfSBCwcbLsELAk/n9eW0CblmMz UvcAn0a1hIhLiocRo8GG431ccPnzDK7/ =2p6F -----END PGP SIGNATURE-----

1 0

Grok 1.3 released!
by Jan-Wijbrand Kolman 20 Jan '11

20 Jan '11

Hi, The Grok development team is happy to announce the Grok 1.3 release! Where the previous release was mostly about slimming down the dependency hierarchy of packages that comprises Grok, this release brings several important changes in functionality typically found Grok-based applications. Grok 1.3 is based on the Zope Toolkit 1.1c1 release! Since the ZTK 1.1 release drops Python-2.4 support and gains Python 2.7 support, it was able to update quite a number of packages, most notably the ZODB. Grok does currently not need to override any version of packages defined in the ZTK! The list of Grok specific package version can be found here: http://grok.zope.org/releaseinfo/1.3/versions.cfg To upgrade existing project you might find the upgrade notes helpful, to be found here: http://grok.zope.org/doc/1.3/upgrade.html Amongst other changes, Grok 1.3 brings: * The long awaited support for the most recent martian version. * The long awaited merge of the template registry refactoring. This should result in considerable less spurious warnings concerning unassociated templates. * Integration of the Fanstatic [1] library and WSGI components. From the Fanstatic website: """ Fanstatic is a small but powerful framework for the automatic publication of resources on a web page. Think Javascript and CSS. It just serves static content, but it does it really well. """ The "static" directory functionality in Grok based projects is now based on Fanstatic and the compatibility layer provided by zope.fanstatic [2]. * Removal of the automatic test discovery and registration that was provided by the z3c.testsetup package. For newly created projects, the grokproject tool will layout examples of setting up test suites. Note that this is a first step in the way towards more drastic improvements in regards to test discovery and running tests. Other important notes: * The updated grokproject tool will not be able to build new project based on Grok version < 1.3. * Besides working on code, the Grok community is also working on improving the documentation, both the "official" documentation and the "community"-driven efforts. This is quite an undertaking and not yet finished. We realize this release will again bring quite some structural changes that might affect your projects in some way. Please let us know when you run into problems upgrading your projects on the grok-dev mailing list or on the #grok IRC channel. We will try to help and it will also help us, the Grok developers, by fixing bugs and other issues. [1] http://fanstatic.org/ [2] http://pypi.python.org/pypi/zope.fanstatic/

1 0