On Fri, Oct 27, 2017 at 07:58:38PM +0900, Carsten Haitzler wrote: > On Fri, 27 Oct 2017 09:24:42 +0000 Andrew Williams <[email protected]> > said: > > > Hi, > > > > Cheers for that but from a documentation point of view we're looking more > > to explore how and why which types of developers might be wanting to > > engage. Rather than an example app list we are trying to gather something > > more like personas or motivations, perhaps along the lines of: > > > > *) Experienced C developer looking to make use of the advanced graphics > > functions available through EFL > > *) First time software engineer starting with C and EFL looks like a great > > way to get something pretty running > > *) Enterprise organisation management says that EFL has been specified and > > I need to know exactly how to get audio and AI related APIs working for my > > embedded system > > I frankly don't have a target audience... well more specifically the C api is > going to have a specific target. other bindings might have other targets... > are > we just talking c api? > > > For example. > > Do we have a concept of our target audience in these terms?
When Cedric was formulating the documentation project, he was kind enough to entertain some questions from me about this. What I gleaned from that discussion and filled in with a lot of my own (possibly incorrect) guesswork is that Samsung HQ is interested in stimulating more application development work by 3rd parties, in particular using the C# bindings, because they're keen on seeing uptake by Windows-oriented developers that are creating or porting software apps to run on Samsung Tizen-based consumer products (Smart TVs, refrigerators, etc.) Given that, if I'm not too far off base, two ideas for target audience might be something like: *) Contract programmer tasked with quickly porting a small/medium sized Windows application to run on a Samsung consumer device, that needs to be adapted to look and feel native in an EFL-based platform. They are skilled in programming and reading English, although their level in one or the other may not be high. They are highly task-focused and want to quickly and easily find solutions to specific bugs or other problems, and appreciate explanations that are definitive and examples that are easily adapted to their case in hand. Their goal is to complete as many problems as possible in a given amount of time. *) Member of a small but experienced programming team aiming to create a new EFL-based applet to run on Tizen. They are conversant in English and expect concise, accurate, professional sounding docs that help them master advanced features needed for their software project. They want to understand the bigger picture and what choices will give them the best results. Their goal is to produce software that is successful in the marketplace, so they can continue building their EFL experience on future projects. Again, Cedric or others can correct me if I'm off base, but the above is what I've been assuming for this documentation effort. More broadly, EFL as a whole targets a wider array of audiences, and upstream EFL developers are probably thinking of a number of different audiences in their work. Some docs are written in a terse style that seem to assume the other person is a fellow EFL core developer. Other docs are written in a more verbosely friendly style that seem to read as if they're explaining things to an EFL enthusist who is relatively new to the project and working their way up the learning curve towards becoming an active community contributor. Of course, ideally the documentation would strike a good balance that addresses the needs of each of these audiences equally. Bryce > > Thanks, > > Andy > > > > On Thu, 19 Oct 2017 at 02:27 Carsten Haitzler <[email protected]> wrote: > > > > > On Wed, 18 Oct 2017 14:36:07 +0000 Andrew Williams <[email protected]> > > > said: > > > > > > > Hi all, > > > > > > > > One of the items summarised from our Malta chats earlier this year was: > > > > "As a community we want to enable great apps to work consistently on a > > > wide > > > > variety of platforms (device and modality) but we currently don't have a > > > > roadmap of how to get there. Additional support would be needed esp. in > > > the > > > > higher level APIs to do this" > > > > > > > > Now we're looking at getting documentation in place to help with this > > > > mission it's become clear that we are not completely aligned on the > > > > types > > > > of thing we should be focusing on guiding developers through. > > > > Would it be possible to work through a couple of user stories or > > > > journeys > > > > that we can organise in priority order so we know we're hitting the top > > > > score items first? > > > > > > > > Any suggestions on what is most important to us or to the developers we > > > > wish to entice? :) > > > > > > ummm well hello world, then a set of simple apps (ok/cancel dialogs, list > > > of > > > items to select something from, getting more and more involved). maybe > > > pick > > > things that have some "boom" like "make your own video player", "make your > > > own > > > music player", note taking app, todo list app. really just simple ones > > > not > > > very involved.... maybe? just thoughts. > > > > > > -- > > > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > > > Carsten Haitzler - [email protected] > > > > > > -- > > http://andywilliams.me > > http://ajwillia.ms > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > Carsten Haitzler - [email protected] > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
