https://wiki-dev.pumpingstationone.org/mediawiki/api.php?action=feedcontributions&feedformat=atom&user=Hef 2026-04-10T10:17:39Z User contributions MediaWiki 1.43.6 https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Member_Storage_Registry&diff=43732 2021-02-21T15:43:11Z

<p>Hef: Undo revision 43725 by Garynhouse (talk)</p> <hr /> <div>== '''NOTE: Storage Review August 2020''' ==<br /> <br /> '''The General Operations Team is charged with Reviewing Member Storage and updating all records. We have inventoried and SURPRISE! this registry wass very inaccurate. We have contacted members with storage rights and those occupying storage inappropriately. over the next weeks, we will be working to open up space and even renumbering the general area lockers. On August 26, 2020, we renumbered lockers and relabeled all shelves and lockers.<br /> <br /> Do not edit this page. If you need a new space, please contact the General Operations Team so that we can incorporate that change into the new accurate records.<br /> <br /> If you find something on this page that seems inaccurate, Please contact the affected member or the General Ops Team. Please do not edit other members' entries.<br /> <br /> You should use the same name here that you have listed on [https://membership.pumpingstationone.org the members site] so that we can verify your membership status. This will help you avoid your storage space getting ticketed and you having to do something about it later.'''<br /> <br /> == Catwalk Shelf Registry ==<br /> <br /> ''' -Alpha Alpha designations refer to mini shelves used for PS1 official projects '''<br /> <br /> The catwalk is where many of our [[Systems]] infrastructure is located. Additionally, member shelves are on the catwalk.<br /> <br /> '''Please do not store items on the catwalk, except on member shelves. Loose items will be ticketed'''<br /> <br /> On the catwalk, numbering starts with the upper left shelf and goes down, then across.<br /> {| class=&quot;wikitable&quot;<br /> | C A || <br /> |-<br /> | C B || <br /> |-<br /> | C C || Andrew Morris<br /> |-<br /> | C D || <br /> |-<br /> | C E || <br /> |-<br /> | C F || <br /> |-<br /> | C G || <br /> |-<br /> | C H || <br /> |-<br /> | C I || <br /> |-<br /> | C J || <br /> |-<br /> | C K || <br /> |-<br /> | C01 || Ron Olson<br /> |-<br /> | C02 || Jennie Plasterer<br /> |-<br /> | C03 || Mark V<br /> |-<br /> | C04 || Erik Wessing<br /> |-<br /> | C05 || Sam Paris<br /> |-<br /> | C06 || McKenzie Reed<br /> |-<br /> | C07 || <br /> |-<br /> | C08 || <br /> |-<br /> | C09 || Darlynn Cole<br /> |-<br /> | C10 || Aushra Abouzeid<br /> |-<br /> | C11 || Ryan Pierce<br /> |-<br /> | C12 || <br /> |-<br /> | C13 || <br /> |-<br /> | C14 || <br /> |-<br /> | C15 || Ananda Stevens<br /> |-<br /> | C16 || <br /> |-<br /> | C17 || Alex Zhu<br /> |-<br /> | C18 || Tatjana Paunesku<br /> |-<br /> | C19 || <br /> |-<br /> | C20 || Ashish Jasani <br /> |-<br /> | C21 || Ed Bennett<br /> |-<br /> | C22 || Anna Yu<br /> |-<br /> | C23 || Brandon Belfontaine<br /> |-<br /> | C24 || <br /> |-<br /> | C25 || Rob Riggs (Colorado Rob)<br /> |-<br /> | C26 || Sky Nova<br /> |-<br /> | C27 || <br /> |-<br /> | C28 || Dan Locks<br /> |-<br /> | C29 || <br /> |-<br /> | C30 || Sean Blum<br /> |-<br /> | C31 || Jacob Dawson<br /> |-<br /> | C32 || David Fell<br /> |-<br /> | C33 || Elizabeth Koprucki<br /> |-<br /> | C34 || Mike Gucciard<br /> |-<br /> | C35 || <br /> |-<br /> | C36 || <br /> |-<br /> | C37 || Abel Greenwald<br /> |-<br /> | C38 || <br /> |-<br /> | C39 || <br /> |-<br /> | C40 || Hef<br /> |-<br /> | C41 || Tim Bielawa<br /> |-<br /> | C42 || <br /> |-<br /> | C43 || Sevin Straus<br /> |-<br /> | C44 || Paul Rapoport<br /> |-<br /> | C45 || Eric Stein<br /> |-<br /> | C46 || <br /> |-<br /> | C47 || <br /> |-<br /> | C48 || <br /> |-<br /> | C49 || Joe Mertz<br /> |-<br /> | C50 || <br /> |-<br /> | C51 || Ben StaGL <br /> |-<br /> | C52 || Brian Barnt<br /> |-<br /> | C53 || <br /> |-<br /> | C54 || <br /> |-<br /> | C55 || Andrew Camardella<br /> |-<br /> | C56 || <br /> |-<br /> | C57 || Daniel Baltudis<br /> |-<br /> | C58 || Carl Karsten<br /> |-<br /> | C59 || Brian Chojnowski<br /> |-<br /> | C60 || <br /> |-<br /> | C61 || <br /> |-<br /> | C62 || Daniel Burke<br /> |-<br /> | C63 || Zlatan Klebic<br /> |-<br /> | C64 || Tony Vetter<br /> |-<br /> | C65 || <br /> |-<br /> | C66 || Eddie Muela<br /> |}<br /> <br /> == General Work Area Shelves ==<br /> In the general area, numbering starts with the upper left shelf and goes down, then across.<br /> <br /> {| class=&quot;wikitable&quot;<br /> | G01 || <br /> |-<br /> | G02 || Ben Marshall<br /> |-<br /> | G03 || <br /> |-<br /> | G04 || <br /> |-<br /> | G05 || <br /> |-<br /> | G06 || Carlos Garcia<br /> |-<br /> | G07 || <br /> |-<br /> | G08 || Ben Starett<br /> |-<br /> | G09 || Chris Iacullo<br /> |-<br /> | G10 || <br /> |-<br /> | G11 || <br /> |-<br /> | G12 || Zack Sasnow<br /> |-<br /> | G13 || William Thompson<br /> |-<br /> | G14 || Paulina Hubli<br /> |-<br /> | G15 || <br /> |}<br /> <br /> == Locker Registry ==<br /> <br /> The beige lockers between the general work area and the [[:Category:Cold_Metals|Cold Metals area]] <br /> <br /> {| class=&quot;wikitable&quot;<br /> | GL 01 || Ralph Brendler<br /> |-<br /> | GL 02 || Drew Reynolds move from l24 1.1<br /> |-<br /> | GL 03 || McTavish McArdle<br /> |-<br /> | GL 04 || <br /> |-<br /> | GL 05 || <br /> |-<br /> | GL 06 || Jim Brink<br /> |-<br /> | GL 07 || <br /> |-<br /> | GL 08 || <br /> |-<br /> | GL 09 || Peter Thomsen<br /> |-<br /> | GL 10 || <br /> |-<br /> | GL 11 || Eric Beauchamp<br /> |-<br /> | GL 12 || <br /> |-<br /> | GL 13 || <br /> |-<br /> | GL 14 || <br /> |-<br /> | GL 15 || <br /> |-<br /> | GL 16 || Earl Wood<br /> |-<br /> | GL 17 || <br /> |-<br /> | GL 18 || Brian Desmond<br /> |-<br /> | GL 19 || <br /> |-<br /> | GL 20 || <br /> |-<br /> | GL 21 || Dubi Kaufman<br /> |-<br /> | GL 22 || Drew Deitch<br /> |-<br /> | GL 23 || <br /> |-<br /> | GL 24 || <br /> |-<br /> | GL 25 || <br /> |-<br /> | GL 26 || <br /> |-<br /> | GL 27 || Jonny Panic Rodriguez<br /> |-<br /> | GL 28 || <br /> |-<br /> | GL 29 || Nemanja Simeunovic<br /> |-<br /> | GL 30 || <br /> |-<br /> | GL 31 || Charles Barker<br /> |-<br /> | GL 32 || <br /> |-<br /> | GL 33 || <br /> |-<br /> | GL 34 || <br /> |-<br /> | GL 35 || <br /> |-<br /> | GL 36 || (there is no 36. its a mystical magical hole in the universe..<br /> |-<br /> | GL 37 || Derek Bever<br /> |-<br /> | GL 38 || <br /> |-<br /> | GL 39 || Daron Wooding<br /> |-<br /> | GL 40 || <br /> |-<br /> | GL 41 || <br /> |-<br /> | GL 42 || <br /> <br /> |}<br /> <br /> <br /> <br /> <br /> [[Category:Registry]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Member_Storage_Registry&diff=43724 2021-02-17T19:13:41Z

<p>Hef: </p> <hr /> <div>== '''NOTE: Storage Review August 2020''' ==<br /> <br /> '''The General Operations Team is charged with Reviewing Member Storage and updating all records. We have inventoried and SURPRISE! this registry wass very inaccurate. We have contacted members with storage rights and those occupying storage inappropriately. over the next weeks, we will be working to open up space and even renumbering the general area lockers. On August 26, 2020, we renumbered lockers and relabeled all shelves and lockers.<br /> <br /> Do not edit this page. If you need a new space, please contact the General Operations Team so that we can incorporate that change into the new accurate records.<br /> <br /> If you find something on this page that seems inaccurate, Please contact the affected member or the General Ops Team. Please do not edit other members' entries.<br /> <br /> You should use the same name here that you have listed on [https://membership.pumpingstationone.org the members site] so that we can verify your membership status. This will help you avoid your storage space getting ticketed and you having to do something about it later.'''<br /> <br /> == Catwalk Shelf Registry ==<br /> <br /> ''' -Alpha Alpha designations refer to mini shelves used for PS1 official projects '''<br /> <br /> The catwalk is where many of our [[Systems]] infrastructure is located. Additionally, member shelves are on the catwalk.<br /> <br /> '''Please do not store items on the catwalk, except on member shelves. Loose items will be ticketed'''<br /> <br /> On the catwalk, numbering starts with the upper left shelf and goes down, then across.<br /> {| class=&quot;wikitable&quot;<br /> | C A || <br /> |-<br /> | C B || <br /> |-<br /> | C C || Andrew Morris<br /> |-<br /> | C D || <br /> |-<br /> | C E || <br /> |-<br /> | C F || <br /> |-<br /> | C G || <br /> |-<br /> | C H || <br /> |-<br /> | C I || <br /> |-<br /> | C J || <br /> |-<br /> | C K || <br /> |-<br /> | C01 || Ron Olson<br /> |-<br /> | C02 || Jennie Plasterer<br /> |-<br /> | C03 || Mark V<br /> |-<br /> | C04 || Erik Wessing<br /> |-<br /> | C05 || Sam Paris<br /> |-<br /> | C06 || McKenzie Reed<br /> |-<br /> | C07 || <br /> |-<br /> | C08 || <br /> |-<br /> | C09 || Darlynn Cole<br /> |-<br /> | C10 || Aushra Abouzeid<br /> |-<br /> | C11 || Ryan Pierce<br /> |-<br /> | C12 || <br /> |-<br /> | C13 || <br /> |-<br /> | C14 || <br /> |-<br /> | C15 || Ananda Stevens<br /> |-<br /> | C16 || <br /> |-<br /> | C17 || Alex Zhu<br /> |-<br /> | C18 || Tatjana Paunesku<br /> |-<br /> | C19 || <br /> |-<br /> | C20 || Ashish Jasani <br /> |-<br /> | C21 || Ed Bennett<br /> |-<br /> | C22 || Anna Yu<br /> |-<br /> | C23 || <br /> |-<br /> | C24 || <br /> |-<br /> | C25 || Rob Riggs (Colorado Rob)<br /> |-<br /> | C26 || Sky Nova<br /> |-<br /> | C27 || <br /> |-<br /> | C28 || Dan Locks<br /> |-<br /> | C29 || <br /> |-<br /> | C30 || Sean Blum<br /> |-<br /> | C31 || Jacob Dawson<br /> |-<br /> | C32 || David Fell<br /> |-<br /> | C33 || Elizabeth Koprucki<br /> |-<br /> | C34 || Mike Gucciard<br /> |-<br /> | C35 || <br /> |-<br /> | C36 || <br /> |-<br /> | C37 || Abel Greenwald<br /> |-<br /> | C38 || <br /> |-<br /> | C39 || <br /> |-<br /> | C40 || Hef<br /> |-<br /> | C41 || Tim Bielawa<br /> |-<br /> | C42 || <br /> |-<br /> | C43 || Sevin Straus<br /> |-<br /> | C44 || Paul Rapoport<br /> |-<br /> | C45 || Eric Stein<br /> |-<br /> | C46 || <br /> |-<br /> | C47 || <br /> |-<br /> | C48 || <br /> |-<br /> | C49 || Joe Mertz<br /> |-<br /> | C50 || <br /> |-<br /> | C51 || Ben StaGL <br /> |-<br /> | C52 || Brian Barnt<br /> |-<br /> | C53 || <br /> |-<br /> | C54 || <br /> |-<br /> | C55 || Andrew Camardella<br /> |-<br /> | C56 || <br /> |-<br /> | C57 || Daniel Baltudis<br /> |-<br /> | C58 || Carl Karsten<br /> |-<br /> | C59 || Brian Chojnowski<br /> |-<br /> | C60 || <br /> |-<br /> | C61 || <br /> |-<br /> | C62 || Daniel Burke<br /> |-<br /> | C63 || Zlatan Klebic<br /> |-<br /> | C64 || Tony Vetter<br /> |-<br /> | C65 || <br /> |-<br /> | C66 || Eddie Muela<br /> |}<br /> <br /> == General Work Area Shelves ==<br /> In the general area, numbering starts with the upper left shelf and goes down, then across.<br /> <br /> {| class=&quot;wikitable&quot;<br /> | G01 || <br /> |-<br /> | G02 || Ben Marshall<br /> |-<br /> | G03 || <br /> |-<br /> | G04 || <br /> |-<br /> | G05 || <br /> |-<br /> | G06 || Carlos Garcia<br /> |-<br /> | G07 || <br /> |-<br /> | G08 || Ben Starett<br /> |-<br /> | G09 || Chris Iacullo<br /> |-<br /> | G10 || <br /> |-<br /> | G11 || <br /> |-<br /> | G12 || Zack Sasnow<br /> |-<br /> | G13 || William Thompson<br /> |-<br /> | G14 || Paulina Hubli<br /> |-<br /> | G15 || <br /> |}<br /> <br /> == Locker Registry ==<br /> <br /> The beige lockers between the general work area and the [[:Category:Cold_Metals|Cold Metals area]] <br /> <br /> {| class=&quot;wikitable&quot;<br /> | GL 01 || Ralph Brendler<br /> |-<br /> | GL 02 || Drew Reynolds move from l24 1.1<br /> |-<br /> | GL 03 || McTavish McArdle<br /> |-<br /> | GL 04 || <br /> |-<br /> | GL 05 || <br /> |-<br /> | GL 06 || Jim Brink<br /> |-<br /> | GL 07 || <br /> |-<br /> | GL 08 || <br /> |-<br /> | GL 09 || Peter Thomsen<br /> |-<br /> | GL 10 || <br /> |-<br /> | GL 11 || Eric Beauchamp<br /> |-<br /> | GL 12 || <br /> |-<br /> | GL 13 || <br /> |-<br /> | GL 14 || <br /> |-<br /> | GL 15 || <br /> |-<br /> | GL 16 || Earl Wood<br /> |-<br /> | GL 17 || <br /> |-<br /> | GL 18 || Brian Desmond<br /> |-<br /> | GL 19 || <br /> |-<br /> | GL 20 || <br /> |-<br /> | GL 21 || Dubi Kaufman<br /> |-<br /> | GL 22 || Drew Deitch<br /> |-<br /> | GL 23 || <br /> |-<br /> | GL 24 || <br /> |-<br /> | GL 25 || <br /> |-<br /> | GL 26 || <br /> |-<br /> | GL 27 || Jonny Panic Rodriguez<br /> |-<br /> | GL 28 || <br /> |-<br /> | GL 29 || Nemanja Simeunovic<br /> |-<br /> | GL 30 || <br /> |-<br /> | GL 31 || Charles Barker<br /> |-<br /> | GL 32 || <br /> |-<br /> | GL 33 || <br /> |-<br /> | GL 34 || <br /> |-<br /> | GL 35 || <br /> |-<br /> | GL 36 || (there is no 36. its a mystical magical hole in the universe..<br /> |-<br /> | GL 37 || Derek Bever<br /> |-<br /> | GL 38 || <br /> |-<br /> | GL 39 || Daron Wooding<br /> |-<br /> | GL 40 || <br /> |-<br /> | GL 41 || <br /> |-<br /> | GL 42 || <br /> <br /> |}<br /> <br /> <br /> <br /> <br /> [[Category:Registry]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Variant2&diff=38740 2019-01-09T16:08:38Z

<p>Hef: </p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = [[User:Hef | hef]]<br /> |certification = no<br /> |hackable = no<br /> |serial = 2<br /> |model = It's a thing running a server, probably.<br /> |contact = [[User:Hef | hef]]<br /> |where = doesn't exist yet<br /> }}<br /> <br /> == Ownership ==<br /> Variant2 is a member project, and is not to be used for space infrastructure, and is not to be considered a donation.</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Variant2&diff=38739 2019-01-09T15:54:32Z

<p>Hef: </p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = [[User:Hef | hef]]<br /> |certification = no<br /> |hackable = no<br /> |serial = 2<br /> |model = It's a thing running a server, probably.<br /> |arrived = 2019-2-1<br /> |doesitwork = no<br /> |contact = [[User:Hef | hef]]<br /> |where = doesn't exist yet<br /> |value = not sure<br /> }}<br /> <br /> == Ownership ==<br /> Variant2 is a member project, and is not to be used for space infrastructure, and is not to be considered a donation.</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Variant2&diff=38738 2019-01-09T15:54:20Z

