sudo-discuss

sudo-discuss@sudoroom.org

4 participants
7481 discussions

Re: [sudo-discuss] Who's SudoRoom's web server admin?

by Lisha Sterling

Woops... I sent the wrong CVE. There was one for Tornado that was also open and when I bopped back and forth between my windows I copy-pasted the wrong URL. Sorry. I'll try to figure out which one I'd pulled up from the scripts I ran on sudoroom.org yesterday (as opposed to the others that popped up from the other things I was looking at. *groan*). - Lish (feeling really dumb at the moment...) On Thu, Mar 7, 2013 at 1:14 PM, Matthew Senate <mattsenate(a)gmail.com> wrote: > you should join our list sudo-sys :D > http://lists.sudoroom.org/listinfo/sudo-sys > > > On Wed, Mar 6, 2013 at 6:56 PM, Lisha Sterling <lishevita(a)gmail.com>wrote: > >> I just wanted to give a heads up that we've got some cross-site scripting >> vulnerabilities in the sudoroom websever that sits at 50.0.83.116 >> >> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-4558 >> for more info... >> >> - Lisha >> >> -- >> http://www.alwayssababa.com/ >> >> >> _______________________________________________ >> sudo-discuss mailing list >> sudo-discuss(a)lists.sudoroom.org >> http://lists.sudoroom.org/listinfo/sudo-discuss >> >> > -- http://www.alwayssababa.com/

13 years

Re: [sudo-discuss] Constable amendment changes

by mattsenate＠gmail.com

I agree with the sentiment, and in lieu of suggesting an alternative at first, decided to ask for more thoughts, so thanks. However, even if it is a process we do now, I disagree that (a) it is absolutely necessary for the exchequer specifically to do this rather than to support the overall process and encourage better systems to automate and (b) it need not be codified in the description of the role, but instead as documentation, best practices, recommendations, etc such as on a wiki page. Further, I would suggest if we did want to keep it in, that we think long and hard, but add it to the fiscal solvency process, for which we are collectively responsible, and the exchequer may be the first or default person to implement or act. Do you think it reasonable to make a new wiki page instead for exchequer operational insight? // Matt ----- Reply message ----- From: "Anthony Di Franco" <di.franco(a)gmail.com> To: "Matthew Senate" <mattsenate(a)gmail.com> Cc: "sudo-discuss" <sudo-discuss(a)lists.sudoroom.org> Subject: [sudo-discuss] Constable amendment changes Date: Thu, Mar 7, 2013 9:04 AM In the second case, I added this because handling the money and being authorized to use the accounts was key to my being exchequer, and will remain so, and even if aspects of the processes of handling money are delegated, distributed, automated, (it happened with wepay a bit,) these basics remain necessary as a default. On Mar 7, 2013 2:49 AM, "Matthew Senate" <mattsenate(a)gmail.com> wrote: > hey all, > > here are the changes I described in the mtg tonight: > http://sudoroom.org/mediawiki/index.php?title=Articles_of_Association%2FCon… > > This page's history has: > (a) the current Articles > (b) the proposal from tonight > (c) my proposed changes > > // Matt > > p.s. > > I left out some bits about Facilitator and Exchequer, but the rest is > mainly re-worded, reduced, and refined. The omitted pieces (due to > unnecessary in the first case since majority vote already over-rules > facilitator, and too specific for the second case): > > Facilitator: > > ** Uses own best judgment to resolve ambiguity in the Articles of > Association about how business is handled in meetings, but may be > challenged in this by anyone who does not consent, which results in a > majority vote on sustaining or overturning the Facilitator's judgment. > > Exchequer: > > ** Receives dues and donations and pays expenses on behalf of the group, > using the group's accounts. > > > _______________________________________________ > sudo-discuss mailing list > sudo-discuss(a)lists.sudoroom.org > http://lists.sudoroom.org/listinfo/sudo-discuss > >

13 years

Who's SudoRoom's web server admin?

by Lisha Sterling

I just wanted to give a heads up that we've got some cross-site scripting vulnerabilities in the sudoroom websever that sits at 50.0.83.116 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-4558 for more info... - Lisha -- http://www.alwayssababa.com/

13 years

Last night: conflict resolution proposal (Eddan)

by Max Klein

