Hi, Leo :)
A few comments,
Leo Lapworth said:
2010/1/2 James E Keenan <jkeen_via_goo...@yahoo.com>
3) Phalanx
Though in one sense it pains me to say it, Phalanx does not need to
be a major tab. It can be demoted to a link somewhere.
<snip history of the project>
I have put it is as a tab on the right called 'old projects'.
I removed the 'Coordination' section and also dropped the link to 'Tasks to
be done'.
I also added 'finished' to the title.
Would you mind changing this to something less "final"? There are a
few marketing considerations, see:
Old = inactive | established; # Which one?
Major tab = Decision about visibility; # What needs more visibility?
Finished = Nothing more to do; # Sure? Is visibility still useful?
Removing or adding topics/projects from the (any!) frontpage will
quite likely have a major impact on those projects. Before doing so, I
ask you to consider a few things:
1) Do the projects have any worthwhile qualities that makes them good
to keep around (keep visible) even if activity levels are down?
2) To what extent can the webpages be used for recruiting people to
useful projects? Is it better to "repurpose" a page to make people
want to join/help instead of demoting the page to "historical value
only"?
3) What context is the most useful one to promote a project within?
("Finished"? "Current projects"? "Community efforts"?)
I suggest that the qa.perl.org frontpage does NOT link to "old"
(which in a software context usually is interpreted as "defunct",
"bad", "lacking maintainance" or "not updated") projects at all.
Instead, be REALLY careful about calling something "old" and only
reserve words like that for projects that we'd like to kill off.
Pick another phrase instead - preferrably something that communicates
the fact that a project is interesting/worth learning about and
relevant for the reader in some way.
Also, keep in mind that the page needs to stay around for a long time,
and that whenever someone reads it, the pages need to convey the
impression of actuality (updatedness, relevance, that it's "current")
no matter if the page is read next week or next year. Avoid
time-related words like "still", "now", "old", "upcoming" etc..
The point here is to make the pages read as "fresh" even if
qa.perl.org is a volunteer effort where the volunteers by default have
almost no time to help. (Everyone having jobs/life/family/kids/etc.
should have as little negative impact as possible on the "updatedness"
of the page. ;)
Hope this is useful! :)
- Salve
--
#!/usr/bin/perl
sub AUTOLOAD{$AUTOLOAD=~/.*::(\d+)/;seek(DATA,$1,0);print# Salve Joshua Nilsen
getc DATA}$"="'};&{'";@_=unpack("C*",unpack("u*",':4@,$'.# <s...@foo.no>
'2!--"5-(50P%$PL,!0X354UC-PP%/0\`'."\n"));eval "&{'@_'}"; __END__ is near! :)