<p>Hef: </p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = [[User:Hef | hef]]<br /> |certification = no<br /> |hackable = no<br /> |serial = 2<br /> |model = It's a server, probably.<br /> |arrived = 2019-2-1<br /> |doesitwork = no<br /> |contact = [[User:Hef | hef]]<br /> |where = doesn't exist yet<br /> |value = not sure<br /> }}<br /> <br /> == Ownership ==<br /> Variant2 is a member project, and is not to be used for space infrastructure, and is not to be considered a donation.</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Variant2&diff=38737 2019-01-09T15:53:08Z

<p>Hef: </p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = {{User:Hef}}<br /> |certification = no<br /> |hackable = no<br /> |serial = 2<br /> |model = <br /> |arrived = 2019-2-1<br /> |doesitwork = no<br /> |contact = hef<br /> |where = doesn't exist yet<br /> |value = not sure<br /> }}<br /> <br /> == Ownership ==<br /> Variant2 is a member project, and is not to be used for space infrastructure, and is not to be considered a donation.</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Variant2&diff=38736 2019-01-09T15:52:42Z

<p>Hef: </p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = hef<br /> |certification = no<br /> |hackable = no<br /> |serial = 2<br /> |model = <br /> |arrived = 2019-2-1<br /> |doesitwork = no<br /> |contact = hef<br /> |where = doesn't exist yet<br /> |value = not sure<br /> }}<br /> <br /> == Ownership ==<br /> Variant2 is a member project, and is not to be used for space infrastructure, and is not to be considered a donation.</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Variant2&diff=38735 2019-01-09T15:52:31Z

<p>Hef: </p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = hef<br /> |certification = no<br /> |hackable = no<br /> |serial = 2<br /> |model = <br /> |arrived = 2019-2-1<br /> |doesitwork = no<br /> |contact = hef<br /> |where = doesn't exist yet<br /> |value = not sure<br /> }}<br /> <br /> == ownership ==<br /> Variant2 is a member project, and is not to be used for space infrastructure, and is not to be considered a donation.</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Variant2&diff=38734 2019-01-09T15:51:36Z

<p>Hef: </p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = hef<br /> |certification = no<br /> |hackable = no<br /> |serial = 1<br /> |model = BeagleBone Black<br /> |arrived = 2019-2-1<br /> |doesitwork = no<br /> |contact = hef<br /> |where = ether<br /> |value = not sure<br /> }}<br /> <br /> <br /> Variant2 is a member project, and is not to be used for space infrastructure, and is not to be considered a donation.</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Variant2&diff=38733 2019-01-09T15:50:34Z

