community:meetings:2011-09-23
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
community:meetings:2011-09-23 [2011/09/14 14:25] – created, initial outline bshum | community:meetings:2011-09-23 [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 20: | Line 20: | ||
- Introductions / roll call; paste "/me is < | - Introductions / roll call; paste "/me is < | ||
- Find a volunteers to: | - Find a volunteers to: | ||
- | - Run the meeting: | + | - Run the meeting: |
- | - Take minutes: | + | - Take minutes: |
- Review action items from [[community: | - Review action items from [[community: | ||
- New Business: | - New Business: | ||
- From the [[http:// | - From the [[http:// | ||
- | | + | * This was discussed quite a bit and ended with the following suggestions: |
- | - Conference committee | + | - mrpeters-isl will be maintaining master demo server while brian_f will maintain a current stable release demo server and EC2 image. |
- | - Documentation Interest Group | + | - Weekly (or twice a week) refresh of data, clearly stated on demo server page. mrpeters-isl provided a rudimentary script to auto refresh the data http:// |
- | - Reports Taskforce report | + | - Provide a list of cronjobs/ |
- | - Developer report | + | - The sample data provided by mrpeters-isl will be used on all demos/ |
- | - Governance | + | - Standardize http:// |
- | - Schedule next meeting: | + | * **ACTION**: moodaepo will send an email to the lists with the summary from this discussion for further discussion/ |
+ | | ||
+ | * __June__: We have posted a list of [[http:// | ||
+ | * __Lori__: One of the areas of development the Web Team recognizes is the need to gather info about about Evergreen enhancement ideas and desires into one place so that the community can bounce ideas around and help percolate the most popular ideas to the top and partnerships could be formed to bring those ideas to fruition. | ||
+ | * __Amy__: Based on suggestions put forth by June Rayner, the web team has adopted the following approach to moving forward with the Evergreen website: | ||
+ | - Technical / Platform changes. | ||
+ | - Ongoing maintenance. | ||
+ | - New Content. | ||
+ | - Major site overhauls. | ||
+ | - **Conference committee** [Report by: Chris Sharp & Ben Shum on behalf of Shauna] | ||
+ | * The conference committee is in the process of reviewing the survey results and will be working on conference submissions and tracks soon. The 2013 site selection committee will announce its selection very soon just got a couple of details to nail down about the venue and how funding will work now that the SFC is involved. | ||
+ | - **Documentation Interest Group** [Report by: June Rayner] | ||
+ | * DIG is looking for priorities for documentation development so please email DIG if you have any thoughts. They also have new documentation added for reporter data sources. | ||
+ | - **Reports Taskforce report** | ||
+ | * They postponed their last meeting so there wasn't much to report. They will probably look through the reporter data sources documentation DIG recently completed. Here are the [[evergreen-reports: | ||
+ | - **Developer report** [report by: dbs] | ||
+ | * 2.1.0 will be released the week of the 26th, if all goes well. | ||
+ | * **ACTION**: phasefx will send out an email regarding end of life for 2.0/1.6, modifying support statement to say " | ||
+ | - **Governance | ||
+ | * The Evergreen Oversight Board met on July 19th and August 16th. This is a brief summary of these two meetings, as well as a conference planning phone call on September 23rd between members of the Board and Bradley Kuhn of the Software Freedom Conservancy. Transfer of funds to the Software Freedom Conservancy: | ||
+ | * The Board is also looking to transfer the Evergreen domains to the SFC. | ||
+ | * The Board will also be drafting some guidelines and looking for community feedback on the following communication issues: how do you propose ideas and get feedback from the community; how to bring a problem to the community' | ||
+ | * Board elections: | ||
+ | * **ACTION**: Amy will send an email to the Web team so they can keep track of the fact that she took over maintaining the [[http:// | ||
+ | - **Schedule next meeting**: [[community: |
community/meetings/2011-09-23.1316024706.txt.gz · Last modified: 2022/02/10 13:34 (external edit)