You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Celeste L. P. <ce...@op...> - 2009-03-30 21:41:39
|
Dear FLOSS Project, The 2009 Season of Usability Call for Projects is now open and available until April 15: http://85.10.193.9/UCCASS/survey.php?sid=47 OpenUsability Season of Usability is a series of sponsored student projects to encourage students of usability, user-interface design, and interaction design to get involved with Free/Libre/Open-Source Software (FLOSS). During a 3 month collaboration, students work together with an experienced usability mentor and key developers of the project to improve the user experience of a FLOSS application. The next Season of Usability student projects will start in May 2009. FLOSS Projects who would like to benefit from a usability student are encouraged to fill in our Call for Projects: After the Call for Projects is finished (April 15th), the usability mentors will get back to the FLOSS projects and start the selection process. Each mentor will decide for one project - based on the need for usability and the availability of a technical mentor in the project, and if a good task can be defined. Examples of successful Season of Usability tasks can be found on the Season of Usability website. The selected projects are published and students start to apply for them. Together with the technical mentor, a student is selected. In a kickoff meeting, the task scope is further defined and a road map is developed. Then, the actual project work begins (also see the time frame below). How can I register a project? We prepared a short questionnaire to register a project. We ask a few questions * about the project * about the acceptance of usability among project members * about the availability of developer resources * and finally, we’ll ask for possible student project tasks. People who register projects should know a project well enough to name a key developer who is willing to function as a technical mentor in the Season of Usability. What’s the timeframe for Season of Usability 2008? Call for Project Participation March 2009 A call for participation is published via OpenUsability and other FLOSS- related media. Project Selection Beginning of April 2009 Usability mentors get in touch with projects they are interested in - they either bring their own one or pick one from the CfP. Possible topics for student projects are discussed, and the usability mentors finally decide for a project. Student Application Phase April 2009 The student project openings are published and students start to apply for specific projects. Student Selection End of April 2009 Usability mentors get in touch with the students who applied. After several cycles of job interviews, the mentors decide for a student. Project Work End of May - August/September The actual scope of the task is defined and the project work starts. Questions may be directed to stu...@op.... -- Celeste Lyn Paul OpenUsability www.openusability.org |
From: Andrea S. <an...@an...> - 2005-08-15 19:44:48
|
Hi all, just a quick update: 35 people have filled in the expressions questionnaire so far. I assumed it helped a lot that Ellen Reitmayr from Openusability.org blogged [1] about the survey (danke!) -- her blog is syndicated on planetkde.org. She took the opportunity to blog about user-centered design in general, so it's definitely worth a read. Again: if you haven't done so yet, fill in the questionnaire [2] or tell someone else about it ;) cheers, Andrea [1] http://www.kdedevelopers.org/node/1325 [2] http://expressions.sourceforge.net/survey/ |
From: Andrea S. <an...@an...> - 2005-08-11 10:34:03
|
Hi all, I've registered expressions with OpenUsability.org (see also the news item at http://sourceforge.net/forum/forum.php?forum_id=3D487630). OpenUsability "brings Open Source Developers and Usability Experts together" -- guess joining them might give us some more useful input. The expressions project page there is http://openusability.org/projects/expressions/; I'll add this link to the expressions web site some time soon. I've posted a news item about our questionnaire at OpenUsability (http://openusability.org/forum/forum.php?forum_id=3D461). OpenUsability's Ellen Reitmayr has promised me to put that news item on their front page, which hopefully will get us some more participants in the questionnaire. Expressions being at OpenUsability also means that if there are people out there who are interested in Expressions, but aren't programmers, have a place to contribute (while still being welcome on this list, of course). So if you know anyone who might be interested, let them know -- and/or sign up yourself (http://openusability.org/account/register.php). Let me know your username, and I'll add you to the expressions project. One last thing: OpenUsability has a SourceForge-like system for the projects hosted there. This means there is some duplication, as expressions now has news items both on SourceForge (which are copied over to the web site) and on OpenUsability. I guess that's not much of a problem, as the news at OpenUsability will "only" be usability-related. The core news will stay at SourceForge (and on the expressions web site). Another thing are the forums which also are provided both by SourceForge and by OpenUsability. I've set up the public OpenUsability forums ("open discussion" and "help") to post every message to this mailing list, and I'm monitoring the other forums to make sure nothing gets lost. I'll be working on a survey report script today that we can use to view the survey results -- so expect to hear more from me sometime today or tomorrow. In the meanwhile, fill in the questionnaire and/or tell someone you know! cheers, Andrea |
From: Andrea S. <an...@an...> - 2005-08-11 00:46:21
|
Hi all,=20 I just uploaded the questionnaire for the expressions survey; you can access it at http://expressions.sourceforge.net/survey/ As I didn't get any feedback last time I asked, I put it online directly this time (I'm not annoyed -- it's just faster this way). So please go and fill in the questionnaire, and tell heaps of people about it! Participants will get an HTML snippet to post on their blog, which might help draw some attention. On a completely unrelated note, you might have seen from the expressions project news that I created a shop at cafepress.com with a few products with the expressions URL and tagline ("blog while it's happening"). I don't really think there'll be too many people who want expressions merchandise (at least not at this point...), but you never know. And just to make it public: I will present a paper about expressions at the Context in Mobile HCI Workshop at the Mobile HCI 2005 conference (http://mobilehci.icts.sbg.ac.at/context/). I have written that paper together with Andreas. Now expressions has moved from vaporware with a web site to vaporware with a web site, t-shirts, a scientific publication and a survey ;) cheers, Andrea |
From: Andrea S. <an...@an...> - 2005-06-16 22:13:36
|
Hi all, On Thu, 2005-06-16 at 22:07 +0200, Andreas L=F6=F6w wrote:=20 > It's been a long time without any activity at all, but hopefully =20 > things will start to progress slowly from now on. and maybe even a bit faster than "slowly" ;) > 1: Write a questionnaire to find out whether the initial concept =20 > using two clients talking to each other and providing a backlog of =20 > entries is a good idea or not and what we could learn from already =20 > existing blogging software. Andrea and I have started a list of =20 > questions we want in the questionnaire; Andrea, could you please send =20 > them to this list? I've put up a version at http://aschweer.backpackit.com/pub/127663 -- this version is publicly viewable, but not editable. So, here's a copy of the questions list to make it easier for you to comment on questions. I will try to keep the online version in sync with whatever comes over the mailing list. It's still worthwile to check out the online version, because there are a few more things there that I'm not posting here. So here goes; but beware: it is a first version. I would be very surprised if any of the questions in the final questionnaire would actually be worded the way they are here; there are probably some questions missing; there are probably a few questions that should be thrown out. Any ideas? Send them to this list. Goals of the questionnaire ----------------------------------------------------------- * find out how people blog * find out what problems exist with existing blogging tools Questions ----------------------------------------------------------- * which blogging tools do you use? * do you think the tool(s) you use are optimal? (careful with phrasing here!) * how often do you have a cell phone with you? * how often do you use text messages/WAP/GPRS? * which features does the phone have (IR, bluetooth, camera, ...) * do you have a laptop/desktop computer? * do you have other toys (PDA, digital camera, ...) * what do you usually blog about? * what's your blogging behaviour (continuously/spurts/...)? * how do you decide what to blog about? * do you use geo location stuff in your blog? how? * what blog software do you use (Blogger, WordPress, ...) * have you ever used moblogging? opinions? * where do you usually blog from (home/uni/work/...) * if your client supports "disconnected" posting: do you use it? * do you ever look at your own old postings? * do you ever look at other peoples old postings? Now it's your turn ;) cheers, Andrea Oh, and: I will set up a wiki for expressions when I find the time for it. If none of you has any problems with that, that is ;) |
From: <an...@al...> - 2005-06-16 20:08:09
|
Hello everyone, It's been a long time without any activity at all, but hopefully things will start to progress slowly from now on. What I think we should do is to: 1: Write a questionnaire to find out whether the initial concept using two clients talking to each other and providing a backlog of entries is a good idea or not and what we could learn from already existing blogging software. Andrea and I have started a list of questions we want in the questionnaire; Andrea, could you please send them to this list? 2: Use the results from the questionnaire together with persona descriptions (a persona is an imaginary user; Andrea and I have already described four personas -- see attached document) and the diagram to write user stories. A user story is a short story describing how a persona might use the software to perform one or a specific set of tasks. The goal is to find out how the workflow should be, or how it shouldn't be. It will also give us an opportunity to think a bit about the requirements (which data do we need where, which parts of the software have to communicate with each other). 3: Write use cases (that's basically a fancy word for "list of things you can do with the software") and requirement specifications based on the user stories. At the end of this step, we should have a prototype GUI which we can test with users. I will try to describe requirement specifications a bit more later in this email, for those of you who are unfamiliar with requirement specifications. 4: In this step we finalize the GUI, and come up with the architecture of the system (for example, which components does the software have, and how are they connected to each other). We also decide on how to store data, and the communication protocol between the mobile client and the desktop client, and how both of them talk to the blog. 5: Make a class diagram. 6: Implement. This might seem like a lot of paperwork, but it will provide contents for those of us who want to publish papers, while also making sure that everyone involved has a clear view of what is going on. Since we are all spread out a bit, and collaborating over the Internet, it will make cooperation much easier if we all know who's doing what, and how it is being done ;) In our requirement specification the most important things we want to have are prioritizing features and the hardware requirements (do we only supporting blue phones with the latest version of java, or do we try to be a bit more generic, and if so, what does the different platforms have to have?) . However, we also want some more descriptions of the project in order to make the requirement specification easier to read by not referring to emails or other documents. It is also very probable that we will have to update this document a few times until we are actually implementing the software. If you want to know more, look at http://www.techwr-l.com/techwhirl/ magazine/writing/softwarerequirementspecs.html, or this template at http://www2.ics.hawaii.edu/~johnson/413/lectures/5.2.html (ignore section 8, 10, 11). If you have any questions, or if anything feel confusing, please bug me ;) Cheers, Andreas |
From: Andrea S. <an...@an...> - 2005-03-28 17:33:09
|
Hi, I just spotted this on planet.debian.org -- I think he's got a point. I'll post it here for future reference. cheers, Andrea --------------------------------------------------------------------- http://liw.iki.fi/liw/texts/software-webpage.html Checklist for free software web pages Abstract =20 A brief checklist for web pages for free software. =20 February 26, 2005, Lars Wirzenius (li...@ik...). =20 A free software web page (or web site) should make it easy and fast to find the following information: * Name of program. =20 * What the program does. =20 * The license. =20 * Where there are screenshots (for program with a user interface), or a demo of some sort, for programs where this can be arranged. =20 * Where the program can be downloaded, at least in source form (a single compressed tar package is preferable), and maybe also in binary forms. =20 * What the program requires for building and running: hardware, libraries, other programs, etc. =20 * Who the authors are and how to contact them. =20 * A few news items about the program, such as the dates of the latest releases. This should preferably come after an explanation of what the program does to server newcomers better (they're more likely to stay that way). =20 This is related to content, not to its presentation. Presentation should make it easy to find all the above information, but is otherwise a topic too large for this little text. |
From: Andrea S. <an...@an...> - 2005-03-23 12:07:19
|
Hi, On Wed, 2005-03-23 at 22:26 +1200, Andreas L=F6=F6w wrote: > Fraggel, a friend of mine which I am trying to recruit, spotted a=20 > mistake on our webpages. > The picture on http://expressions.sourceforge.net/about.html has the=20 > text "Java Mobile Edition", whereas it should be "Java Micro Edition"=20 > according to http://java.sun.com/j2me/index.jsp. >=20 > Could Andrea please fix this(since you have the good program :) )? done -- the webpage should reflect that after the next time cron updates our web pages. and don't ask me when that is, because I don't want to enter timezone hell ;) cheers, Andrea |
From: <an...@al...> - 2005-03-23 10:28:03
|
Hi, Fraggel, a friend of mine which I am trying to recruit, spotted a mistake on our webpages. The picture on http://expressions.sourceforge.net/about.html has the text "Java Mobile Edition", whereas it should be "Java Micro Edition" according to http://java.sun.com/j2me/index.jsp. Could Andrea please fix this(since you have the good program :) )? Regards Andreas |
From: <an...@al...> - 2005-03-21 01:47:10
|
Hi, I might as well make a public announcement that I will be too busy the next 2-3 weeks to do any work on the project. I am trying to finish my Master's thesis, which definitely have to take precedence over any hobby projects. Regards Andreas |
From: Andrea S. <an...@an...> - 2005-03-19 19:52:14
|
I've started to spread the word by blogging about our project: http://an.andaka.org/blog/index.cgi/basteln/blog/2005-expressions.html (sorry for the German -- I'm basically asking for opinions and telling people to use the expressions sourceforge forum for comments instead of my blog). And now I'm even using the project mailing list ;) Andrea |