<p>Hef: Created page with &quot;{{Template:EquipmentPage |owner = hef |certification = no |hackable = no |serial = 1 |model = BeagleBone Black |arrived = 2019-2-1 |doesitwork = no |contact = hef |where = eth...&quot;</p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = hef<br /> |certification = no<br /> |hackable = no<br /> |serial = 1<br /> |model = BeagleBone Black<br /> |arrived = 2019-2-1<br /> |doesitwork = no<br /> |contact = hef<br /> |where = ether<br /> |value = not sure<br /> }}</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User_talk:Hef/Vote_on_Property_Protection_Policies&diff=37281 2018-06-18T04:38:39Z

<p>Hef: </p> <hr /> <div><br /> <br /> == TODO ==<br /> * add a liability waiver that PS:One is not responsible for damage to property used at the space.<br /> * Change his or her to They/Their<br /> * Add notes heavily suggesting that property in use at PS:One for an extended length of time receive an equipment page and a label<br /> * Add language to indicate that PS:One is still able to remove property under tidy space<br /> * Add expectation on property owners for handling property removal from the organization.<br /> ** include notification to the membership<br /> ** include timetable expectations, but allow for extenuating circumstances<br /> * Add text that indicates that an owner may reclaim an item after it has been tidy spaced if the item is still retrievable. If the item has been disposed of, and retrieving it is not feasible, the organization is not responsible for reimbursement, repairs, etc.<br /> * Add text indicating that all items are subject to tidy space<br /> * Clean up this paragraph and add it to the language<br /> <br /> &lt;blockquote&gt;<br /> As for restricting access, there are several reasons:<br /> * A property owner may want to ensure that sufficient training is taking place<br /> * The member may be using the tool or service in an abusive, damaging, or unsafe way, and needs their access revoked<br /> * Their may be multiple tiers of maintenance, where the highest levels of maintenance are only perform able by the property owner, or by a select few the property owner has selected.<br /> I'd treat the bullying case and harassment cases similar to any other fundamental disagreement on usage. That is, If the property owner insists on too high a level of training or over restricts utilization in any way, have the owner take the item home. If the owner doesn't do it willingly, apply tidy space to have the item removed from the space.<br /> a case that come to mind outside of harassment and bullying are that the owner insists on a training level for authorization that an area hosts feels is too high, and that the space can purchase similar equipment and apply more approachable authorization<br /> I also feel that in cases of bullying and harassment, there are repercussions available for violating the membership agreement, and would encourage anyone that feels bullied or harassed to pursue them.<br /> &lt;/blockquote&gt;<br /> <br /> <br /> == Specific comments to address ==<br /> * What makes a project a community contribution vs a loan to the space vs a pure personal project?<br /> ** I believe this would be the intent of the project/property owner. I don't see a significant difference between &quot;loan to the space&quot; and &quot;pure personal project&quot;. In all cases, without proper paperwork, the property is not a community contribution, and should be regarding as such taking the associated risks into account. Basically, don't use it if you need to own it and don't own it. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * How can ownership be effectively managed and tracked so as to reduce disputes among members?<br /> ** An EquipmentPage or similar template in the wiki would suffice. They allow both knowledge of current ownership and transfer of ownership. I Think I'll add some supporting text to suggest that but not require it. I'm afraid of people stealing because &quot;It wasn't in the wiki&quot; --[[User:Hef|Hef]] ([[User talk:Hef|talk]])<br /> * What authority does the Board have to set reasonable guidelines for any personal project that is installed into the common space, so as to promote safety, cleanliness, and fairness to all members, yet still encouraging the spirit of JFDI space modification?<br /> ** I believe the &quot;membership agreement&quot; and &quot;Tidy space&quot; already cover this. Do you think there is anything left that needs to be covered that is not already in those 2 policies? --[[User:Hef|Hef]] ([[User talk:Hef|talk]])<br /> * Software and network configuration are nuanced enough that they deserve special mention - especially since there are multiple people modifying these systems over time, multiple software licenses at play, etc.<br /> ** As for modifications of things over time, modifications and maintenance to member owned equipment doesn't &quot;muddy the waters&quot; it still belongs to the person that brought it in. This would apply to software as well. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Member personal data is nuanced enough that it deserves special mention. I believe that members' personal data needs to be protected by the Board per a strong privacy policy; that personal projects are distinct from members' personal data; and that personal projects should never put personal data at risk.<br /> ** Agreed. An organizational privacy policy would need to be followed by anyone doing any kind of data entry related to member data, and anyone doing data entry may need to secure appropriate agreements with vendors of services. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** This is fairly tangential to this proposal, but it would be nice to limit how data collected in the space can be used without permission. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** I believe it would be appropriate for vendors to secure agreements with member's directly where appropriate. e.g. I'd like to send you an email, can I have your email address. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** I think that writing a privacy policy in addition to property protections is a lot of scope creep for what this proposal is trying to accomplish. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Clarify what happens when a member spends their own money to modify the space in a permanent manner.<br /> ** The member should submit a written record that it is a donation, and get a donation receipt. Failing that, if they want to retrieve the permanent modification that is difficult but possible, that's fine. If it's an architectural modification, they are modifying something that has an owner (the space) and ownership doesn't implicitly transfer.<br /> * Define a lightweight, formal process for contributing a personal project to the community.<br /> ** I was thinking any paperwork would do, but I like your suggestion as a streamlined process in the wiki would help. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Create a glossary that defines these terms formally in your proposal.<br /> ** Which terms do you have in mind? I was thinking of dropping the phrase &quot;project, property, or service&quot; and just use &quot;property&quot; and then give a longer definition of property to include these terms, and to clarify I mean created, brought in or purchased. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User_talk:Hef/Vote_on_Property_Protection_Policies&diff=37280 2018-06-18T01:09:46Z

<p>Hef: </p> <hr /> <div><br /> <br /> == TODO ==<br /> * add a liability waiver that PS:One is not responsible for damage to property used at the space.<br /> * Change his or her to They/Their<br /> * Add notes heavily suggesting that property in use at PS:One for an extended length of time receive an equipment page and a label<br /> * Add language to indicate that PS:One is still able to remove property under tidy space<br /> * Add expectation on property owners for handling property removal from the organization.<br /> ** include notification to the membership<br /> ** include timetable expectations, but allow for extenuating circumstances<br /> <br /> <br /> <br /> == Specific comments to address ==<br /> * What makes a project a community contribution vs a loan to the space vs a pure personal project?<br /> ** I believe this would be the intent of the project/property owner. I don't see a significant difference between &quot;loan to the space&quot; and &quot;pure personal project&quot;. In all cases, without proper paperwork, the property is not a community contribution, and should be regarding as such taking the associated risks into account. Basically, don't use it if you need to own it and don't own it. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * How can ownership be effectively managed and tracked so as to reduce disputes among members?<br /> ** An EquipmentPage or similar template in the wiki would suffice. They allow both knowledge of current ownership and transfer of ownership. I Think I'll add some supporting text to suggest that but not require it. I'm afraid of people stealing because &quot;It wasn't in the wiki&quot; --[[User:Hef|Hef]] ([[User talk:Hef|talk]])<br /> * What authority does the Board have to set reasonable guidelines for any personal project that is installed into the common space, so as to promote safety, cleanliness, and fairness to all members, yet still encouraging the spirit of JFDI space modification?<br /> ** I believe the &quot;membership agreement&quot; and &quot;Tidy space&quot; already cover this. Do you think there is anything left that needs to be covered that is not already in those 2 policies? --[[User:Hef|Hef]] ([[User talk:Hef|talk]])<br /> * Software and network configuration are nuanced enough that they deserve special mention - especially since there are multiple people modifying these systems over time, multiple software licenses at play, etc.<br /> ** As for modifications of things over time, modifications and maintenance to member owned equipment doesn't &quot;muddy the waters&quot; it still belongs to the person that brought it in. This would apply to software as well. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Member personal data is nuanced enough that it deserves special mention. I believe that members' personal data needs to be protected by the Board per a strong privacy policy; that personal projects are distinct from members' personal data; and that personal projects should never put personal data at risk.<br /> ** Agreed. An organizational privacy policy would need to be followed by anyone doing any kind of data entry related to member data, and anyone doing data entry may need to secure appropriate agreements with vendors of services. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** This is fairly tangential to this proposal, but it would be nice to limit how data collected in the space can be used without permission. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** I believe it would be appropriate for vendors to secure agreements with member's directly where appropriate. e.g. I'd like to send you an email, can I have your email address. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** I think that writing a privacy policy in addition to property protections is a lot of scope creep for what this proposal is trying to accomplish. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Clarify what happens when a member spends their own money to modify the space in a permanent manner.<br /> ** The member should submit a written record that it is a donation, and get a donation receipt. Failing that, if they want to retrieve the permanent modification that is difficult but possible, that's fine. If it's an architectural modification, they are modifying something that has an owner (the space) and ownership doesn't implicitly transfer.<br /> * Define a lightweight, formal process for contributing a personal project to the community.<br /> ** I was thinking any paperwork would do, but I like your suggestion as a streamlined process in the wiki would help. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Create a glossary that defines these terms formally in your proposal.<br /> ** Which terms do you have in mind? I was thinking of dropping the phrase &quot;project, property, or service&quot; and just use &quot;property&quot; and then give a longer definition of property to include these terms, and to clarify I mean created, brought in or purchased. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User_talk:Hef/Vote_on_Property_Protection_Policies&diff=37279 2018-06-18T00:29:06Z

