[axxs-sysadmin] a proposal
dave at netaxxs.com.au
Fri Jun 1 01:32:26 UTC 2007
On Fri, 2007-06-01 at 11:02 +1000, aketus wrote:
> > On Thu, 31 May 2007, andy nicholson wrote:
> >> I think there needs to be a some thought to when to _stop_ taking new
> >> hosting requests.
> >> Obviously this didnt happen on the first server, and consequently became
> >> unusable without rebooting various services daily.
> I don't know about 'stopping' taking new hosting requests. I thought
> the idea was to get appropriate individuals or individuals from orgs
> wanting hosting on axxs to come on board in the collective and help
> maintain the server(s).
Yes, I suppose there are 2 ways to look at it ..
current geeks 'sponsoring' a project that _they will manage_
new groups that have techs and wish to get involved
so really there's 2 elements to hosting requests I suspect.
> Obviously the idea being that the more hosting of sites = the more
> individuals willing to maintain the collective of sites and donate =
> more self-management = potentially more servers collectively
Yes and no, and we need to take things as they come. If we hadn't of
taken sites pro bono at the start, we wouldn't have had a base to call
on for donations to get another server up, but we can't just end up
'another free hosting service', however geeks doing stuff on the server
should have the ability to host sites if they wish to sponsor it.
Example: boud wishes points a mate at axxs.org sysadmin list to put
forward a proposal, which he seconds. It's for a site about cute little
puppies. they have no techs. should boud be able to 'sponsor' the site?
I think so.
> Which of course = more online communities under self-management.
> To me it seems crazy for a collective promoting self-management &
> organisation to effectively say 'let's build online communities... but
> only a few...' surely the aim is the opposite - the more the merrier.
To an extent I think, we don't want geeks managing other geeks projects
and a few doing all the work, hence we do need some sort of
self-management, or sponsorship of a project (ie: you sponsored them
Dave, you fix their issue)
I think we also need to work out a healthy limit on what can be done on
servers, where the limit is. ie: Dave doesn't do an aweful lot, but he's
got ### sites running, and I do a whole heap, and only have 1!
this again I think takes that dreaded word .. MEETINGS. I think we
should start having regular meetings and discussions over this. and a
good overview of whats on servers and who is sponsoring the sites etc
.. at least a start toward not blowing some workers out of the water
compared to others. transparency I think is the key as always, let's
explore how we can do this.
> I think the problem with axxs overload was having just the one server,
> is all. I hope we get more hosting requests, get more people into the
> collective, and have more donations coming from these organisations,
> and end up with one mother of an axxs server farm all sharing the load
I think we need to look at getting the new server organised for
donations to get the next year going soon, with groups that are on it
organising to keep their hosting going with other groups that are on it.
> Ideally the more hosting requests we approve, the collective of geeks
> will grow, and also I'd like to see donations grow. Everytime a server
> reaches its healthy peak of sites hosted on it, it ought to be
> feasible to get a new server and grow exponentially. (i hope this
> works in practice)
We do need to work out limits tho on servers and workloads on
individuals. we can't have a few doing all the work!! there should be
regular discussions regularly as a start about this very aspect, and
highlighting those that are doing the labour and protecting them.
again ..transparency while we work out a methodology that works fairly
> axxs-sysadmin mailing list
> axxs-sysadmin at lists.indymedia.org
20 Chisholm St
+613 5722 9622
More information about the axxs-sysadmin