I'm responding to what Eddan has said, with my perspective from faciliator last night. 1. The Articles say that amendments require consensus. 2. From my perspective as Facilitator last night, consensus on the Constable changes were almost reached, because 3, A straw poll of those wanting to vote, gave a unanimous yes, 4, and then a straw poll for accepting constable changes was almost unanimous, except that, 5. A member blocked the consensus process, which 6. Is an allowable and natural part of the consensus process. Up to here, I think that the process and content ran properly and validly - albeit tiring and onerous (to be expected). 7. The next step in the Consensus process, is to address the blocking concern (I may not have faciltated this portion correctly). 8. The reason given, as I saw it, from the blocking member was that they wanted more time to personally comb and edit the Constable policy. 9. Group must consider if there is valid reason to extend blocking member additional time, beyond the prescribed proposal process. En sum, I think that as facilitator I should have extended the discussion past 6 to 7,8, and 9. That's my lesson from last night. notconfusing From: Eddan <eddan(a)clear.net> > To: sudo-discuss <sudo-discuss(a)lists.sudoroom.org> > Cc: > Date: Thu, 7 Mar 2013 02:43:28 -0800 > Subject: Re: [sudo-discuss] conflict resolution proposal > Dear Sudo folk - > > As now ought to be assumed amongst the illustrious Sudo Room body, > dedicated as we are to a deliberative process, a point of contention arose > around the process itself. The honest disagreement and confusion, as far > as I understand it, is fundamentally about how we agree to approve the > establishment of a position deputized to make sure the process is followed > and make sure that conflicts move towards fair and efficient resolution. > If the previous sentence makes some sense but also makes your head hurt, as > it does mine, you won't be surprised to find out there was some confusion > in this evening's meeting over what exactly we're supposed to do. > > The vote on adding the role of constable came up as was announced last > week, and it was agreed that Anthony has followed meticulous process as we > have it laid out so far, giving everyone plentiful opportunity to discuss > and object and to make available in-person and on-line opportunities to > improve on the proposal. Discussion over the need for such a role has > persistently come up that represented various points of view on several > specific aspects of the proposal. Debate was halted at regular intervals > to give the less aggressive and talkative folks (in addition to me) around > an opportunity to interject; and everyone was reminded of the option for > anonymous commenting on the etherpad and for direct editing on the wiki. > This took place over a period of about 6 weeks and more, in as formal a > method as we've made up along the way so far. > > The reasonable difference in interpretation to put it simply, is how to > add a position to the Articles of Association by: (1) 2/3 vote; or must be > done (2) by consensus. There are many other issues implied by this for > sure, some of which have been brought up already and other conditionals > still to be worked out. I also think re-hashing the play-by-play events of > tonight would be unproductive and that considerations on the merits of the > constable role be limited to high-level comments and would be best served > without delving into too many details about the role. In other words, I'm > suggesting we separate out the process by which we (a) find consensus on > language amending the articles of association; and (b) decide on whether we > need to add a Constable (or related functionary) role. > > So this is the part where it gets kind of tricky. Here are some questions > it seems to me need to be clarified in order to move forward: > What does the Amendments section of the Articles ( > http://sudoroom.org/wiki/Articles_of_Association#Article_4._Amendments) > say about the process by which we approve adding a functionary position? > What does the Functionaries section ( > http://sudoroom.org/wiki/Articles_of_Association#Section_2.2_Sudo_Functiona…) > say about how to amend the Articles to create another position? > Do the decision procedures categorized in the dispute resolution process ( > http://sudoroom.org/wiki/Articles_of_Association#Section_3.4_Enforcement) > give us guidance on the process that should be followed in creating a new > functionary role? > If so, what process ( > http://sudoroom.org/wiki/Articles_of_Association#Sub-Section_3.40_Process) > for approving the addition of a Constable (or equivalent) role be followed? > What part of the agenda structure ( > http://sudoroom.org/wiki/Articles_of_Association#Sub-Section_3.0.1_Agenda) > is the most appropriate category for adding a functionary role? > How do we go about advancing our values ( > http://sudoroom.org/wiki/Articles_of_Association#Values) in making these > decisions? > > I won't represent anyone else's position on their behalf, but will say > that I think consensus is not the right process by which the Constable role > be approved. This being said, I do think that whatever language is drafted > to amend the Articles to include this new role be done by consensus. > Having a common understanding of how this ought to be done in detail is > crucial, in my opinion, to avoid further misunderstandings and wide > divergence of interpretation. I propose as I did at the meeting tonight > that these two parts of the decision need to be disentangled for any > progress to be made. Upon reflection, I would have presented that proposal > differently and with more specific reference to the Articles. Suffice it > to say that we're figuring out how to do this stuff in some ways we're not > used to, and that we all have a lot to learn from each other. > > In sum, I propose that there be a vote next week on adding a Constable (or > equivalent) to the functionaries in the Articles, and that the vote require > 2/3 approval, our highest threshold thus far. Since there are so many > ancillary issues, I'd rather hear other Sudo folks' perspective before > making too much of a case for this way of moving forward. Seems to me that > the complications of getting to this vote make the greatest case for the > need for such a role, to keep things moving in a productive direction. The > constable (or ombudsperson as I had proposed), is not an ultimate judge of > conflicts in my understanding. In fact, rotating ombudspeople and/or a > jury of peers is more along the lines of what I've heard proposed. Rather, > I think we need someone like a Constable to make sure we get unstuck when > trying to resolve disputes and decide on things. > > May God Bless Sudo Room. > > sent from eddan.com > > > ---- > > On Feb 22, 2013 11:17 PM, "Anthony Di Franco" <di.franco(a)gmail.com> wrote: > Sudyo, > I have edited in a more advanced draft of my proposal for a rigorous > conflict resolution process and for the role of a Constable to facilitate > the keeping of open and transparent records about conflicts and where their > resolution stands. > I emailed a bit about this a few weeks ago in response to the long and > unsatisfactory non-process the group had just spent a lot of time in, and I > presented a much briefer version of this proposal at last week's meeting. I > intend to have it up for a vote at the next eligible meeting. > I have tried to incorporate the feedback I received during the meeting > and to think through a process that would capture the original intent of > the sketchy previous language but flesh it out with comprehensive detail > and precision, and I had firmly in mind the memories of the shortcomings of > the old process in practice. While I was there mucking around in the > articles I fixed a few other odd things that were lying around. (It also > still seems to me that the numbering is off.) > The whole draft, with my and other changes, is, as usual, here: > http://sudoroom.org/wiki/Articles_of_Association/Draft > > Highlights: > Emphasize horizontality in the Functionaries in general and in the > Constable in particular: section 2.2: "Any member of sudoroom may perform > any of the functions of any of the Functionaries, but the Functionaries are > expected to perform their duties regularly and must perform them if no one > else can or will." and section 3.4.1 below. > Define role of Constable (section 2.2) > Point person for facilitating the conflict resolution process according to > the Articles, but not necessarily a moderator. > Stewards selection of a moderator and schedules meetings among conflicting > parties and moderator. > Documents all meetings and communications relevant to the conflict > resolution process. > Promotes good-faith participation in the process by conflicting parties on > a basis of mutual respect and growth towards better relationships and a > stronger community. > If conflict resolution goes before the whole group, co-facilitates with > Facilitator, and handles points of information about conflict resolution > with reference to the documentation. > Does not act as Constable in conflicts involving self. > Precise and comprehensive conflict resolution procedure: > > Section 3.4 Enforcement > [edit]Sub-Section 3.4.0 Process > The resolution of disputes and disagreements within sudo room is > encouraged through informal process and the spirit of a collaborative > environment. There is a process, however, by which issues that are not > resolved informally and that arise within the scope of these articles of > association: > The party who seeks resolution finds someone to act as Constable in the > matter, and works with this Constable to find a Mediator. > The Mediator is an impartial and uninvolved third party who consents to > assist, and with whom all conflicting parties consent to work with towards > a solution. > The Constable organizes meetings for conflict resolution and maintains > records of all meetings and relevant communications among the conflicting > parties. > The Constable, Mediator, and the conflicting parties arrange to meet to > work out a resolution to the conflict that all conflicting parties consent > to. > If at least one conflicting party does not consent to meet, or if at least > one conflicting party is unavailable to meet in a reasonable time, all > relevant circumstances considered, or if the Constable and Mediator agree > after at least one meeting that further meetings would not be likely to > lead to resolution, the issue is brought before the group in the following > way: > The issue is added to the agenda of the next official meeting scheduled at > least one week in the future, and all relevant documentation is gathered > together by the Constable and made available to the group at least one week > beforehand, preferably on the wiki, and notice is broadcast to the group, > preferably on the mailing list, but information that would compromise > anyone's privacy or dignity is not made public. In the description of the > issue, the form of redress sought in by the plaintiff(s) is included. Both > the Constable and Mediator must give their approval of the factual content > of the documentation before it is posted. Both the Constable and Mediator > must expressly affirm that the form of redress sought by the plaintiff(s) > is consistent with sudo room's values. > During each meeting's agenda item on Conflict Resolution, all unresolved > issues on the wiki are brought up for discussion followed by a vote. > First, the Constable presents all relevant documentation about the issue. > Then, a category of severity is established by consensus according to sudo > room's values and the facts of the case. The category determines the voting > threshold for sustaining a sanction against any party to the conflict. The > categories are (in order of decreasing severity): > Any matter calling for membership suspension or termination. > Decision Procedure: 2/3 vote > Other serious conflict. > Decision Procedure: 2/3 vote > Conflict where only fiscal issues are involved and only fiscal redress is > sought. > Decision Procedure: 1/2 vote > All other conflicts. > Decision Procedure: Consensus > Positive feedback. > Decision Procedure: Auto-approval > Then, the opportunity to represent perspective is granted to each > conflicting party and to the Mediator, and general discussion may be held > about the issue if any member wishes. The Constable co-facilitates with the > Facilitator in order to answer questions specific to the conflict and > provides information about the history of the conflict by referring to the > documentation. > Then, a brief period of deliberation of definite time is held, during > which members are free to consider the issue or discuss it directly with > others. > Then, members may propose alternative remedies to the conflict, which are > added to a list of potential remedies if neither the Constable nor the > Mediator objects. They may be overruled in their objections if a second > member supports the proposal. > Finally, a vote is held on the plaintiff(s)' proposed remedy, and then > alternative remedies are voted upon in the order they were proposed, but > only if at least one member indicates that the one under consideration is > still relevant. After all remedies have been considered in this way, the > matter is considered resolved. > Any conflicting party unsatisfied with the decision may place an appeal on > the agenda in the same way that conflicts are placed on the agenda, except > that a majority of the group must vote to accept the appeal during a > meeting, and the process begins anew. The appeal must propose an > alternative remedy and refer to values that were not served by the original > decision. > If at the end of any step in the process more than an hour has passed > during the current meeting in considering the conflict, any member may > request that a majority vote be held on whether to table the conflict until > the next meeting. > [edit]Sub-Section 3.4.1 Principles and Values Specific to Conflicts > The accused are presumed innocent unless and until proven otherwise beyond > reasonable doubt. > Respect for the privacy and dignity of all members is consistently > maintained. > Proportional and effective remedies should be sought. > Restorative remedies are strongly preferred over retributive remedies. > More precise language about functionaries: > Facilitator > Maintains the agenda for meetings, ensures topics are dealt with, and > recognizes speakers in a fair and inclusive way. > Ensures that all group business is handled and all group decisions are > made in the way described in these Articles of Association, by bearing them > in mind and referring to them whenever needed. > Uses own best judgment to resolve ambiguity in the Articles of Association > about how business is handled in meetings, but may be challenged in this by > anyone who does not consent, which results in a majority vote on sustaining > or overturning the Facilitator's judgment. > Scribe > Takes notes during meetings and collaborates with others to include their > notes in final meeting minutes. > Posts notes publicly after each meeting. > Exchequer > Presents the budget during meetings, as articulated in the budget process > below. > Receives dues and donations and pays expenses on behalf of the group, > using the group's accounts. > Maintains accurate budget documentation and makes it available to the > group. > Constable > Point person for facilitating the conflict resolution process according to > the Articles, but not necessarily a moderator. > Stewards selection of a moderator and schedules meetings among conflicting > parties and moderator. > Documents all meetings and communications relevant to the conflict > resolution process. > Promotes good-faith participation in the process by conflicting parties on > a basis of mutual respect and growth towards better relationships and a > stronger community. > If conflict resolution goes before the whole group, co-facilitates with > Facilitator, and handles points of information about conflict resolution > with reference to the documentation. > Does not act as Constable in conflicts involving self. > >