<p>Hef: </p> <hr /> <div><br /> <br /> == TODO ==<br /> * add a liability waiver that PS:One is not responsible for damage to property used at the space.<br /> * Change his or her to They/Their<br /> * Add notes heavily suggesting that property in use at PS:One for an extended length of time receive an equipment page and a label<br /> * Add language to indicate that PS:One is still able to remove property under tidy space<br /> <br /> <br /> == Specific comments to address ==<br /> * What makes a project a community contribution vs a loan to the space vs a pure personal project?<br /> ** I believe this would be the intent of the project/property owner. I don't see a significant difference between &quot;loan to the space&quot; and &quot;pure personal project&quot;. In all cases, without proper paperwork, the property is not a community contribution, and should be regarding as such taking the associated risks into account. Basically, don't use it if you need to own it and don't own it. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * How can ownership be effectively managed and tracked so as to reduce disputes among members?<br /> ** An EquipmentPage or similar template in the wiki would suffice. They allow both knowledge of current ownership and transfer of ownership. I Think I'll add some supporting text to suggest that but not require it. I'm afraid of people stealing because &quot;It wasn't in the wiki&quot; --[[User:Hef|Hef]] ([[User talk:Hef|talk]])<br /> * What authority does the Board have to set reasonable guidelines for any personal project that is installed into the common space, so as to promote safety, cleanliness, and fairness to all members, yet still encouraging the spirit of JFDI space modification?<br /> ** I believe the &quot;membership agreement&quot; and &quot;Tidy space&quot; already cover this. Do you think there is anything left that needs to be covered that is not already in those 2 policies? --[[User:Hef|Hef]] ([[User talk:Hef|talk]])<br /> * Software and network configuration are nuanced enough that they deserve special mention - especially since there are multiple people modifying these systems over time, multiple software licenses at play, etc.<br /> ** As for modifications of things over time, modifications and maintenance to member owned equipment doesn't &quot;muddy the waters&quot; it still belongs to the person that brought it in. This would apply to software as well. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Member personal data is nuanced enough that it deserves special mention. I believe that members' personal data needs to be protected by the Board per a strong privacy policy; that personal projects are distinct from members' personal data; and that personal projects should never put personal data at risk.<br /> ** Agreed. An organizational privacy policy would need to be followed by anyone doing any kind of data entry related to member data, and anyone doing data entry may need to secure appropriate agreements with vendors of services. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** This is fairly tangential to this proposal, but it would be nice to limit how data collected in the space can be used without permission. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** I believe it would be appropriate for vendors to secure agreements with member's directly where appropriate. e.g. I'd like to send you an email, can I have your email address. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** I think that writing a privacy policy in addition to property protections is a lot of scope creep for what this proposal is trying to accomplish. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Clarify what happens when a member spends their own money to modify the space in a permanent manner.<br /> ** The member should submit a written record that it is a donation, and get a donation receipt. Failing that, if they want to retrieve the permanent modification that is difficult but possible, that's fine. If it's an architectural modification, they are modifying something that has an owner (the space) and ownership doesn't implicitly transfer.<br /> * Define a lightweight, formal process for contributing a personal project to the community.<br /> ** I was thinking any paperwork would do, but I like your suggestion as a streamlined process in the wiki would help. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Create a glossary that defines these terms formally in your proposal.<br /> ** Which terms do you have in mind? I was thinking of dropping the phrase &quot;project, property, or service&quot; and just use &quot;property&quot; and then give a longer definition of property to include these terms, and to clarify I mean created, brought in or purchased. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User_talk:Hef/Vote_on_Property_Protection_Policies&diff=37277 2018-06-18T00:21:23Z

<p>Hef: </p> <hr /> <div><br /> <br /> == TODO ==<br /> * add a liability waiver that PS:One is not responsible for damage to property used at the space.<br /> * Change his or her to They/Their<br /> * Add notes heavily suggesting that property in use at PS:One for an extended length of time receive an equipment page and a label<br /> <br /> <br /> == Specific comments to address ==<br /> * What makes a project a community contribution vs a loan to the space vs a pure personal project?<br /> ** I believe this would be the intent of the project/property owner. I don't see a significant difference between &quot;loan to the space&quot; and &quot;pure personal project&quot;. In all cases, without proper paperwork, the property is not a community contribution, and should be regarding as such taking the associated risks into account. Basically, don't use it if you need to own it and don't own it. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * How can ownership be effectively managed and tracked so as to reduce disputes among members?<br /> ** An EquipmentPage or similar template in the wiki would suffice. They allow both knowledge of current ownership and transfer of ownership. I Think I'll add some supporting text to suggest that but not require it. I'm afraid of people stealing because &quot;It wasn't in the wiki&quot; --[[User:Hef|Hef]] ([[User talk:Hef|talk]])<br /> * What authority does the Board have to set reasonable guidelines for any personal project that is installed into the common space, so as to promote safety, cleanliness, and fairness to all members, yet still encouraging the spirit of JFDI space modification?<br /> ** I believe the &quot;membership agreement&quot; and &quot;Tidy space&quot; already cover this. Do you think there is anything left that needs to be covered that is not already in those 2 policies? --[[User:Hef|Hef]] ([[User talk:Hef|talk]])<br /> * Software and network configuration are nuanced enough that they deserve special mention - especially since there are multiple people modifying these systems over time, multiple software licenses at play, etc.<br /> ** As for modifications of things over time, modifications and maintenance to member owned equipment doesn't &quot;muddy the waters&quot; it still belongs to the person that brought it in. This would apply to software as well. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Member personal data is nuanced enough that it deserves special mention. I believe that members' personal data needs to be protected by the Board per a strong privacy policy; that personal projects are distinct from members' personal data; and that personal projects should never put personal data at risk.<br /> ** Agreed. An organizational privacy policy would need to be followed by anyone doing any kind of data entry related to member data, and anyone doing data entry may need to secure appropriate agreements with vendors of services. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** This is fairly tangential to this proposal, but it would be nice to limit how data collected in the space can be used without permission. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** I believe it would be appropriate for vendors to secure agreements with member's directly where appropriate. e.g. I'd like to send you an email, can I have your email address. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** I think that writing a privacy policy in addition to property protections is a lot of scope creep for what this proposal is trying to accomplish. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Clarify what happens when a member spends their own money to modify the space in a permanent manner.<br /> ** The member should submit a written record that it is a donation, and get a donation receipt. Failing that, if they want to retrieve the permanent modification that is difficult but possible, that's fine. If it's an architectural modification, they are modifying something that has an owner (the space) and ownership doesn't implicitly transfer.<br /> * Define a lightweight, formal process for contributing a personal project to the community.<br /> ** I was thinking any paperwork would do, but I like your suggestion as a streamlined process in the wiki would help. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Create a glossary that defines these terms formally in your proposal.<br /> ** Which terms do you have in mind? I was thinking of dropping the phrase &quot;project, property, or service&quot; and just use &quot;property&quot; and then give a longer definition of property to include these terms, and to clarify I mean created, brought in or purchased. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User_talk:Hef/Vote_on_Property_Protection_Policies&diff=37275 2018-06-17T19:05:12Z

<p>Hef: Created page with &quot;* What makes a project a community contribution vs a loan to the space vs a pure personal project? ** I believe this would be the intent of the project/property owner. I don&#039;...&quot;</p> <hr /> <div>* What makes a project a community contribution vs a loan to the space vs a pure personal project?<br /> ** I believe this would be the intent of the project/property owner. I don't see a significant difference between &quot;loan to the space&quot; and &quot;pure personal project&quot;. In all cases, without proper paperwork, the property is not a community contribution, and should be regarding as such taking the associated risks into account. Basically, don't use it if you need to own it and don't own it. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * How can ownership be effectively managed and tracked so as to reduce disputes among members?<br /> ** An EquipmentPage or similar template in the wiki would suffice. They allow both knowledge of current ownership and transfer of ownership. I Think I'll add some supporting text to suggest that but not require it. I'm afraid of people stealing because &quot;It wasn't in the wiki&quot; --[[User:Hef|Hef]] ([[User talk:Hef|talk]])<br /> * What authority does the Board have to set reasonable guidelines for any personal project that is installed into the common space, so as to promote safety, cleanliness, and fairness to all members, yet still encouraging the spirit of JFDI space modification?<br /> ** I believe the &quot;membership agreement&quot; and &quot;Tidy space&quot; already cover this. Do you think there is anything left that needs to be covered that is not already in those 2 policies? --[[User:Hef|Hef]] ([[User talk:Hef|talk]])<br /> * Software and network configuration are nuanced enough that they deserve special mention - especially since there are multiple people modifying these systems over time, multiple software licenses at play, etc.<br /> ** As for modifications of things over time, modifications and maintenance to member owned equipment doesn't &quot;muddy the waters&quot; it still belongs to the person that brought it in. This would apply to software as well. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Member personal data is nuanced enough that it deserves special mention. I believe that members' personal data needs to be protected by the Board per a strong privacy policy; that personal projects are distinct from members' personal data; and that personal projects should never put personal data at risk.<br /> ** Agreed. An organizational privacy policy would need to be followed by anyone doing any kind of data entry related to member data, and anyone doing data entry may need to secure appropriate agreements with vendors of services. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** This is fairly tangential to this proposal, but it would be nice to limit how data collected in the space can be used without permission. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** I believe it would be appropriate for vendors to secure agreements with member's directly where appropriate. e.g. I'd like to send you an email, can I have your email address. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> ** I think that writing a privacy policy in addition to property protections is a lot of scope creep for what this proposal is trying to accomplish. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Clarify what happens when a member spends their own money to modify the space in a permanent manner.<br /> ** The member should submit a written record that it is a donation, and get a donation receipt. Failing that, if they want to retrieve the permanent modification that is difficult but possible, that's fine. If it's an architectural modification, they are modifying something that has an owner (the space) and ownership doesn't implicitly transfer.<br /> * Define a lightweight, formal process for contributing a personal project to the community.<br /> ** I was thinking any paperwork would do, but I like your suggestion as a streamlined process in the wiki would help. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)<br /> * Create a glossary that defines these terms formally in your proposal.<br /> ** Which terms do you have in mind? I was thinking of dropping the phrase &quot;project, property, or service&quot; and just use &quot;property&quot; and then give a longer definition of property to include these terms, and to clarify I mean created, brought in or purchased. --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 14:04, 17 June 2018 (CDT)</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37269 2018-06-17T16:56:00Z

<p>Hef: </p> <hr /> <div><br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> Pumping Station: One member's are creators of incredible things and are often generous individuals. Sometimes these things get taken for granted or taken advantage of in unfair ways. This vote is intended to protect PS:One members so that they may feel secure in continuing to create and share at PS:One without feeling obligated to give more than they are willing.<br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** Pumping Station: One, NFP may not take ownership of a project, property, or service without explicit consent from the owner.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service. If the reasons for disallowing usage are in conflict with PS:One policies, the property, project, or service may be removed following the Tidy Space policy procedures.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Intentional destruction, tampering, or theft of a person's property, project, or service are not acceptable in any situation, including dispute resolution, but the project, property, or service may still be removed via normal Tidy Space procedures.<br /> ** If the organization has mistakenly acted as the owner of a project, property, or service, It must take all necessary corrective actions to restore rightful ownership of the project, property, or service upon discovering or being informed of the mistake.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37267 2018-06-17T14:05:41Z

