Issues to Be Raised at the Next Board Meeting: Difference between revisions

From SoylentNews
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
If there is an issue that you would like to be raised at the next Board meeting, please include it in the list below. The list will be cleared following each meeting. If you feel that your issue was not adequately addressed at the meeting, please feel free to add it to the list again, with additional detail as needed, and it will be raised at the following meeting.
If there is an issue that you would like to be raised at the next Board meeting, please include it in the list below. The list will be cleared following each meeting. If you feel that your issue was not adequately addressed at the meeting, please feel free to add it to the list again, with additional detail as needed, and it will be raised at the following meeting.


==Proposed next meeting==
==Next meeting==
Time: To Be Confirmed<br />
Time: 11pm UTC (7pm EDT)<br />
Place: irc.sylnt.us:6667/6697#staff<br />
Place: irc.sylnt.us:6667/6697#staff ([http://50.116.18.95:3989/ Webchat])<br />
Chair: To Be Confirmed
Chair: To Be Determined
<p>From the "Site News" slashbox on http://soylentnews.org:</p>
<blockquote>The next general staff and board meeting for the site will be on Wednesday, August 20th, at 7PM EDT (11PM UTC) in #staff on our IRC network. All are welcome to attend.</blockquote>


==Issues==
==Issues==
* Issue 1: Add support for crypto-currency via bitpay.com or gocoin.com for Subscription payment method [[User:Mrcoolbp|mrcoolbp]] ([[User talk:Mrcoolbp|talk]]) 17:59, 18 July 2014 (UTC)
* Issue 1: What mechanism should we use to transfer important assets (accounts, domains, database, other rights, etc.) to the corporation? [[Mechanisms_for_the_Transfer_of_Assets_to_SoylentNews_PBC|Here is a discussion of possible mechanisms.]] [[User:BlackHole|BlackHole]]
* Issue 2: Currently our hosting costs are high for the amount of traffic we have, is there any way we can reduce that with minimal drawbacks? I realize this has been discussed before, and that our current setup allows us some room for growth, but as I understand additional nodes could be spun up as needed. [[User:Mrcoolbp|mrcoolbp]]
* Issue 2: Notification best practices for future Staff and Board meetings. This meeting was not announced to the staff email list, nor the topic blurb on #Staff.
* Issue 3: Enrol in the [https://spideroak.com/ SpiderOak] Affiliate Program. See the [http://www.shareasale.com/shareasale.cfm?merchantID=29362 ShareASale page] for more information. [[User:Mrcoolbp|mrcoolbp]] ([[User talk:Mrcoolbp|talk]]) 16:38, 29 July 2014 (UTC)
* Issue 3:
* Issue 4: Would we be better off just selling "gold stars" than swag? [[User:Mrcoolbp|mrcoolbp]]
* Issue 5: What mechanism should we use to transfer important assets (accounts, domains, database, other rights, etc.) to the corporation? [[Mechanisms_for_the_Transfer_of_Assets_to_SoylentNews_PBC|Here is a discussion of possible mechanisms.]] [[User:BlackHole|BlackHole]]
* Issue 6: Notification best practices for future Staff and Board meetings. This meeting was not announced to the staff email list, nor the topic blurb on #Staff.

Revision as of 01:08, 21 August 2014

If there is an issue that you would like to be raised at the next Board meeting, please include it in the list below. The list will be cleared following each meeting. If you feel that your issue was not adequately addressed at the meeting, please feel free to add it to the list again, with additional detail as needed, and it will be raised at the following meeting.

Next meeting

Time: 11pm UTC (7pm EDT)
Place: irc.sylnt.us:6667/6697#staff (Webchat)
Chair: To Be Determined

Issues

  • Issue 1: What mechanism should we use to transfer important assets (accounts, domains, database, other rights, etc.) to the corporation? Here is a discussion of possible mechanisms. BlackHole
  • Issue 2: Notification best practices for future Staff and Board meetings. This meeting was not announced to the staff email list, nor the topic blurb on #Staff.
  • Issue 3: