The problem with Lord_Pall is briefly noticed in that:
- He doesn't take into consideration any other choices/opinions than the site he built and he is leading unilaterally, since the beginning. He doesn't want to drop Joomla at any stake, and this is starting to look like a race.
- He has been proposed several times to unite, discuss and decide. Even if he said momentarily "yes", nevertheless he continued pushing in his development, calling people on the way.
At this time it's very unfair to say what has been posted at the hotud.org forum, since it's not true:
Nobody closed the door for him, and he's gathering many help from this community.2009/3/30 Acharis <krzyszt...@gmail.com>
Regarding this http://www.hotud.org/index.php?option=com_smf&Itemid=87&topic=6.msg195#msg195
Lord_Pall, when did you get "hostile brush off" from me? I never
contacted you and I never got any email from you...
I can share with you fixed database of games and all the user created
content. Also I'm more than willing to share downloads part. If you
want to cooperate we can do it anytime.
On 26 Mar, 22:45, Siddhartha Kasivajhula
<siddhartha.kasivajh...@gmail.com> wrote:
> Nice, I like the basic look of it a lot! Can we make it a bit more like a
> Wiki? Allow users to modify game info, screenshots, etc? I believe this was
> something Sarinee wanted in the new site, too.
> Also, although the interface is nice, there is still a lot of information,
> and there is probably a better way to place it on the screen/convey it to
> the user. We should probably have a User Interface designer take a look and
> offer suggestions..
>
> In particular, I am in favor of making the sidebar less prominent and thus
> making the display more content-centric ("cleaner"). (see Wikipedia, for
> example).
>
> On Thu, Mar 26, 2009 at 7:36 AM, Lord_Pall <lordp...@gmail.com> wrote:
>
> > Http://www.hotud.org
>
> > Status Update: March 26th, 2009
>
> > Full dataset is up. Forums are up. Comment system is up. Community
> > System is up. Downloads are available, figure 50% so far, some gaps in
> > the archive but that's easy enough to backfill.
>
> > It's ready for community expansion with user reviews, and more
> > listings as well. File backend is automated to the point that the
> > archive can live anywhere, and it'll batch update the necessary ID's
> > based off of user expansion.
>
> > I'm probably going to add some "editor" level functionality so
> > community members who want to expand the collection can quickly see
> > where the gaps are.
>
> > I'll work with Dan P. at Portsmouth to make sure we split the backups
> > between my end, local machines, Amazon S3 and a few other secure
> > repositories. I figure I'll setup a weekly or monthly dump of the site
> > to guarantee we don't lose anything.
>
>
You're totally right. I've been trying myself to keep people together
since the beginning but it has been mostly impossible to try to
coordinate any effort.
I'll express sincerely my personal opinion about the Revival project
looking not to heat the mailing list, since I'm starting to feel
really tired about this project.
First of all, -as I insisted since the beginning- there's need for
some structure in the group. To work individually in bursts harms the
community and divides effort and people. Teams had to be naturally
established with some key people around...people should technically
cool down and build the community first. At this time we have several
websites, but we don't have a real, solid, cooperative working
community.
Second, a community is built up in some key contributors, natural
leaders or whatever. I felt that Dan, Andrew and Sarinee are the ones
to take the lead because they've already shown common sense,
experience and some kind of belongingness. They are the ones that can
step actively forward to organise and be heard by the rest of the
people more than anybody else. There are some others like Walter,
Simon...but they need to change they way of working. Instead of only
thinking in short term, you should think also in middle-long terms. I
bet that many helpful people have left the bus since we started.
Third, Unite, Discuss, Decide. Easy...but why nobody listens to this?
Some people offered they help (including me) and the only answer they
got is that somebody else was already doing what they thought that was
assigned to them. Even no mail was sent to tell "Hey man, don't do it.
Thanks, we have somebody else on it" Who cares about helping people?
Somebody seriously should.
Finally, everything has been mostly done individually (with some
exceptions) and many efforts are producing parallel websites.
we can do major proper testing on the KEEP emulation project... which I'm committed to as I think emulation is really the only future-proof means of properly preserving this stuff.
But what I will say is this: projects need project managers. Not community builds. That only works in long-term, relatively unstructured or additive projects. My suggestion would be a steering committee: elect six people onto this that best represent the diverse interests of the community. People put their names forwards, it goes to the group, vote them in. They then draw up the plan: everyone gets on board with the plan, puts up, shuts up, or leaves. End of discussion. A job list is drawn against the plan: this is released, volunteers come on board against specific jobs. And, critically, one person is elected to manage the whole thing, take responsibility for delivering the plan to the community: so it's a community agreed plan, drawn up by an elected committee, delivered by volunteers managed by a single person who is responsible back to the committee, who are responsible back to the community. But the key thing is that you have a named individual leading the project, who has a plan to work to that has been agreed in advance. Working like this reduces the room for power battles and disputes to expand into and it's not too late to put it all in place.
My take on things is this: I see us as a very safe backup host for the files. As far as the live site goes, I'm not sure what we can do, it'll certainly take longer, and there's no reason why we can't spread the files around as is currently being done. What I can do is take a full dump of the entire contents and put them in safe storage, and commit to updating this every couple of months, so the core files are protected and preserved, even if we're not actually *serving* downloads. How does this sound to everyone?
But what I will say is this: projects need project managers. Not community builds.
That only works in long-term, relatively unstructured or additive projects.
My suggestion would be a steering committee: elect six people onto this that best represent the diverse interests of the community. People put their names forwards, it goes to the group, vote them in. They then draw up the plan: everyone gets on board with the plan, puts up, shuts up, or leaves. End of discussion.
In terms of the ongoing stuff, my 5cents: two sites in parallel development will kill this project. Lord_Pall has worked bloody hard, regardless of what you think of his approach or results, and it's just daft to let a schism develop. Nacho is absolutely right, it's just a waste of time an effort developing parallel solutions to a problem we ALL want to solve.
Thoughts?
It's great having 150+ people interested in the project but eventually
things actually need to get done. If you have people in different
timezones, with different skillsets, and different amounts of time/
energy to contribute, I think the current approach of random
implementations is quite a pragmatic start. Once we find a basic
site that the community wants to buy in to, then they can buy in in
non-developmental ways.
What about the recent posts about sharing resources gathered
this far (SQL dumps, files, etc.)? I think this is cooperation in
the truest sense, and confirms that implementors are keen on seeing
the site rebuilt regardless of whose efforts eventually receive
community approval.
Third, Unite, Discuss, Decide. Easy...but why nobody listens to this?
Well, instead of talking in generalisations, how about you provide
some practical suggestions as to how non-developers can provide
support at this early stage?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Home of the Underdogs Revival Project" group.
To post to this group, send email to hotu-r...@googlegroups.com
To unsubscribe from this group, send email to hotu-revival...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hotu-revival?hl=en
-~----------~----~----~----~------~----~------~--~---
Walter, you have a point, but I disagree that polarizing our efforts at this early stage is not necessary. You're right -- we might eventually find one website that starts to gain momentum and people might want to get on board with this site. But this website could already be on a non-optimal path. Everyone will contribute to it and it will get somewhere, but will it ever get to where a structured, planned, effort starting NOW could go? And along the way, we would have lost many that were passionate and capable and could have contributed, but who no longer have time to waste on something that is not "theirs". If you spent months on a website and it didn't make it, would you be as diligent at helping out with the successful effort? We could lose good people. It's a risk that I don't know if you've considered.It's great having 150+ people interested in the project but eventually
things actually need to get done. If you have people in different
timezones, with different skillsets, and different amounts of time/
energy to contribute, I think the current approach of random
implementations is quite a pragmatic start. Once we find a basic
site that the community wants to buy in to, then they can buy in in
non-developmental ways.
Third, Unite, Discuss, Decide. Easy...but why nobody listens to this?Good call. We should get specific on things like this if we are to make progress. Perhaps one way is in defining a specification from a user point of view. The interface, the look and feel, what features are desired -- these aren't necessarily developer roles, and only demand a critical eye for detail and convenience. If we form a structured community similar to what Dan is proposing, we would have an infrastructure that would allow such suggestions to be made, heard and be useful. What do you think?Well, instead of talking in generalisations, how about you provide
some practical suggestions as to how non-developers can provide
support at this early stage?
Regarding your suggestions 1-7, I feel that it is very difficult for a newbie to take initiative on his own to discover what needs to be done.
Maybe you would be interested in creating some sort of Wiki that would help people get up to speed, then they would be able to implement your suggestions more effectively.
As I recall the database dump was released as creative commons, so I think that the
'put up, shut up, or leave' idea is totally against the spirit of that decision.
And along the way, we would have lost many that were passionate and capable and could have contributed, but who no longer have time to waste on something that is not "theirs"
The position of taking a "Anyone can build a site so let them" as I've
seen from my reading of things now I'm back from GDC is there is a
distinct lack of cooperation. If one site was worked on, people could
contribute information to one source, with one name.
Anything that goes against that, frankly, does look a bit bad for the
person saying it - like "This is my site now, you can't take it away
from me", and kind of power-mad - if you won't work on one site, why
would you ever make anyone else an admin? (for instance).
As for people contributing material to the group, fair enough, but this
is why one site would be better - it could be put on that site, not just
in the group (where large files can't go anyway).
This is no bickering. If you think it is, please re-read what Dan
posted. We do need some project management, especially if the files are
going to be hosted by Dan, where he wants only a limited amount of
people to have access so the repository is actually a proper archive of
files and not just a FTP share.
Andrew
Maybe you would be interested in creating some sort of Wiki that would help people get up to speed, then they would be able to implement your suggestions more effectively.
Sure, I'll do it tonight.
Just to be straight: the data wasn't ever licence under creative
commons.
You realise factual data cannot be copyrighted?
The position of taking a "Anyone can build a site so let them" as I've
seen from my reading of things now I'm back from GDC is there is a
distinct lack of cooperation.
If one site was worked on, people could
contribute information to one source, with one name.
My take on things is this: I see us as a very safe backup host for the files. As far as the live site goes, I'm not sure what we can do, it'll certainly take longer, and there's no reason why we can't spread the files around as is currently being done. What I can do is take a full dump of the entire contents and put them in safe storage, and commit to updating this every couple of months, so the core files are protected and preserved, even if we're not actually *serving* downloads. How does this sound to everyone?
There is a degree of self-interest at work here of course - it means we get access to the files ourselves, which means we can do major proper testing on the KEEP emulation project... which I'm committed to as I think emulation is really the only future-proof means of properly preserving this stuff. But it also means we've got a budget and a vested interest in keeping stuff safe.
But what I will say is this: projects need project managers. Not community builds. That only works in long-term, relatively unstructured or additive projects. My suggestion would be a steering committee: elect six people onto this that best represent the diverse interests of the community. People put their names forwards, it goes to the group, vote them in. They then draw up the plan: everyone gets on board with the plan, puts up, shuts up, or leaves. End of discussion. A job list is drawn against the plan: this is released, volunteers come on board against specific jobs. And, critically, one person is elected to manage the whole thing, take responsibility for delivering the plan to the community: so it's a community agreed plan, drawn up by an elected committee, delivered by volunteers managed by a single person who is responsible back to the committee, who are responsible back to the community. But the key thing is that you have a named individual leading the project, who has a plan to work to that has been agreed in advance. Working like this reduces the room for power battles and disputes to expand into and it's not too late to put it all in place.
Thanks!
dan
Maybe the level of coordination you are thinking of is not yet
appropriate?
It's great having 150+ people interested in the project but eventually
things actually need to get done. If you have people in different
timezones, with different skillsets, and different amounts of time/
energy to contribute, I think the current approach of random
implementations is quite a pragmatic start. Once we find a basic
site that the community wants to buy in to, then they can buy in in
non-developmental ways. Anything more structured at this
early stage assumes a non community-driven (ie: centralised)
approach, which hasn't happened thus far, may not be a good
idea, and quite frankly it may be too late to create.
That's a pity, since I think it's fair to say that everyone's
contributions are valued.
What about the recent posts about sharing resources gathered
this far (SQL dumps, files, etc.)? I think this is cooperation in
the truest sense, and confirms that implementors are keen on seeing
the site rebuilt regardless of whose efforts eventually receive
community approval.
I personally find it a bit offensive for you to label people who are
jumping right in to the project as somehow working in the wrong
way and/or with 'short term' views. That's all I'll say on this point,
though I'd also like to point out that it's clear that nobody actively
discussing things on this list is thinking in the short term, at
least technically.
If you have some actual points to make regarding middle and
long term concerns that people on-list may be missing, a
reasonable and certainly more useful approach may be to raise
those issues on the list and explain your concerns, rather than
simply pointing the finger without contributing anything positive
that we can move forward on.
Third, Unite, Discuss, Decide. Easy...but why nobody listens to this?
Well, instead of talking in generalisations, how about you provide
some practical suggestions as to how non-developers can provide
support at this early stage?
I for one have tried to solicit new ideas from the group to stimulate
interest and involvement from non developers, but have
frankly received almost no response.
I do so again below, hopefully we can get some more discussion
going this time around.Some people offered they help (including me) and the only answer they
got is that somebody else was already doing what they thought that was
assigned to them. Even no mail was sent to tell "Hey man, don't do it.
Thanks, we have somebody else on it" Who cares about helping people?
Somebody seriously should.
I'm unaware of this sort of thing going on, perhaps this was
some time ago or off the list in some other forum? If you'd like
to help here's a few suggestions:
1. Find out which resources are missing and help to gather them.
As I've mentioned, I'll be posting a list of missing box and/or
screenshot images, later we should have additional
'scavenger hunt' lists (rarer games, missing utilities, etc.).
2. Write some new content that is not present on the mirrored site
(for example newer game reviews, tech notes about how to
get games working in modern DOSBox, new walkthroughs,
strategy guides, etc)
3. Take a lot of newer, higher resolution screenshots for the
existing games, label them, and contribute them when
that becomes possible.
4. Think, dream and contribute some new ideas
5. Find new old games that aren't yet covered by database
6. Learn to program so you can get involved in code development
7. Compile quotes for a new quotes database
Finally, everything has been mostly done individually (with some
exceptions) and many efforts are producing parallel websites.
This is not a bad thing.
Look at free software - competition is good. Remember developers
are working for the love of it, not for any other reason. To illustrate
the point (in the spirit of the old site and it's fantastic quotes
database)...
You're right that things need to get done, but they could be done in a more pragmatic approach: many people spent time and effort could be discarded if we continue going into a random implementation manner, because only one site should stay as the only Hotu revival project.
A nice approach to work randomly but towards a mainstream solution could be start using a common versioning system for all the code, like SVN, CVS...etc. Mercurial is a nice choice indeed for spreading a common code repository for all the developers.
What about the recent posts about sharing resources gathered
this far (SQL dumps, files, etc.)? I think this is cooperation in
the truest sense, and confirms that implementors are keen on seeing
the site rebuilt regardless of whose efforts eventually receive
community approval.
Yes, this is a cooperative approach. If you see I tried not to express myself in absolute terms: the problem comes when you have four sites at hand being implemented instead of only one.
It has been there, Walter: regarding a perl script for a full dump on the Hotu SQL Database Schema.
Finally, everything has been mostly done individually (with some
exceptions) and many efforts are producing parallel websites.
Not bad, but it tends to confuse the regular visitors and to create political issues among the developers (site A is better than B, no, B is better than A...no, C is better....!....). It can be very unmotivating to see that all your time and effort could be dropped later on.
Yes, competition is good...but in the Unix-Programming hacker culture one of their goals is "Don't reinvent the wheel". :-)
We are creating competition inside our own project (!).
They also can't all use Portsmouth University for file hosting. Even if you disagree with working together, that is a sticking point you didn't address.
I myself am here for the archiving side. I have suggestions for providing downloadable database access, backup ideas, and necessary version control whether a site is editor controlled or community controlled.
Whether or not things will go anywhere nearer the community managed and
worked on aspect, with reliability being a key point, we'll see.
Andrew
I hope that everything went smoothly. I agree with many things you say,
but I disagree in some others, let me reply to polarize some comments to
complete the view. The way to agreement goes always through the contrast
of ideas and views.
>> Suggesting everyone helps with one site, well, might work, if that site
>> had been agreed upon by a majority (you seem to be suggesting yours?),
>> but more to the point, that a site had the right goals, functionality,
>> accessibility, and so on. Some people want what would be a new site -
>> more in depth, and covering more items, some want a new identity, some
>> want certain web technologies, others want other things...
>>
>
> I think this is where we hit our big clash at the beginning of all of
> this. The arguments or debates ended up coming down to "Scrap what you
> have, we'll do it as a group". It's nice in theory, but it basically
> involves stopping development and stepping back, which frankly, isn't
> as easy as you'd expect.
>
>
Yes, people was saying to stop for a while until there was a common
agreement at an early stage of your development, so there was not the
possibility to scrap the hotud.org initiative at the beggining. On
today's perspective it means effectively to scrap it partially or not or
to let it go on...and it's understandable your position.
>> personally should have basically sorted this more from the start,
>> outlined a plan which I should have started discussing with Dan and
>> Sarinee when the group was created, and the material from the site
>> should have been kept until something had been decided then released
>> with creative commons licensing (although at least it was released).
>> However, since I can't go back and do this, we should try and
>> consolidate now.
>>
> See, I'm not sure that any of this is a negative. Let's be honest..
>
> If we end up with 10 viable variants on Home of the Underdogs, each
> with a vibrant community and expanding dataset, along with a
> university grade archive of the source material, backed up and logged
> in a secure fashion, are we worse off?
>
Not necessarily worse, but the normal people accessing them could be
really confused. At some point competivity should pop up between sites.
It's the same story as with the Unix wars: at the beginning every Unix
development was friendly, but it ended in a total war for rights and
power that harmed deeply the Unix initiative.
> We're not talking about branding or trademarks or anything of that
> nature. We're talking about a game archive and community of people who
> love them..
>
> It really is the more the merrier.
>
> The sad part for me is to pop back into the google groups after moving
> and see this "us or them" mentality, the perception that this is a
> competition or some sort of winner takes all approach to community
> management.
>
That has never been the mentality. Not "us or them", but together:
"unite, discuss and decide". The competition started with the hotud.org
itself, looking like a race to show up as the leading website regardless
of the debate that was going on there.
> Let's lay this out on the table.
>
Yes, we shall work together indeed and discuss the best way to carry
hotu alive and lasting for many years.
> I'm not going to drown the home-of-the-underdogs.com/Hotud.org site
> because people don't like Joomla. I'm not going to toss the work that
> has been done, and the fledgling community that exists there. Sorry.
>
> I'll admit, it's probably ego. I'm proud of the fact that I was able
> to take the immense amount of work done by the Underdogs admins and
> Sarinee and get it back up and running in a timely fashion. I don't
> believe I did anything wrong, or violated any sort of social contract
> with the community by doing so.
>
>
Yes, you made a very strong effort and you spent many way more hours
than many of us on it or om something similar. Nobody will ask you to
drop it, but we want to move to something bigger than the old hotu site.
Hotud can go on freely as many other sites fitting the vision of some
people. Some other people will focus their effort in this other way indeed.
> Like I said, this might be ego, but this is how I view it.
>
> I think everyone has done stellar work on their individual sites and
> the community as a whole. I don't think it's reasonable to expect
> people to scrap their work at any level.
>
> So what do we do?
>
> I'll pop up another thread to talk about the next steps, so at least
> there's a bit of transparency...
>
>
Ok! It's a nice start, by my side I'll follow that thread too.
Regards,
Nacho