<p>Hef: </p> <hr /> <div><br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> Pumping Station: One member's are creators of incredible things and are often generous individuals. Sometimes these things get taken for granted or taken advantage of in unfair ways. This vote is intended to protect PS:One members so that they may feel secure in continuing to create and share at PS:One without feeling obligated to give more than they are willing.<br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** Pumping Station: One, NFP may not take ownership of a project, property, or service without explicit consent from the owner.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Intentional destruction, tampering, or theft of a person's property, project, or service are not acceptable in any situation, including dispute resolution, but the project, property, or service may still be removed via normal Tidy Space procedures.<br /> ** If the organization has mistakenly acted as the owner of a project, property, or service, It must take all necessary corrective actions to restore rightful ownership of the project, property, or service upon discovering or being informed of the mistake.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37254 2018-06-16T12:23:19Z

<p>Hef: /* Background */</p> <hr /> <div><br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> Pumping Station: One member's are creators of incredible things and are often generous individuals. Sometimes these things get taken for granted or taken advantage of in unfair ways. This vote is intended to protect PS:One members so that they may feel secure in continuing to create and share at PS:One without feeling obligated to give more than they are willing.<br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** Pumping Station: One, NFP may not take ownership of a project, property, or service without explicit consent from the owner.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Intentional destruction, tampering, or theft of a person's property, project, or service are not acceptable in any situation, including dispute resolution.<br /> ** If the organization has mistakenly acted as the owner of a project, property, or service, It must take all necessary corrective actions to restore rightful ownership of the project, property, or service upon discovering or being informed of the mistake.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Policies&diff=37253 2018-06-16T12:16:56Z

<p>Hef: Hef moved page User:Hef/Vote on Property Policies to User:Hef/Vote on Property Protection Policies</p> <hr /> <div>#REDIRECT [[User:Hef/Vote on Property Protection Policies]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37252 2018-06-16T12:16:56Z

<p>Hef: Hef moved page User:Hef/Vote on Property Policies to User:Hef/Vote on Property Protection Policies</p> <hr /> <div><br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** Pumping Station: One, NFP may not take ownership of a project, property, or service without explicit consent from the owner.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Intentional destruction, tampering, or theft of a person's property, project, or service are not acceptable in any situation, including dispute resolution.<br /> ** If the organization has mistakenly acted as the owner of a project, property, or service, It must take all necessary corrective actions to restore rightful ownership of the project, property, or service upon discovering or being informed of the mistake.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Vote_on_Property_Policies&diff=37251 2018-06-16T12:16:37Z

<p>Hef: Hef moved page User:Vote on Property Policies to User:Hef/Vote on Property Policies</p> <hr /> <div>#REDIRECT [[User:Hef/Vote on Property Policies]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37250 2018-06-16T12:16:37Z

<p>Hef: Hef moved page User:Vote on Property Policies to User:Hef/Vote on Property Policies</p> <hr /> <div><br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** Pumping Station: One, NFP may not take ownership of a project, property, or service without explicit consent from the owner.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Intentional destruction, tampering, or theft of a person's property, project, or service are not acceptable in any situation, including dispute resolution.<br /> ** If the organization has mistakenly acted as the owner of a project, property, or service, It must take all necessary corrective actions to restore rightful ownership of the project, property, or service upon discovering or being informed of the mistake.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/vote_Draft&diff=37249 2018-06-16T12:14:29Z

<p>Hef: Hef moved page User:Hef/vote Draft to User:Vote on Property Policies</p> <hr /> <div>#REDIRECT [[User:Vote on Property Policies]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37248 2018-06-16T12:14:29Z

<p>Hef: Hef moved page User:Hef/vote Draft to User:Vote on Property Policies</p> <hr /> <div><br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** Pumping Station: One, NFP may not take ownership of a project, property, or service without explicit consent from the owner.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Intentional destruction, tampering, or theft of a person's property, project, or service are not acceptable in any situation, including dispute resolution.<br /> ** If the organization has mistakenly acted as the owner of a project, property, or service, It must take all necessary corrective actions to restore rightful ownership of the project, property, or service upon discovering or being informed of the mistake.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37247 2018-06-16T12:12:16Z

<p>Hef: </p> <hr /> <div><br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** Pumping Station: One, NFP may not take ownership of a project, property, or service without explicit consent from the owner.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Intentional destruction, tampering, or theft of a person's property, project, or service are not acceptable in any situation, including dispute resolution.<br /> ** If the organization has mistakenly acted as the owner of a project, property, or service, It must take all necessary corrective actions to restore rightful ownership of the project, property, or service upon discovering or being informed of the mistake.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37246 2018-06-16T12:11:31Z

