Posted Feb 10, 2012 21:40 UTC (Fri) by Kit (guest, #55925)
[Link]
The Wayland Dev's message was directed at the wayland-devel mailing list, anyone on there certainly is well aware of what Wayland is. It would be quite unfair to say that a simple release announcement, on a development mailing list, must include a description of what exactly the project is. It wouldn't really accomplish anything at all. Especially a project like Wayland, which is still quite a ways away from being all that relevant to people that aren't working on the Linux graphics stack (most of which are likely well aware of Wayland by this point).
LWN did, in their blurb, refer to Wayland as a 'display system', which should lead most people in the general direction of what Wayland is.
Wayland and Weston 0.85.0 released
Posted Feb 10, 2012 23:20 UTC (Fri) by lambda (subscriber, #40735)
[Link]
When announcing a new release of a piece of software, even if it's to a mailing list, it is useful to include at least a standard blurb about what it is, and and brief overview of what is new in this version (I would except software that pretty much everyone is expected to recognize, like the Linux kernel).
People quote release announcements, forward them to other lists, treat them as press releases, use them for summaries on aggregator sites, and the like. Having the essentials covered in your release announcement means that anyone who sees that message out of context will still get the information that they need, they won't have to go hunting in several other locations to figure out what you are talking about.
Wayland and Weston 0.85.0 released
Posted Feb 12, 2012 0:16 UTC (Sun) by k8to (subscriber, #15413)
[Link]
Perhaps it is best viewed as a low-investiment high-payoff form of self promotion. An early development project of course does not need users, but it might garner mindshare and possibly developers?