16 Feb
2014
16 Feb
'14
9:34 p.m.
I dont like regimentation probably more than the next person, however I see a need to be
a bit more methodical in our organizing of activities so thst we can become more
accountable to one another.
I see this as helping to build bonds without stressing as a lot of the logistics work can
be done if we follow this format:
SUDO Registry
Tue.2:28am Oct.8.2013
Wheres the sudo registry?
name
contact info :
E.mail
Phone ( for txting)
Best times to contact members : "Anytime" is an unaccountable cop.out :(
Interests
Projects they are working on currently
When those projects are sceduled for work on
Resources available to help make the project successful
Resources required to maje the project
successful
Transparency is one of our principles, so we should utilize it for its positive uses and
become commited / accountable to one another as we work together and share space, time,
and resources.
I think this should go to the list in a truncated form asking people what they think of
the idea.
Yes I will work on making a wiki out of this,,,
"You are the source of Freedom : the price of Freedom is awareness and action"
18 Feb
18 Feb
9:30 a.m.
I'd be into helping set up a database to store this info, especially where it comes to
tracking projects so new people can browse through more interactively than just reading
down a page of text on the wiki. has anyone done some basic frontend to a SQL database
that we can copypasta?
cheers
Feb 16, 2014 09:35:55 PM, ecoeconomist11(a)gmail.com wrote:
I dont like regimentation probably more than the next person, however I see a need to be
a bit more methodical in our organizing of activities so thst we can become more
accountable to one another.
I see this as helping to build bonds without stressing
as a lot of the logistics work can be done if we follow this format:
SUDO Registry
Tue.2:28am Oct.8.2013
Wheres the sudo registry?
name
contact info :
E.mail
Phone ( for txting)
Best times to contact members : "Anytime" is an unaccountable cop.out :(
Interests
Projects they are working on currently
When those projects are sceduled for work on
Resources available to help make the project successful
Resources required to maje the project
successful
Transparency is one of our principles, so we should utilize it for its positive uses and
become commited / accountable to one another as we work together and share space, time,
and resources.
I think this should go to the list in a truncated form asking people what they think of
the idea.
Yes I will work on making a wiki out of this,,,
"You are the source of Freedom : the price of Freedom is awareness and action"
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
10:04 a.m.
Any chance of using something like civicrm as a starting point? I've set
that up a couple times (but am far from expert). there are a number of good
reasons not to reinvent the wheel, among them is having a reliable system
for keeping any sensitive data restricted to a trusted group.
Pete
On Feb 18, 2014 9:30 AM, "Hol Gaskill" <hol(a)gaskill.com> wrote:
I'd be into helping set up a database to store
this info, especially where
it comes to tracking projects so new people can browse through more
interactively than just reading down a page of text on the wiki. has
anyone done some basic frontend to a SQL database that we can copypasta?
cheers
Feb 16, 2014 09:35:55 PM, ecoeconomist11(a)gmail.com wrote:
I dont like regimentation probably more than the next person, however I
see a need to be a bit more methodical in our organizing of activities so
thst we can become more accountable to one another.
I see this as helping to build bonds without
stressing as a lot of the
logistics work can be done if we follow this format:
SUDO Registry
Tue.2:28am Oct.8.2013
Wheres the sudo registry?
name
contact info :
E.mail
Phone ( for txting)
Best times to contact members : "Anytime" is an unaccountable cop.out :(
Interests
Projects they are working on currently
When those projects are sceduled for work on
Resources available to help make the project successful
Resources required to maje the project
successful
Transparency is one of our principles, so we should utilize it for its
positive
uses and become commited / accountable to one another as we work
together and share space, time, and resources.
I think this should go to the list in a truncated form asking people what
they
think of the idea.
Yes I will work on making a wiki out of this,,,
"You are the source of Freedom : the price of Freedom is awareness and
action"
_______________________________________________
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
10:22 a.m.
just from browsing through their site it doesn't look like what I'm envisioning.
the work involved in setting up the database and the frontend shouldn't be much.
i've done it a number of times, but that was along time ago and try not to puke but it
was in visual basic 6. that being said, all of it would've failed promptly upon sql
injection. marc was working on something called mycelia for tracking projects and finding
people with matching skillsets, etc. haven't heard any news from that end. this has
been a persistent need for sudo room since the beginning though - if it requires
significant in-house tinkering i am not dissuaded
Feb 18, 2014 10:04:27 AM, peteforsyth(a)gmail.com wrote:
Any chance of using something like civicrm as a starting point? I've set that up a
couple times (but am far from expert). there are a number of good reasons not to reinvent
the wheel, among them is having a reliable system for keeping any sensitive data
restricted to a trusted group.
Pete
On Feb 18, 2014 9:30 AM, "Hol Gaskill" hol(a)gaskill.com> wrote:
I'd be into helping set up a database to store this info, especially where it
comes to tracking projects so new people can browse through more interactively than just
reading down a page of text on the wiki. has anyone done some basic frontend to a SQL
database that we can copypasta?
cheers
Feb 16, 2014 09:35:55 PM,
ecoeconomist11(a)gmail.com wrote:
I dont like regimentation probably more than
the next person, however I see a need to be a bit more methodical in our organizing of
activities so thst we can become more accountable to one another.
>I see this as helping to build bonds without
stressing as a lot of the logistics work can be done if we follow this format:
>SUDO Registry
>Tue.2:28am Oct.8.2013
>Wheres the sudo registry?
>name
>contact info :
>E.mail
>Phone ( for txting)
>Best times to contact members :
"Anytime" is an unaccountable cop.out :(
>Interests
>Projects they are working on currently
>When those projects are sceduled for work
on
>Resources available to help make the project
successful
>Resources required to maje the project
>successful
>Transparency is one of our principles, so we
should utilize it for its positive uses and become commited / accountable to one another
as we work together and share space, time, and resources.
>I think this should go to the list in a
truncated form asking people what they think of the idea.
>Yes I will work on making a wiki out of
this,,,
>"You are the source of Freedom : the
price of Freedom is awareness and action"
>_______________________________________________
>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
10:48 a.m.
There is a stillborn and defunct project on gitorious called
sudosuite<https://gitorious.org/sudosuite> that
may serve as a point of organization.
It seems to me that a happy medium should be found between starting from
scratch and using something out of the box, and that that medium is close
to out-of-the-box-remix. Details very hazy.
On Tue, Feb 18, 2014 at 10:22 AM, Hol Gaskill <hol(a)gaskill.com> wrote:
just from browsing through their site it doesn't look like what I'm
envisioning. the work involved in setting up the database and the frontend
shouldn't be much. i've done it a number of times, but that was along
time ago and try not to puke but it was in visual basic 6. that being
said, all of it would've failed promptly upon sql injection. marc was
working on something called mycelia for tracking projects and finding
people with matching skillsets, etc. haven't heard any news from that end.
this has been a persistent need for sudo room since the beginning though -
if it requires significant in-house tinkering i am not dissuaded
Feb 18, 2014 10:04:27 AM, peteforsyth(a)gmail.com wrote:
Any chance of using something like civicrm as a starting point? I've set
that up a couple times (but am far from expert). there are a number of good
reasons not to reinvent the wheel, among them is having a reliable system
for keeping any sensitive data restricted to a trusted group.
Pete
On Feb 18, 2014 9:30 AM, "Hol Gaskill" hol(a)gaskill.com> wrote:
I'd be into helping set up a database to store this info, especially where
it comes to tracking projects so new people can browse through more
interactively than just reading down a page of text on the wiki. has
anyone done some basic frontend to a SQL database that we can copypasta?
cheers
Feb 16, 2014 09:35:55 PM,
ecoeconomist11(a)gmail.com wrote:
I dont like regimentation probably more
than the next person, however I
see a need to be a bit more methodical in our organizing of activities so
thst we can become more accountable to one another.
>I see this as helping to build bonds
without stressing as a lot of the
logistics work can be done if we follow this format:
>SUDO Registry
>Tue.2:28am Oct.8.2013
>Wheres the sudo registry?
>name
>contact info :
>E.mail
>Phone ( for txting)
>Best times to contact members :
"Anytime" is an unaccountable cop.out :(
>Interests
>Projects they are working on
currently
>When those projects are
sceduled for work on
>Resources available to help
make the project successful
>Resources required to maje the
project
>successful
>Transparency is one of our
principles, so we should utilize it for its
positive uses and become commited / accountable to one another as we work
together and share space, time, and resources.
>I think this should go to the
list in a truncated form asking people what
they think of the idea.
>Yes I will work on making a
wiki out of this,,,
>"You are the source of
Freedom : the price of Freedom is awareness and
action"
>_______________________________________________
>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
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
1:29 p.m.
Hey Troy! Thanks for the poke!
tl;dr: Fill out your wiki userpage with current projects and contact info!
Help with the membership registry (PHP) and/or mycelia (node)!
ABOUT THE DATA
a) I don't want everyone at sudo room to be able to call or text me. Fairly
certain I'm not alone in this. If you ask for my number and I give it to
you, we've just created trust through consent. Would like to promote a
case-by-case approach to providing sensitive information, and not store it
ourselves. This is why, when I asked for up-to-date membership information,
I only asked for an email and a name/nym.
b) I think we should encourage people to fill out their user pages on the
wiki, and include there things like projects, contact info, and public
keys. We sent out a template for user pages long ago, can't remember who
put it together (Marina, I think?). Here are some examples of nice user
pages:
https://sudoroom.org/wiki/User:Juul
https://sudoroom.org/wiki/User:Tunabananas
https://sudoroom.org/wiki/User:Mk30
https://sudoroom.org/wiki/User:Maximilianklein
ABOUT THE MEMBER REGISTRY / SELTZERCRM
I'm running the nascent member registry at http://mycelia.cc/crm, the code
for which is here <https://github.com/elplatt/seltzer> if anyone wants to
look and see if they can build something on top of this. It's PHP. I did a
decent bit of research and this was the most viable FOSS membership
registry system I could find. Soon will port it over to sudoroom.org and
push to Github (hopefully tomorrow). I've been asking for help at the
meetings as it would be great to have more people who want to work on this,
but it needs to happen so I'm not waiting around for a team to form.
ABOUT MYCELIA
The goal of Mycelia <http://mycelia.cc> is to create a decentralized
database for documenting projects, people (skills) and objects between
hackerspaces and also matchmaking between them. Pub/sub [publish /
subscribe] model encouraging folks to have concrete projects about which
they publish updates, or otherwise be a subscriber consuming the updates of
others :)
Unfortunately, I can't code it myself and Marc's busy with sudomesh and
freestore. What's up on Github is essentially Labitrack (the QR-code
sticker inventory system we're using at sudo) converted into NodeJS and
LevelDB. It's definitely a priority project, but not #1 right now. CC'ing
substack in case he's interested in this project.
Cheers,
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 Tue, Feb 18, 2014 at 10:48 AM, Anthony Di Franco <di.franco(a)gmail.com>wrote;wrote:
There is a stillborn and defunct project on gitorious
called sudosuite<https://gitorious.org/sudosuite> that
may serve as a point of organization.
It seems to me that a happy medium should be found between starting from
scratch and using something out of the box, and that that medium is close
to out-of-the-box-remix. Details very hazy.
On Tue, Feb 18, 2014 at 10:22 AM, Hol Gaskill <hol(a)gaskill.com> wrote:
just from browsing through their site it doesn't look like what I'm
envisioning. the work involved in setting up the database and the frontend
shouldn't be much. i've done it a number of times, but that was along
time ago and try not to puke but it was in visual basic 6. that being
said, all of it would've failed promptly upon sql injection. marc was
working on something called mycelia for tracking projects and finding
people with matching skillsets, etc. haven't heard any news from that end.
this has been a persistent need for sudo room since the beginning though -
if it requires significant in-house tinkering i am not dissuaded
Feb 18, 2014 10:04:27 AM, peteforsyth(a)gmail.com wrote:
Any chance of using something like civicrm as a starting point? I've set
that up a couple times (but am far from expert). there are a number of good
reasons not to reinvent the wheel, among them is having a reliable system
for keeping any sensitive data restricted to a trusted group.
Pete
On Feb 18, 2014 9:30 AM, "Hol Gaskill" hol(a)gaskill.com> wrote:
I'd be into helping set up a database to store this info, especially
where it comes to tracking projects so new people can browse through more
interactively than just reading down a page of text on the wiki. has
anyone done some basic frontend to a SQL database that we can copypasta?
cheers
Feb 16, 2014 09:35:55 PM,
ecoeconomist11(a)gmail.com wrote:
I dont like regimentation probably more
than the next person, however I
see a need to be a bit more methodical in our organizing of activities so
thst we can become more accountable to one another.
>I see this as helping to build bonds
without stressing as a lot of the
logistics work can be done if we follow this format:
>SUDO Registry
>Tue.2:28am Oct.8.2013
>Wheres the sudo registry?
>name
>contact info :
>E.mail
>Phone ( for txting)
>Best times to contact members :
"Anytime" is an unaccountable cop.out :(
>Interests
>Projects they are working on
currently
>When those projects are
sceduled for work on
>Resources available to help
make the project successful
>Resources required to maje the
project
>successful
>Transparency is one of our
principles, so we should utilize it for its
positive uses and become commited / accountable to one another as we work
together and share space, time, and resources.
>I think this should go to the
list in a truncated form asking people
what they think of the idea.
>Yes I will work on making a
wiki out of this,,,
>"You are the source of
Freedom : the price of Freedom is awareness and
action"
>_______________________________________________
>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
_______________________________________________
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
1:35 p.m.
Oh! I should add that we could do really interesting things with our user
pages, linking to projects through tags and categories, creating portals.
I'd love to spend a Today We Learned working on making our wiki more
awesome, semantic, navigable (Vicky? Pete?).
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 Tue, Feb 18, 2014 at 1:29 PM, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Hey Troy! Thanks for the poke!
tl;dr: Fill out your wiki userpage with current projects and contact info!
Help with the membership registry (PHP) and/or mycelia (node)!
ABOUT THE DATA
a) I don't want everyone at sudo room to be able to call or text me.
Fairly certain I'm not alone in this. If you ask for my number and I give
it to you, we've just created trust through consent. Would like to promote
a case-by-case approach to providing sensitive information, and not store
it ourselves. This is why, when I asked for up-to-date membership
information, I only asked for an email and a name/nym.
b) I think we should encourage people to fill out their user pages on the
wiki, and include there things like projects, contact info, and public
keys. We sent out a template for user pages long ago, can't remember who
put it together (Marina, I think?). Here are some examples of nice user
pages:
https://sudoroom.org/wiki/User:Juul
https://sudoroom.org/wiki/User:Tunabananas
https://sudoroom.org/wiki/User:Mk30
https://sudoroom.org/wiki/User:Maximilianklein
ABOUT THE MEMBER REGISTRY / SELTZERCRM
I'm running the nascent member registry at http://mycelia.cc/crm, the
code for which is here <https://github.com/elplatt/seltzer> if anyone
wants to look and see if they can build something on top of this. It's PHP.
I did a decent bit of research and this was the most viable FOSS membership
registry system I could find. Soon will port it over to sudoroom.org and
push to Github (hopefully tomorrow). I've been asking for help at the
meetings as it would be great to have more people who want to work on this,
but it needs to happen so I'm not waiting around for a team to form.
ABOUT MYCELIA
The goal of Mycelia <http://mycelia.cc> is to create a decentralized
database for documenting projects, people (skills) and objects between
hackerspaces and also matchmaking between them. Pub/sub [publish /
subscribe] model encouraging folks to have concrete projects about which
they publish updates, or otherwise be a subscriber consuming the updates of
others :)
Unfortunately, I can't code it myself and Marc's busy with sudomesh and
freestore. What's up on Github is essentially Labitrack (the QR-code
sticker inventory system we're using at sudo) converted into NodeJS and
LevelDB. It's definitely a priority project, but not #1 right now. CC'ing
substack in case he's interested in this project.
Cheers,
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 Tue, Feb 18, 2014 at 10:48 AM, Anthony Di Franco <di.franco(a)gmail.com>wrote;wrote:
There is a stillborn and defunct project on
gitorious called sudosuite<https://gitorious.org/sudosuite> that
may serve as a point of organization.
It seems to me that a happy medium should be found between starting from
scratch and using something out of the box, and that that medium is close
to out-of-the-box-remix. Details very hazy.
On Tue, Feb 18, 2014 at 10:22 AM, Hol Gaskill <hol(a)gaskill.com> wrote:
just from browsing through their site it doesn't look like what I'm
envisioning. the work involved in setting up the database and the frontend
shouldn't be much. i've done it a number of times, but that was along
time ago and try not to puke but it was in visual basic 6. that being
said, all of it would've failed promptly upon sql injection. marc was
working on something called mycelia for tracking projects and finding
people with matching skillsets, etc. haven't heard any news from that end.
this has been a persistent need for sudo room since the beginning though -
if it requires significant in-house tinkering i am not dissuaded
Feb 18, 2014 10:04:27 AM, peteforsyth(a)gmail.com wrote:
Any chance of using something like civicrm as a starting point? I've set
that up a couple times (but am far from expert). there are a number of good
reasons not to reinvent the wheel, among them is having a reliable system
for keeping any sensitive data restricted to a trusted group.
Pete
On Feb 18, 2014 9:30 AM, "Hol Gaskill" hol(a)gaskill.com> wrote:
I'd be into helping set up a database to store this info, especially
where it comes to tracking projects so new people can browse through more
interactively than just reading down a page of text on the wiki. has
anyone done some basic frontend to a SQL database that we can copypasta?
cheers
Feb 16, 2014 09:35:55 PM,
ecoeconomist11(a)gmail.com wrote:
I dont like regimentation probably more
than the next person, however I
see a need to be a bit more methodical in our organizing of activities so
thst we can become more accountable to one another.
>I see this as helping to build bonds
without stressing as a lot of the
logistics work can be done if we follow this format:
>SUDO Registry
>Tue.2:28am Oct.8.2013
>Wheres the sudo registry?
>name
>contact info :
>E.mail
>Phone ( for txting)
>Best times to contact members :
"Anytime" is an unaccountable cop.out :(
>Interests
>Projects they are working on
currently
>When those projects are
sceduled for work on
>Resources available to help
make the project successful
>Resources required to maje the
project
>successful
>Transparency is one of our
principles, so we should utilize it for its
positive uses and become commited / accountable to one another as we work
together and share space, time, and resources.
>I think this should go to the
list in a truncated form asking people
what they think of the idea.
>Yes I will work on making a
wiki out of this,,,
>"You are the source of
Freedom : the price of Freedom is awareness and
action"
>_______________________________________________
>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
_______________________________________________
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
1:56 p.m.
This project brings up the age-old issue of transparency vs privacy. Too
much 'transparency' can be bad in ways Jenny pointed out, too much privacy
keeps work from being more collaborative which is endemic to the attraction
of hackerspaces and collectives. In general i feel transparency is too
privileged. We forget transparency often involves a loss or giving up of
individual agency and control, not just a gain in centralizeable,
actionable 'data'.
I do think this tradeoff needs to be modulated and controlled at all
times by individuals themselves. In my view there shouldnt be a repo where
you are expected to list what you deem is your personal info, even matching
names to 'nym's if ppl arent down for that. But i think matching nym's to
projects would be useful, if folks are willing to document say what part of
what project they are working on, as in dev environments. And perhaps
people could set their own privacy settings, only share at their discretion
certain info with certain people. I would participate in something like
this if such privacy controls were part of it from the outset. Privacy,
with respect to user-controllable visibility of personal info, needs to be
thought of as a fundamental integral component, not an add-on, for every
software product.
my 2c. carry on
On Tuesday, February 18, 2014, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Oh! I should add that we could do really interesting
things with our user
pages, linking to projects through tags and categories, creating portals.
I'd love to spend a Today We Learned working on making our wiki more
awesome, semantic, navigable (Vicky? Pete?).
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 Tue, Feb 18, 2014 at 1:29 PM, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Hey Troy! Thanks for the poke!
tl;dr: Fill out your wiki userpage with current projects and contact info!
Help with the membership registry (PHP) and/or mycelia (node)!
ABOUT THE DATA
a) I don't want everyone at sudo room to be able to call or text me.
Fairly certain I'm not alone in this. If you ask for my number and I give
it to you, we've just created trust through consent. Would like to promote
a case-by-case approach to providing sensitive information, and not store
it ourselves. This is why, when I asked for up-to-date membership
information, I only asked for an email and a name/nym.
b) I think we should encourage people to fill out their user pages on the
wiki, and include there things like projects, contact info, and public
keys. We sent out a template for user pages long ago, can't remember who
put it together (Marina, I think?). Here are some examples of nice user
pages:
https://sudoroom.org/wiki/User:Juul
https://sudoroom.org/wiki/User:Tunabananas
https://sudoroom.org/wiki/User:Mk30
https://sudoroom.org/wiki/User:Maximilianklein
ABOUT THE MEMBER REGISTRY / SELTZERCRM
I'm running the nascent member registry at http://mycelia.cc/crm, the
code for which is here <https://github.com/elplatt/seltzer> if anyone
wants to look and see if they can build something on top of this. It's PHP.
I did a decent bit of research and this was the most viable FOSS membership
registry system I could find. Soon will port it over to sudoroom.org and
push to Github (hopefully tomorrow). I've been asking for help at the
meetings as it would be great to have more people who want to work on this,
but it needs to happen so I'm not waiting around for a team to form.
ABOUT MYCELIA
The goal of Mycelia <http://mycelia.cc> is to create a decentralized
database for documenting projects, people (skills) and objects between
hackerspaces and also matchmaking between them. Pub/sub [publish /
subscribe] model encouraging folks to have concrete projects about which
they publish updates, or otherwise be a subscriber consuming the updates of
others :)
Unfortunately, I can't code it myself and Marc's busy with sudomesh and
freestore. What's up on Github is essentially Labitrack (the QR-code
sticker inventory system we're using at sudo) converted into NodeJS and
LevelDB. It's definitely a priority project, but not #1 right now. CC'ing
substack in case he's interested in this project.
Cheers,
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 Tue, Feb 18, 2014 at 10:48 AM, Anthony Di Franco <di.franco(a)gmail.com>wrote;wrote:
There is a stillborn and defunct project on gitorious called
sudosuite<https://gitorious.org/sudosuite> that
may serve as a point of organization.
2:39 p.m.
And I should add, Mycelia does seem like the most useful way to aggregate
info re: people, things, skills.
Ideally what we'd want in my view for a directory Mycelia might query is
one somewhat like a password manager, in which user contact info is
encrypted at rest to that user even to admins (as with passwords),
with fields invisiblizable to everyone else unless they are shared (not
unlike filesharing). IE a privacy token could be set for specific fields,
so users toggle what fields are visible to whom, or template which fields
are shared by default (ie email) and which fields must be manually made
accessible to specific users (ie celfone, home address, etc), or
reshareable by others, etc. I realize this doesnt exist (or does it..?) but
it could be useful architecture for safely sharing personal info.
Then a way to publish/sub this db via carddav so we can have this sync
to our phones..
I was looking into this the other day and in general the current state of
the market with respect to directory services, contact mgmt & CRM
still seems pretty impoverished with respect to user-settable access
controls and field-specific privacy, so far as I can tell: You either add
your (private) cel to your vCard, or you dont. No way to modulate down to
this level. Actually I think M$ has some basic way to do this in AD-enabled
GALs.. but nothing OSS-based as far as I know of, at least.
On Tuesday, February 18, 2014, David Keenan <dkeenan44(a)gmail.com> wrote:
This project brings up the age-old issue of
transparency vs privacy. Too
much 'transparency' can be bad in ways Jenny pointed out, too much privacy
keeps work from being more collaborative which is endemic to the attraction
of hackerspaces and collectives. In general i feel transparency is too
privileged. We forget transparency often involves a loss or giving up of
individual agency and control, not just a gain in centralizeable,
actionable 'data'.
I do think this tradeoff needs to be modulated and controlled at all
times by individuals themselves. In my view there shouldnt be a repo where
you are expected to list what you deem is your personal info, even matching
names to 'nym's if ppl arent down for that. But i think matching nym's to
projects would be useful, if folks are willing to document say what part of
what project they are working on, as in dev environments. And perhaps
people could set their own privacy settings, only share at their discretion
certain info with certain people. I would participate in something like
this if such privacy controls were part of it from the outset. Privacy,
with respect to user-controllable visibility of personal info, needs to be
thought of as a fundamental integral component, not an add-on, for every
software product.
my 2c. carry on
On Tuesday, February 18, 2014, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Oh! I should add that we could do really interesting things with our user
pages, linking to projects through tags and categories, creating portals.
I'd love to spend a Today We Learned working on making our wiki more
awesome, semantic, navigable (Vicky? Pete?).
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 Tue, Feb 18, 2014 at 1:29 PM, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Hey Troy! Thanks for the poke!
tl;dr: Fill out your wiki userpage with current projects and contact info!
Help with the membership registry (PHP) and/or mycelia (node)!
ABOUT THE DATA
a) I don't want everyone at sudo room to be able to call or text me.
Fairly certain I'm not alone in this. If you ask for my number and I give
it to you, we've just created trust through consent. Would like to promote
a case-by-case approach to providing sensitive information, and not store
it ourselves. This is why, when I asked for up-to-date membership
information, I only asked for an email and a name/nym.
b) I think we should encourage people to fill out their user pages on the
wiki, and include there things like projects, contact info, and public
keys. We sent out a template for user pages long ago, can't remember who
put it together (Marina, I think?). Here are some examples of nice user
pages:
https://sudoroom.org/wiki/User:Juul
https://sudoroom.org/wiki/User:Tunabananas
https://sudoroom.org/wiki/User:Mk30
https://sudoroom.org/wiki/User:Maximilianklein
ABOUT THE MEMBER REGISTRY / SELTZERCRM
I'm running the nascent member registry at http://mycelia.cc/crm, the
code for which is here <https://github.com/elplatt/seltzer> if anyone
wants to look and see if they can build something on top of this. It's PHP.
I did a decent bit of research and this was the most viable FOSS membership
registry system I could find. Soon will port it over to sudoroom.org and
push to Github (hopefully tomorrow). I've been asking for help at the
meetings as it would be great to have more people who want to work on this,
but it needs to happen so I'm not waiting around for a team to form.
ABOUT MYCELIA
The goal of Mycelia <http://mycelia.cc> is to create a decentralized
database for documenting projects, people (skills) and objects between
hackerspaces and also matchmaking between them. Pub/sub [publish /
subscribe] model encouraging folks to have concrete projects about which
they publish updates, or otherwise be a subscriber consuming the updates of
others :)
Unfortunately, I can't code it myself and Marc's busy with sudomesh and
freestore. What's up on Github is essentially Labitrack (the QR-code
sticker inventory system we're using at sudo) converted into NodeJS and
LevelDB. It's definitely a priority project, but not #1 right now. CC'ing
substack in case he's interested in this project.
Cheers,
Jenny
http://jennyryan.net
http://thepyre.org
http://thevirtualcampfire.org
<http://technomadic.tumblr.com/>
2:49 p.m.
I just wanted to chime in to thank everyone working on this, especially Jenny, for being
so thoughtful and careful about these trade-offs between varying degrees of transparency
and collaborative effectiveness. Sudo Room has been most exceptional in this regard
throughout, even when it's been hard and when there've been no examples to
follow.
I also wanted to add that I think there are also circumstances in which having a subset of
people (from multi-stakeholder points of view, etc), be the trusted gatekeepers of these
borderline cases of information sharing is the wisest course to maximize benefits for all.
So long as the gatekeepers aren't and don't become choke-points without enough
capacity to double-check and distribute oversight to affirm people's trust in the
process.
In an earlier email, I had expressed concern that this would be funneled through only one
person. Someone pointed out to me that its brevity made it come off as rude, and I
apologize for that.
On Feb 18, 2014, at 2:39 PM, David Keenan wrote:
And I should add, Mycelia does seem like the most
useful way to aggregate info re: people, things, skills.
Ideally what we'd want in my view for a directory Mycelia might query is one somewhat
like a password manager, in which user contact info is encrypted at rest to that user even
to admins (as with passwords), with fields invisiblizable to everyone else unless they are
shared (not unlike filesharing). IE a privacy token could be set for specific fields, so
users toggle what fields are visible to whom, or template which fields are shared by
default (ie email) and which fields must be manually made accessible to specific users (ie
celfone, home address, etc), or reshareable by others, etc. I realize this doesnt exist
(or does it..?) but it could be useful architecture for safely sharing personal info.
Then a way to publish/sub this db via carddav so we can have this sync to our phones..
I was looking into this the other day and in general the current state of the market with
respect to directory services, contact mgmt & CRM still seems pretty impoverished with
respect to user-settable access controls and field-specific privacy, so far as I can tell:
You either add your (private) cel to your vCard, or you dont. No way to modulate down to
this level. Actually I think M$ has some basic way to do this in AD-enabled GALs.. but
nothing OSS-based as far as I know of, at least.
On Tuesday, February 18, 2014, David Keenan <dkeenan44(a)gmail.com> wrote:
This project brings up the age-old issue of transparency vs privacy. Too much
'transparency' can be bad in ways Jenny pointed out, too much privacy keeps work
from being more collaborative which is endemic to the attraction of hackerspaces and
collectives. In general i feel transparency is too privileged. We forget transparency
often involves a loss or giving up of individual agency and control, not just a gain in
centralizeable, actionable 'data'.
I do think this tradeoff needs to be modulated and controlled at all times by individuals
themselves. In my view there shouldnt be a repo where you are expected to list what you
deem is your personal info, even matching names to 'nym's if ppl arent down for
that. But i think matching nym's to projects would be useful, if folks are willing to
document say what part of what project they are working on, as in dev environments. And
perhaps people could set their own privacy settings, only share at their discretion
certain info with certain people. I would participate in something like this if such
privacy controls were part of it from the outset. Privacy, with respect to
user-controllable visibility of personal info, needs to be thought of as a fundamental
integral component, not an add-on, for every software product.
my 2c. carry on
On Tuesday, February 18, 2014, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Oh! I should add that we could do really interesting things with our user pages, linking
to projects through tags and categories, creating portals. I'd love to spend a Today
We Learned working on making our wiki more awesome, semantic, navigable (Vicky? Pete?).
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 Tue, Feb 18, 2014 at 1:29 PM, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Hey Troy! Thanks for the poke!
tl;dr: Fill out your wiki userpage with current projects and contact info! Help with the
membership registry (PHP) and/or mycelia (node)!
ABOUT THE DATA
a) I don't want everyone at sudo room to be able to call or text me. Fairly certain
I'm not alone in this. If you ask for my number and I give it to you, we've just
created trust through consent. Would like to promote a case-by-case approach to providing
sensitive information, and not store it ourselves. This is why, when I asked for
up-to-date membership information, I only asked for an email and a name/nym.
b) I think we should encourage people to fill out their user pages on the wiki, and
include there things like projects, contact info, and public keys. We sent out a template
for user pages long ago, can't remember who put it together (Marina, I think?). Here
are some examples of nice user pages:
https://sudoroom.org/wiki/User:Juul
https://sudoroom.org/wiki/User:Tunabananas
https://sudoroom.org/wiki/User:Mk30
https://sudoroom.org/wiki/User:Maximilianklein
ABOUT THE MEMBER REGISTRY / SELTZERCRM
I'm running the nascent member registry at http://mycelia.cc/crm, the code for which
is here if anyone wants to look and see if they can build something on top of this.
It's PHP. I did a decent bit of research and this was the most viable FOSS membership
registry system I could find. Soon will port it over to sudoroom.org and push to Github
(hopefully tomorrow). I've been asking for help at the meetings as it would be great
to have more people who want to work on this, but it needs to happen so I'm not
waiting around for a team to form.
ABOUT MYCELIA
The goal of Mycelia is to create a decentralized database for documenting projects,
people (skills) and objects between hackerspaces and also matchmaking between them.
Pub/sub [publish / subscribe] model encouraging folks to have concrete projects about
which they publish updates, or otherwise be a subscriber consuming the updates of others
:)
Unfortunately, I can't code it myself and Marc's busy with sudomesh and
freestore. What's up on Github is essentially Labitrack (the QR-code sticker inventory
system we're using at sudo) converted into NodeJS and LevelDB. It's definitely a
priority project, but not #1 right now. CC'ing substack in case he's interested in
this project.
Cheers,
Jenny
http://jennyryan.net
http://thepyre.org
http://thevirtualcampfire.org
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
5:42 p.m.
Perusing userpages on break at work, and Romy's is extra-inspiring!
https://sudoroom.org/wiki/User:Romyilano
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 Tue, Feb 18, 2014 at 2:49 PM, eddan.com <eddan(a)sudoroom.tv> wrote:
I just wanted to chime in to thank everyone working on
this, especially
Jenny, for being so thoughtful and careful about these trade-offs between
varying degrees of transparency and collaborative effectiveness. Sudo Room
has been most exceptional in this regard throughout, even when it's been
hard and when there've been no examples to follow.
I also wanted to add that I think there are also circumstances in which
having a subset of people (from multi-stakeholder points of view, etc), be
the trusted gatekeepers of these borderline cases of information sharing is
the wisest course to maximize benefits for all. So long as the gatekeepers
aren't and don't become choke-points without enough capacity to
double-check and distribute oversight to affirm people's trust in the
process.
In an earlier email, I had expressed concern that this would be funneled
through only one person. Someone pointed out to me that its brevity made it
come off as rude, and I apologize for that.
On Feb 18, 2014, at 2:39 PM, David Keenan wrote:
And I should add, Mycelia does seem like the most useful way to aggregate
info re: people, things, skills.
Ideally what we'd want in my view for a directory Mycelia might query is
one somewhat like a password manager, in which user contact info is
encrypted at rest to that user even to admins (as with passwords),
with fields invisiblizable to everyone else unless they are shared (not
unlike filesharing). IE a privacy token could be set for specific fields,
so users toggle what fields are visible to whom, or template which fields
are shared by default (ie email) and which fields must be manually made
accessible to specific users (ie celfone, home address, etc), or
reshareable by others, etc. I realize this doesnt exist (or does it..?) but
it could be useful architecture for safely sharing personal info.
Then a way to publish/sub this db via carddav so we can have this sync
to our phones..
I was looking into this the other day and in general the current state of
the market with respect to directory services, contact mgmt & CRM
still seems pretty impoverished with respect to user-settable access
controls and field-specific privacy, so far as I can tell: You either add
your (private) cel to your vCard, or you dont. No way to modulate down to
this level. Actually I think M$ has some basic way to do this in AD-enabled
GALs.. but nothing OSS-based as far as I know of, at least.
On Tuesday, February 18, 2014, David Keenan <dkeenan44(a)gmail.com> wrote:
This project brings up the age-old issue of
transparency vs privacy. Too
much 'transparency' can be bad in ways Jenny pointed out, too much privacy
keeps work from being more collaborative which is endemic to the attraction
of hackerspaces and collectives. In general i feel transparency is too
privileged. We forget transparency often involves a loss or giving up of
individual agency and control, not just a gain in centralizeable,
actionable 'data'.
I do think this tradeoff needs to be modulated and controlled at all
times by individuals themselves. In my view there shouldnt be a repo where
you are expected to list what you deem is your personal info, even matching
names to 'nym's if ppl arent down for that. But i think matching nym's to
projects would be useful, if folks are willing to document say what part of
what project they are working on, as in dev environments. And perhaps
people could set their own privacy settings, only share at their discretion
certain info with certain people. I would participate in something like
this if such privacy controls were part of it from the outset. Privacy,
with respect to user-controllable visibility of personal info, needs to be
thought of as a fundamental integral component, not an add-on, for every
software product.
my 2c. carry on
On Tuesday, February 18, 2014, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Oh! I should add that we could do really interesting things with our user
pages, linking to projects through tags and categories, creating portals.
I'd love to spend a Today We Learned working on making our wiki more
awesome, semantic, navigable (Vicky? Pete?).
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 Tue, Feb 18, 2014 at 1:29 PM, Jenny Ryan <tunabananas(a)gmail.com>wrote;wrote:
Hey Troy! Thanks for the poke!
tl;dr: Fill out your wiki userpage with current projects and contact
info! Help with the membership registry (PHP) and/or mycelia (node)!
ABOUT THE DATA
a) I don't want everyone at sudo room to be able to call or text me.
Fairly certain I'm not alone in this. If you ask for my number and I give
it to you, we've just created trust through consent. Would like to promote
a case-by-case approach to providing sensitive information, and not store
it ourselves. This is why, when I asked for up-to-date membership
information, I only asked for an email and a name/nym.
b) I think we should encourage people to fill out their user pages on the
wiki, and include there things like projects, contact info, and public
keys. We sent out a template for user pages long ago, can't remember who
put it together (Marina, I think?). Here are some examples of nice user
pages:
https://sudoroom.org/wiki/User:Juul
https://sudoroom.org/wiki/User:Tunabananas
https://sudoroom.org/wiki/User:Mk30
https://sudoroom.org/wiki/User:Maximilianklein
ABOUT THE MEMBER REGISTRY / SELTZERCRM
I'm running the nascent member registry at http://mycelia.cc/crm, the
code for which is here <https://github.com/elplatt/seltzer> if anyone
wants to look and see if they can build something on top of this. It's PHP.
I did a decent bit of research and this was the most viable FOSS membership
registry system I could find. Soon will port it over to sudoroom.org and
push to Github (hopefully tomorrow). I've been asking for help at the
meetings as it would be great to have more people who want to work on this,
but it needs to happen so I'm not waiting around for a team to form.
ABOUT MYCELIA
The goal of Mycelia <http://mycelia.cc/> is to create a decentralized
database for documenting projects, people (skills) and objects between
hackerspaces and also matchmaking between them. Pub/sub [publish /
subscribe] model encouraging folks to have concrete projects about which
they publish updates, or otherwise be a subscriber consuming the updates of
others :)
Unfortunately, I can't code it myself and Marc's busy with sudomesh and
freestore. What's up on Github is essentially Labitrack (the QR-code
sticker inventory system we're using at sudo) converted into NodeJS and
LevelDB. It's definitely a priority project, but not #1 right now. CC'ing
substack in case he's interested in this project.
Cheers,
Jenny
http://jennyryan.net
http://thepyre.org
http://thevirtualcampfire.org
<http://technomadic.tumblr.com/>
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
11:53 p.m.
I wouldn't mind contributing to this/sharing some info about myself as it's
reasonably easy to update (honest, I really am not that web savvy).
Otherwise, it will happen when it happens.
-chrisbee
On Tue, Feb 18, 2014 at 5:42 PM, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Perusing userpages on break at work, and Romy's is
extra-inspiring!
https://sudoroom.org/wiki/User:Romyilano
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 Tue, Feb 18, 2014 at 2:49 PM, eddan.com <eddan(a)sudoroom.tv> wrote:
I just wanted to chime in to thank everyone
working on this, especially
Jenny, for being so thoughtful and careful about these trade-offs between
varying degrees of transparency and collaborative effectiveness. Sudo Room
has been most exceptional in this regard throughout, even when it's been
hard and when there've been no examples to follow.
I also wanted to add that I think there are also circumstances in which
having a subset of people (from multi-stakeholder points of view, etc), be
the trusted gatekeepers of these borderline cases of information sharing is
the wisest course to maximize benefits for all. So long as the gatekeepers
aren't and don't become choke-points without enough capacity to
double-check and distribute oversight to affirm people's trust in the
process.
In an earlier email, I had expressed concern that this would be funneled
through only one person. Someone pointed out to me that its brevity made it
come off as rude, and I apologize for that.
On Feb 18, 2014, at 2:39 PM, David Keenan wrote:
And I should add, Mycelia does seem like the most useful way to aggregate
info re: people, things, skills.
Ideally what we'd want in my view for a directory Mycelia might query is
one somewhat like a password manager, in which user contact info is
encrypted at rest to that user even to admins (as with passwords),
with fields invisiblizable to everyone else unless they are shared (not
unlike filesharing). IE a privacy token could be set for specific fields,
so users toggle what fields are visible to whom, or template which fields
are shared by default (ie email) and which fields must be manually made
accessible to specific users (ie celfone, home address, etc), or
reshareable by others, etc. I realize this doesnt exist (or does it..?) but
it could be useful architecture for safely sharing personal info.
Then a way to publish/sub this db via carddav so we can have this sync
to our phones..
I was looking into this the other day and in general the current state
of the market with respect to directory services, contact mgmt & CRM
still seems pretty impoverished with respect to user-settable access
controls and field-specific privacy, so far as I can tell: You either add
your (private) cel to your vCard, or you dont. No way to modulate down to
this level. Actually I think M$ has some basic way to do this in AD-enabled
GALs.. but nothing OSS-based as far as I know of, at least.
On Tuesday, February 18, 2014, David Keenan <dkeenan44(a)gmail.com> wrote:
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
This project brings up the age-old issue of
transparency vs privacy. Too
much 'transparency' can be bad in ways Jenny pointed out, too much privacy
keeps work from being more collaborative which is endemic to the attraction
of hackerspaces and collectives. In general i feel transparency is too
privileged. We forget transparency often involves a loss or giving up of
individual agency and control, not just a gain in centralizeable,
actionable 'data'.
I do think this tradeoff needs to be modulated and controlled at all
times by individuals themselves. In my view there shouldnt be a repo where
you are expected to list what you deem is your personal info, even matching
names to 'nym's if ppl arent down for that. But i think matching nym's to
projects would be useful, if folks are willing to document say what part of
what project they are working on, as in dev environments. And perhaps
people could set their own privacy settings, only share at their discretion
certain info with certain people. I would participate in something like
this if such privacy controls were part of it from the outset. Privacy,
with respect to user-controllable visibility of personal info, needs to be
thought of as a fundamental integral component, not an add-on, for every
software product.
my 2c. carry on
On Tuesday, February 18, 2014, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Oh! I should add that we could do really interesting things with our
user pages, linking to projects through tags and categories, creating
portals. I'd love to spend a Today We Learned working on making our wiki
more awesome, semantic, navigable (Vicky? Pete?).
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 Tue, Feb 18, 2014 at 1:29 PM, Jenny Ryan <tunabananas(a)gmail.com>wrote;wrote:
Hey Troy! Thanks for the poke!
tl;dr: Fill out your wiki userpage with current projects and contact
info! Help with the membership registry (PHP) and/or mycelia (node)!
ABOUT THE DATA
a) I don't want everyone at sudo room to be able to call or text me.
Fairly certain I'm not alone in this. If you ask for my number and I give
it to you, we've just created trust through consent. Would like to promote
a case-by-case approach to providing sensitive information, and not store
it ourselves. This is why, when I asked for up-to-date membership
information, I only asked for an email and a name/nym.
b) I think we should encourage people to fill out their user pages on
the wiki, and include there things like projects, contact info, and public
keys. We sent out a template for user pages long ago, can't remember who
put it together (Marina, I think?). Here are some examples of nice user
pages:
https://sudoroom.org/wiki/User:Juul
https://sudoroom.org/wiki/User:Tunabananas
https://sudoroom.org/wiki/User:Mk30
https://sudoroom.org/wiki/User:Maximilianklein
ABOUT THE MEMBER REGISTRY / SELTZERCRM
I'm running the nascent member registry at http://mycelia.cc/crm, the
code for which is here <https://github.com/elplatt/seltzer> if anyone
wants to look and see if they can build something on top of this. It's PHP.
I did a decent bit of research and this was the most viable FOSS membership
registry system I could find. Soon will port it over to sudoroom.organd push to Github
(hopefully tomorrow). I've been asking for help at the
meetings as it would be great to have more people who want to work on this,
but it needs to happen so I'm not waiting around for a team to form.
ABOUT MYCELIA
The goal of Mycelia <http://mycelia.cc/> is to create a decentralized
database for documenting projects, people (skills) and objects between
hackerspaces and also matchmaking between them. Pub/sub [publish /
subscribe] model encouraging folks to have concrete projects about which
they publish updates, or otherwise be a subscriber consuming the updates of
others :)
Unfortunately, I can't code it myself and Marc's busy with sudomesh and
freestore. What's up on Github is essentially Labitrack (the QR-code
sticker inventory system we're using at sudo) converted into NodeJS and
LevelDB. It's definitely a priority project, but not #1 right now. CC'ing
substack in case he's interested in this project.
Cheers,
Jenny
http://jennyryan.net
http://thepyre.org
http://thevirtualcampfire.org
<http://technomadic.tumblr.com/>
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-discuss
2:11 p.m.
On Tue, Feb 18, 2014 at 1:35 PM, Jenny Ryan <tunabananas(a)gmail.com> wrote:
Oh! I should add that we could do really interesting
things with our user
pages, linking to projects through tags and categories, creating portals.
I'd love to spend a Today We Learned working on making our wiki more
awesome, semantic, navigable (Vicky? Pete?).
Bigtime, yeah. There are lots of cool ways we could use the wiki for
non-private info useful in support of community mutual visibility and
collaboration. (David's concerns are very valid though -- MediaWiki doesn't
support private data in any meaningful way, so doing this would of
necessity mean that we could *not* include certain kinds of data in the
same system.) I see pros and cons to both approaches, but am happy to
explore the MediaWiki side of things, through a "Today We Learned" and/or
other formats.
Pete
[[User:Peteforsyth]]
3959
days inactive
3961
days old
12 comments
8 participants
participants (8)
-
Anthony Di Franco -
Chris Bee -
David Keenan -
eddan.com -
Hol Gaskill -
Jenny Ryan -
Pete Forsyth -
Troy Massey