<p>Hef: </p> <hr /> <div>To submit a vote fill out the following template with pertinent information and follow voting rules as listed in [[Bylaws#Votes_of_the_Membership]]<br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** Pumping Station: One, NFP may not take ownership of a project, property, or service without explicit consent from the owner.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Intentional destruction, tampering, or theft of a person's property, project, or service are not acceptable in any situation, including dispute resolution.<br /> ** If the organization has mistakenly acted as the owner of a project, property, or service, It must take all necessary corrective actions to restore rightful ownership of the project, property, or service upon discovering or being informed of the mistake.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37245 2018-06-16T12:09:57Z

<p>Hef: </p> <hr /> <div>To submit a vote fill out the following template with pertinent information and follow voting rules as listed in [[Bylaws#Votes_of_the_Membership]]<br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Intentional destruction, tampering, or theft of a person's property, project, or service are not acceptable in any situation, including dispute resolution.<br /> ** If the organization has mistakenly acted as the owner of a project, property, or service, It must take all necessary corrective actions to restore rightful ownership of the project, property, or service upon discovering or being informed of the mistake.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37244 2018-06-16T12:03:30Z

<p>Hef: /* Language */</p> <hr /> <div>To submit a vote fill out the following template with pertinent information and follow voting rules as listed in [[Bylaws#Votes_of_the_Membership]]<br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Intentional destruction, tampering, or theft of a person's property, project, or service are not acceptable in any situation, including dispute resolution.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37243 2018-06-16T12:02:37Z

<p>Hef: /* Language */</p> <hr /> <div>To submit a vote fill out the following template with pertinent information and follow voting rules as listed in [[Bylaws#Votes_of_the_Membership]]<br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A person cannot lose ownership of their project, property, or service, but may be asked to remove the project, property or service.<br /> ** Destruction, tampering, or theft of a person's property, project, or service are not acceptable outcomes in any situation, including dispute resolution.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37242 2018-06-16T12:01:19Z

<p>Hef: /* Language */</p> <hr /> <div>To submit a vote fill out the following template with pertinent information and follow voting rules as listed in [[Bylaws#Votes_of_the_Membership]]<br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** A person is free to remove his or her project, property, or service from PS:One at any time for any reason.<br /> ** A person decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A member cannot lose ownership of their project, but may be asked to remove the project, property or service. Destruction, tampering, or theft of the property, project, or service are not acceptable outcomes.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37241 2018-06-16T12:00:31Z

<p>Hef: /* Language */</p> <hr /> <div>To submit a vote fill out the following template with pertinent information and follow voting rules as listed in [[Bylaws#Votes_of_the_Membership]]<br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a person belongs to the person, not Pumping Station: One, NFP.<br /> ** An owner is free to remove a project, property, or service from PS:One at any time for any reason.<br /> ** An owner may decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A member cannot lose ownership of their project, but may be asked to remove the project, property or service. Destruction, tampering, or theft of the property, project, or service are not acceptable outcomes.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37240 2018-06-16T12:00:01Z

<p>Hef: </p> <hr /> <div>To submit a vote fill out the following template with pertinent information and follow voting rules as listed in [[Bylaws#Votes_of_the_Membership]]<br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a member belongs to the member, not Pumping Station: One, NFP.<br /> ** An owner is free to remove a project, property, or service from PS:One at any time for any reason.<br /> ** An owner may decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a project, property, or service must not be misrepresented to anyone, including the owner.<br /> ** In the case of a dispute of access or usage to an owned project, property, or service, A member cannot lose ownership of their project, but may be asked to remove the project, property or service. Destruction, tampering, or theft of the property, project, or service are not acceptable outcomes.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37239 2018-06-16T11:58:55Z

<p>Hef: </p> <hr /> <div>To submit a vote fill out the following template with pertinent information and follow voting rules as listed in [[Bylaws#Votes_of_the_Membership]]<br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies:<br /> ** A project created by a member belongs to the member, not Pumping Station: One, NFP.<br /> ** A member, or project creator, is free to remove a project, property, or service from PS:One at any time for any reason.<br /> ** A member may decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service, and to what extent they will allow other's to use the project, property, or service.<br /> ** The state of a member owned project, property, or service must not be represented to the member.<br /> ** In the case of a dispute of access or usage to a member owned project, property, or service, A member cannot lose ownership of their project, but may be asked to remove the project, property or service. Destruction, tampering, or theft of the property, project, or service are not acceptable outcomes.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/Vote_on_Property_Protection_Policies&diff=37238 2018-06-16T11:55:48Z

<p>Hef: Created page with &quot;To submit a vote fill out the following template with pertinent information and follow voting rules as listed in Bylaws#Votes_of_the_Membership == Sponsors == * hef ==...&quot;</p> <hr /> <div>To submit a vote fill out the following template with pertinent information and follow voting rules as listed in [[Bylaws#Votes_of_the_Membership]]<br /> <br /> == Sponsors ==<br /> <br /> * hef<br /> <br /> == History ==<br /> <br /> <br /> == Background ==<br /> <br /> * <br /> <br /> == Language ==<br /> <br /> * Adopt the following policies.<br /> ** A project created by a member belongs to the member, not Pumping Station: One, NFP.<br /> ** A member, or project creator, is free to remove a project, property, or service from PS:One at any time for any reason.<br /> ** A member may decide of his or her own volition that who he or she does and does not trust to use his or her property, project, or service.<br /> <br /> == Results ==<br /> <br /> <br /> [[Category:Votes]]<br /> [[Category:2018 Votes]]</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Jenkins&diff=26539 2015-11-10T17:38:11Z

<p>Hef: /* Github Integration */</p> <hr /> <div>== General info ==<br /> <br /> Jenkins is an automatic build server. It compiles code projects on change<br /> <br /> == Github Integration ==<br /> <br /> * Go to your projects &quot;settings&quot; link in github<br /> * Click &quot;Webhooks &amp; Services&quot;<br /> * Click &quot;Add Service&quot; <br /> * Type &quot;Jenkins&quot; and then click &quot;Jenkisn (Git Plugin)&quot;<br /> * In the '''Jenkins Url ''' field, type &quot;https://jenkins.pumpingstationone.org/github-webhook/&quot;<br /> * Clock &quot;Add Service&quot;<br /> <br /> After following these steps, you will be able to turn on the &quot;Build when a change is pushed to GitHub&quot; build trigger for projects.<br /> <br /> == Adding A Buildslave ==<br /> <br /> sudo pacman -S libvirt qemu jdk8-openjdk<br /> sudo useradd --home-dir /srv/jenkins --groups kvm --create-home --system jenkins<br /> sudo -u jenkins mkdir ~jenkins/.ssh<br /> sudo chown jenkins:jenkins /srv/jenkins/.ssh/authorized_keys<br /> sudo chmod 700 /srv/jenkins/.ssh/authorized_keys</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Talk:Board_Meeting_Notes_2015-10-13&diff=26227 2015-10-15T12:40:42Z

<p>Hef: /* Comcast Letters */</p> <hr /> <div>==$13k IRS Penalty==<br /> <br /> First off, MWE drafted text to include with the 2011-2013 990-EZs that explained why PS:One was late in filing and asked that penalties be abated. Are you certain that these statements were included in the filings made to the IRS? These were a separate Word doc that Derek would have needed to include in what he mailed. Without these, the IRS would automatically charge penalties. So are you certain that the IRS actually received these, considered them, and ruled against abating the penalties? If not, these requests need to be brought to the IRS's attention.<br /> <br /> At the end of the day, the 2011-13 returns were very late, so the IRS is within its rights to fine PS:One. Still, I suggest that the Board contact MWE with this ASAP to see if any actions or appeals can reasonably be made. --[[User:Rdpierce|Rdpierce]] ([[User talk:Rdpierce|talk]]) 22:25, 13 October 2015 (CDT)<br /> <br /> Yes, I sent the statements from MWE. I will obviously be discussing this with our professional counsel before any action is taken. --[[User:Dbever|Dbever]] ([[User talk:Dbever|talk]]) 23:01, 13 October 2015 (CDT)<br /> <br /> ==RT 3231==<br /> <br /> Plante Moran is an accounting firm that the 2014 Board hired to take numbers from the bookkeeper the 2014 Board also hired and prepare 990-EZ returns for 2011-2013. Ultimately the 2015 Board chose not to file the returns Plante Moran prepared, and hired Jeff Upchurch to prepare new returns for 2011-2014 which were filed with the IRS. This is a tax preparation expense that the organization was obligated to pay. --[[User:Rdpierce|Rdpierce]] ([[User talk:Rdpierce|talk]]) 22:25, 13 October 2015 (CDT)<br /> <br /> ==RT 2782==<br /> <br /> We incurred three expenses pertaining to the Heidenhain encoder repairs, which should be classified under the CNC Bridgeport vote if they were incurred before the expiration of funding authority:<br /> <br /> # UPS shipping charge to send the broken encoder to the repair facility<br /> # Repair cost that the repair facility charged us<br /> # UPS shipping charge to send the encoder back to the repair facility, as the encoder shaft friction was incorrect.<br /> <br /> I can confirm that at the end of all this, we had a fully repaired and functioning encoder. It is currently installed in the CNC Bridgeport. --[[User:Rdpierce|Rdpierce]] ([[User talk:Rdpierce|talk]]) 22:25, 13 October 2015 (CDT)<br /> <br /> == Comcast Letters ==<br /> <br /> The Comcast letters warned about downloads. We've received warnings like that before and systems people (Hef? Toba? I can't remember) did stuff to mitigate any behaviors like that. Dave took the letters and techie folks will handle it again. [[User:Skm|Skm]] ([[User talk:Skm|talk]]) 08:33, 14 October 2015 (CDT)<br /> <br /> :I posted them under [[DMCA_Notices]], and asked people not to do that: https://groups.google.com/d/msg/pumping-station-one/ASsYYx2fiPg/MFOzxWL8RtoJ --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 07:40, 15 October 2015 (CDT)</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Talk:Board_Meeting_Notes_2015-10-13&diff=26226 2015-10-15T12:40:25Z

<p>Hef: /* Comcast Letters */</p> <hr /> <div>==$13k IRS Penalty==<br /> <br /> First off, MWE drafted text to include with the 2011-2013 990-EZs that explained why PS:One was late in filing and asked that penalties be abated. Are you certain that these statements were included in the filings made to the IRS? These were a separate Word doc that Derek would have needed to include in what he mailed. Without these, the IRS would automatically charge penalties. So are you certain that the IRS actually received these, considered them, and ruled against abating the penalties? If not, these requests need to be brought to the IRS's attention.<br /> <br /> At the end of the day, the 2011-13 returns were very late, so the IRS is within its rights to fine PS:One. Still, I suggest that the Board contact MWE with this ASAP to see if any actions or appeals can reasonably be made. --[[User:Rdpierce|Rdpierce]] ([[User talk:Rdpierce|talk]]) 22:25, 13 October 2015 (CDT)<br /> <br /> Yes, I sent the statements from MWE. I will obviously be discussing this with our professional counsel before any action is taken. --[[User:Dbever|Dbever]] ([[User talk:Dbever|talk]]) 23:01, 13 October 2015 (CDT)<br /> <br /> ==RT 3231==<br /> <br /> Plante Moran is an accounting firm that the 2014 Board hired to take numbers from the bookkeeper the 2014 Board also hired and prepare 990-EZ returns for 2011-2013. Ultimately the 2015 Board chose not to file the returns Plante Moran prepared, and hired Jeff Upchurch to prepare new returns for 2011-2014 which were filed with the IRS. This is a tax preparation expense that the organization was obligated to pay. --[[User:Rdpierce|Rdpierce]] ([[User talk:Rdpierce|talk]]) 22:25, 13 October 2015 (CDT)<br /> <br /> ==RT 2782==<br /> <br /> We incurred three expenses pertaining to the Heidenhain encoder repairs, which should be classified under the CNC Bridgeport vote if they were incurred before the expiration of funding authority:<br /> <br /> # UPS shipping charge to send the broken encoder to the repair facility<br /> # Repair cost that the repair facility charged us<br /> # UPS shipping charge to send the encoder back to the repair facility, as the encoder shaft friction was incorrect.<br /> <br /> I can confirm that at the end of all this, we had a fully repaired and functioning encoder. It is currently installed in the CNC Bridgeport. --[[User:Rdpierce|Rdpierce]] ([[User talk:Rdpierce|talk]]) 22:25, 13 October 2015 (CDT)<br /> <br /> == Comcast Letters ==<br /> <br /> The Comcast letters warned about downloads. We've received warnings like that before and systems people (Hef? Toba? I can't remember) did stuff to mitigate any behaviors like that. Dave took the letters and techie folks will handle it again. [[User:Skm|Skm]] ([[User talk:Skm|talk]]) 08:33, 14 October 2015 (CDT)<br /> <br /> :I posted them under [DMCA_Notices], and asked people not to do that: https://groups.google.com/d/msg/pumping-station-one/ASsYYx2fiPg/MFOzxWL8RtoJ --[[User:Hef|Hef]] ([[User talk:Hef|talk]]) 07:40, 15 October 2015 (CDT)</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/raspbian_sdk&diff=25980 2015-09-21T12:28:41Z

<p>Hef: /* everything else = */</p> <hr /> <div>== raspbian dependencies ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt-get install -y libpulse-dev libopenal-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libasound2-dev libgeoclue-dev libbluetooth-dev libicu-dev libglib2.0-dev libffi-dev libxslt1-dev libjasper-dev libmng-dev libtiff4-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> raspbian has a 0.3.x series libwebp, which is too old for qt 5.5. Get a newer one.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> wget http://downloads.webmproject.org/releases/webp/libwebp-0.4.3.tar.gz<br /> cd libwebp<br /> tar -xvzf libwebp-0.4.3.tar.gz<br /> cd libwebp-0.4.3/<br /> ./configure<br /> make<br /> sudo make install<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Creating a sysroot ==<br /> <br /> === compiler ===<br /> <br /> Get a linaro cross compiler. For linux, there are official ones available, for OS X, I used http://www.welzels.de/blog/en/arm-cross-compiling-with-mac-os-x/comment-page-1/<br /> <br /> I needed to use the gcc 4.8 version for my compiled binaries to work on raspbian. GCC 4.9 worked fine on alarmpi.<br /> <br /> == everything else ==<br /> <br /> In this case a sysroot is just a copy of the important files for compiling built for the target system. It's also easier to just include a superset of the import files by grabbing pretty much everything. <br /> <br /> There are a couple ways to do this, but I just created a case sensitive OS X volume and did and rsyncd the rpi to that volume.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -P -rt --ignore-errors --delete --copy-unsafe-links --links --exclude /home --exclude /tmp --exclude /proc --exclude /sys --exclude /srv --exclude /var/cache --exclude /dev --exclude /var/log --exclude /root --exclude /run --exclude /lost+found --exclude /var/tmp --exclude /var --exclude /usr/share --exclude /etc --exclude /usr/lib/ssl pi@raspbian.local:/ /Volumes/raspbian/<br /> &lt;/syntaxhighlight&gt;<br /> <br /> If you want a narrower approach, I suspect the important files are in<br /> <br /> * /usr/include<br /> * /usr/lib<br /> * /usr/local/include<br /> * /usr/local/lib<br /> * /lib<br /> * /opt/vc<br /> <br /> Another common approach is to create an nfs server an the rpi2 and just mount nfs:/ from the rpi2 on the dev machine.<br /> <br /> == Build qt5.5 for the rpi2 ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> ./configure -v -nomake examples -nomake tests -release -opengl es2 -device linux-rasp-pi2-g++ -device-option CROSS_COMPILE=/usr/local/linaro/arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf- -sysroot /Volumes/raspbian -prefix /usr/local/qt5.5-raspbian -confirm-license -opensource<br /> &lt;/syntaxhighlight&gt;<br /> <br /> <br /> build, takes 43 minutes, 32 seconds on my 8 core MBP.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> make -j8<br /> make install -j8<br /> &lt;/syntaxhighlight&gt;<br /> <br /> <br /> once make install is run, there will be a a /volumes/rasbpian/usr/local/qt5.5-raspbian folder. copy that back to the pi in the same location<br /> <br /> First make a target location on the pi<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo mkdir /usr/local/qt5.5-raspbian<br /> chown pi:pi /usr/local/qt5.5-raspbian<br /> &lt;/syntaxhighlight&gt;<br /> <br /> Copy the files from the host machine to the pi.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -auP /usr/local/qt5.5-raspbian pi@raspbian.local:/usr/local<br /> &lt;/syntaxhighlight&gt;</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/raspbian_sdk&diff=25979 2015-09-21T12:28:16Z

<p>Hef: </p> <hr /> <div>== raspbian dependencies ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt-get install -y libpulse-dev libopenal-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libasound2-dev libgeoclue-dev libbluetooth-dev libicu-dev libglib2.0-dev libffi-dev libxslt1-dev libjasper-dev libmng-dev libtiff4-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> raspbian has a 0.3.x series libwebp, which is too old for qt 5.5. Get a newer one.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> wget http://downloads.webmproject.org/releases/webp/libwebp-0.4.3.tar.gz<br /> cd libwebp<br /> tar -xvzf libwebp-0.4.3.tar.gz<br /> cd libwebp-0.4.3/<br /> ./configure<br /> make<br /> sudo make install<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Creating a sysroot ==<br /> <br /> === compiler ===<br /> <br /> Get a linaro cross compiler. For linux, there are official ones available, for OS X, I used http://www.welzels.de/blog/en/arm-cross-compiling-with-mac-os-x/comment-page-1/<br /> <br /> I needed to use the gcc 4.8 version for my compiled binaries to work on raspbian. GCC 4.9 worked fine on alarmpi.<br /> <br /> == everything else ===<br /> <br /> In this case a sysroot is just a copy of the important files for compiling built for the target system. It's also easier to just include a superset of the import files by grabbing pretty much everything. <br /> <br /> There are a couple ways to do this, but I just created a case sensitive OS X volume and did and rsyncd the rpi to that volume.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -P -rt --ignore-errors --delete --copy-unsafe-links --links --exclude /home --exclude /tmp --exclude /proc --exclude /sys --exclude /srv --exclude /var/cache --exclude /dev --exclude /var/log --exclude /root --exclude /run --exclude /lost+found --exclude /var/tmp --exclude /var --exclude /usr/share --exclude /etc --exclude /usr/lib/ssl pi@raspbian.local:/ /Volumes/raspbian/<br /> &lt;/syntaxhighlight&gt;<br /> <br /> If you want a narrower approach, I suspect the important files are in<br /> <br /> * /usr/include<br /> * /usr/lib<br /> * /usr/local/include<br /> * /usr/local/lib<br /> * /lib<br /> * /opt/vc<br /> <br /> Another common approach is to create an nfs server an the rpi2 and just mount nfs:/ from the rpi2 on the dev machine.<br /> <br /> == Build qt5.5 for the rpi2 ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> ./configure -v -nomake examples -nomake tests -release -opengl es2 -device linux-rasp-pi2-g++ -device-option CROSS_COMPILE=/usr/local/linaro/arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf- -sysroot /Volumes/raspbian -prefix /usr/local/qt5.5-raspbian -confirm-license -opensource<br /> &lt;/syntaxhighlight&gt;<br /> <br /> <br /> build, takes 43 minutes, 32 seconds on my 8 core MBP.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> make -j8<br /> make install -j8<br /> &lt;/syntaxhighlight&gt;<br /> <br /> <br /> once make install is run, there will be a a /volumes/rasbpian/usr/local/qt5.5-raspbian folder. copy that back to the pi in the same location<br /> <br /> First make a target location on the pi<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo mkdir /usr/local/qt5.5-raspbian<br /> chown pi:pi /usr/local/qt5.5-raspbian<br /> &lt;/syntaxhighlight&gt;<br /> <br /> Copy the files from the host machine to the pi.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -auP /usr/local/qt5.5-raspbian pi@raspbian.local:/usr/local<br /> &lt;/syntaxhighlight&gt;</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/raspbian_sdk&diff=25960 2015-09-20T03:45:39Z

<p>Hef: </p> <hr /> <div>== raspbian dependencies ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt-get install -y libpulse-dev libopenal-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libasound2-dev libgeoclue-dev libbluetooth-dev libicu-dev libglib2.0-dev libffi-dev libxslt1-dev libjasper-dev libmng-dev libtiff4-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> raspbian has a 0.3.x series libwebp, which is too old for qt 5.5. Get a newer one.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> wget http://downloads.webmproject.org/releases/webp/libwebp-0.4.3.tar.gz<br /> cd libwebp<br /> tar -xvzf libwebp-0.4.3.tar.gz<br /> cd libwebp-0.4.3/<br /> ./configure<br /> make<br /> sudo make install<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Creating a sysroot ==<br /> <br /> In this case a sysroot is just a copy of the important files for compiling built for the target system. It's also easier to just include a superset of the import files by grabbing pretty much everything. <br /> <br /> There are a couple ways to do this, but I just created a case sensitive OS X volume and did and rsyncd the rpi to that volume.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -P -rt --ignore-errors --delete --copy-unsafe-links --links --exclude /home --exclude /tmp --exclude /proc --exclude /sys --exclude /srv --exclude /var/cache --exclude /dev --exclude /var/log --exclude /root --exclude /run --exclude /lost+found --exclude /var/tmp --exclude /var --exclude /usr/share --exclude /etc --exclude /usr/lib/ssl pi@raspbian.local:/ /Volumes/raspbian/<br /> &lt;/syntaxhighlight&gt;<br /> <br /> If you want a narrower approach, I suspect the important files are in<br /> <br /> * /usr/include<br /> * /usr/lib<br /> * /usr/local/include<br /> * /usr/local/lib<br /> * /lib<br /> * /opt/vc<br /> <br /> Another common approach is to create an nfs server an the rpi2 and just mount nfs:/ from the rpi2 on the dev machine.<br /> <br /> == Build qt5.5 for the rpi2 ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> ./configure -v -nomake examples -nomake tests -release -opengl es2 -device linux-rasp-pi2-g++ -device-option CROSS_COMPILE=/usr/local/linaro/arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf- -sysroot /Volumes/raspbian -prefix /usr/local/qt5.5-raspbian -confirm-license -opensource<br /> &lt;/syntaxhighlight&gt;<br /> <br /> <br /> build, takes 43 minutes, 32 seconds on my 8 core MBP.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> make -j8<br /> make install -j8<br /> &lt;/syntaxhighlight&gt;</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/raspbian_sdk&diff=25959 2015-09-20T03:44:54Z

<p>Hef: /* Build qt5.5 for the rpi2 */</p> <hr /> <div>== raspbian dependencies ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt-get install -y libpulse-dev libopenal-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libasound2-dev libgeoclue-dev libbluetooth-dev libicu-dev libglib2.0-dev libffi-dev libxslt1-dev libjasper-dev libmng-dev libtiff4-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> raspbian has a 0.3.x series libwebp, which is too old for qt 5.5. Get a newer one.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> wget http://downloads.webmproject.org/releases/webp/libwebp-0.4.3.tar.gz<br /> cd libwebp<br /> tar -xvzf libwebp-0.4.3.tar.gz<br /> cd libwebp-0.4.3/<br /> ./configure<br /> make<br /> sudo make install<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Creating a sysroot ==<br /> <br /> In this case a sysroot is just a copy of the important files for compiling built for the target system. It's also easier to just include a superset of the import files by grabbing pretty much everything. <br /> <br /> There are a couple ways to do this, but I just created a case sensitive OS X volume and did and rsyncd the rpi to that volume.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -P -rt --ignore-errors --delete --copy-unsafe-links --links --exclude /home --exclude /tmp --exclude /proc --exclude /sys --exclude /srv --exclude /var/cache --exclude /dev --exclude /var/log --exclude /root --exclude /run --exclude /lost+found --exclude /var/tmp --exclude /var --exclude /usr/share --exclude /etc --exclude /usr/lib/ssl pi@raspbian.local:/ /Volumes/raspbian/<br /> &lt;/syntaxhighlight&gt;<br /> <br /> If you want a narrower approach, I suspect the important files are in<br /> <br /> * /usr/include<br /> * /usr/lib<br /> * /usr/local/include<br /> * /usr/local/lib<br /> * /lib<br /> * /opt/vc<br /> <br /> Another common approach is to create an nfs server an the rpi2 and just mount nfs:/ from the rpi2 on the dev machine.<br /> <br /> == Build qt5.5 for the rpi2 ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> ./configure -v -nomake examples -nomake tests -release -opengl es2 -device linux-rasp-pi2-g++ -device-option CROSS_COMPILE=/usr/local/linaro/arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf- -sysroot /Volumes/raspbian -prefix /usr/local/qt5.5-raspbian -confirm-license -opensource<br /> &lt;/syntaxhighlight&gt;<br /> <br /> <br /> build, takes 43 minutes, 32 seconds on my 8 core MBP.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> make -j8<br /> make install -j8<br /> &lt;/syntaxhighlight&gt;</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/raspbian_sdk&diff=25958 2015-09-20T03:43:08Z

<p>Hef: /* Creating a sysroot */</p> <hr /> <div>== raspbian dependencies ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt-get install -y libpulse-dev libopenal-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libasound2-dev libgeoclue-dev libbluetooth-dev libicu-dev libglib2.0-dev libffi-dev libxslt1-dev libjasper-dev libmng-dev libtiff4-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> raspbian has a 0.3.x series libwebp, which is too old for qt 5.5. Get a newer one.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> wget http://downloads.webmproject.org/releases/webp/libwebp-0.4.3.tar.gz<br /> cd libwebp<br /> tar -xvzf libwebp-0.4.3.tar.gz<br /> cd libwebp-0.4.3/<br /> ./configure<br /> make<br /> sudo make install<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Creating a sysroot ==<br /> <br /> In this case a sysroot is just a copy of the important files for compiling built for the target system. It's also easier to just include a superset of the import files by grabbing pretty much everything. <br /> <br /> There are a couple ways to do this, but I just created a case sensitive OS X volume and did and rsyncd the rpi to that volume.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -P -rt --ignore-errors --delete --copy-unsafe-links --links --exclude /home --exclude /tmp --exclude /proc --exclude /sys --exclude /srv --exclude /var/cache --exclude /dev --exclude /var/log --exclude /root --exclude /run --exclude /lost+found --exclude /var/tmp --exclude /var --exclude /usr/share --exclude /etc --exclude /usr/lib/ssl pi@raspbian.local:/ /Volumes/raspbian/<br /> &lt;/syntaxhighlight&gt;<br /> <br /> If you want a narrower approach, I suspect the important files are in<br /> <br /> * /usr/include<br /> * /usr/lib<br /> * /usr/local/include<br /> * /usr/local/lib<br /> * /lib<br /> * /opt/vc<br /> <br /> Another common approach is to create an nfs server an the rpi2 and just mount nfs:/ from the rpi2 on the dev machine.<br /> <br /> == Build qt5.5 for the rpi2 ==<br /> <br /> build, takes 43 minutes, 32 seconds on my 8 core MBP.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> make -j8<br /> make install -j8<br /> &lt;/syntaxhighlight&gt;</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/raspbian_sdk&diff=25957 2015-09-20T03:36:00Z

<p>Hef: /* Creating a sysroot */</p> <hr /> <div>== raspbian dependencies ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt-get install -y libpulse-dev libopenal-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libasound2-dev libgeoclue-dev libbluetooth-dev libicu-dev libglib2.0-dev libffi-dev libxslt1-dev libjasper-dev libmng-dev libtiff4-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> raspbian has a 0.3.x series libwebp, which is too old for qt 5.5. Get a newer one.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> wget http://downloads.webmproject.org/releases/webp/libwebp-0.4.3.tar.gz<br /> cd libwebp<br /> tar -xvzf libwebp-0.4.3.tar.gz<br /> cd libwebp-0.4.3/<br /> ./configure<br /> make<br /> sudo make install<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Creating a sysroot ==<br /> <br /> There are a couple ways to do this, but I just created a case sensitive OS X volume and did and rsyncd the rpi to that volume.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -P -rt --ignore-errors --delete --copy-unsafe-links --links --exclude /home --exclude /tmp --exclude /proc --exclude /sys --exclude /srv --exclude /var/cache --exclude /dev --exclude /var/log --exclude /root --exclude /run --exclude /lost+found --exclude /var/tmp --exclude /var --exclude /usr/share --exclude /etc --exclude /usr/lib/ssl pi@raspbian.local:/ /Volumes/raspbian/<br /> &lt;/syntaxhighlight&gt;<br /> <br /> build, takes 43 minutes, 32 seconds on my 8 core MBP.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> make -j8<br /> make install -j8<br /> &lt;/syntaxhighlight&gt;</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/raspbian_sdk&diff=25956 2015-09-20T03:31:21Z

<p>Hef: /* raspbian dependencies */</p> <hr /> <div>== raspbian dependencies ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt-get install -y libpulse-dev libopenal-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libasound2-dev libgeoclue-dev libbluetooth-dev libicu-dev libglib2.0-dev libffi-dev libxslt1-dev libjasper-dev libmng-dev libtiff4-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> raspbian has a 0.3.x series libwebp, which is too old for qt 5.5. Get a newer one.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> wget http://downloads.webmproject.org/releases/webp/libwebp-0.4.3.tar.gz<br /> cd libwebp<br /> tar -xvzf libwebp-0.4.3.tar.gz<br /> cd libwebp-0.4.3/<br /> ./configure<br /> make<br /> sudo make install<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Creating a sysroot ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -P -rt --ignore-errors --delete --copy-unsafe-links --links --exclude /home --exclude /tmp --exclude /proc --exclude /sys --exclude /srv --exclude /var/cache --exclude /dev --exclude /var/log --exclude /root --exclude /run --exclude /lost+found --exclude /var/tmp --exclude /var --exclude /usr/share --exclude /etc --exclude /usr/lib/ssl pi@raspbian.local:/ /Volumes/raspbian/<br /> &lt;/syntaxhighlight&gt;<br /> <br /> build, takes 43 minutes, 32 seconds on my 8 core MBP.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> make -j8<br /> make install -j8<br /> &lt;/syntaxhighlight&gt;</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/raspbian_sdk&diff=25955 2015-09-20T03:31:01Z

<p>Hef: /* raspbian dependencies */</p> <hr /> <div>== raspbian dependencies ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt-get install -y libpulse-dev libopenal-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libasound2-dev libgeoclue-dev libbluetooth-dev libicu-dev libglib2.0-dev libffi-dev libxslt1-dev libjasper-dev libmng-dev libtiff4-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> raspbian has a 0.3.x series libwebp, which is too old for qt 5.5. Get a newer one.<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> wget http://downloads.webmproject.org/releases/webp/libwebp-0.4.3.tar.gz<br /> cd libwebp<br /> tar -xvzf libwebp-0.4.3.tar.gz<br /> cd libwebp-0.4.3/<br /> ./configure<br /> make<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Creating a sysroot ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -P -rt --ignore-errors --delete --copy-unsafe-links --links --exclude /home --exclude /tmp --exclude /proc --exclude /sys --exclude /srv --exclude /var/cache --exclude /dev --exclude /var/log --exclude /root --exclude /run --exclude /lost+found --exclude /var/tmp --exclude /var --exclude /usr/share --exclude /etc --exclude /usr/lib/ssl pi@raspbian.local:/ /Volumes/raspbian/<br /> &lt;/syntaxhighlight&gt;<br /> <br /> build, takes 43 minutes, 32 seconds on my 8 core MBP.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> make -j8<br /> make install -j8<br /> &lt;/syntaxhighlight&gt;</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/raspbian_sdk&diff=25954 2015-09-20T03:29:40Z

<p>Hef: </p> <hr /> <div>== raspbian dependencies ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt-get install -y libpulse-dev libopenal-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libasound2-dev libgeoclue-dev libbluetooth-dev libicu-dev libglib2.0-dev libffi-dev libxslt1-dev libjasper-dev libmng-dev libtiff4-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> wget http://downloads.webmproject.org/releases/webp/libwebp-0.4.3.tar.gz<br /> cd libwebp<br /> tar -xvzf libwebp-0.4.3.tar.gz<br /> cd libwebp-0.4.3/<br /> ./configure<br /> make<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Creating a sysroot ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -P -rt --ignore-errors --delete --copy-unsafe-links --links --exclude /home --exclude /tmp --exclude /proc --exclude /sys --exclude /srv --exclude /var/cache --exclude /dev --exclude /var/log --exclude /root --exclude /run --exclude /lost+found --exclude /var/tmp --exclude /var --exclude /usr/share --exclude /etc --exclude /usr/lib/ssl pi@raspbian.local:/ /Volumes/raspbian/<br /> &lt;/syntaxhighlight&gt;<br /> <br /> build, takes 43 minutes, 32 seconds on my 8 core MBP.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> make -j8<br /> make install -j8<br /> &lt;/syntaxhighlight&gt;</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=User:Hef/raspbian_sdk&diff=25953 2015-09-20T03:29:22Z

<p>Hef: opening with commands</p> <hr /> <div>== raspbian dependencies ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt-get install -y libpulse-dev libopenal-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libasound2-dev libgeoclue-dev libbluetooth-dev libicu-dev libglib2.0-dev libffi-dev libxslt1-dev libjasper-dev libmng-dev libtiff4-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> wget http://downloads.webmproject.org/releases/webp/libwebp-0.4.3.tar.gz<br /> cd libwebp<br /> tar -xvzf libwebp-0.4.3.tar.gz<br /> cd libwebp-0.4.3/<br /> ./configure<br /> make<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Creating a sysroot ===<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> rsync -P -rt --ignore-errors --delete --copy-unsafe-links --links --exclude /home --exclude /tmp --exclude /proc --exclude /sys --exclude /srv --exclude /var/cache --exclude /dev --exclude /var/log --exclude /root --exclude /run --exclude /lost+found --exclude /var/tmp --exclude /var --exclude /usr/share --exclude /etc --exclude /usr/lib/ssl pi@raspbian.local:/ /Volumes/raspbian/<br /> &lt;/syntaxhighlight&gt;<br /> <br /> build, takes 43 minutes, 32 seconds on my 8 core MBP.<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> make -j8<br /> make install -j8<br /> &lt;/syntaxhighlight&gt;</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Canyon&diff=25951 2015-09-19T04:56:22Z

<p>Hef: </p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = hef<br /> |certification = no<br /> |hackable = no<br /> |model = Odroid Xu4 and STEB5000100<br /> |arrived = 2015-09-18<br /> |doesitwork = yes<br /> |contact = hef<br /> |where = comms closet<br /> |value = $252.79<br /> }}<br /> <br /> == Canyon Backup Server ==<br /> <br /> This machine is sitting quitely in the comms closet running as a backup server to proxmox. proxmox back's up it's vm's to this machines hard drive nightly.</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Canyon&diff=25950 2015-09-19T02:00:18Z

<p>Hef: </p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = hef<br /> |certification = no<br /> |hackable = no<br /> |serial = 1<br /> |model = Odroid Xu4 and STEB5000100<br /> |arrived = 2015-09-18<br /> |doesitwork = yes<br /> |contact = hef<br /> |where = comms closet<br /> |value = $252.79<br /> }}<br /> <br /> == Canyon Backup Server ==<br /> <br /> This machine is sitting quitely in the comms closet running as a backup server to proxmox. proxmox back's up it's vm's to this machines hard drive nightly.</div>

Hef https://wiki-dev.pumpingstationone.org/mediawiki/index.php?title=Canyon&diff=25949 2015-09-19T01:55:01Z

<p>Hef: Created page with &quot;{{Template:EquipmentPage |owner = hef |certification = no |hackable = no |serial = 1 |model = Odroid Xu4 and STEB5000100 |arrived = 2015-09-18 |doesitwork = yes |contact = hef...&quot;</p> <hr /> <div>{{Template:EquipmentPage<br /> |owner = hef<br /> |certification = no<br /> |hackable = no<br /> |serial = 1<br /> |model = Odroid Xu4 and STEB5000100<br /> |arrived = 2015-09-18<br /> |doesitwork = yes<br /> |contact = hef<br /> |where = comms closet<br /> |value = $252.79<br /> }}</div>

Hef