13 years

Constable amendment changes

by Matthew Senate

hey all, here are the changes I described in the mtg tonight: http://sudoroom.org/mediawiki/index.php?title=Articles_of_Association%2FCon… This page's history has: (a) the current Articles (b) the proposal from tonight (c) my proposed changes // Matt p.s. I left out some bits about Facilitator and Exchequer, but the rest is mainly re-worded, reduced, and refined. The omitted pieces (due to unnecessary in the first case since majority vote already over-rules facilitator, and too specific for the second case): Facilitator: ** Uses own best judgment to resolve ambiguity in the Articles of Association about how business is handled in meetings, but may be challenged in this by anyone who does not consent, which results in a majority vote on sustaining or overturning the Facilitator's judgment. Exchequer: ** Receives dues and donations and pays expenses on behalf of the group, using the group's accounts.

13 years

conflict resolution proposal

by Anthony Di Franco

Sudyo, I have edited in a more advanced draft of my proposal for a rigorous conflict resolution process and for the role of a Constable to facilitate the keeping of open and transparent records about conflicts and where their resolution stands. I emailed a bit about this a few weeks ago in response to the long and unsatisfactory non-process the group had just spent a lot of time in, and I presented a much briefer version of this proposal at last week's meeting. I intend to have it up for a vote at the next eligible meeting. I have tried to incorporate the feedback I received during the meeting and to think through a process that would capture the original intent of the sketchy previous language but flesh it out with comprehensive detail and precision, and I had firmly in mind the memories of the shortcomings of the old process in practice. While I was there mucking around in the articles I fixed a few other odd things that were lying around. (It also still seems to me that the numbering is off.) The whole draft, with my and other changes, is, as usual, here: http://sudoroom.org/wiki/Articles_of_Association/Draft *Highlights:* *Emphasize horizontality in the Functionaries in general and in the Constable in particular: section 2.2:* "Any member of sudoroom may perform any of the functions of any of the Functionaries, but the Functionaries are expected to perform their duties regularly and must perform them if no one else can or will." *and section 3.4.1 below.* - *Define role of Constable (section 2.2)* - - Point person for facilitating the conflict resolution process according to the Articles, but not necessarily a moderator. - Stewards selection of a moderator and schedules meetings among conflicting parties and moderator. - Documents all meetings and communications relevant to the conflict resolution process. - Promotes good-faith participation in the process by conflicting parties on a basis of mutual respect and growth towards better relationships and a stronger community. - If conflict resolution goes before the whole group, co-facilitates with Facilitator, and handles points of information about conflict resolution with reference to the documentation. - Does not act as Constable in conflicts involving self. *Precise and comprehensive conflict resolution procedure:* Section 3.4 Enforcement [edit<http://sudoroom.org/mediawiki/index.php?title=Articles_of_Association/Draft…> ]Sub-Section 3.4.0 Process The resolution of disputes and disagreements within *sudo room* is encouraged through informal process and the spirit of a collaborative environment. There is a process, however, by which issues that are not resolved informally and that arise within the scope of these articles of association: 1. The party who seeks resolution finds someone to act as Constable in the matter, and works with this Constable to find a Mediator. 1. The Mediator is an impartial and uninvolved third party who consents to assist, and with whom all conflicting parties consent to work with towards a solution. 2. The Constable organizes meetings for conflict resolution and maintains records of all meetings and relevant communications among the conflicting parties. 3. The Constable, Mediator, and the conflicting parties arrange to meet to work out a resolution to the conflict that all conflicting parties consent to. 2. If at least one conflicting party does not consent to meet, or if at least one conflicting party is unavailable to meet in a reasonable time, all relevant circumstances considered, or if the Constable and Mediator agree after at least one meeting that further meetings would not be likely to lead to resolution, the issue is brought before the group in the following way: 1. The issue is added to the agenda of the next official meeting scheduled at least one week in the future, and all relevant documentation is gathered together by the Constable and made available to the group at least one week beforehand, preferably on the wiki, and notice is broadcast to the group, preferably on the mailing list, but information that would compromise anyone's privacy or dignity is not made public. In the description of the issue, the form of redress sought in by the plaintiff(s) is included. Both the Constable and Mediator must give their approval of the factual content of the documentation before it is posted. Both the Constable and Mediator must expressly affirm that the form of redress sought by the plaintiff(s) is consistent with *sudo room's* values. 2. During each meeting's agenda item on Conflict Resolution, all unresolved issues on the wiki are brought up for discussion followed by a vote. 1. First, the Constable presents all relevant documentation about the issue. 2. Then, a category of severity is established by *consensus* according to *sudo room'*s values and the facts of the case. The category determines the voting threshold for sustaining a sanction against any party to the conflict. The categories are (in order of decreasing severity): 1. Any matter calling for membership suspension or termination. - *Decision Procedure:* 2/3 vote 2. Other serious conflict. - *Decision Procedure:* 2/3 vote 3. Conflict where only fiscal issues are involved and only fiscal redress is sought. - *Decision Procedure:* 1/2 vote 4. All other conflicts. - *Decision Procedure:* Consensus 5. Positive feedback. - *Decision Procedure:* Auto-approval 3. Then, the opportunity to represent perspective is granted to each conflicting party and to the Mediator, and general discussion may be held about the issue if any member wishes. The Constable co-facilitates with the Facilitator in order to answer questions specific to the conflict and provides information about the history of the conflict by referring to the documentation. 4. Then, a brief period of deliberation of definite time is held, during which members are free to consider the issue or discuss it directly with others. 5. Then, members may propose alternative remedies to the conflict, which are added to a list of potential remedies if neither the Constable nor the Mediator objects. They may be overruled in their objections if a second member supports the proposal. 6. Finally, a vote is held on the plaintiff(s)' proposed remedy, and then alternative remedies are voted upon in the order they were proposed, but only if at least one member indicates that the one under consideration is still relevant. After all remedies have been considered in this way, the matter is considered resolved. 7. Any conflicting party unsatisfied with the decision may place an appeal on the agenda in the same way that conflicts are placed on the agenda, except that a majority of the group must vote to accept the appeal during a meeting, and the process begins anew. The appeal must propose an alternative remedy and refer to values that were not served by the original decision. 8. If at the end of any step in the process more than an hour has passed during the current meeting in considering the conflict, any member may request that a majority vote be held on whether to table the conflict until the next meeting. [edit<http://sudoroom.org/mediawiki/index.php?title=Articles_of_Association/Draft…> ]Sub-Section 3.4.1 Principles and Values Specific to Conflicts 1. The accused are presumed innocent unless and until proven otherwise beyond reasonable doubt. 2. Respect for the privacy and dignity of all members is consistently maintained. 3. Proportional and effective remedies should be sought. 4. Restorative <https://en.wikipedia.org/wiki/Restorative_justice> remedies are strongly preferred over retributive<https://en.wikipedia.org/wiki/Retributive_justice> remedies. *More precise language about functionaries:* - Facilitator - Maintains the agenda for meetings, ensures topics are dealt with, and recognizes speakers in a fair and inclusive way. - Ensures that all group business is handled and all group decisions are made in the way described in these Articles of Association, by bearing them in mind and referring to them whenever needed. - Uses own best judgment to resolve ambiguity in the Articles of Association about how business is handled in meetings, but may be challenged in this by anyone who does not consent, which results in a majority vote on sustaining or overturning the Facilitator's judgment. - Scribe - Takes notes during meetings and collaborates with others to include their notes in final meeting minutes. - Posts notes publicly after each meeting. - Exchequer - Presents the budget during meetings, as articulated in the budget process below. - Receives dues and donations and pays expenses on behalf of the group, using the group's accounts. - Maintains accurate budget documentation and makes it available to the group. - Constable - Point person for facilitating the conflict resolution process according to the Articles, but not necessarily a moderator. - Stewards selection of a moderator and schedules meetings among conflicting parties and moderator. - Documents all meetings and communications relevant to the conflict resolution process. - Promotes good-faith participation in the process by conflicting parties on a basis of mutual respect and growth towards better relationships and a stronger community. - If conflict resolution goes before the whole group, co-facilitates with Facilitator, and handles points of information about conflict resolution with reference to the documentation. - Does not act as Constable in conflicts involving self.

13 years, 1 month

Subiir, you are loved, but we need to do something about these:

by mattsenate＠gmail.com

// Matt

13 years, 1 month

Anaerobic Digester

by Matthew Meier

Hey Sudoers, I think this is kind of neat. I'm working today on an anaerobic digester. The first of its kind in America. Imported from Germany. It uses "Green Waste" (Food Garbage and Branches and Other Plant matter) and Digests it the same way a cow does. In the end you're left with High Nutrition Fertilizer, and natural gas which is pumped into a generator which powers the facility. There is no waste generated in this process. That's all I know but yeah. It's pretty neat! -Wolfy

13 years, 1 month

Fwd: [nerdsfornature] Fwd: Actipedia has launched!

by Marina Kukso

this may be relevant to our community's interests! ---------- Forwarded message ---------- From: Martha Pettit <marthagpettit(a)gmail.com> Date: Wed, Mar 6, 2013 at 2:39 PM Subject: [nerdsfornature] Fwd: Actipedia has launched! To: civic-design(a)googlegroups.com, nerdsfornature(a)googlegroups.com, occupy-design(a)googlegroups.com, occupydata(a)googlegroups.com Awesomeness! ---------- Forwarded message ---------- From: The Yes Lab <info(a)tmwrk.com> Date: Wed, Mar 6, 2013 at 2:14 PM Subject: Actipedia has launched! To: marthagpettit(a)gmail.com [image: Yes Lab] *"Actipedia" Crowdsourcing Platform Goes Public* *Database of creative activism case studies will inform and inspire a new generation of activists* The Yes Lab <http://yeslab.org/> and the Center for Artistic Activism<http://artisticactivism.org/>are announcing the launch of Actipedia.org, an open-access, user-generated database of creative activism case studies designed to inspire activists. "We designed Actipedia to inspire activists to more creative—and effective—actions," explains Stephen Duncombe, co-founder of the Center for Creative Activism. "Actipedia is about sharing the ways people challenge power and envision a better society," adds Andy Bichlbaum of the Yes Lab. "To change the world we've got to learn from each other." Actipedia is built on an open-source platform and is designed for ease of use, with simple formats for viewing, searching and posting examples. The site draws case studies from original submissions, reprinted news articles, and informal snippets of action reports. Although it is only now launching, Actipedia already hosts over 400 case studies and counting, from countries from all over the world. "Actipedia provides a space for inspiration and for contribution," noted one recent user. "Seeing all the amazing work going on around the world motivates me and makes me realize the potential impact I can have." Contact: Stephen Duncombe 212-998-7327 srd(a)artisticactivism.org http://actipedia.org *The Yes Lab <http://yeslab.org/> helps activist groups carry out media-getting creative actions, focused on their own campaign goals. Through brainstorms and trainings, social justice organizations can take advantage of all that the Yes Men—Andy Bichlbaum and Mike Bonanno—have learned, not only about our their own ways of doing things, but those practices they’ve come in contact with over the decade and a half they've been engaging in creative activism and tactical media.* *The Center for Artistic Activism <http://artisticactivism.org/> is a place to explore, analyze, and strengthen connections between social activism and artistic practice. The Center was founded by Stephen Duncombe, longtime activist and professor at New York University and Steve Lambert, longtime artist and professor at SUNY Purchase. Since 2009, the center has has served as a site for artistic activist trainings, actions, research and resources. The Center seeks to foster more creative activists and more effective artists.* Actipedia can be found at http://actipedia.org/ or on twitter @Actipedia<https://twitter.com/Actipedia/>, and the collaborators are available for interviews upon request. To unsubscribe from this newsletter, click here<http://tmwrk.com/civicrm/mailing/unsubscribe?reset=1&jid=147&qid=75941&h=5e…> . To never receive email from the Yes Lab, click here<http://tmwrk.com/civicrm/mailing/optout?reset=1&jid=147&qid=75941&h=5e9ebd4…> . This email was sent from: 20 Cooper Square Fifth Floor New York, NY 10003 United States [image: This has been a Yes Lab communique.] -- *Martha Pettit * User Experience Designer, Diligent Creative martha(a)diligentcreative.com http://staydiligent.com/ <http://diligentcreative.com/> (415) 283-5733 901 Mission Street, Suite 105 San Francisco, CA 94103 -- --- You received this message because you are subscribed to the Google Groups "NerdsforNature" group. To unsubscribe from this group and stop receiving emails from it, send an email to nerdsfornature+unsubscribe(a)googlegroups.com. To post to this group, send email to nerdsfornature(a)googlegroups.com. Visit this group at http://groups.google.com/group/nerdsfornature?hl=en. For more options, visit https://groups.google.com/groups/opt_out.

13 years, 1 month

Re: [sudo-discuss] 3/5 Microcontroller Project Hack Night: Wrap-up

by Jenny Ryan

Yay! I want to come and learn next week! wrt scheduling, please check out http:sudoroom.org/calendar for any potential conflicts, and make the recurring event ( http://sudoroom.org/wp-admin). Let me know if you need any help with that! Jenny http://jennyryan.net http://thepyre.org http://thevirtualcampfire.org http://technomadic.tumblr.com `~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~` "Technology is the campfire around which we tell our stories." -Laurie Anderson "Storytelling reveals meaning without committing the error of defining it." -Hannah Arendt "To define is to kill. To suggest is to create." -Stéphane Mallarmé ~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~` On Wed, Mar 6, 2013 at 1:21 PM, Morten H. D. Fuglsang <vallebo(a)gmail.com>wrote: > Yes. Yesterday was awesome and I am all in favor of making this a regular > thing. Suggested times work well for me, albeit I have no clue about > scheduling conflicts in terms of other things. > Having it split into two segments seem to make sense. Let's try it out > and see what happens :) > > Make a great day, > Morten H. D. Fuglsang > US: +1 415 799 6931 // skype: FlyvendeHest > > > On Wed, Mar 6, 2013 at 11:02 AM, rusty lindgren <rustylindgren(a)gmail.com>wrote: > >> I wish I had more time, or I would have stayed and learned some arduino >> stuffz. >> >> Good work sudo peepz! >> >> >> On Wed, Mar 6, 2013 at 11:01 AM, <hol(a)gaskill.com> wrote: >> >>> Hi Folks, >>> >>> We had a good session last night, with a mushroom environmental control >>> system and an RGB color mixer both advancing to the next operational stage, >>> a beer brewing robot gaining a good amount of ground on its grainy prey, >>> and a wood gasifier control system not getting much attention at all as the >>> maker was having such a good time helping others out and generally talking >>> shop. Also had a first-time solderer successfully execute a cut-and-solder >>> list on some heavy amperage connections, learned how to google our >>> debugging problems into submission, extolled the virtues of power >>> transistor arrays, and determined experimentally that it probably isn't a >>> good idea to put a glass jar of process water in a bench vise. Throw in >>> some chips and salsa, and a good night was had by all. >>> >>> I'd like to make this a recurring thing and build momentum in the cycle >>> of getting an idea, turning it into a project, building the project, and >>> coming away with more and better ideas. To facilitate this, we could take >>> over the newly (?) vacated alternating tuesday meetup spot at sudo room. I >>> propose we break it up into one night a month for fresh ideas and new >>> entrants, one night a month for refining and implementing more developed >>> ideas. Here is what I propose: >>> >>> Microcontroller Project Hack Night >>> @sudo room >>> March 26 @ 5:30PM - 11PM >>> April 23 @ 5:30PM - 11PM >>> May 21 @ 5:30PM - 11PM >>> "A shared worktime for tackling microcontroller and robotics projects. >>> Bring that complex project you've been putting off finishing and hunker >>> down around the communal soldering iron and serial terminal for a >>> high-productivity, high-spirited build night. Both independent work and >>> collaboration strongly engouraged, as are snacks and other refreshments." >>> >>> Basic Microcontroller Hack Night >>> @sudo room >>> April 9 @ 5:30PM - 11PM >>> May 7 @ 5:30PM - 11PM >>> "A good night for both beginning and more experienced microcontroller >>> users. Emphasis is on first principles, trying out new sensors and >>> actuators, testing out new ideas that haven't yet found a home in a >>> project, and cracking open black boxes of all sorts for fresh ideas. >>> Eventually we will have low-cost starter kits available to get beginners >>> hacking right away." >>> >>> Are there any scheduling conflicts? Do people want to meet up more than >>> twice a month or does this seem like enough to satisfy your need for group >>> hacking sessions in this area? My theory is that we can always meet more >>> than this, but scheduling too many (ie weekly) meetups will max out peoples >>> bandwidth and result in decreased cohesion between attendees. I will also >>> work on getting this added to the calendar in the near future. >>> >>> Cheers, >>> Hol >>> _______________________________________________ >>> sudo-discuss mailing list >>> sudo-discuss(a)lists.sudoroom.org >>> http://lists.sudoroom.org/listinfo/sudo-discuss >>> >> >> >> >> -- >> Cheers, >> >> Rusty Lindgren >> ** >> >> >> >> >> _______________________________________________ >> sudo-discuss mailing list >> sudo-discuss(a)lists.sudoroom.org >> http://lists.sudoroom.org/listinfo/sudo-discuss >> >> > > _______________________________________________ > sudo-discuss mailing list > sudo-discuss(a)lists.sudoroom.org > http://lists.sudoroom.org/listinfo/sudo-discuss > >

13 years, 1 month

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

sudo-discuss