Sam Geeraerts <[email protected]> writes: > So: > - Builder Team > - Website Team > - Artwork Team > - Documentation Team > - Freedom Verification Team > - Tranlation Teams > - Community Management Team > > For the description of the Freedom Verification Team: > Check if code is free of binary blobs and distributed under a free license. >
I like the way the page is coming along. I would suggest saying something at the top about what gNewSense is *most* looking for help with at this moment in time. People may have the skills to help with any of these tasks, and so they will wonder which one would be most important to help with. I also think that something should be said about the fact that gNewSense does not have the support of corporations behind it like many other distributions do, and so it depends on volunteer help to make things happen. I think that will help motivate people to want to contribute. >> I am still waiting for someone at the FSF/gNewSense to open an email >> alias for the Volunteer Coordinator. >> >> gvc at nongnu.org? >> >> gvc at gnu.org already exists >> gvc at gnewsense.org I don't know if it's possible to have. >> > > I'd rather make it a full word instead of an acronym, e.g. > [email protected] or [email protected]. Although, if we can't > have a @gnewsense.org one, an acronym might be more practicle. > [email protected] seems like a good idea. I agree about the acronym, now that you mention it. -- John Sullivan Manager of Operations GPG Key: AE8600B6 _______________________________________________ gNewSense-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
