- From: Daniel Yacob <yacob@geez.org>
- Date: Thu, 02 Mar 2017 17:54:00 +0000
- To: r12a <ishida@w3.org>, public-i18n-ethiopic@w3.org
- Message-ID: <CACvO6KD_quUMm90K5O96arjyP3pvptFku_S-Xog2XopgXFyzZA@mail.gmail.com>
Richard, That is a good idea. I had been thinking along the lines of a paper survey, which the burden of collection and consolidation of the results. I'll add the links, we should be prepared for both online and offline approaches. Going further, a fully online survey would be helpful as well. I think the github issues can include the images and be re-expressed to match the survey question text in the survey document. Giving us an online survey of sorts with tracking to a github issue. Just thinking out loud now... Perhaps a github wiki page helps to order and collect only the issues that are part of the survey which would be a less confusing starting point for participants (who may be experiencing github for the first time). I'll give that a try. The only downside I see is that a participant is exposed to the responses of others and that may influence how he or she responds -this may go against a surveying principle. Nonetheless I still think its good to have. thanks, -Daniel On Thu, Mar 2, 2017 at 5:41 AM r12a <ishida@w3.org> wrote: > On 27/02/2017 19:40, Daniel Yacob wrote: > > With the holidays past, I'm hoping > > to resume the effort to execute a survey of stakeholders. > > hi Daniel, > > it's a bit of work, but one thing you might consider is linking to the > appropriate github issue from each of the questions in the > http://w3c.github.io/elreq/ document, so that someone reading the > document and thinking to make a comment can just click on the link and > get straight to the issue thread. > > that should significantly lower the barriers for people who are reading > the document to create comments. > > just an idea. > > ri > >
Received on Thursday, 2 March 2017 17:54:44 UTC