Hi guys,
As everyone should know by now, Paul Cutler has stepped down from
organizing the many non-development facets for Foresight. We can only
thank him for doing this work for so long and in such an exemplary
manner, and try to fill in the (big) void he's leaving behind.
This last Friday I was given the chance to help out with the release
of Foresight 2.1.1. With the help of Ken I stepped up to the plate and
managed to get it done for the first time! In the process I got to
play with mercurial, edit some files and send out emails in name of
the community. The type and quality of feedback that poured after all
this was done was amazing and I'm still sort of enjoying the buzz of
seeing people excited about Foresight Linux!
Last night ermo and TForsman pointed out a few typos and minor issues
with the web page and we immediately launched into a mini sprint mode,
knocking out all the blatant errors and overall improving and
polishing the web page. THAT felt awesome! and we want MORE! We want
to take on the User Guide too!!!
To get the ball rolling, here is what ermo had to say on #foresight-qa today:
09:43:10 < ermo> Ok. 1) We're using server side includes, meaning that
the layout of the pages is backwards
09:43:57 < ermo> By backwards, I mean that, instead of a having a
standard header/footer inserted and doing simple mixed
content (like you would in simple php), we insert
content and copy/paste headers
09:44:23 < OgMaciel> gotcha
09:45:11 < ermo> 2) pscott is - sensible fellow that he is - suggested
'tagging' release_version numbers with a <span
class="release_version">X.Y.Z</span> so that it can
simply be grep'ed for through the html
09:45:15 < ermo> in an editor
09:45:42 < ermo> So if we create a lightweight release process with
one editor and 2 reviewers who sign it off, we should
in theory be good to go.
09:45:54 < ermo> And already be in much better shape than now
09:46:16 < OgMaciel> amen!
09:46:18 < ermo> We should probably also take a look at what we can do
with mailing-lists/groups
09:46:42 < OgMaciel> what do u have in mind?
09:46:42 < ermo> The foresight user mailing list is averaging less
than 5 posts per month
09:48:25 < ermo> I'm trying to phrase a question here
09:48:40 < ermo> So that we can answer it as opposed to me bickering
09:49:16 < ermo> Q: What is the primary support forum for foresight?
google-group? mailing-list? forum?
09:49:53 < ermo> for users, I mean
09:50:26 < ermo> Q: What is the primary communication means between
developers for larger changes? the -devel mailing
list?
09:50:57 < ermo> These are all questions that pop up when you click
through the website that we have
09:51:24 < ermo> For users, I'd prefer pointing them to the forum
09:51:59 < ermo> For short HOWTOs, I'd prefer a dedicated wiki space
09:53:16 < ermo> Now, we have a forum and we have a wiki, so no new
infrastructure is required. What IS required,
however, is policy and that we spring clean the wiki
in particular.
09:54:00 < ermo> In terms of teams, I think we should simply start
with a generic QA-team
09:54:41 < ermo> Which handles both packaging and documentation
I'd like to invite everyone to also get up and stand up (like the Bob
Marley song) for Foresight and let us all come up with ideas and
suggestions to make our community and distro rock solid! I will be
setting up a wiki shortly where you'll be able to pitch in your
suggestions easily, but in the meantime, feel free to comment here.
Thank you all!
--
Og B. Maciel
[email protected]
[email protected]
[email protected]
GPG Keys: D5CFC202
http://www.ogmaciel.com (en_US)
http://blog.ogmaciel.com (pt_BR)
_______________________________________________
Foresight-devel mailing list
[email protected]
http://lists.rpath.org/mailman/listinfo/foresight-devel
