[sudo-discuss] SUDOregistry?

[Anthony Di Franco]

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 at 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 at 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 at 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 at 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 at lists.sudoroom.org
> >
> >http://lists.sudoroom.org/listinfo/sudo-discuss
> >
> >
> >
> _______________________________________________
> >
> sudo-discuss mailing list
> >
> sudo-discuss at lists.sudoroom.org
> >
> http://lists.sudoroom.org/listinfo/sudo-discuss
> >
>
> _______________________________________________
> sudo-discuss mailing list
> sudo-discuss at lists.sudoroom.org
> http://lists.sudoroom.org/listinfo/sudo-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sudoroom.org/pipermail/sudo-discuss/attachments/20140218/8e444042/attachment.html>