|
Grex > Coop13 > #365: The Staff and Board Alert Item | |
|
| Author |
Message |
| 18 new of 92 responses total. |
naftee
|
|
response 75 of 92:
| 
Oct 14 00:08 UTC 2006 |
re 65
And now Fronttalk is basically in the same situation as Picospan, except with
more bugs. The real question is whether janc would've put more work into it
if he noticed that it was GreX's primary BBS software, or if we would've wound
up using an almost unsupported program with more bugs and fewer options.
|
cross
|
|
response 76 of 92:
|
Oct 14 02:23 UTC 2006 |
The thing about fronttalk that is qualitatively different than Picospan,
however, is that we (a) have the source code to fronttalk, and (b) have a
license that allows us to modify it.
|
cyklone
|
|
response 77 of 92:
|
Oct 14 02:26 UTC 2006 |
Re #74: And where did I ever say you thought it wasn't doable? Your exact
words were "pain in the neck." And your "sideline" comment was a small
aside in the discussion, so let's not try to rewrite history.
The fact is there ARE volunteers who are not on the sidelines, and the
board has no policy to maximize their value to grex. Try focusing on what
you can do as a board member, rather then responding with
characterizations of those who are not on the board or staff as doing
less.
|
cross
|
|
response 78 of 92:
|
Oct 14 02:29 UTC 2006 |
Regarding #74; But even the problem who volunteer the work don't get the
opportunity!
|
slynne
|
|
response 79 of 92:
|
Oct 14 02:48 UTC 2006 |
resp:77 Indeed. It is much easier to sit on the sidelines with
"brilliant" ideas complaining that others arent doing the work to
implement them. And that work *is* a pain in the neck sometimes. That
doesnt mean it isnt doable. It does make the work somewhat less likely
to get done.
resp:78 I think that comes down to something the board certainly should
talk about. In the past, staff decisions (as far as I know) were reached
by some consensus. That worked well when the staff communicated with
each other better. But now, as far as I can tell, that doesnt seem to be
happening. So I think we probably should discuss how decisions about
technical issues are made.
|
cyklone
|
|
response 80 of 92:
|
Oct 14 03:12 UTC 2006 |
Re #79: Thanks for recognizing the brilliance of my ideas, though your
tone could use some work. And this "sitting on the sidelines" obsession of
yours is doing nothing to address the redundancy problems. You already
have (or recently had) volunteers who could, at least with some training,
have filled those roles.
And then there's folks like me, who have no useful skills that would
benefit grex. Giving me root would ensure its quick destruction. And yet
you keep coming back with the "sidelines" zingers while ignoring the very
assets you should be utilizing. That's quite a neat illustration of how
dysfunctional grex has become.
|
slynne
|
|
response 81 of 92:
|
Oct 14 03:22 UTC 2006 |
Really? Are you volunteering? Because if you are, that changes things.
What would you like to do? Perhaps you would be willing to coordinate a
project like organizing our documentation or setting up a mentoring
program?
|
naftee
|
|
response 82 of 92:
|
Oct 14 04:31 UTC 2006 |
Who would volunteer for GreX right now, in light of recent events?
|
cross
|
|
response 83 of 92:
|
Oct 14 04:35 UTC 2006 |
I would volunteer to work on some pet projects.
|
cyklone
|
|
response 84 of 92:
|
Oct 14 14:27 UTC 2006 |
Re #81: Once again you (deliberately?) ignore my point. Cross would be a
volunteer AND has the skills I lack. Lacking those skills, the best I can
come up with is: Have staff describe the specific aspects of their grex
work and then prioritize them in order of importance. Next, find a
volunteer who is willing to learn at least the high-priority items. Set up
a meeting for the volunteer to meet the staff and set up a training
timetable. The board should then monitor the process. And rather than
commend me on the brilliance of this idea, perhaps you could simply raise
it at the next board meeting. Finally, since it appears the board has not,
to date, come up with a plan similar to mine, from now on you can no
longer complain I have done nothing for grex.
|
slynne
|
|
response 85 of 92:
|
Oct 14 15:01 UTC 2006 |
resp:83 Cross, that is great! What do you want to do and what do you
need to do it? I cant promise anything to you other than to bring it up
with the board but you'll need board approval if you need root anyways.
resp:84 Ok then. It would be a big help to have the staff describe the
specific aspects of their grex work and determine which work is high
priority. It would be an even bigger help to find a volunteer who is
willing to learn at least the high-priority items. Setting up the
meeting and the training timetable is a nice touch too. If you are
willing to do that stuff, I would LOVE it. It would be good for Grex and
I am most willing to ask the board to authorize you to do it.
|
gelinas
|
|
response 86 of 92:
|
Oct 15 00:29 UTC 2006 |
(He wants to change the password-hashing algorithm, at least as a start,
Lynne. ;)
|
cross
|
|
response 87 of 92:
|
Oct 15 00:41 UTC 2006 |
Joe's right, I do want to change that. I'm pretty disappointed that
discussion about it has stopped in garage (and I would assume the staff
conference and mailing list, too). But I also want to update grexsrc and
work on getting a local grexdoc that's mirrorable to remote systems via some
standard protocol (cvsup, cvsync, etc). Ultimately, a merge of grexdoc and
grexsoft would be nice. Getting an updated newuser running would be nice; I
found - and fixed - lots of bugs in my private version derived from the
sources running on grex. Removing unused code and support for absolutely
ancient operating systems (4.2BSD [ca. 1983], Ultrix, AIX version 3,
NeXTstep) and just focusing on POSIX+a simple system dependent library as a
target environment reduced line counts by a third; I figure I can strip out
another 1,000 or so lines by simplifying and correcting some of the logic.
There's at least one faily major security hole lurking in newuser which,
only due to a misconfiguration, isn't exploitable on grex at the moment. I
think working towards a viable replacement for Picospan is a worthy goal.
Like Cyklone, I think process is important and it would be well to impose
some on grex.
Yes, root access would be required for a lot of this.
|
tod
|
|
response 88 of 92:
|
Oct 15 00:49 UTC 2006 |
3DES..then the hard stuff
|
slynne
|
|
response 89 of 92:
|
Oct 15 02:25 UTC 2006 |
resp:87 Ok, I'll admit that I dont understand most of that. But, I will
print it out and will bring it up at the next board meeting where I am
sure at least some of my fellow board members will know what it means. I
will let you know the outcome of that discussion shortly after the
meeting which is in just under two weeks.
|
cyklone
|
|
response 90 of 92:
|
Oct 15 03:53 UTC 2006 |
"I'll admit that I dont understand most of that." Now you now how I feel ;)
I'm glad you're bringing it up for discussion. IMNSHO, that's exactly the kind
of thing the board should be looking at. Thanks.
|
naftee
|
|
response 91 of 92:
|
Oct 15 18:06 UTC 2006 |
re 88
not alcohol, silly !
|
cross
|
|
response 92 of 92:
|
Oct 16 02:34 UTC 2006 |
Regarding #89; Okay, Thanks.
|